SharpCap Forums

Posted: **Wed Sep 11, 2024 5:47 pm**

Hi Robin,
Per your request in viewtopic.php?t=8032t, I am posting a bug report, Attached are also the logs form today.

I am using an SCT with a finder scope on top of it. The purpose is to overcome the narrow field of the SCT and have an automatic GoTo.
The SCT is using a ZWO EAF focuser and has an SV605cc camera, and the finder scope is using LPI-G advanced camera. The mount is AZ-EQ5 in EQ mode. All are connected to my laptop through a USB Hub with 5V power boosted 5m cable.
When Sharpcap is using the SV605cc, it has three short beeps every scan. for example, if I am using 5 second captures (and not even doing stacking), the bar at the bottom advances, and when ending 5th-second, it sounds three beeps and starts allover the scan. It's IMPORTANT to say the beeps sounds similar to when you connect a USB cable to the laptop, so the might represent a re-connect try' but why at the end of the 5 seconds?
When I am switching to the LPI-G camera, sometimes it's crushes. But the beeps still does on. However; if I disconnect the LPI-G camera cable' the beeps stops, and the SV605cc as well as the focuser works well.
Sometimes' when both cameras are connected' there are beeps also when changing the focuser position.

I have checked the issue with two different models of powered USB hubs, nd it's there. Also, I used a power bank with a current consumption indication, and it's not going beyond 0.7 amp for all the ports together - much below the max for USB 3.2 or Thunderbolt.

Saying all the above, if I connect the USB hub without the extension cable, the beeps are gone. But I don't think it's necessarily a cable issue. Please note that adding a cable changes the port number the AZ-EQ5 needs. Maybe it's a hint. I also suspect that after a 5-seconds scan there is a re-check of connected cameras'; and maybe that's creates a current spike?

Thanks,
Ehud.

Posted: **Fri Sep 13, 2024 2:03 pm**

Hi,

thanks for posting the logs - they tend to confirm that you have an issue at the USB hardware level that is causing the Meade LPI_GM to repeatedly disconnect and reconnect to the USB system, seemingly related to the SVBony camera finishing capturing a frame. Here's an example of the entries in the log

Code: Select all

