An older PLC, meter, RTU, weighing terminal, pump controller, or field instrument does not need to be replaced simply because it still communicates through a serial port. A correctly specified RS232 RS485 industrial router can create a cellular path to that equipment while the proven field device remains in service. The important decision is not whether the router has a SIM slot. It is whether its serial option, wiring, communication mode, network route, and recovery behaviour match the existing system.
This guide starts with the buying decision. It explains when to choose RS232, when to choose RS485, what H750tt configuration to request, when a different router or gateway is required, and how to prove the complete connection before a wider rollout.
The direct answer before you buy
Choose an RS232 configuration when one router will connect to one point-to-point serial device and the project can document TX, RX, GND, serial format, and any required flow-control signals.
Choose an RS485 configuration when the field side is an addressed multi-drop bus with one or more compatible devices sharing the same pair of communication wires.
Do not assume one H750tt configuration provides both interfaces. The published order models include H750tt-W-RS232 with one RS232 port and H750tt-W-RS485 with one RS485 port. State the required version in the quotation and purchase order.
Do not assume a serial port automatically converts protocols. Transparent serial transmission, virtual COM access, Modbus RTU pass-through, and Modbus RTU-to-TCP conversion are different requirements. Ask for the exact supported communication mode before ordering.
Start with the legacy device, not the router specification
A serial migration is most predictable when the existing device already communicates reliably through a known local cable or bus. The router then replaces the distance between the field equipment and the remote software; it does not repair an undocumented protocol or an unstable local connection.
Good first projects usually involve scheduled meter readings, status messages, alarm reporting, parameter checks, log collection, or controlled maintenance sessions. These applications commonly exchange small request-and-response frames and can tolerate a carefully tested cellular delay.
Strong migration candidates
- The device works correctly through RS232 or RS485 before the router is added.
- The baud rate, parity, data bits, stop bits, address, and protocol are known.
- The task is monitoring, reading, reporting, diagnostics, or approved maintenance.
- The software can tolerate realistic network delay and controlled retries.
- A local service method can remain available during the pilot.
Projects requiring additional proof
- The original application expects a local COM port with very short timing.
- The protocol is proprietary, undocumented, or sensitive to frame gaps.
- More than one system may try to poll the same RS485 devices.
- The serial link carries safety-related or deterministic control commands.
- The existing local communication is already intermittent or poorly documented.
Build a one-page device record
Before comparing router models, record the device manufacturer and model, interface type, connector or terminal layout, serial settings, protocol, address, local software, polling interval, cable route, power source, cabinet environment, and present maintenance method.
Also capture one known-good local transaction. A request-and-response frame from the working system gives the pilot team a reference when the cellular path is introduced. Without that reference, a wiring problem, protocol problem, and network problem can all look like the same “no data” fault.
RS232 or RS485: choose the field interface correctly
RS232 and RS485 are both serial interfaces, but they should not be treated as interchangeable order options. RS232 is generally used for a point-to-point connection between two devices. RS485 commonly supports an addressed bus in which several compatible devices share one communication line.
| Decision point | RS232 project | RS485 project |
|---|---|---|
| Typical layout | One router serial port connected to one PLC, terminal, meter, controller, or service port. | One router serial port connected to an addressed bus with one or more compatible devices. |
| Information to collect | TX, RX, GND, connector pinout, cable type, baud rate, parity, stop bits, and possible RTS/CTS use. | A/B terminal definition, device order, addresses, baud rate, parity, termination, biasing, shielding, and grounding. |
| Common purchasing mistake | Assuming every serial cable has the same pinout or that signal ground is unnecessary. | Assuming every device can be placed on the same bus without checking addressing, electrical loading, and polling control. |
| Acceptance test | Send a known request and confirm that the expected single device returns the correct response. | Poll each documented address separately, then test the complete bus for errors, timeouts, and duplicate replies. |
A practical RS485 warning
An RS485 port does not mean an unlimited number of devices can be added. Real capacity depends on the transceivers, cable length, topology, baud rate, termination, electrical environment, device timing, and polling design. Confirm the actual bus during the pilot instead of relying on a generic device-count promise.
Define the serial data path before choosing hardware
“We need Modbus” is not a complete router requirement. The purchasing request must explain how the remote application will communicate with the field device and whether the serial payload should remain unchanged.
Transparent serial transmission
Serial bytes are carried through a TCP or UDP connection without intentionally changing the application payload. The remote system must already understand the original field protocol.
Virtual COM access
The remote software continues to work with a COM-style interface while a driver carries the session across IP. Compatibility must be tested with the actual software version and operating system.
Modbus RTU pass-through
The Modbus RTU frame remains a serial request-and-response transaction. Cellular connectivity changes the route, but it does not automatically change RTU framing into Modbus TCP.
Modbus RTU-to-TCP gateway conversion
A gateway function converts between the serial and TCP communication structures. If this is required, ask the supplier to confirm the function on the exact model and firmware rather than assuming that every router with an RS485 port provides it.
The Modbus specifications and implementation guides distinguish serial-line and TCP/IP implementations and describe client, server, and gateway roles. Use the current project terminology in new documents, while recognising that older equipment manuals may still use legacy master/slave wording.
Check who starts each transaction
One defined client or polling system should initiate requests, and the addressed field device should reply. Problems arise when a local SCADA system and a remote maintenance application both send uncontrolled requests to the same serial bus. Decide which system owns normal polling, how maintenance access is opened, and what happens to the regular poll while a technician is connected.
Do not copy local-cable timeout settings blindly
A local cable may return a response almost immediately. A cellular route adds radio registration, carrier routing, VPN processing, packet transport, and possible reconnection. The application timeout must be long enough for the tested route but still short enough to report a genuine device or network fault.
Frame packaging also matters. Protocols that depend on silent intervals or exact boundaries may require different serial-to-IP packetisation settings. Test complete request and response frames rather than approving the project from a successful network ping.
Plan remote reachability without publicly exposing the serial service
Cellular routers often receive a dynamic or carrier-managed address. A SIM can register successfully while the field router remains unreachable from the remote office. The network design therefore needs to define the connection direction before the SIM plan and router configuration are approved.
Document these five network decisions
- Connection direction: does the field router open an outbound session, or must the remote system initiate a connection toward the site?
- SIM addressing: does the service use a public APN, private APN, fixed address, dynamic address, or carrier-grade NAT?
- Protected route: which VPN endpoint, route, credentials, and permitted source networks will be used?
- Service mapping: which TCP or UDP service maps to the required serial function?
- Recovery order: after power restoration, how will cellular registration, VPN recovery, serial service, and application polling resume?
Opening a legacy serial service directly to the public internet should not be the default design. Many older controllers and instruments were built for trusted local networks and may not provide modern authentication or encryption. NIST SP 800-82 Rev. 3 provides broader guidance for securing operational technology while accounting for availability, reliability, and safety requirements.
In practice, a private APN, controlled VPN, restrictive firewall rules, approved maintenance users, and a defined access window provide a clearer path than publishing an unrestricted serial port. The final design should follow the organisation’s OT security policy and risk review.
Which E-Lins configuration fits the project?
H750tt is a practical model to evaluate for a cabinet retrofit that needs cellular connectivity, local Ethernet, and one selected serial interface. The important point is the order configuration. The published model table identifies separate RS232 and RS485 variants rather than one order model with both serial interfaces active at the same time.
| Project requirement | Starting direction | What to confirm before ordering |
|---|---|---|
| One point-to-point RS232 device | H750tt-W-RS232 | Pinout, TX/RX/GND arrangement, baud rate, parity, flow control, remote software mode, cellular bands, and VPN path. |
| One RS485 bus | H750tt-W-RS485 | A/B definition, device addresses, bus topology, termination, baud rate, polling ownership, remote software mode, and VPN path. |
| Simultaneous RS232 and RS485, or several independent serial ports | Compare other industrial 4G router configurations | Required number and type of serial ports, isolation, Ethernet count, protocol gateway functions, and whether an external serial gateway is acceptable. |
| Cellular connectivity built into an OEM machine or terminal | Review embedded cellular systems | Board dimensions, power, host interface, firmware integration, antenna design, certification responsibilities, and development support. |
H750tt for an RS232 or RS485 retrofit pilot
The H750tt product range lists dual cellular connectivity, three Fast Ethernet ports, and optional serial configurations. For a serial migration project, request the exact RS232 or RS485 order model and confirm the cellular region, SIM plan, VPN method, firmware function, power arrangement, antenna set, and mounting accessories in the supplier response.
The pictured unit shows the RS232 terminal layout. The H750tt-W-RS485 order model uses a different serial terminal definition, so confirm the exact version before wiring.
When H750tt should not be treated as the automatic choice
Compare another configuration when the project needs RS232 and RS485 at the same time, more than one independent serial channel, confirmed RTU-to-TCP gateway conversion, specialised electrical isolation, additional Ethernet integration, or another mandatory interface that is not included in the selected order model.
A different solution may also be required when the serial task is part of a safety function, when the application cannot tolerate cellular delay, or when site certification and environmental requirements go beyond the documented product configuration. These points should be resolved during technical review rather than after equipment arrives on site.
What to include in the quotation request
- Country, mobile operator, required cellular bands, SIM quantity, and APN type.
- RS232 or RS485 requirement and the exact number of serial interfaces.
- Device model, protocol, baud rate, parity, data bits, stop bits, and device addresses.
- Transparent TCP/UDP, virtual COM, Modbus pass-through, or gateway conversion requirement.
- Remote connection direction, VPN type, server address, and access-control policy.
- Cabinet power, mounting method, antenna location, environment, and cable requirements.
- Expected pilot quantity, rollout quantity, and acceptance test conditions.
Prove the complete path with a controlled pilot
A pilot should use the real device, cable, router configuration, SIM, operator, APN, VPN endpoint, remote application, and server route. A bench test using different components may prove a concept, but it does not approve the field deployment.
1. Preserve the working baseline. Photograph the original wiring, save serial settings, record the local software version, and capture a known request-and-response exchange.
2. Add the router before adding network complexity. Verify the correct RS232 or RS485 order model, terminal wiring, serial format, and intended communication mode.
3. Introduce the real cellular route. Install the intended SIM, APN, VPN, routing, firewall, and remote endpoint. Repeat the same transaction used for the local baseline.
4. Test interruption and recovery. Simulate loss of cellular service, VPN interruption, router reboot, and cabinet power cycling. Record the time and sequence required for normal polling to resume.
5. Keep a rollback path. The technician should be able to restore the previous local communication method without designing new wiring during an outage.
Acceptance should be based on evidence
- Returned values match the known local reference.
- Each intended RS485 address responds without duplicate or crossed replies.
- The remote application reconnects after a temporary session failure.
- The VPN, route, and serial service recover after a controlled restart.
- Response time remains within the approved application timeout.
- Configuration files, order model, firmware version, SIM record, and wiring photos are stored with the site record.
One successful poll is not a rollout approval. Run the pilot long enough to include normal traffic, repeated reconnects, weaker coverage periods, maintenance access, and realistic power events.
Troubleshoot from the device outward
When no data appears, avoid changing several settings at once. Move through the communication chain in a fixed order: field power, serial wiring, serial format, local device response, router service mode, cellular registration, APN, VPN, route, port rule, and remote application timeout.
| Symptom | Most likely area | First practical checks |
|---|---|---|
| Router is online, but the serial device never replies. | Serial option, wiring, or format | Verify the exact RS232 or RS485 order model, terminal definition, TX/RX or A/B wiring, ground reference, baud rate, parity, stop bits, and device address. |
| The device works locally but not through the cellular path. | APN, NAT, VPN, route, port, or application timeout | Check the connection direction, VPN state, permitted source, destination address, mapped service, and whether the remote software is waiting long enough. |
| RS485 devices respond intermittently. | Bus design or competing polling | Inspect A/B polarity, termination, shielding, grounding, duplicate addresses, cable branches, retry rate, and whether two clients are polling the bus. |
| Characters are readable only sometimes or frames look incomplete. | Serial-format mismatch, noise, or packetisation | Match all serial parameters, separate communication cable from noisy power wiring, and review the serial-to-IP frame or timeout settings. |
| The router reconnects, but data does not resume after a power event. | Recovery sequence | Confirm cellular registration, VPN restoration, route availability, serial service restart, and application reconnection in that order. |
The troubleshooting rule that prevents repeated site visits
Record the result before changing the next setting. If the APN, parity, VPN route, and software timeout are all modified together, the team may restore communication without knowing which change fixed it. A repeatable record is more valuable than a one-time successful connection.
Related E-Lins guides
4G LTE Router vs 4G Modem
Use this comparison when deciding whether the project needs routing, LAN management, VPN, and remote diagnostics or only a cellular connection managed by another host.
Cellular Router for PLC Remote Maintenance
Review this guide when the project includes PLC engineering access, Ethernet automation devices, maintenance permissions, and a dedicated service network.
Dual SIM 4G Router for Remote Monitoring
Useful when the next design question is cellular continuity, primary and backup SIM planning, remote monitoring, and recovery after an operator outage.
Frequently asked questions
Does one H750tt include both RS232 and RS485?
Do not assume so. The published order table lists H750tt-W-RS232 with one RS232 interface and H750tt-W-RS485 with one RS485 interface. Put the required model and interface into the quotation and purchase order.
Can an RS485 H750tt connect to several meters?
It can be evaluated for an addressed RS485 bus, but the usable device count cannot be decided from the router name alone. Confirm device addresses, transceivers, cable length, topology, termination, baud rate, bus loading, and polling behaviour in the actual pilot.
Is transparent serial transmission the same as Modbus RTU-to-TCP conversion?
No. Transparent transmission carries the existing serial payload through an IP connection. RTU-to-TCP conversion requires a gateway function that translates between the relevant communication structures. Confirm the exact mode on the selected hardware and firmware.
Can old serial software work through a cellular router?
It may work through transparent TCP/UDP or a virtual COM path, but compatibility depends on the software, protocol timing, operating system, driver, timeout, and reconnection behaviour. Test the exact application rather than only a generic serial utility.
Should the serial service use a public IP address?
Direct public exposure should not be the default. Legacy devices may have limited authentication and encryption. A private APN, controlled VPN, restrictive firewall policy, and approved maintenance access are generally clearer starting points, subject to the organisation’s OT security requirements.
What should be tested before approving a rollout?
Test the real field device, wiring, order model, serial mode, SIM, operator, APN, VPN, remote software, response time, weak-signal behaviour, power recovery, cellular reconnection, and rollback process. Keep the resulting logs and configurations as the rollout reference.
When is an embedded cellular system a better choice?
An embedded system is a better direction when cellular communication must become part of a new machine, terminal, gateway, or OEM product. A finished router is normally easier to evaluate for an existing cabinet and legacy-device retrofit.
Send the serial requirement, not only a model name
A useful inquiry identifies the device, RS232 or RS485 interface, wiring, communication settings, protocol path, remote application, cellular operator, APN, VPN, power, antenna, installation environment, pilot quantity, and acceptance test.
E-Lins can then confirm whether H750tt-W-RS232, H750tt-W-RS485, another industrial router configuration, or an embedded system is the more appropriate starting point.
