Hi...my 678 mono cam is not coming up 'recognized' in the software. It does get seen in Firecapture though. I've updated ASCOM, Sharpcap and my ZWO drivers...any thoughts?
Oddly enough...my 432 mono does get recognized.
thanks,
Joe
ZWO 678 mono not recognized
-
admin
- Site Admin
- Posts: 17510
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: ZWO 678 mono not recognized
Hi Joe,
that's an odd one, since the 678 has been around for a while and has been usable in SharpCap since the last dozen or so updates to SharpCap 4.0 (back in 2022) and all the way through SharpCap 4.1 up to the current version. I don't have one to test myself, but I do have usage data that tells me people have been using the 678 successfully in 4.1.13447 within the last week or two. I can't see any obvious reason why it would be broken in newer versions than that, since the ZWO camera handling hasn't changed since then.
From your description, I am assuming that the camera is not showing up at all in the 'Cameras' menu where it should show (in the ZWO ASI Cameras section), but other ZWO cameras are. Do you see the camera in Windows device manager (it will be in the imaging devices section). I guess you probably do or Firecapture would not see it.
It may be worth trying a shorter USB cable if you are using any extensions (and remove any hubs too to simplify for testing purposes). However, while those sort of things can cause problems, it's more often issues once the camera is opened, not with detecting it in the first place.
I have just checked and can see that ZWO have updated their SDK with a new version that isn't in SharpCap yet - I will include that update in the next SharpCap 4.1 update release (later today) - maybe that could help as the SDK change list includes 'fixed some issues'. Otherwise, it may also be worth looking at the SharpCap log just after starting the program to see if there are any errors shown - by looking just after starting all that will be in the log is application startup and camera/device detection, so it would be relatively easy to spot any error that might be coming from detecting ZWO cameras (feel free to share the log text here for me to check).
cheers,
Robin
that's an odd one, since the 678 has been around for a while and has been usable in SharpCap since the last dozen or so updates to SharpCap 4.0 (back in 2022) and all the way through SharpCap 4.1 up to the current version. I don't have one to test myself, but I do have usage data that tells me people have been using the 678 successfully in 4.1.13447 within the last week or two. I can't see any obvious reason why it would be broken in newer versions than that, since the ZWO camera handling hasn't changed since then.
From your description, I am assuming that the camera is not showing up at all in the 'Cameras' menu where it should show (in the ZWO ASI Cameras section), but other ZWO cameras are. Do you see the camera in Windows device manager (it will be in the imaging devices section). I guess you probably do or Firecapture would not see it.
It may be worth trying a shorter USB cable if you are using any extensions (and remove any hubs too to simplify for testing purposes). However, while those sort of things can cause problems, it's more often issues once the camera is opened, not with detecting it in the first place.
I have just checked and can see that ZWO have updated their SDK with a new version that isn't in SharpCap yet - I will include that update in the next SharpCap 4.1 update release (later today) - maybe that could help as the SDK change list includes 'fixed some issues'. Otherwise, it may also be worth looking at the SharpCap log just after starting the program to see if there are any errors shown - by looking just after starting all that will be in the log is application startup and camera/device detection, so it would be relatively easy to spot any error that might be coming from detecting ZWO cameras (feel free to share the log text here for me to check).
cheers,
Robin
Re: ZWO 678 mono not recognized
Awesome...thanks Robin...I'll look for it.
Joe
Joe