BRIAN GLACKIN wrote: > Based on your description, I think that is what was causing me to lose > steps. I was able to start the router in motion, drop down to a > cutting position and then begin cutting. Since I was cutting at 1 > depth for more than 10 seconds, I always seemed to miss steps on the > Z. I would notice that the when the g0 would pull the router up then > out, it would stall the z avis then proceed to plow m router through > the workpiece back to 0,0,0. > > This sounds like the activation could easily be initiated by HAL and > sent across the parrallel port to the board. Looks like I need to > read up on code writing.... not one of my forte's.
Thanks for reminding me about this - there's no need to write any code. The motion controller already has a set of drive enables which are turned on whenever the motors are under motion control. This includes when they're supposed to stay still. The pins are named axis.#.amp-enable-out, where # is replaced with the axis number. All that needs to be done is to connect the enable line to a parallel port output instead of a switch (with any buffering needed so that parport can drive the signal). You can do separate enables for each motor, or use any amp-enable-out for all motors. You make the HAL connection like so: net motor-enables axis.0.amp-enable-out parport.0.pin-09-out (or wherever you connected it). In fact, if you used stepconf to set up your machine, amp enable is one of the available output assuignments. - Steve ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
