To my surprise, the N & S contacts showed immediate proper response
OOOhhh, that surprised me. Normally its N/S that doesnt "appear" to work properly, due to the lag on reversing, however, if you see movement, then it means that its working.
However, for the E & W contacts, I was not able to tell the effect.
That is truly weird, as the E/W merely speeds up/slows down the drive, and it is normally very evident when it happens.
I test by setting the scope up altaz, but telling it its polar.
Then i track along a fenceline ( using a webcam feed ), so i can see N/S moves
as well as speed up/slow downs.
Oohhh , before that
a) What firmware are you running
b) Have you patched it
c) How did you align it
In the new code, ( IIRC ) if you issue an Alt Guide first, you would have to wait 20secs before the system reverts to pure polar tracking.
In non pure polar mode, all bets are off re guiding as the mechanisms change.
Its a truly horrible bit of code used in that scenario.
Also Pre A3S4 uses a totally different mechanism to apply guide commands compared to A3S4.
Sooo we need to clarify whats happening.
I'm beginning to think the tracking speed may be the main problem and not the autoguider.
One of the very first bugs looked at was very
slow tracking, but we are talking massively slow tracking here, not just a bit. Again, need to confirm firmware used.
The LX80 specs says it has 2000 incremental drive rates.
Depending on firmware version, it has more than that.
You can adjust the base tracking rate in increments of 0.1% for all firmwares
up to A3S4, at which point it went to 0.01%.
However, that has NOTHING to do with the guiding.
Guiding ( as noted earlier ) can operate 2 ways when pulseguiding.
Pre A3S4, the system reads the guide time supplied, calculates how many encoder ticks this is equivalent to, and then applies this in a "burst". This process is done 10x per second.
In A3S4, the system merely invokes the std guide speed ( ie baserate +/-10arcsec/sec ) and sets a timer.
This is also done 10x per second, but the timer always overruns a bit, hence if the ST4 line is asserted full time, the timer just resets before a stop is required and you keep guiding.
Thus it is smoother than the old ST4 method, but it also has new problems of its own.
Either way tho, you should see the equivalent of a baserate +/- 10arcsec per sec guide
ie any errors in base tracking really shouldnt affect you seeing the guides.
My next move will be to calculate this slower tracking speed.
Also, if yr game, you can apply the latest patch i have put out.
There is a special option in there to forcibly reset the motor speeds when polar.
This should provide a self repairing system if in fact the LX80 cards are behaving differently ( as i still suspect )
Andrew Johansen Melbourne Australia