Industrierouter: AT, Dual-SIM, Modbus
June 3, 2026 · 8 min read · Technical Whitepapers
AT+CSQ vor Montage. Ping-Failover. Statische IP-SIM.
TL;DR: An industrial cellular router is not a consumer hotspot with a rugged case. It is a protocol converter, a failover engine, and a remote diagnostic terminal —and the difference between one that works for 5 years without a site visit and one that generates monthly truck rolls is in about 30 lines of configuration. Three areas where configuration meets connectivity procurement: AT+CSQ before drilling mounting holes, ping-failure over RSSI for failover, and static-IP SIM provisioning for Modbus server-initiated polling. Get these right and the site visit schedule drops from monthly to never.
AT Commands: The Direct Line to the Modem When the GUI Lies
Every cellular module inside an industrial router speaks AT commands —the Hayes command set that predates GSM but remains the only way to query the modem directly. When the web interface shows "Connected" but no data is passing, AT commands reveal what is actually happening.
Essential diagnostic commands for field deployment:
| Command | Returns | Why it matters |
|---|---|---|
| --------- | --------- | --------------- |
| AT+CSQ | Signal quality (0-31, 99=unknown) | Validates RSSI before permanent installation. Below 10 = unreliable data. |
| AT+CREG? | Network registration status (0-5) | 1=registered on home network, 5=registered roaming. If 2 or 3, the SIM is not provisioned correctly. |
| AT+COPS? | Current operator name and PLMN ID | Confirms which MNO the device actually attached to —not which MNO the SIM was supposed to use. |
| AT+CGATT? | GPRS/PS attach status (0/1) | 1=attached. If 0, the APN is wrong, the SIM has no data plan, or the modem is not LTE-compatible for the current band. |
| AT+CMGS | Send SMS | Can trigger alerts or accept remote commands when IP connectivity is down. Requires SMS-enabled SIM plan. |
Practical workflow: before drilling mounting holes, connect a laptop, open a terminal (PuTTY, 115200 baud), send AT+CSQ. If the value is below 10, move the antenna —or move the installation location. A single AT command at installation prevents a site visit 3 months later when "intermittent connectivity" becomes a ticket.
Source: Robustel, "Mastering AT Over COM: Industrial Router Configuration & Commands 2026". Available at https://robustel.com/fr/mastering-at-over-com-industrial-router-configuration-commands-2026/
Dual-SIM Failover: Designing Triggers That Actually Prevent Downtime
Dual-SIM slots are standard on industrial routers (Robustel EG5120, R1511 series, GWR-I, Amuse Tech). But dual SIM hardware does not equal reliable failover —the trigger logic determines whether the failover happens before or after the SCADA system alarms.
Three failover trigger approaches, ranked by effectiveness:
1. Ping failure detection (best): The router sends ICMP pings to a reliable endpoint (8.8.8.8 or a private server) at configurable intervals —typically every 30 seconds. If N consecutive pings fail (usually 3-5), the router switches SIMs. This detects end-to-end connectivity failure, not just RF signal loss —if the carrier's PGW is down but the tower is up, ping failure triggers a switch; RSSI threshold does not.
2. RSSI threshold (acceptable as secondary): The router switches when signal quality drops below a defined threshold (e.g., -105 dBm). This catches tower-level issues but does not detect upstream network failures. Use as a secondary trigger alongside ping failure.
3. Timer-based switching (worst): Switching SIMs on a fixed schedule regardless of connectivity state. This guarantees periodic downtime with no guarantee of improvement. Avoid.
Auto-failback: Once the primary SIM's network is stable again (ping succeeds for M consecutive intervals), the router should automatically switch back. Without auto-failback, the deployment runs indefinitely on the backup SIM —potentially at higher roaming rates or with degraded coverage.
SIM procurement implication: the two SIMs must be on different carrier networks. Two SIMs from the same MNO provide zero redundancy —they share the same tower, same core network, and same failure domain. A multi-IMSI SIM with two different MNO profiles achieves the same result in a single physical card —but the failover is SIM-level (profile switch), not modem-level (physical SIM slot switch). SIM-level switching is faster (under 5 seconds vs 60-90 seconds for modem-level) because the modem does not need to re-initialize the radio.
Source: Robustel, "Dual SIM Failover: Achieving 99.9% Uptime in Industrial IoT", 2025. Available at https://robustel.com/
Modbus RTU to TCP: The Protocol Bridge That Keeps Old PLCs Alive
Thousands of industrial sites run Modbus RTU over RS-232 or RS-485 serial links —PLCs, RTUs, flow meters, power monitors. These devices were installed before IP networking reached the factory floor. Replacing them is capital-intensive and operationally disruptive.
An industrial cellular router with a built-in Modbus RTU-to-TCP gateway solves this at the connectivity layer: the router's serial port connects to the Modbus RTU device (physical RS-485 wiring), the router converts Modbus RTU frames to Modbus TCP packets, and the TCP packets are routed over the cellular connection to a central SCADA system or cloud IoT platform.
Configuration steps (vendor-agnostic):
1. Physical: connect the serial device to the router's RS-485 terminal block. Match baud rate, data bits, parity, and stop bits to the Modbus device (typically 9600-115200 baud, 8N1).
2. Protocol: in the router's serial port settings, select "Modbus RTU to TCP" mode. Assign a TCP port (default 502 —the standard Modbus TCP port).
3. Network: configure the cellular WAN interface with the correct APN. For Modbus traffic, a standard internet APN is usually sufficient unless the SCADA system requires a private APN with static IP.
4. SIM provisioning: the SIM must support inbound connections if the SCADA system initiates polls (TCP client mode from the router to the SCADA server). If the SCADA server initiates connections to the router, the SIM must have a public or static private IP —standard consumer SIMs with carrier-grade NAT will not work.
The SIM decision point: a standard IoT data plan with a private APN and static IP is required for server-initiated Modbus polling. Catalogue IoT SIMs with dynamic IPs behind NAT work only if the router initiates the connection (TCP client mode). This is a procurement question, not a configuration question —and it must be answered before the router is shipped to the site.
Source: Robustel R1511/R1511P product documentation. Available at https://robustel.com/product/r1511/
Antenna Placement and Signal Validation: The Physical Layer That Configuration Cannot Fix
AT commands and failover logic cannot compensate for a badly placed antenna. Industrial routers are often installed inside metal enclosures, concrete plant rooms, or underground vaults —all of which attenuate cellular signals by 15-30 dB. Key rules:
1. External antenna is mandatory for metal enclosures. A PCB trace antenna inside a steel cabinet experiences 20+ dB attenuation —enough to drop from LTE to no service.
2. Antenna diversity: routers with dual antenna connectors support MIMO (Multiple Input Multiple Output) which improves data rates and signal reliability. Both antennas must be connected and positioned at 90° to each other for effective diversity.
3. Cable loss: every meter of antenna cable adds 0.5-2 dB of loss depending on frequency and cable quality. Keep antenna cable runs under 5 meters. Use LMR-400 or equivalent low-loss cable for longer runs.
4. Validate before bolting down: before permanent installation, use AT+CSQ at the intended antenna position. Record the value. Move the antenna 30 cm in each direction and re-test. A 30 cm move can change signal quality by 5-10 points on the CSQ scale due to multipath reflections.