Originally Posted by
datac
Neat ! Thanks for actually trying it. I was wondering about the Dir change, but sounds like that worked too.
So, no issue with dropped steps because of pulse width ? Or, is it possible one can drop steps based on turning speed, but it wouldn't really matter if it did because of the particular use ?
Maybe I have just seen too many really fussy drivers in need of defined perams... (Polarity, pulse width, time between steps, direction-step setup delay time and direction lag, etc.)
The reason I am curious is simply what stops one from paralleling into any driver input along side of a control software signal ? Sure, the software would not have a clue and fail if you tried using it in the middle of a job, but there are times where I would just love to jog a machine somewhere without care of what the control thinks location is... times when I don't need.the control per say... sort of use three to create "digital hand wheels" ? (probably put diodes in the MPG lines so a control can not send pulses to the MPG, or relay the control wires to only work if the control is not enabled)
Sounds like I have another project to try out........