Hello wildi,

Using a GTO CP3 with a recent firmware (V2) driven by the AP experimental driver, I see 2 problematic usecases that should be considered and fixed (if possible, of course) :
- Case 1 : The mount is initialized and properly set (precise time and location), and the Park positions are processed by the driver. Slewing to Park3 position is fine. Then I slew to a real star, far away from the celestial pole to improve the precision. I sync the mount on that star. Re-slewing to the Park3 position, the mount does not come back this park position, but may be off by many degrees. I suspect the Park3 error is the same as the star position error before I sync the mount. So maybe park positions should be re-processed each time the mount is sync'ed.
- Case 2 : A star is located in the eastern hemisphere, not very far from the meridian. By that time, I properly initialize the mount. As I want to track this star whenever it is in the western hemisphere (so after it has crossed the meridian) I just sit and wait until say 15-30 min after the actual crossing (to make sure the crossing has occurred). Then, if I slew the mount to that star, the mount moves to that star, but goes on the wrong side of the pier, with the counterweight up. Maybe the mount internal time is not updated, or ... I do not know. If, after this sequence, I restart the entire Ekos process, re-initialize the mount, slew to that star, then the mount behaves normally by going to the correct side of the pier.

I hope my explanations are clear enough. It would be fine if you could reproduce and fix these issues.
However, thank you for your time and good work.

J.

Read More...