Do you see any sign of overheating near the connector? The same current which overheated the camera would have passed through the Jetson. If there is a relation to your Jetson, then chances are somewhat high that the Jetson’s USB port was damaged. Still, this isn’t very likely if common USB components are used in the camera itself (USB bridges tend to have built in ESD protection…this is likely at both the camera end of the cable and the Jetson too…both would have to fail if the jolt comes from the Jetson, only one would need to fail if the jolt came while the cable was disconnected). The only thing I can think of as the highest risk in your use case would be if a desktop were not anti-static, when additionally the material is some form of plastic or paper.Īs is, the risk of failure for you would be greatest when the USB cable is not connected and is sitting freely on the wrong material. Various plastics used on a desktop also have a high electrostatic potential similar to what you might expect when walking across carpet. For example, paper on a desktop was banned. Some of the more dangerous materials to sit a part on were very good insulators…the issue was in fact about electrostatic potential for non-conductive surfaces/table tops, and grounding for conductive surfaces/table tops. There was a strong awareness of what type of material any part was allowed to sit on. Components in a circuit are far more resilient, but still susceptible to larger jolts. Components which are not in a circuit can be destroyed rather easily…a single discharge could destroy a shelf with around $10k worth of parts. There was properly a bit of paranoia over protection from static. Long ago I worked as a certified inspector at a small electronics manufacturing company, mostly designing just-in-time through-hole lines. Running the Jetson without a surge suppressor could over time lead to failure (you can’t really test ESD components, nor use them, without them degrading…eventually a large number of surges could conceivably propagate through the hardware…but the odds are low that the USB device would fail first). Unless there was a power surge which destroyed the ESD protection and overcurrent protection of the USB port the odds of the Jetson causing the problem are very low. Is the camera self-powered or bus-powered? Is a HUB involved, and is the HUB self-powered or bus-powered? If that device is self-powered, and if that power source is not surge protected, then odds go up quite a bit that this could damage the camera. I could see a Jetson plugged in without a surge protector as being at risk…but the ESD over the USB port makes me think it would be more likely for a surge to destroy the Jetson and leave the USB device working. If the camera is self-powered then the 5V bus lines don’t even matter (some self-powered device have the option to be bus powered as well if self-power is removed). If the camera is connected to a HUB then the HUB could have issues with a particular port, especially if the camera is bus powered (you could check the 5V pins on any port connector you’ve used to see if it is still 5V). Additionally, so far as I know Jetsons and any USB port contain ESD protection as well. Linux racebot 4.4.USB provides a standardized 5V…max current is higher on USB3 than on USB2, but voltage is not configurable. usb 2-1.1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 2-1.1.4: New USB device found, idVendor=2b03, idProduct=f580 usb 2-1.1.4: new SuperSpeed USB device number 8 using xhci-tegra xhci-tegra 3530000.xhci: tegra_xhci_mbox_work mailbox command 6 usb 2-1.4: USB disconnect, device number 7 usb 1-2.1.3: USB disconnect, device number 12 uvcvideo: Found UVC 1.10 device ZED (2b03:f582) usb 1-2.4: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 1-2.4: New USB device found, idVendor=093a, idProduct=2510 usb 1-2.4: new low-speed USB device number 13 using xhci-tegra uvcvideo 1-3:1.0: Entity type for entity Camera 1 was not initialized! uvcvideo 1-3:1.0: Entity type for entity ZED was not initialized! uvcvideo: Found UVC 1.00 device ZED (2b03:f580) usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 1-3: New USB device found, idVendor=2b03, idProduct=f580 usb 1-3: new high-speed USB device number 5 using xhci_hcd " usb 2-1: USB disconnect, device number 3 I have got same error, when ZED was connected Ubuntu 16.04, it was working fine on Jetson TX1, but when connected to laptop, it throws following error "ZED camera not found".
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |