> hundreds of hours
Does that apply to cables designed for use in robots? eg https://okielectriccable.com/okis-robot-cables/
Does that apply to cables designed for use in robots? eg https://okielectriccable.com/okis-robot-cables/
The problem with USB is that the protocol is designed with no data loss in mind. A single bit flip due to EM interference or bad cable, and the camera firmware (or the host driver) hangs and require a restart. Intel RealSense and Microsoft Kinect Azure cameras all have to be plugged into USB hubs which allow power cycling. Otherwise, it's just not practical. And even then, after a few hundreds of hours the frequency of restarts it degrades even further.
I might sound a bit dramatic, it's mostly that my scars are too fresh.
USB employs two error checking methods to ensure that data is sent correctly:
https://web.archive.org/web/20130615145009/http://www.totalp...
In Ethernet, on the other hand, packet loss is routinely handled, and higher level protocols can work when physical media is less than perfect.
> If there is a data error and the CRC check fails, however, the receiver will not reply with an ACK, and the transmitter is required to resend the data with the same toggle bit. The transmitter will continue to resend the same data with the same toggle bit until the receiver ACKs its reception.
Then my explanation of the observed phenomena is likely wrong either partially or fully.