SharpCap Forums

I am unable to consistently connect to my AM5 and EAF.

Both devices work if I use the native controls.

They are recognized in Sharp Cap but indicate a not connected status.

When I try to set up either device they do not connect.

I have verified the hardware settings. All USB connections are secure and working.

This is a new issue which started occurring after I changed my OTA. I know their is not correlation with that but it is the only change I have made in my configuration. I have updated my ASCOM drivers and ZWO drivers. I also updated the AM5 firmware.

I am attaching two log files. A current one created with the problem described and an earlier one from a session before this problem started.

Thanks for your assistance.

Hi,

the larger of the two log files contains a record of what looks like the problem. Interestingly, SharpCap connects successfully to the AM5 mount at about 20:57:32 and can read all the details of the mount at that point (movement rates, capabilities, date and time, etc). However, at 22:10:38 we get an error from trying to read the status of the mount.

A couple of interesting things are recorded in the log in the hour or so between those two events...

1) at about 20:59:12, a USB device disconnects and then reconnects
2) There are a few dropped frames recorded in that time too.

We also see an error relating to disconnecting from the mount as you close down SharpCap right at the end of the log.

The two errors both point towards the separate ZWO application that provides the ASCOM driver for the mount (I think this is the 'ASI Mount ASCOM Server' application) having crashed/stopped responding/shut down, so that when SharpCap tries to request status updates or do something, it is not getting a response.

I don't think SharpCap is seeing the primary cause of the problem here - something is going wrong between the mount and the ASI ASCOM Server (or in the software of that application), and the SharpCap log is only recording the fact that the ASCOM server application is no longer working. It would be nice if the ASI ASCOM driver created some sort of log, as that might reveal the underlying cause, but as far as I can see it doesn't have that sort of option available

It's difficult to come up with any specific ideas in this situation - the fact that things seemed to work for more than 1 hour is encouraging that things are not completely broken, but unreliable is almost as bad as broken. I would be tempted to sidestep your usual USB connections and try with two direct cables back to the PC - one for the camera, one for the mount (both <2 metres, no extensions or hubs) . Even if this isn't practical for actual use, if things work stably in this setup then USB cables/hubs/etc would need to be investigated.

cheers,

Robin