Your factory floor still runs on RS485. The power meters talk Modbus RTU. The CNC machines expect RS232. The legacy HVAC controllers haven't been upgraded in a decade. Meanwhile, your SCADA system and cloud dashboard live on an IP network. The bridge between these two worlds? A serial-to-ethernet converter.
But not all serial servers are equal. A $30 transparent converter will pass raw bytes over TCP. A purpose-built industrial gateway handles Modbus protocol translation, wide temperature ranges, DIN-rail mounting, and MQTT cloud integration. Choosing the wrong one means CRC errors, frozen COM ports, and emergency site visits.
This guide covers the 6 criteria that matter when buying a serial-to-ethernet converter for industrial IoT deployments — whether you need a standalone device server or an integrated cellular router approach.
RS232, RS485, and RS422: Know Your Serial Type
Before comparing converters, identify what serial interface your legacy equipment uses. This determines the converter hardware you need.
| Parameter | RS232 | RS485 | RS422 |
|---|---|---|---|
| Topology | Point-to-point | Multi-drop bus (up to 32 devices) | Point-to-point (full-duplex) |
| Max Distance | 15 meters | 1,200 meters | 1,200 meters |
| Signaling | Single-ended | Differential (half-duplex, 2-wire) | Differential (full-duplex, 4-wire) |
| Typical Devices | CNC machines, barcode scanners, older PLCs | Power meters, environmental sensors, VFDs | Long-distance telemetry, legacy instrumentation |
| Wiring | TX, RX, GND (DB9 or terminal block) | D+, D− (terminal block) | TX+, TX−, RX+, RX− (terminal block) |
If you have a mix of RS232 and RS485 devices — common in most industrial sites — look for a converter that supports both modes via software configuration. Models like the InHand IR305 offer RS232 and RS485 on the same unit, so you do not need separate hardware for each serial standard.
Criterion 1: Serial Interface Type and Port Count
Match the converter's serial ports to your actual equipment. Key questions:
- How many serial devices need to connect? A single RS485 bus can daisy-chain up to 32 devices, so you may only need one serial port for an entire sensor chain.
- Do you need RS232 and RS485 simultaneously? Some converters offer dual-mode ports. Others require separate hardware for each type.
- What baud rates does your equipment use? Most converters support 300 bps to 115,200 bps. If you have high-speed serial at 230,400 bps or higher, verify the converter supports it.
For multi-port deployments, look for converters with 2, 4, or 8 serial ports on a single DIN-rail unit. This reduces cabinet space and simplifies cable management compared to stacking individual single-port servers.
Criterion 2: Protocol Conversion — Transparent vs Modbus Gateway
This is the most common and costly mistake buyers make.
A transparent serial server wraps raw RS485 bytes into TCP packets. Modbus RTU relies on a strict 3.5-character silence rule to determine message boundaries. When raw RTU frames traverse an Ethernet network, packet jitter and fragmentation break this timing, causing CRC errors and constant timeouts at the SCADA master.
The fix: specify a Modbus TCP gateway that actively translates Modbus TCP requests from your SCADA into Modbus RTU polling on the serial bus. This eliminates timing issues and requires zero changes to your PLC ladder logic.
Here is the difference:
| Feature | Transparent Serial Server | Modbus TCP Gateway |
|---|---|---|
| Operation | Passes raw bytes between serial and TCP | Actively translates Modbus TCP ↔ Modbus RTU |
| Timing handling | None — breaks Modbus RTU framing | Reconstructs proper RTU frame timing |
| Multi-host support | Limited — serial bus contention | Built-in polling cache (storage gateway mode) |
| Best use case | Custom proprietary protocols, debug tools | Modbus SCADA, power monitoring, sensor networks |
If your site runs Modbus RTU over RS485 — and most industrial facilities do — buy a gateway, not a transparent server. Check the product datasheet for "Modbus TCP to Modbus RTU conversion" or "Modbus gateway mode."
Criterion 3: Virtual COM Port Driver Stability
If your legacy software expects a physical COM port (common with older SCADA packages, custom VB applications, or CNC programming tools), you need a Virtual COM port (VCOM) driver that maps the remote serial device to a local COM port on your PC.
The hardware itself is only half the equation. Cheap converters ship with VCOM drivers that crash on network latency, fail to reconnect after a dropped connection, or break after Windows updates. Look for:
- Actively maintained drivers — not abandoned downloads from 2018
- Auto-reconnect behavior — the driver should recover gracefully when the network drops and comes back
- Multi-OS support — Windows, Linux, and ideally macOS
- Bulk configuration tools — if you are deploying 20+ units, a tool that configures multiple converters from a single interface saves hours
Check user forums and Reddit's r/PLC before committing to a converter brand. VCOM driver quality is the most frequently cited frustration in real-world deployments.
Criterion 4: Environmental Rating and Mounting
Where will the converter live? The deployment environment determines the hardware spec you need.
| Environment | Required Rating | Key Specs |
|---|---|---|
| Climate-controlled server room | Commercial (0 to 40°C) | Standard enclosure is acceptable |
| Indoor control panel | Standard industrial (0 to 60°C) | DIN-rail mount, IP30 minimum |
| Outdoor cabinet / unheated space | Wide temperature (−40 to +85°C) | Conformal coating, IP30+, wide voltage DC input |
| Hazardous location (oil & gas) | Class 1 Division 2 or ATEX | Intrinsically safe barriers, certified enclosure |
A converter that works in a lab will freeze in a Minnesota pumping station at −25°C. If your deployment includes outdoor enclosures, specify wide-temperature hardware from the start. Retrofitting in winter conditions costs significantly more than buying the right hardware upfront.
Also check power input range. Industrial sites typically run on 12V or 24V DC buses. A converter that accepts 9-36V DC covers most installations without a separate power supply. Dual redundant power inputs add failover for critical monitoring points.
Criterion 5: Network Security Features
Serial communication was originally point-to-point and physically isolated. Once you bridge it to Ethernet — especially over the internet — security matters.
Look for these features in any serial-to-ethernet converter handling sensitive data:
- TLS/SSL encryption for data in transit — prevents eavesdropping on serial traffic
- SSH for management access — never configure a converter over unencrypted HTTP in production
- IP/MAC address filtering — restrict which hosts can connect to the serial port
- 802.1X authentication — for enterprise networks with RADIUS servers
- Firmware update signing — prevents unauthorized firmware modifications
Industrial cellular routers (like the InHand IR305 or IG502) add another security layer: all serial data travels over a private APN or VPN tunnel to your network, rather than traversing a shared Ethernet LAN. This matters when the converter sits at a remote site with physical security risks.
Criterion 6: Cloud Integration and MQTT Support
Modern IIoT deployments bypass local SCADA entirely. Instead of polling serial devices from a local Windows machine, data goes directly to a cloud platform.
For this workflow, you need a converter with native MQTT support. The device reads serial data (typically Modbus registers), packages it into JSON payloads, and publishes to your MQTT broker — whether that is AWS IoT Core, Azure IoT Hub, or a private Mosquitto server.
Key MQTT features to verify:
- MQTT v3.1.1 or v5 — v5 adds shared subscriptions and message expiry
- TLS encryption — MQTT over TLS (port 8883) for production
- Offline buffering — if the network drops, the device should cache data locally and forward when connectivity returns
- Configurable polling intervals — match the update rate your sensors actually produce
If your serial devices are at a remote location without Ethernet infrastructure, a cellular router with serial ports eliminates the need to install a local network. The InHand IR305 (RS232/RS485) or IG502 (industrial gateway with Modbus and OPC UA) connects serial equipment directly over 4G/5G to your MQTT cloud — no Ethernet switch, no local IT support required. Learn more about bridging Modbus RTU to MQTT with an industrial gateway.
Standalone Converter vs Router-Integrated: Which Approach?
You have two hardware paths to get serial data onto an IP network:
| Factor | Standalone Serial Server | Cellular Router with Serial Ports |
|---|---|---|
| Hardware count | Converter + separate router/modem = 2 devices | Single device handles both functions |
| Remote management | Manage converter separately from network | Single cloud-managed interface for router + serial |
| Connectivity | Requires local Ethernet or Wi-Fi | Built-in 4G/5G — works anywhere with cellular coverage |
| Protocol support | Varies — check Modbus, MQTT per model | Typically includes Modbus TCP gateway, MQTT, OPC UA |
| Security | Depends on model — basic on budget units | Built-in firewall, VPN (IPsec/WireGuard), private APN |
| Best for | Indoor LAN environments, existing network infrastructure | Remote sites, no local network, cellular-only locations |
If your serial equipment sits in a building with Ethernet and local IT support, a standalone serial server works fine. If the equipment is at a remote wellhead, pump station, or construction site with no wired network, a cellular router with serial ports gives you both connectivity and protocol conversion in one box.
InHand offers several routers with integrated serial-to-ethernet capability:
InHand IR305
LTE Cat-6 industrial router with RS232 and RS485 ports. Supports Modbus RTU to MQTT conversion, WireGuard VPN, and cloud management via Device Live. Designed for DIN-rail mounting in control cabinets.
InHand IG502
Industrial edge gateway with RS232/RS485, Modbus RTU/TCP, OPC UA, and MQTT. Built for protocol conversion at the network edge — bridges legacy OT equipment directly to IT systems and cloud platforms.
InHand IR615-S
Compact LTE Cat-6 router with serial port support. Lower-cost option for applications that need basic serial-to-cellular connectivity without the full gateway feature set.
Quick Comparison: Selection Decision Matrix
Use this matrix to narrow your choice based on your deployment scenario:
| Your Scenario | Serial Type | Recommended Type | Key Feature to Verify |
|---|---|---|---|
| Indoor PLC on factory LAN | RS485 Modbus RTU | Modbus TCP gateway (standalone) | Multi-host polling, VCOM stability |
| Remote pump station | RS485 sensors | Cellular router with serial ports | 4G/5G connectivity, MQTT, wide temp |
| CNC machine programming | RS232 | Transparent serial server | Reliable VCOM driver for Windows |
| Power meter monitoring | RS485 Modbus | Modbus gateway or industrial router | Storage gateway mode (cached polling) |
| Multi-site cloud dashboard | RS232/RS485 mix | Cellular router with MQTT support | TLS, offline buffering, cloud management |
For a deeper look at choosing industrial cellular gateways for IoT sensor integration, see our industrial cellular gateway buying guide.
Frequently Asked Questions
What is the difference between RS232, RS485, and RS422 serial interfaces?
RS232 is a point-to-point interface limited to 15 meters, commonly used for older CNC machines and barcode scanners. RS485 supports multi-drop networks up to 1,200 meters with up to 32 devices on a single bus, making it the standard for industrial sensors and power meters. RS422 offers point-to-point communication over longer distances with differential signaling for noise immunity.
Do I need a transparent serial server or a Modbus TCP gateway?
If your SCADA software uses Modbus TCP to poll Modbus RTU devices on an RS485 bus, you need a Modbus TCP gateway that actively translates protocols. A transparent serial server only wraps raw bytes into TCP packets, which causes CRC errors and timeouts with Modbus RTU due to its strict 3.5-character silence timing rule.
Can a cellular router replace a standalone serial-to-ethernet converter?
Yes. Industrial cellular routers like the InHand IR305 or IG502 include built-in RS232/RS485 ports with native serial-to-ethernet and Modbus TCP conversion. This eliminates the need for a separate converter plus a separate network connection, reducing hardware count and simplifying remote management through a single cloud-managed device.
What environmental ratings should I look for in an industrial serial server?
For indoor control panels, a standard industrial rating of 0 to 60°C is sufficient. For outdoor cabinets or unheated enclosures, specify wide-temperature operation from −40 to +85°C. Look for DIN-rail mounting, IP30 minimum ingress protection, and dual redundant DC power inputs for critical installations.
How do serial-to-ethernet converters connect to cloud IoT platforms?
Modern converters support MQTT protocol natively, packaging serial data into lightweight JSON payloads for direct upload to AWS IoT, Azure IoT Hub, or private dashboards. This bypasses traditional SCADA entirely. Devices with cellular connectivity can push data over 4G/5G without requiring a local Ethernet network or Wi-Fi infrastructure.
Bottom Line
Serial-to-ethernet converters are the workhorses of industrial IoT — they bridge decades of legacy equipment into modern IP networks. The buying decision comes down to six criteria: serial type and port count, protocol conversion (transparent vs Modbus gateway), VCOM driver quality, environmental rating, network security, and cloud integration support.
If your deployment involves remote sites without wired Ethernet, consider industrial cellular routers with integrated serial ports. They combine connectivity and protocol conversion in a single device, managed through one cloud interface. Products like the InHand IR305 and IG502 are built for exactly this use case.
For technical questions about serial port configuration or Modbus setup on InHand devices, reach out to InHand technical support.
