On 11 July 2012 15:29, Viesturs Lācis <[email protected]> wrote:
> Second of all, I am surprised to see MIN_VELOCITY parameter. ... > BTW placing all those velocity and acceleration parameters in [TRAJ] > section, where they belong, would make the file easier to read for > others. You somehow have them in Display section... The parameters in the [DISPLAY} section are for the feed over-ride sliders etc. That's OK. As a style thing I would change the references for Y2 in the HAL to point to the [AXIS_1] Section and add a STEP_SCALE_2 parameter to hold the negative scale value for the other motor. But that is just to save the trouble of editing in two places to keep things the same. I think you still need the [AXIS_3] section but I think most of it will be ignored. I don't see any reason to load and poll the parallel port in this configuration. (or, in fact, to run a base thread at all) unless other HAL files are using the parport. I would be tempted to set the stepgen maxaccel to 0 (n the HAL, not the INI!) , and let the trajectory planner handle accelleration. -- atp If you can't fix it, you don't own it. http://www.ifixit.com/Manifesto ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
