I'm running an AM5 mount and ZWO camera using ASI software. I've been able to get SharpCap to run the ZWO EAF and it appears SharpCap will also plate solve and re-center targets (although I'll need a clear night to be sure). However, have been unable to fully connect SharpCap to the AM5 to direct mount movements, go home, etc. When I try to connect I get an SC error message that says "The mount failed to report its current time." How do I get the mount to "report its current time" to SC, or get SC to "set the mount time?"
Many Thanks, Frank
SharpCap/AM5 problem
SharpCap/AM5 problem
- Attachments
-
- SCAM5C.jpg (987.53 KiB) Viewed 552 times
Re: SharpCap/AM5 problem
SORRY - I don't know to edit original post so adding this:I am running the mount with ASI software but the ASI camera with SharpCap, not ASIair or ASI software.fgreen wrote: Sun Apr 26, 2026 8:45 am I'm running an AM5 mount and ZWO camera using ASI software. I've been able to get SharpCap to run the ZWO EAF and it appears SharpCap will also plate solve and re-center targets (although I'll need a clear night to be sure). However, have been unable to fully connect SharpCap to the AM5 to direct mount movements, go home, etc. When I try to connect I get an SC error message that says "The mount failed to report its current time." How do I get the mount to "report its current time" to SC, or get SC to "set the mount time?"
Many Thanks, Frank
- admin
- Site Admin
- Posts: 17574
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: SharpCap/AM5 problem
Hi,
fortunately, what you are seeing is just a warning, not an error (yellow message, not orange/red). It indicates that the ZWO ASCOM driver is probably not following the ASCOM standard quite properly, but if everything works properly in spite of seeing that message then you can ignore it.
To give a bit of a deeper explanation, when SharpCap connects to an ASCOM telescope mount driver, it asks the driver for the current time according to the mount. There are three things that can happen at that point...
1) The time reported by the mount matches the system time that SharpCap sees - all is good, nothing happens
2) The time reported by the mount is out by more than 1 minute compared to system time. In this case SharpCap will try to adjust the mount time via the ASCOM driver to correct the problem
3) The ASCOM driver/mount claims it cannot report a time - in this case SharpCap will try to set the time via the ASCOM driver
It's the third case that is happening to you, but when SharpCap is trying to 'fix' the problem of the missing time, that fails and that error is being reported in the yellow box.
I don't think that the ASI Mount server really has a problem with the time - I just think that the part of the ASCOM specification to do with this isn't implemented correctly in the ASI code, and that's triggering the warning from SharpCap.
cheers,
Robin
fortunately, what you are seeing is just a warning, not an error (yellow message, not orange/red). It indicates that the ZWO ASCOM driver is probably not following the ASCOM standard quite properly, but if everything works properly in spite of seeing that message then you can ignore it.
To give a bit of a deeper explanation, when SharpCap connects to an ASCOM telescope mount driver, it asks the driver for the current time according to the mount. There are three things that can happen at that point...
1) The time reported by the mount matches the system time that SharpCap sees - all is good, nothing happens
2) The time reported by the mount is out by more than 1 minute compared to system time. In this case SharpCap will try to adjust the mount time via the ASCOM driver to correct the problem
3) The ASCOM driver/mount claims it cannot report a time - in this case SharpCap will try to set the time via the ASCOM driver
It's the third case that is happening to you, but when SharpCap is trying to 'fix' the problem of the missing time, that fails and that error is being reported in the yellow box.
I don't think that the ASI Mount server really has a problem with the time - I just think that the part of the ASCOM specification to do with this isn't implemented correctly in the ASI code, and that's triggering the warning from SharpCap.
cheers,
Robin
Re: SharpCap/AM5 problem
Hi Robin, thanks for the detailed response. Upon further poking around it appears I am unable to open COM3 with SC. It's on COM3 but I can't get SC to open COM3 and connect to the mount. I am able to connect to the ZWO EAF and run the focuser with SC.I think I may have found the problem: The AM5, camera, focuser, dew heater are all powered from a Pegasus Powerbox Advance Gen 2. My remote laptop runs the camera and other devices via a single USB 3 cable that goes into the powerbox via COM3 (I control the mount with a tablet and the ASI app). Is the powerbox tying up COM3, can it not be shared with SC?
If it COM3 can't be shared by the powerbox and SC, I think I'm out of luck. What I hoped to do was to be able to plate solve and re-center using SC so I would not have to buy and use an ASIair but at this point that may be the best solution.
If it COM3 can't be shared by the powerbox and SC, I think I'm out of luck. What I hoped to do was to be able to plate solve and re-center using SC so I would not have to buy and use an ASIair but at this point that may be the best solution.
Re: SharpCap/AM5 problem
OMG. Doh! Figured out the problem - you need to USB hardwire the desktop to the AM5! My bad. Apologies for wasting anyone's time.
- admin
- Site Admin
- Posts: 17574
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: SharpCap/AM5 problem
Hi,
yes, that would help
Interestingly, the fact that you got the message you did without having the hardware connected points to a slightly different oddity in the ASCOM driver for the ASI mount. It seems like it is allowing a connection to happen when the hardware isn't present, which lets SharpCap get to the next stage of checking the time.
Really, the connection attempt to the ASCOM driver should fail in this case (if that happened you would get a much more helpful error message from SharpCap), however there may be some reason to make it behave the way that it does, so if it all works when everything is connected then happy days...
cheers,
Robin
yes, that would help
Interestingly, the fact that you got the message you did without having the hardware connected points to a slightly different oddity in the ASCOM driver for the ASI mount. It seems like it is allowing a connection to happen when the hardware isn't present, which lets SharpCap get to the next stage of checking the time.
Really, the connection attempt to the ASCOM driver should fail in this case (if that happened you would get a much more helpful error message from SharpCap), however there may be some reason to make it behave the way that it does, so if it all works when everything is connected then happy days...
cheers,
Robin
Re: SharpCap/AM5 problem
Thanks Robin. I've used SharpCap and the AM5 for years for EAA but always controlled the mount wirelessly using ASI software and had no experience controlling it via the desktop using SharpCap.
The reason I want to control with SharpCap is to do plate solving and re-centering. Using SharpCap settings I configured plate solving to sync mount and re-center target after a GOTO and the test function says test was successful but I have yet to get it out under the stars. Will SharpCap automatically begin a plate solve and re-center each time a GOTO command from the tablet has been executed, or do I need to do something before or after a GOTO? Thanks, Frank
The reason I want to control with SharpCap is to do plate solving and re-centering. Using SharpCap settings I configured plate solving to sync mount and re-center target after a GOTO and the test function says test was successful but I have yet to get it out under the stars. Will SharpCap automatically begin a plate solve and re-center each time a GOTO command from the tablet has been executed, or do I need to do something before or after a GOTO? Thanks, Frank
Re: SharpCap/AM5 problem
Disregard question above about plate solving/re-center, I found a Youtube explainer. Thanks again