Info   	19:54:29.055487	#1 	Received hardware removal event for \\?\USB#VID_0547&PID_E00A#7&18df9163&0&2#{05476310-0000-0000-0000-000000000000}				in void SharpCap.UI.MainWindowSupport.HandleMessage(Message m)
Info   	19:54:29.056101	#21	Processing hardware removal event for \\?\USB#VID_0547&PID_E00A#7&18df9163&0&2#{05476310-0000-0000-0000-000000000000}				in async Task SharpCap.UI.MainWindowSupport.HandleDeviceNotificationAsync(string name, bool arrival)
Info   	19:54:29.056794	#21	Processed hardware change removal event for \\?\USB#VID_0547&PID_E00A#7&18df9163&0&2#{05476310-0000-0000-0000-000000000000} (Meade_LPI-GM_Advanced)				in async Task SharpCap.UI.MainWindowSupport.HandleDeviceNotificationAsync(string name, bool arrival)
Info   	19:54:29.056982	#21	Flagging camera list as invalid																							in void SharpCap.Models.Application.RefreshCameras(bool userInitiated)
Info   	19:54:29.065935	#1 	Received hardware removal event for \\?\USB#VID_0547&PID_E00A#7&18df9163&0&2#{dee824ef-729b-4a0e-9c14-b7117d33a817}				in void SharpCap.UI.MainWindowSupport.HandleMessage(Message m)
Info   	19:54:29.066411	#39	Processing hardware removal event for \\?\USB#VID_0547&PID_E00A#7&18df9163&0&2#{dee824ef-729b-4a0e-9c14-b7117d33a817}				in async Task SharpCap.UI.MainWindowSupport.HandleDeviceNotificationAsync(string name, bool arrival)
Info   	19:54:29.067032	#39	Processed hardware change removal event for \\?\USB#VID_0547&PID_E00A#7&18df9163&0&2#{dee824ef-729b-4a0e-9c14-b7117d33a817} (Meade_LPI-GM_Advanced)				in async Task SharpCap.UI.MainWindowSupport.HandleDeviceNotificationAsync(string name, bool arrival)
Info   	19:54:29.067193	#39	Flagging camera list as invalid																							in void SharpCap.Models.Application.RefreshCameras(bool userInitiated)
Info   	19:54:29.068854	#1 	Received hardware removal event for \\?\USB#VID_0547&PID_E00A#7&18df9163&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}				in void SharpCap.UI.MainWindowSupport.HandleMessage(Message m)
Info   	19:54:29.069178	#39	Processing hardware removal event for \\?\USB#VID_0547&PID_E00A#7&18df9163&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}				in async Task SharpCap.UI.MainWindowSupport.HandleDeviceNotificationAsync(string name, bool arrival)
Info   	19:54:29.069838	#39	Processed hardware change removal event for \\?\USB#VID_0547&PID_E00A#7&18df9163&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed} (Meade_LPI-GM_Advanced)				in async Task SharpCap.UI.MainWindowSupport.HandleDeviceNotificationAsync(string name, bool arrival)
Info   	19:54:29.069962	#39	Flagging camera list as invalid																							in void SharpCap.Models.Application.RefreshCameras(bool userInitiated)
Info   	19:54:29.366881	#1 	Received hardware arrival event for \\?\USB#VID_0547&PID_E00A#7&18df9163&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}				in void SharpCap.UI.MainWindowSupport.HandleMessage(Message m)
Info   	19:54:29.367445	#22	Processing hardware arrival event for \\?\USB#VID_0547&PID_E00A#7&18df9163&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}				in async Task SharpCap.UI.MainWindowSupport.HandleDeviceNotificationAsync(string name, bool arrival)
Info   	19:54:29.368197	#22	Processed hardware change arrival event for \\?\USB#VID_0547&PID_E00A#7&18df9163&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed} (Meade_LPI-GM_Advanced)				in async Task SharpCap.UI.MainWindowSupport.HandleDeviceNotificationAsync(string name, bool arrival)
Info   	19:54:29.368377	#22	Flagging camera list as invalid																							in void SharpCap.Models.Application.RefreshCameras(bool userInitiated)
Info   	19:54:29.372063	#1 	Received hardware arrival event for \\?\USB#VID_0547&PID_E00A#7&18df9163&0&2#{05476310-0000-0000-0000-000000000000}				in void SharpCap.UI.MainWindowSupport.HandleMessage(Message m)
Info   	19:54:29.372460	#22	Processing hardware arrival event for \\?\USB#VID_0547&PID_E00A#7&18df9163&0&2#{05476310-0000-0000-0000-000000000000}				in async Task SharpCap.UI.MainWindowSupport.HandleDeviceNotificationAsync(string name, bool arrival)
Info   	19:54:29.373066	#22	Processed hardware change arrival event for \\?\USB#VID_0547&PID_E00A#7&18df9163&0&2#{05476310-0000-0000-0000-000000000000} (Meade_LPI-GM_Advanced)				in async Task SharpCap.UI.MainWindowSupport.HandleDeviceNotificationAsync(string name, bool arrival)
Info   	19:54:29.373210	#22	Flagging camera list as invalid																							in void SharpCap.Models.Application.RefreshCameras(bool userInitiated)
Info   	19:54:29.376238	#1 	Received hardware arrival event for \\?\USB#VID_0547&PID_E00A#7&18df9163&0&2#{dee824ef-729b-4a0e-9c14-b7117d33a817}				in void SharpCap.UI.MainWindowSupport.HandleMessage(Message m)
Info   	19:54:29.376568	#22	Processing hardware arrival event for \\?\USB#VID_0547&PID_E00A#7&18df9163&0&2#{dee824ef-729b-4a0e-9c14-b7117d33a817}				in async Task SharpCap.UI.MainWindowSupport.HandleDeviceNotificationAsync(string name, bool arrival)
Info   	19:54:29.377030	#22	Processed hardware change arrival event for \\?\USB#VID_0547&PID_E00A#7&18df9163&0&2#{dee824ef-729b-4a0e-9c14-b7117d33a817} (Meade_LPI-GM_Advanced)				in async Task SharpCap.UI.MainWindowSupport.HandleDeviceNotificationAsync(string name, bool arrival)
Info   	19:54:29.377156	#22	Flagging camera list as invalid

Basically, the camera seems to be dropping off of USB, Windows spots that (makes a disconnect noise) and tells SharpCap about the device gone. SharpCap logs it (three times - there are three sub-devices by the look of it). Then, about a quarter of a second later, the camera re-initializes USB, Windows detects it (makes a connect noise), SharpCap gets notified and records the reconnect information in the log.

Somehow, it looks like the two cameras are incompatible (at least when used with extension cables/hubs as you describe). It's impossible to be sure why, but perhaps the SVBony camera draws more power at the end of the frame and that causes the USB voltage to dip enough to reset the Meade camera? (That's guesswork really, but might be the case).

I think you are going to have to work around this at the hardware level - there's nothing that can be done in software to resolve this. If you have a USB configuration that works without the extra extension cable then that's one possibility. In this sort of situation, it's good to be methodical - find a setup that works then change one thing at a time until it breaks, since then you know the last thing you changed broke it and you can go back to the step before.

It's also possible that you might find a different model of guide camera might be less sensitive to this sort of thing, but it's impossible to be sure - if your USB cable lengths/hubs are pushing things to the edge then a different camera might also struggle.

Sorry not to be able to provide an easy answer,

Robin

Posted: **Fri Sep 13, 2024 4:11 pm**

Hi Kevin,

Thanks for the detailed analysis and reply!
I think I will start from connecting the LPI-G using a separate cable, not through the hub.

Ehud.

SharpCap Forums

USB Beeps and/or Disconnects

USB Beeps and/or Disconnects

Re: USB Beeps and/or Disconnects

Re: USB Beeps and/or Disconnects