Re: [Bdi4emc-help] Trajectory planner accel limits
From: Gene Heskett <[email protected]> I don't know if this is a 'datapoint' or not, but I looked at that with the halscope in emc2 testing, then looked at the code. The code overshoots the starting positions starting radius of the circle by 1.5 units, I assume as a chip clearing move possibly.
Thanks, Gene. I didn't even notice the intentional overshoot.
Looking at its traces with emc2 testing code, neither the initial move nor the reverseing at that point seemed to violate the maxvels set, the angle of the approach to the endpoint, there was a small radius in the trace as it turned around, then rose at exactly the mirror angle to the real starting point before the y motion was started.
That's definitely not the case for me. Paul seems to have got it -- I'll try his suggestion and write back.
One thing thats not too clear to me is how I should translate the halscopes traces into something that would correspond to motion in seconds type of data. The seconds is easy enough, but how does the displayed voltage trace translate in motion at the cutter?
I use tkemc/Settings.../Logging..., which can capture a variety of things in real units and gnuplot them. -- Matt
On Saturday 18 February 2006 20:38, [email protected] wrote:
From: Gene Heskett <[email protected]> I don't know if this is a 'datapoint' or not, but I looked at that with the halscope in emc2 testing, then looked at the code. The code overshoots the starting positions starting radius of the circle by 1.5 units, I assume as a chip clearing move possibly.
Thanks, Gene. I didn't even notice the intentional overshoot.
Looking at its traces with emc2 testing code, neither the initial move nor the reverseing at that point seemed to violate the maxvels set, the angle of the approach to the endpoint, there was a small radius in the trace as it turned around, then rose at exactly the mirror angle to the real starting point before the y motion was started.
That's definitely not the case for me. Paul seems to have got it -- I'll try his suggestion and write back.
One thing thats not too clear to me is how I should translate the halscopes traces into something that would correspond to motion in seconds type of data. The seconds is easy enough, but how does the displayed voltage trace translate in motion at the cutter?
I use tkemc/Settings.../Logging..., which can capture a variety of things in real units and gnuplot them.
I can't get it to actually open the logfile here, spits out a box with the error, then opens the selector screen. Or do I need to touch the file first? We did get the M101 function working here tonight, so now I can see the values of the #vars I'm using, which will help a lot when writing code by hand for onesies and twosies projects.
-- Matt
_______________________________________________ Bdi4emc-help mailing list [email protected] http://lists.ourproject.org/cgi-bin/mailman/listinfo/bdi4emc-help
-- Cheers, Gene People having trouble with vz bouncing email to me should add the word 'online' between the 'verizon', and the dot which bypasses vz's stupid bounce rules. I do use spamassassin too. :-) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
From: Gene Heskett <[email protected]> I can't get it to actually open the logfile here, spits out a box with the error, then opens the selector screen. Or do I need to touch the file first?
You need to click start, stop, save, and plot. The log files are actually scripts that run gnuplot. "save" saves it and "plot" runs the saved script. That's pretty handy, because you can edit the script to get a closer look at the point of interest. If you click "plot" without "save", it'll complain. Note the file it complains about and make sure you have permission to write in that directory. I really have no idea how well this all works with emc2, or even a non-bdi config, so ymmv. -- Matt
On Sunday 19 February 2006 19:53, [email protected] wrote:
From: Gene Heskett <[email protected]> I can't get it to actually open the logfile here, spits out a box with the error, then opens the selector screen. Or do I need to touch the file first?
You need to click start, stop, save, and plot. The log files are actually scripts that run gnuplot. "save" saves it and "plot" runs the saved script. That's pretty handy, because you can edit the script to get a closer look at the point of interest.
If you click "plot" without "save", it'll complain. Note the file it complains about and make sure you have permission to write in that directory.
I really have no idea how well this all works with emc2, or even a non-bdi config, so ymmv.
Thanks Matt, but I think I'd better leave emc2 stuff out of here. Wrong list... -- Cheers, Gene People having trouble with vz bouncing email to me should add the word 'online' between the 'verizon', and the dot which bypasses vz's stupid bounce rules. I do use spamassassin too. :-) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
participants (2)
-
Gene Heskett -
mt0000＠sympatico.ca