Hi, Again. First, Duh! The 1Volt O'scope readings are my fault. The variable gain on the scope was set. Now the traces show 3V logic for everything.
Glad you discovered it, Don. Was actually hoping you'd find a similar fault of yours with the direction pulsing issue
Hi, again Dan. It appeared after I installed the dwell in the program that the offsetting went away except at the extremely slow acceleration rate of 0.5... Why would very slow accel. cause the steps/direction signals to malfunction?
Have got no explanation to this at this point.
The fact that sometimes the pulses are leading vs. lagging bothers me a lot. I would expect that the direction pulses ( if they are supposed to be pulses) wouls stay in the proper timing sequence. The two O'scope pictures show clearly a timing difference, sometimes during the same line of code execution.
Thanks for the help, Don
This is something to be worried about indeed. Absolutely not the way it was meant to be.
I just tried the jog mode. Set the Dir Pin to Pin 2 hooked up the scope to pin 2 and ground, terminated the pin with a 4.7k resistor to ground, and set the jog rate to 30% feedrate. Note that the little ticks on the lower part of the trace are the screen reticle. The timing of the direction "Pulses" seems to be varying, even across the screen.
Again, this needs to be investigated. Have never tried to look at the Mach signals with a scope, but I do know that I can measure the direction state with a voltmeter and it would show 5V or 0V depending on the direction. Could be Brian has changed something in last versions...? Don't think so. But would be nice of him to chime in here and confirm this.
When I ran jog at 100%, the trace was jittering and flickering. Not steady. It is definitely not setting a steady state!
A symptom of a not perfect driver test, though yours looks good (if the picture shows the worst case).