Lost Connection to Camera

[Peter B]

Just recently I've noticed an error message popping up in the PHD2 screen "Lost connection to camera PHD will make several attempts to re-connect the camera"

This is something I've not seen before and I'm wondering what might be causing it?   Maybe a USB issue or driver problem?  I'm using a ZWO 120-MM guide camera.

I've attached the guidelog.  I've also got the debug log however the file is too big to upload here.

Thanks,

Peter

[Peter B]

I've read the instructions and uploaded the logs now :)

- here is the link

https://openphdguiding.org/logs/dl/PHD2_logs_2TxB.zip

[Bruce Waddington]

Since you’re running on the dev4 release, you should first be sure you’re using the latest ZWO drivers for your camera.  Beyond that, our recommended trouble-shooting procedure for these problems is in the manual:

 

https://openphdguiding.org/manual/?section=Trouble_shooting.htm#Problems-_Camera_Timeouts

 

There are many parts to this covering both power delivery and data traffic, so you should probably investigate all of them. 

 

Hope you can track the problem down quickly,

Bruce

--
You received this message because you are subscribed to the Google Groups "Open PHD Guiding" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-phd-guidi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/d54a2a62-0aa0-455f-9714-277ddbce606cn%40googlegroups.com.

[Brian Valente]

In addition, If you are using the ZWO ASCOM drivers, you may want to switch to the built-in ZWO driver. Sometimes the ASCOM drivers switch the camera without you knowing, and switches to the imaging camera

To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/002901d72f1a%2470e8a930%2452b9fb90%24%40earthlink.net.

--

Brian 

Brian Valente

portfolio brianvalentephotography.com 

[George Shoup]

Brian:

I suggest a brief explanation of:

• PhD built-in drivers
• Ascom drivers
• Where does each type of driver come from?
• How are they different?  Why are there two?
• How can the casual observer determine which one he is using?

George

To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/CAJa45i5xAdRxm1_seMJZP-fxP%2BhrCg9pxQwN6MHWNVcRm3351A%40mail.gmail.com.

[Peter B]

Bruce/Brian,

Thanks for the checklist.  So far I can confirm:

1. I'm using the ZWO driver (not ascom).

2.  I am using the latest driver version.

3. I'm using powered hubs so hopefully power is not an issue.

4. All USB hubs/leads are Lindy gear so not cheap and nasty and less than 1 year old.  I previously had Belkin leads that lasted for 10+ years.

5. The camera is running in 16 bit mode but I'm using 2x bin.

I've switched the computer USB hub power management off tonight however this is not something I've ever touched before.  I also noticed another USB device was reporting a driver issue and I've rectified this tonight.

Will give it a try tonight to see how that goes.  If the problem re-occurs, next step will be to try changing out usb cables.

I'm also interested in any tools that can be used to monitor USB port load - it is mentioned in the troubleshooting guide but the tool is not specified.
"If you’re running Windows, you can use a Microsoft tool to map out how the various USB ports are tied to the USB controllers in the computer.  Then you can try to isolate the two cameras on separate USB buses."

Peter

[Bruce Waddington]

If you had another USB  device that was reporting a problem, that could also have caused the issue with your guide camera.  A single misbehaving device or driver can crater the whole USB subsystem.  If you’re running Windows 10, there is also a strong likelihood its power management scheme allows shut-down of the USB ports - so that’s definitely something to check.  With regard to the Microsoft tool, Google is your friend: J

 

https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/usbview

 

Good luck,

To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/0e12e6b5-aff6-47fe-bb15-1316a58f1be8n%40googlegroups.com.

[Peter B]

Bruce,

Thanks for the link.  I had a play with that tonight and it does show which devices are connected to each port however I couldn't see a way to view traffic - or at least anything that I could understand.  In any case it seems to be behaving for now so hopefully it was just the driver for the other device that was playing up.

Cheers,

Peter

[federico bonino]

Hello Ihave a similar problem using New asus tuf gamer.

Peter could you give more detail about this comments please 

""If you’re running Windows, you can use a Microsoft tool to map out how the various USB ports are tied to the USB controllers in the computer.  Then you can try to isolate the two cameras on separate USB buses."

Thanks!!!

Federico

To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/d0609317-11af-4c54-834d-0245174f577bn%40googlegroups.com.

[Peter B]

Hi Federico.  The tool Bruce is talking about is this one:

https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/usbview

The website explains how to install and run it.

Peter

[fbon...@gmail.com]

OK Peter Thanks I will try... (USBView.. you say)

The problem that I have is not only on PHD, and not only in QHY camera... the problem is on ZWO too and It could see on SharpCap or EZPlanetary etc.... and also in ALL the tree USB 3.0 ports that ASUS have.... So I Don´t Know How the problem will be...  :(  

Any comments will be usefull for me !!!....

I saw a Post on cloudy night with similars issues....but they don give any solution...

Regards!!

Federico 

[Bruce Waddington]

It doesn’t measure the traffic, that’s in fact difficult to do with USB connections.  What it does show is how the various USB ports are distributed across the USB “tree” architecture so you can try to distribute high-speed devices evenly.

To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/d0609317-11af-4c54-834d-0245174f577bn%40googlegroups.com.

[Peter B]

OK - understand, that makes sense.  I've got mine pretty well distributed with three USB connections to the computer, guide cam and main imaging cam each using a different connection.

PHD2 ran all night last night without issue so it was either the USB power saving setting or the dodgy driver for the other device that was causing the issue.

Thanks the the advice,

Peter