I read the APM#909 is for the LX90. For the LX80, it's the APM#07509 - attached.
The code in the handbox really hasnt changed comms wise, and i know A3S4 will happily talk with the OLD APM909 modules, ( which were discontinued ). Therefore, the assumption is this new beastie MUST work the same way ( but i have never got my hands on a unit to test its comms )
Ie The old APM909 modules should work on any scope via A3S4
and the new 909 guide only should also work on old 497 Hbxs on any scope.
I'm guessing there aren't $5 worth of parts in it
At a minimum, there is a PIC microprocessor, as the lump talks to the Hbx using Meades proprietary I2C comms on the Aux bus.
I've got a 497EP with A3S4, in Polar mode, with PEC off.
Do a Factory reset of your PEC and then turn PEC ON and retry.
The whole drive/tracking system can change the way it operates based on this.
Meade support told me the problem could be due to backlash and to train the drive.
Quite possible for DEC, but not RA.
In RA, the drive will not reverse, but asserting the E/W pins should make the drive slow down or speed up.
In DEC, you need to hold the assertion long enough for the backlash to be accounted for.
Guiding works at 10 arcsec per sec so if you had say 150 arcsec of lash in DEC, it would take 15 seconds of assertion for the drive to reverse.
What you could do testing wise is set the DEC percentage to 100 and then do a DEC train.
You should see a result them.
I assume the procedure gives some kind of feedback, i.e. numbers?
If you do a drive train, in normal means you cannot see the results.
If you load our patches, that allows inspection of a lot of data and hence you can dynamically read the data. Unpatched, you can still use my PEC editor to read the data, but it requires going into download mode to do it.
Andrew Johansen Melbourne Australia