TBH, this is what I do expect from such a system.
If it "blends in" the move over time, then it can really upset other processes that rely on the time.
esp as the IOPtron "appears" to be telling the pulse sender that the guide is done when it isnt.
This kills PHD, esp the way it does its calibrations.
In the second unannotated plot above, you can see the RA moved 90arcsec according to commander
PHD had sent enough pulses to move 430 arcsec in the same time.
It then sent 430 arcsec worth of reverse pulses to get back
PHD doesnt actually care what the "selected" guide rate is, it uses its own internally calculated rate to come up with pulse times, so a bad cal really affects things.
I wonder how such a plot would look for other mounts
For my Meade mounts, pulses apply at the rate specified if the std motor commands are used
or at a higher rate for less time, if the specialised motor commands are used.
In the Syntas, we have been experimenting with using "gotos" to do DEC guiding
ie we convert the guide rate * pulse time to equivalent microsteps and issue a command
It allows easy application of backlash and is deadly fast/accurate
2000ms of lash can be applied in about 100ms :-)
Recently, Roland from AstroPhysics posted the pulse guide characteristics for the new Mach 2
He posted data for tracking with encoder on then off then on, and also response to guides.
It appeared to be deadly accurate.
Andrew Johansen Melbourne Australia