When I connect my AM3 mount to SC, it appears to connect fine. And when I launch Cartes du Ciel, it shows that the scope is pointed at the NCP ( approximately) . But the mount section in the control panel shows an azimuth of 180 degrees, not due north. The mount has recently been sent to the home position using the AM3 hand controller.
Do you have any thoughts on this ?
Attached is the log, if that provides any useful info.
Thanks
John
Odd azimuth
Forum rules
If you have a problem or question, please check the FAQ to see if it already has an answer : https://www.sharpcap.co.uk/sharpcap-faqs
Please also read about Troubleshooting USB Issues before posting.
*** Please do not post license keys - please report any problems with licensing to 'admin' by private message ***
Please include the following details in any bug report:
* Version of SharpCap
* Camera and other hardware being user
* Operating system version
* Contents of the SharpCap log after the problem has occurred.
[If SharpCap crashes, please send the bug report when prompted instead of including the log]
If you have a problem or question, please check the FAQ to see if it already has an answer : https://www.sharpcap.co.uk/sharpcap-faqs
Please also read about Troubleshooting USB Issues before posting.
*** Please do not post license keys - please report any problems with licensing to 'admin' by private message ***
Please include the following details in any bug report:
* Version of SharpCap
* Camera and other hardware being user
* Operating system version
* Contents of the SharpCap log after the problem has occurred.
[If SharpCap crashes, please send the bug report when prompted instead of including the log]
-
admin
- Site Admin
- Posts: 17378
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: Odd azimuth
Hi John,
unfortunately the log in the standard form doesn't give any information on the mount co-ordinates (although it does confirm that the mount time is set correctly and that the mount connected with no error).
SharpCap typically reads the altitude, azimuth (and RA/dec) direct from the ASCOM driver and then reports the values that it gets on screen without changing it, so I suspect that the ASCOM driver itself is creating the value of -180. You can if you want turn on additional logging of 'Mount hardware communications' in the SharpCap settings, then connect to the mount - that will record in the log all of SharpCap's communications with the ASCOM driver for the AM3 mount and would show if the bad value comes via the ASCOM driver.
From the point of view of Carte-du-ciel and moving the mount around the sky, most applications (including SharpCap) really work mostly with the RA/Dec co-ordinates, so if those are coming through correctly then the mount will show in the right place and move as required. Very little actually uses the mount azimuth value as the basis of how the functionality of the software works, so this sort of glitch wouldn't easily get noticed unless you spot the odd Az readout.
I suppose it is worth checking that your lat/long in the AM3 ASCOM driver is set correctly - a southern hemisphere latitude might confuse things somehow? Another thing to check is to see if the altitude is showing as more than 90 degrees (say 130 or so) when the azimuth is 180 - that would kind of make twisted sense as a set of co-ordinates referring to the NCP.
cheers,
Robin
unfortunately the log in the standard form doesn't give any information on the mount co-ordinates (although it does confirm that the mount time is set correctly and that the mount connected with no error).
SharpCap typically reads the altitude, azimuth (and RA/dec) direct from the ASCOM driver and then reports the values that it gets on screen without changing it, so I suspect that the ASCOM driver itself is creating the value of -180. You can if you want turn on additional logging of 'Mount hardware communications' in the SharpCap settings, then connect to the mount - that will record in the log all of SharpCap's communications with the ASCOM driver for the AM3 mount and would show if the bad value comes via the ASCOM driver.
From the point of view of Carte-du-ciel and moving the mount around the sky, most applications (including SharpCap) really work mostly with the RA/Dec co-ordinates, so if those are coming through correctly then the mount will show in the right place and move as required. Very little actually uses the mount azimuth value as the basis of how the functionality of the software works, so this sort of glitch wouldn't easily get noticed unless you spot the odd Az readout.
I suppose it is worth checking that your lat/long in the AM3 ASCOM driver is set correctly - a southern hemisphere latitude might confuse things somehow? Another thing to check is to see if the altitude is showing as more than 90 degrees (say 130 or so) when the azimuth is 180 - that would kind of make twisted sense as a set of co-ordinates referring to the NCP.
cheers,
Robin