Geek Answers Handbook

Problems with Websockets vs. WiFi - driver

I use Node and Socket.io to stream the processed data stream from various external sensors (accelerometers, gyroscopes, etc.) connected to the IGEP board (similar to Beagleboard) for several clients - smartphones, computers, etc. In the end, the device must be connected to the battery and the wireless network. The data transfer rate is quite low, approximately 100 characters are transmitted 30 times per second.

Everything works fine when clients are connected to IGEP using a wired ethernet and switch, but when using Wi-Fi, something breaks. As soon as more than one client is connected, timeouts and lost connections begin to appear, which makes it practically unusable. Ping times seem to ever grow for packages that do this. I tried ad hoc WiFi and also used an access point. It seems I can’t keep WiFi connected to more than one client.

Should I be able to do this or are there some limitations in the WiFi spec? If not, where can I focus on troubleshooting? Problems with the drivers? WiFi chipset (try a USB dongle instead)? Node / socket.io? Problem with OS? In the other place?

Thanks, Erik

UPDATE - Additional troubleshooting revealed that the WiFi drivers are causing the problems.

+7
source share
1 answer

It turned out to be a WiFi driver problem. I switched to an earlier version, and now everything works fine and wirelessly.

+1
source

More articles:


All Articles