2025-09-29, 02:55 AM
Hi Phil
The mount location is set in the mount control SW to my GPS coordinates. To download the NEO I just input the name (e.g. 2025 SS5) via an under the hood function that queries an MPC database then creates the object in the mount sky chart (in the wrong place for close NEOs).
I am wondering if this operation might be bypassing the mount Lat and Long and using geocentric coordinates in the “hidden” query process?
The next time, I might test the following:
If this works, I retain the benefits of the mount modelling but have the accuracy and functionality of SkyTools to place the target on the camera sensor.
Cheers
Dennis.
The mount location is set in the mount control SW to my GPS coordinates. To download the NEO I just input the name (e.g. 2025 SS5) via an under the hood function that queries an MPC database then creates the object in the mount sky chart (in the wrong place for close NEOs).
I am wondering if this operation might be bypassing the mount Lat and Long and using geocentric coordinates in the “hidden” query process?
The next time, I might test the following:
- Decouple the mount from the native Driver and set it to choose the ACCOM Driver, then connect with SkyTools via ASCOM and perform the GoTo using SkyTools to obtain the correct pointing location.
- Locate the “false” position plotted by the mount SW and set the Custom Track Rate on the “false” object in that SW.
- See if the mount will then perform Custom Tracking and remain faithful to the accurate SkyTools pointing location. A kind of “offset” or “bypass” experiment.
If this works, I retain the benefits of the mount modelling but have the accuracy and functionality of SkyTools to place the target on the camera sensor.
Cheers
Dennis.