RS232 and RS485 on Industrial Routers: Modbus, SCADA, and What to Spec

How to specify RS232 and RS485 on industrial cellular routers for Modbus RTU and SCADA — wiring, isolation, baud rates, RTU-to-TCP, and common commissioning mistakes.

RS232 and RS485 on Industrial Routers: Modbus, SCADA, and What to Spec

Industrial projects rarely fail because the cellular link is slow — they fail because the serial side was never specified correctly. A PLC speaking Modbus RTU on RS485, an RTU with a legacy RS232 port, or a power meter that only exposes a serial interface all need the router to behave as a reliable protocol bridge, not just a Wi-Fi hotspot with a SIM slot.

This guide explains what to verify when you specify an industrial cellular router with RS232 and RS485 for SCADA and field automation — with examples from the Yifan lineup such as the NR130, YF325, and G100 gateway.

RS232 vs RS485 in one minute

RS232 is point-to-point: one router port to one device (PLC, meter, display). Common on older equipment and small controllers. Distance is short (typically under 15 m without repeaters), and electrical noise matters.

RS485 is multi-drop: one bus, many devices (Modbus RTU slaves) with addressing. Used heavily in energy, water, building automation, and factory floors. Cable length and termination (120 Ω at the ends of the bus) affect reliability more than most IT teams expect.

Many industrial routers offer one or more serial ports — sometimes configurable as RS232 or RS485. Confirm whether your SKU is fixed RS485 or software-selectable, and whether you need galvanic isolation for outdoor cabinets or substations.

Modbus RTU vs Modbus TCP over cellular

Modbus RTU runs on the serial wire. The router typically converts RTU to Modbus TCP (or forwards raw serial to a cloud collector) so your SCADA master can reach remote sites over VPN or a secure tunnel.

Modbus TCP is already Ethernet-framed. If the device has Ethernet, you may not need serial at all — but many legacy RTUs and meters do not.

When surveying a site, list every device: protocol (Modbus RTU/TCP, DNP3 serial, proprietary), baud rate, parity, stop bits, and whether the master polls or the device pushes data. Mismatch on baud or parity produces “random” timeouts that look like a bad cellular signal.

What to spec on the datasheet (checklist)

  1. Port count and type — RS232 only, RS485 only, or mixed; DB9 vs terminal block vs RJ45 serial
  2. Isolation — isolated vs non-isolated transceivers (important near motors, VFDs, and outdoor gear)
  3. Supported baud rates — 9600 is common on legacy gear; confirm up to 115200+ if needed
  4. Modbus gateway features — RTU↔TCP conversion, master/slave modes, register mapping limits
  5. Concurrent protocols — serial polling plus VPN plus firewall without CPU starvation
  6. Power and environment — wide temperature and DIN-rail mounting for cabinet installs; pair with our operating temperature guide
  7. Remote access — can engineering reach the serial diagnostics after deploy via remote management without truck rolls?

Typical deployment patterns

Remote RTU / substation — RS485 Modbus RTU to multiple meters; router runs VPN (see VPN guide) to the control center; dual SIM for uptime (dual SIM guide).

EV charger or street cabinet — single RS485 or RS232 to a charge controller; 4G/5G backhaul; often needs compact router like NR130 or 4G YF325. See EV charging connectivity.

Factory edge — gateway with serial + Ethernet + optional edge compute; G100 class devices when you need protocol aggregation beyond a simple serial server.

Common commissioning mistakes

  • Wrong termination on RS485 (missing or double termination)
  • Sharing a ground path with VFDs without isolated ports
  • Polling interval too aggressive for cellular latency — SCADA timeout before the round trip completes
  • Testing VPN only from a laptop, never from the SCADA server’s actual polling path
  • Assuming “Modbus supported” means your exact register map is preconfigured — it usually is not

FAQ

Do I need RS485 if my PLC already has Ethernet?

If every field device is on Ethernet and speaks Modbus TCP (or your SCADA protocol) natively, serial may be unnecessary. RS485 matters when meters, legacy RTUs, or OEM boards only expose serial.

Can one industrial router poll multiple Modbus RTU devices on RS485?

Yes, when the firmware supports Modbus master/gateway mode and the bus is wired correctly (A/B polarity, termination, unique slave IDs). Confirm the maximum number of slaves and poll rate in the manual.

Does 5G help Modbus over serial?

5G improves IP throughput and latency to the VPN/cloud path; it does not change serial timing on the local RS485 bus. Serial reliability is still about wiring, baud settings, and isolation.

What certifications matter for utility or EU projects?

Radio marks (FCC, CE/RED) cover the cellular module; serial ports do not replace electrical safety or grid compliance your end customer may require. For import and radio paperwork, see our FCC & CE buying guide.

Next step: Send your device list (protocol, baud, port type) and cabinet environment. Request a serial-capable router recommendation from Yifan sales engineering, or browse industrial routers and Industrial IoT & SCADA solutions.