Usb disconnects randomly

Submitted by maaac on #1

Hello everyone,

When I send my USB over WiFi and I launch a software to establish communication between this software and the USB, it disconnects randomly only when I start it up.
It's a USB B female connector on my electronic board, but when I send a USB C female connector with roughly the same board, it works. Could the problem come from there?

Thanks.

Submitted by Michael on Wed, 2024/04/10 - 08:29

#2

Sounds like a power supply problem to me. Put a powered usb hub between your device and the server.

Submitted by maaac on Wed, 2024/04/10 - 23:12

#3

I tried this : https://www.amazon.fr/WAVLINK-daccueil-Universelle-Ordinateur-Portable/dp/B019XOJ874/ref=asc_df_B019XOJ874/?tag=googshopfr-21&linkCode=df0&hvadid=395414520919&hvpos=&hvnetw=g&hvrand=1349225518391137172&hvpone=&hvptwo=&hvqmt=&hvdev=c&hvdvcmdl=&hvlocint=&hvlocphy=9055538&hvtargid=pla-493512543103&psc=1&mcid=9fd44a2bc8063286a0b6d0447d7fbba1&tag=&ref=&adgrpid=80679264697&hvpone=&hvptwo=&hvadid=395414520919&hvpos=&hvnetw=g&hvrand=1349225518391137172&hvqmt=&hvdev=c&hvdvcmdl=&hvlocint=&hvlocphy=9055538&hvtargid=pla-493512543103
It's seems like i have the same thing.

Submitted by Michael on Thu, 2024/04/11 - 06:51

#4

What device are you using to run virtualhere server?

Submitted by Michael on Thu, 2024/04/11 - 07:51

#6

can you follow syslog and post the results here when the device drops

sudo tail -f /var/log/syslog

(or sudo journalctl -f)


Can you post the results here

Submitted by maaac on Thu, 2024/04/11 - 17:34

#7

Apr 11 08:24:57 pi0 kernel: dwc2 20980000.usb: Not connected
Apr 11 08:24:57 pi0 kernel: usb 1-1: usbfs: usb_submit_urb returned -19
Apr 11 08:24:57 pi0 kernel: dwc2 20980000.usb: Not connected
Apr 11 08:24:57 pi0 kernel: usb 1-1: usbfs: usb_submit_urb returned -19
Apr 11 08:24:57 pi0 kernel: dwc2 20980000.usb: Not connected
Apr 11 08:24:57 pi0 kernel: usb 1-1: usbfs: usb_submit_urb returned -19
Apr 11 08:24:57 pi0 kernel: dwc2 20980000.usb: Not connected
Apr 11 08:24:57 pi0 kernel: dwc2 20980000.usb: Not connected
Apr 11 08:24:57 pi0 kernel: dwc2 20980000.usb: Not connected
Apr 11 08:24:57 pi0 kernel: usb 1-1: reset full-speed USB device number 2 using dwc2
Apr 11 08:25:02 pi0 kernel: usb 1-1: device descriptor read/all, error -110
Apr 11 08:25:06 pi0 vhusbdarm.1[366]: Device 11 [0483:5000] SURPRISE UNBOUND from connection 1
Apr 11 08:25:06 pi0 kernel: usb 1-1: USB disconnect, device number 2
Apr 11 08:25:06 pi0 vhusbdarm.1[366]: Unmanaging device 11 [0483:5000]
Apr 11 08:25:09 pi0 kernel: usb usb1-port1: attempt power cycle

Submitted by Michael on Thu, 2024/04/11 - 17:43

#8

OK it seems like the firmware inside the "electronic board" you mention is crashing and the usb bus is disconnecting it because its stopped responding. It might be sensitive to latency. Perhaps your other board is not as sensitive to latency (e.g buffer underrun) so it works fine.

 

Submitted by maaac on Thu, 2024/04/11 - 23:57

#9

i'm not usb expert so what is the thing or things i have to check then may be i have to modify ?

Submitted by Michael on Fri, 2024/04/12 - 08:40

#10

There is nothing you can modify its the manufacturer which would need to investigate.

Submitted by Michael on Fri, 2024/04/12 - 17:22

#12

You need to debug it yourself if you have the firmware source code.

Put HID outbound/inbound data into a queue before putting on the USB bus rather than just writing to the bus without a queue. That way you  wont lose data.

Submitted by Michael on Fri, 2024/04/12 - 17:37

#14

No, its different

Submitted by Michael on Fri, 2024/04/12 - 20:36

#16

I don't know,

Submitted by maaac on Wed, 2024/04/17 - 23:08

#17

I tested it on macOS.
I encounter the same issue, but the USB reappears on macOS and not on Windows.

Submitted by maaac on Thu, 2024/11/21 - 23:13

#18

Hello,

It's been a long time.

I came back to work on that and someone told me to test with ethernet cable to send the USB from a PC to another PC and all the test i did (4 hours of running), i didn't get cuts.

He said the cuts i have with the Pi0, it's probably due to the latency of the wifi 4. I have to test with wifi 6, so i have to look for another board.