Someone built an open-source tool that transfers large files directly between devices, with no relay server in between. The reason was practical: sending large files through the cloud is slow, comes with size limits, and requires accounts. Public benchmark data shows the gap clearly — transferring a 1 GB file on the same network takes about 3 minutes via cloud relay, versus under 5 seconds with a direct device-to-device connection, roughly a 40x difference. The bottleneck is not the devices; it is the upstream bandwidth of the internet connection(typically 30–50 Mbps). A direct local connection is limited only by the local network itself.
The same logic applies directly to industrial sites: for data moving between devices, or from devices to a platform, the path chosen determines speed, stability, and cost.
① Cloud (relay through the cloud)
Pros: cross-region access, reachable from anywhere. Costs: data travels up to the public internet and back down, capped by upstream bandwidth; large files and high-frequency data collection stay stuck at the bandwidth ceiling; routing through third-party servers adds latency and raises security concerns. Suitable for low-frequency, small-packet remote monitoring — not for bulk transfer.
② USB
Convenient for one-off copying, but requires someone to plug and unplug and to operate manually — no long-term online operation, no automation. In environments where fixed devices run 24/7, it can only serve as a temporary measure.
③ Wi-Fi
No cabling needed, well suited to mobile devices. But wireless is a shared medium: the more devices in the same area, the more collisions and retransmissions, and the less predictable the latency. The signal is also affected by electromagnetic interference and metal obstacles.
④ Ethernet (wired)
Physical cable; each device sends and receives independently through a switch, with dedicated bandwidth, stable latency, and deterministic connections. The default choice on industrial sites.
Why is Ethernet usually the choice for bulk data transfer between fixed devices? Not out of habit — four real problems decide it.
1. Electromagnetic interference is real
Motor start/stops, variable-frequency drives (VFDs), and welding equipment generate strong EMI. In such an environment, wireless signals suffer packet loss and retransmissions, and throughput drops visibly. A wired link blocks interference at the physical layer with shielded twisted pair plus isolation — for example, the Ethernet port of the USR-TCP232-410s carries 1.5KV electromagnetic isolation for exactly this purpose.
2. Metal equipment blocks signals
Industrial sites are full of metal cabinets and metal enclosures. Wi-Fi cannot pass through metal, and coverage dead zones are hard to troubleshoot. Cabling is a one-time hassle, but the path is deterministic: wherever the cable goes, the signal goes.
3. With many devices talking at once, wireless devices crowd each other
When dozens or hundreds of devices report data simultaneously, Wi-Fi shares a single channel: simultaneous transmissions cause collisions and retransmissions, and there is no predictability in who transmits first. On Ethernet, each device has its own switch port, latency is predictable, and collection cycles stay accurate.
4. Fixed devices run long-term and cannot afford disconnects
Long-running equipment has zero tolerance for disconnects and packet loss. The common engineering practice: TCP persistent connections plus heartbeat packets and a hardware watchdog — auto-reconnect on drop, auto-reset on abnormality. This mechanism only makes sense on a stable physical link — during the Wi-Fi disconnect-and-reconnect window, business data is lost.
Fixed installations with data-sensitive devices → wired serial to ethernet adapter
For a single device, a serial to ethernet adapter is enough. The USR-TCP232-410s is the classic example: RS232 and RS485 serial ports working simultaneously, a 10/100M Ethernet port with 1.5KV electromagnetic isolation, -40°C to +85°C operating temperature, DC 9–36V wide-input power, and a metal housing. It supports Modbus RTU/TCP conversion and MQTT reporting — on top of transparent transmission, it also handles protocol conversion, so fixed devices such as meters, PLCs, and sensors go online with a single unit.
Multiple serial devices to connect centrally → multi-port models
When there are many devices and it is not worth giving each one its own converter, use a multi-port serial device server. The USR-N540 provides 4 RS485 ports with Modbus multi-host polling; the USR-N520 is a 2-port secure model with SSL/TLS encryption. One unit handles many devices, and there are fewer maintenance points.
Moving devices, or sites where cabling is truly impossible → only then consider Wi-Fi
For mobile equipment such as AGVs and robots, or retrofit sites where cables really cannot be run, choose a wireless solution — but pick one with fast roaming. The USR-W660 is a dual-band Wi-Fi 6 converter (2.4G/5.8G) with roaming handover under 100 ms, dual Gigabit ports plus RS232/RS485, designed for mobile scenarios like AGVs. One caveat: no matter how fast roaming is, there is still a handover window — when the control link demands extreme real-time performance, wired is still the priority.
No need to memorize complex specs. Ask three questions before selection:
The answers settle it in most cases. In industrial data transfer, the reliability gap is not in the devices themselves — it is decided at the moment the transmission path is chosen.
