hey all, is there a pin, parameter, or signal for the current feed rate? i've looked, but cannot seem to find one.
I don't think so
seems like it's gotta be a variable somewhere? in motion?
it gets complex when you consider that you might have angular feeds and linear feeds at the same time
is it in/min, or deg/min
ok, sure, how about whatever is read in from Fxxx in a gcode file?
that has the same issue (which is why it is recommended to use inverse time when doing mixed angular/linear moves)
well, i just would like to display the current f
F rate in big numbers in a pyvcp.
if its a three axis machine, thats not hard
that' s all i have at the moment.
send x, y, z, pos thru ddt blocks to get x, y, z velocity, then send thru a hypot block to merge the three
root of the sum of the squares?
thats what hypot does
I think one (or more) of the sim configs has that setup already
so, that will give me the current velocity. how about the feed rate as read in?
you mean before feed override, etc?
that will be a lot harder to get
it's read in, isn't it stored somewhere?
or could be?
it is in the data that is passed to the motion controller
but extracting it isn't trivial
should i put in a 'feature request'?
if you want
be sure to put in the "why I want this"
gotta convince people that it is usefull
ok, i'll see what i can do. thanks for the help.
hello, guys, trying to set up my demo for the Workshop!
Good GAWD, Jeff, I see you added this test for the parport register address SEVEN MONTHS ago, it seems there is a problem. I get the error message "PPMC: ERROR: invalid port_addr: 378"
I'd swear I downloaded and tested from CVS since then, but maybe not. Anyway, any comments on what could be wrong? I rmmod'ed ppdev, lp and parport with no effect. I specified the port addr in the loadrt command, no effect.
maybe the leading 0x indicator for hex is required? 0x378
er, no, that's probably not it
Yes, I specified it as loadrt hal_ppmc port_addr="0x378"
I get the same message when it defaults to the hard-coded default
if you just want to get on with life you can remove just that change and see if it fixes things:
cvs up -j1.52 -j1.51 hal_ppmc.c
(in the src/hal/drivers directory, then recompile)
(if you're compiling yourself, that is)
I see that change is in all the 2.2.x versions too
OK, thanks for that bit of CVS magic, but if you can make some guesses to what is wrong, it would be far better to fix it and commit a fix.
I would be willing to spend an hour or so to get it working right and then commit the fix.
do you have just one bus on this system?
Just the one standard on-mobo parport on that system. I have added a PCI parport to my server machine, and do board testing with it. It is a BDI descendant.
can you cat /proc/ioports and put it in pastebin.ca?
Sure, give me a minute....
just let me know the url when it spits it back out
Hmmmm, verrry interesting. cat /proc/ioports causes a segment violation! Even with sudo. Uhhh, maybe I should reboot?
yes, that's likely to clear it up
there's something I do in probe_parport that can lead to that .. did you use probe_parport while working on this?
Mm, very odd. after reboot, not only does cat /proc/ioports work normally, but the ppmc driver now seems to work OK, too.
I did some lsmod and rmmod commands to remove several drivers.
This boot, I didn't have to mess with any drivers.
not too big a surprise: the data structure that rtapi_reserve_region looks at is the same one that is used to print /proc/ioports so if it is screwed up it might lead to both of those results
run emc a few times and see whether the error returns ..
I do get a RAFT of shmctl : invalid argument messages, I'll have to see what that is about.
OK, I had loaded and shut down the older version of EMC2 a number of times while tweaking the hal files to make the spindle speed control work.
By the way, do you know how to do a type conversion in hal? There seems to be a conv_s32_float conversion fuction, but I can't find any docs on how to specify it.
elson: I think you'd add something like this in a hal file: loadrt conv-s32-float count=1 / addf conv-s32-float.0 servo-thread / net your-integer-signal => conv-s32-float.0.in / net your-new-float-signal <= conv-s32-float.0.out
Oh, to correct an earlier statement, I restarted the current version of EMC2 a number of times when it was rejecting the parport address, too.
(consider thread order when you choose where to 'addf')
OK thanks for the info on the conversion function, will have to try it.
elson: conv-s32-float doesn't apply scaling, you can use a 'scale' component for that.
OK, I was going to use mult2, but I guess the scale function would do the same.
yeah that works too
on this fresh boot, has emc restarted properly a few times?
OK, well, I will probably be re-starting EMC a number of times, but I have not doen that yet. I want to play with it a bit first, and try out the G33.1 function.
I will certainly let you know if this wierdness shows up again.
I appreciate it.
OK, I'm doing this on a different computer, so I will get off IRC for a while. I'll send a message later, one way or the other.
And, thaks for the help!
see you later
Hello, Jeff, I've got one really up your alley right now.
In Axis, if you set the spindle running with M03 S750, and then go to manual, it stops the spindle. Then, in manual, when you hit the spindle run buttons on screen or F10/F11, you get a motion.spindle-out value of +1 or -1, instead of the +/- 750!
elson: you might be interested in the change that was recently made to improve spindle when switching modes .. let me dig you up a reference to the mailing list post about it
[01:48:45] <jepler> http://thread.gmane.org/gmane.linux.distributions.emc.user/7580/focus=7581
er maybe http://article.gmane.org/gmane.linux.distributions.emc.user/7581
using emc2 from June 4 or later and the new inifile line you may be happier with the behavior
OK, I see that every time you stop the spindle, you have to step up the speed again with the + button. Works, but kind of inconvenient.
Well, I'm not sure those options are all that safe. The problem here is that the manual mode sets the speed back to 1 RPM every time you hit stop.
I'd much rather it left the speed at whatever the last S word set it in MDI or programmed run.
I just did the first G33.1 and it did reverse the spindle and back out. I'm still cutting air, but will try it in real metal soon.
elson: that might have been the first rigid tap on ppmc.
I also don't care for the manual spindle control. alex's fix is fine, I think. You can MDI S250M3 and then switch to manual to cut with the jog keys for instance
(in pure manual mode, there's no way to get S250)
you can get 201 or 301, iirc.
Well, I got it working, to some extent, but it is mangling the threads at the top of the hole. After shutting it down, It ocurred to me that the tap returns to the starting Z coord, but it has to decelerate at the end of the move, so it starts decelerating before the tap is out of the hole, mangling the top thread or two. I am using a combination drill-tap, so I drill at slow feed, then start the G33.1 tapping operation.
What I will try tomorrow is to drill through first, back up and then do the G33.1 with the tap section farther up. This will make the retract cycle also come farther up before decelerating. I have fair confidence this will fix it!
And, yes, I suspect this may be the first rigid tapping with the PPMC driver, and most likely with the UPC board. Stuart Stevenson may have done rigid tapping on his machines, which use the PPMC board set.
Signing off for the night! Thanks for the help!
EMC: 03jepler 07v2_2_branch * 10emc2/docs/src/gcode/main.lyx: m66 is both digital and analog
EMC: 03jepler 07TRUNK * 10emc2/docs/src/gcode/main.lyx: from branch: m66 is both digital and analog
jepler: thanks ;)
[22:14:46] <BigJohnT> http://imagebin.ca/view/BXU9ULrt.html
[22:14:58] <BigJohnT> http://pastebin.ca/1042389
seems to be a bit of a bug in the G64 Pnn when run on larger arcs
the bottom two were run with G64 and the first two arcs are funky
the rest were run with G61 and cut fine...
removed extra line feeds on this one http://pastebin.ca/1042392
and the parts came out like the plot...
I guess someone fixed it all ready as I don't get the same error down here in the beer cave
I'll have to drag the other computer down here and get the latest on it and try again
jmkasunich_ is now known as jmkasunich