Teltonika Modbus Gateway Guide: RTU, TCP, RS485 & RS232

Q: Can I connect several Modbus RTU devices to one Teltonika router?

Yes, where the RS485 bus and devices are designed accordingly. Devices use unique server IDs and the gateway can address the required RTU device.

Q: Should I open TCP port 502 on a public 4G SIM?

Direct public exposure is generally a poor security design. Restrict access and use a controlled path such as a VPN or private routed network wherever practical.

Q: Does every Teltonika router have RS485?

No. Hardware interfaces vary by model, so select a device with the serial interface required by the field equipment and verify current RutOS support.

Guides & Explainers · Teltonika · Industrial IoT

Teltonika Modbus Gateway: Connecting RS485 and RS232 Equipment to IP, 4G and the Cloud

A Modbus gateway is the bridge between equipment that may have been designed decades ago and the IP networks, VPNs and cloud platforms used today. This guide explains Modbus RTU, Modbus TCP and how a Teltonika router or gateway can sit between the two, with practical examples, configuration logic and the mistakes that cause most commissioning problems.

IoTPortal.co.uk · September 2026 · Practical industrial connectivity guide

TL;DR

Modbus TCP and Modbus RTU can carry essentially the same industrial conversation over different transports. A suitable Teltonika device can accept a Modbus TCP request over Ethernet or a secure remote IP path, translate/forward it to an RS485 or RS232 Modbus RTU device, then return the response. That lets an existing meter, PLC, inverter, BMS controller or RTU become reachable over an IP network without replacing the field equipment.

Why Modbus gateways still matter

Industrial IoT is full of equipment that works perfectly well but was never designed for Ethernet, 4G or cloud connectivity. Energy meters, PLCs, drives, environmental controllers, solar inverters and building-management equipment may expose an RS485 or RS232 port and speak Modbus RTU. The machine can have another decade of useful life in it; the communications interface is simply from a different era.

A gateway solves that mismatch. Instead of replacing the controller, the gateway sits at the edge of the installation and gives the old serial world a route into the new IP world.

SCADA / BMS / Modbus TCP client → Ethernet, VPN or private IP network → Teltonika gateway → RS485 / RS232 Modbus RTU device

This is one reason devices such as the Teltonika RUT956 keep appearing in industrial designs. It combines cellular WAN, Ethernet, RS232 and RS485 with the software needed to bridge those worlds.

First: Modbus RTU and Modbus TCP are not the same connection

The word Modbus gets used as though it describes one cable and one configuration. It does not. Two of the forms encountered most often in industrial IoT are Modbus RTU and Modbus TCP.

	Modbus RTU	Modbus TCP
Transport	Serial, commonly RS485, sometimes RS232	TCP/IP over Ethernet or another routed IP network
Device identity	Server/slave ID on the serial bus	IP address plus Unit/Server ID where required
Typical physical settings	Baud rate, data bits, parity, stop bits	IP address and TCP port; 502 is the conventional Modbus TCP port
Typical use	Meters, PLCs, drives, sensors and legacy controllers	SCADA, BMS, PLC and software systems on an IP network

The gateway’s job is to sit in the middle. A Modbus TCP client asks for a register. The Teltonika device passes that request to the correct RTU device on the serial bus, waits for the response and sends the answer back over TCP.

Useful mental model

The gateway does not magically understand your plant. It provides the transport bridge. You still need to know which device ID, function code and register the field device expects. The meter or PLC manufacturer’s Modbus register map remains essential.

A real-world example: an energy meter in a remote cabinet

Imagine an energy meter with RS485 Modbus RTU installed in a remote plant room. Locally, an engineer can connect to the serial bus and read voltage, current, power and accumulated energy. The business now wants those same values available at a central SCADA system.

Replacing the meter with a cellular product would be unnecessary. Instead, a Teltonika router with RS485 is installed in the cabinet.

The meter remains connected over its existing RS485 pair.
The Teltonika serial interface is configured to match the meter, for example its baud rate, parity and stop bits.
The Modbus TCP-over-Serial Gateway listens for permitted TCP requests.
The remote SCADA system reaches the router through the site’s secure IP path.
A request for the meter’s server ID and register is forwarded onto RS485.
The meter replies; the gateway returns the response to SCADA.

The result is not a new meter. It is an old meter that has become remotely reachable.

This same pattern appears in utilities, EV charging, solar, generators, pumps, agriculture and building management. Our Schneider Electric and Teltonika explainer shows the same idea applied to industrial controllers and meters.

Which Teltonika device?

Do not assume every Teltonika router has a physical RS485 or RS232 interface. The software family is broad, but the hardware interfaces vary by model. For a direct Modbus RTU gateway, choose a model with the serial interface your field equipment actually uses.

Example device	Why it fits
RUT956	Industrial 4G router with RS232 and RS485, dual SIM, Ethernet, I/O and a strong fit for SCADA/automation cabinets.
TRB145	Compact RS485 cellular gateway where the job is primarily to connect serial equipment rather than provide a larger router/switch platform.
Other RUT / TRB models	Capabilities differ. Check the exact hardware interfaces and current RutOS package support before specifying.
IP-only Teltonika device	Can still participate in Modbus TCP networks, but cannot directly terminate an RS485/RS232 RTU bus without external serial hardware.

For a wider discussion of why industrial routers increasingly do more than simply route packets, see SBC vs Industrial Router for IoT Edge Computing.

Configuration: get the serial side right first

Most failed Modbus gateway commissioning sessions are not caused by 4G. They are caused by two ends of an RS485 link disagreeing about something basic.

Before thinking about the remote connection, establish the field-device settings from its manual or existing configuration:

Interface: RS485 or RS232.
Baud rate: both ends must use the same speed.
Data bits.
Parity: none, odd or even as required.
Stop bits.
Server/slave ID: the address of the Modbus RTU device on the bus.
Register map: register number/address, data type and supported function code.

Commissioning rule

Prove the serial conversation locally before adding the WAN. If the gateway cannot reliably query the RTU device from a few centimetres away, a SIM card, VPN and cloud server will not fix it.

RS485 wiring matters

RS485 is robust, but it is not immune to poor installation. Check the A/B pair against the equipment documentation, use appropriate cabling, maintain sensible topology and apply termination/biasing according to the bus design and equipment requirements. Different manufacturers have historically labelled the two RS485 conductors inconsistently, so never rely on the letter printed beside a terminal without checking the manual.

If you receive no response at all, reversed A/B conductors are one of the quickest things to investigate. If communication is intermittent rather than completely absent, look harder at bus length, topology, termination, grounding, interference and mismatched serial parameters.

Configure the Modbus TCP-over-Serial Gateway

On supported RutOS devices, create a Modbus TCP over Serial Gateway instance and select the serial interface. The exact menu position can move between firmware releases, but the underlying job remains the same.

You then define the network-facing behaviour: the listening IP, TCP port, permitted server IDs and other serial/gateway timing options exposed by the firmware. Teltonika’s current implementation supports multiple TCP client connections on supported devices, and recent RutOS releases have added further timing and gateway improvements.

There are two common ways to handle the Modbus RTU server ID:

User-defined: the gateway forwards requests to a specified RTU ID.
Obtained from the TCP request: the Unit/Server ID in the Modbus TCP request determines which RTU device is addressed.

The second method becomes particularly useful where several Modbus devices share one RS485 bus. A SCADA system can address different RTU devices through the same gateway rather than creating a separate physical connection for each one.

Do not expose Modbus port 502 to the public internet

This is the point where an otherwise clever installation can become a security problem. Modbus was designed for industrial communication, not as a secure internet-facing remote-access protocol. A working gateway does not mean you should forward TCP port 502 from a public mobile IP straight to a PLC or meter network.

Restrict the gateway to the systems that actually need to reach it. Teltonika provides IP filtering for the Modbus TCP-over-Serial Gateway, and the router also gives you firewall and VPN capabilities.

For remote sites, a much better architecture is usually:

SCADA → encrypted VPN / private routed network → Teltonika → Modbus RTU equipment

That keeps the industrial protocol inside a controlled path. For an example of this wider architecture, see our VPS for SCADA guide.

Security rule

Connectivity and exposure are not the same thing. The objective is to make the field device reachable by authorised systems, not reachable by everybody on the internet.

What if you want the router to collect the data instead?

A transparent TCP-to-RTU bridge is only one way to use Modbus. In many IoT projects you do not want a central SCADA platform continuously polling a serial device across a mobile connection. You may instead want the edge device to poll locally, store or process the readings, then send selected data upstream.

RutOS supports broader Modbus client/server functionality on compatible devices and can use Modbus data with services such as Data to Server and MQTT-related functions. This changes the architecture:

Meter / PLC → local Modbus polling → Teltonika edge device → MQTT / HTTPS / platform

That can reduce WAN chatter and gives you more control over what leaves the site. It also starts to blur the line between router and edge gateway, a theme we explore in our industrial router vs SBC guide.

Troubleshooting: work from the field device outwards

Symptom	Check first
No RTU response	Power, RS485 A/B polarity, server ID, baud rate, parity, stop bits and correct serial interface.
Some devices respond, others do not	Duplicate/wrong IDs, bus wiring, permitted ID range and individual device settings.
Intermittent or corrupt responses	Termination, topology, interference, grounding, timing and serial parameters.
Works locally but not remotely	IP route/VPN, firewall, listening IP, IP filter and TCP port.
TCP connection works but register value is wrong	Register map, zero/one-based addressing, function code, byte/word order and data type.
Remote polling uses too much data	Polling interval and architecture; consider local collection and sending only required values upstream.

The key is to avoid troubleshooting everything at once. Establish the RTU layer, then the gateway, then the LAN/IP path, then the cellular/VPN path, and finally the application.

Register address versus register number: the classic trap

A Modbus manual may describe a value as register 40001 while a client asks for address 0, or it may present the raw offset directly. Different software packages and device manuals use different conventions. A connection can therefore be perfectly healthy while the engineer is simply asking for the wrong location.

If you can communicate with the device but the data is wrong or you receive an illegal-address exception, check whether the documentation and your client are using register numbers or zero-based register addresses. Then check the data representation: 16-bit integer, signed value, 32-bit value, float and word/byte order can all change the apparent result.

A sensible commissioning sequence

Identify the field interface. Confirm RS485/RS232 and the device’s Modbus RTU settings.
Get the register map. Know exactly what you intend to read or write.
Prove local serial communication. Do this before involving cellular connectivity.
Configure the Teltonika serial interface. Match baud, data bits, parity and stop bits.
Create the Modbus TCP-over-Serial Gateway. Define listening interface/port and ID handling.
Restrict access. Use IP filters, firewall rules and preferably a VPN/private network for remote access.
Test from the LAN. Prove TCP-to-RTU translation before testing remotely.
Test through the real WAN path. Use the same VPN/private cellular architecture the live system will use.
Record a known-good request. Device ID, function, register, expected value and response time become your troubleshooting baseline.
Only then optimise polling. Avoid hammering a slow serial bus or wasting cellular data with unnecessarily aggressive polling.

Modbus gateway at a glance

Legacy device: Usually speaks Modbus RTU over RS485 or RS232.
Teltonika role: Bridges the serial Modbus device to a TCP/IP network.
Remote system: SCADA, BMS, PLC software or another Modbus TCP client.
Most common fault: Mismatched serial settings, wrong ID/register or RS485 wiring.
Remote access: Prefer VPN/private routed connectivity rather than exposing Modbus directly to the internet.
Alternative architecture: Poll locally at the edge and publish selected data upstream via MQTT/HTTPS.

The bigger picture: the router becomes part of the control architecture

This is why an industrial cellular router should not be selected purely by download speed. A Cat 4 router with the correct serial interface and protocol support can be far more useful to a plant engineer than a much faster 5G router that cannot physically talk to the equipment in the cabinet.

The gateway is doing something deceptively important: preserving the investment in proven field equipment while making its data available to modern systems.

That is industrial IoT at its most practical. You do not always need to replace the machine. Sometimes you simply need to give it a secure route out of the cabinet.

Frequently asked questions

What is a Teltonika Modbus gateway?

On supported Teltonika devices, Modbus gateway functionality can bridge Modbus TCP requests from an IP network to Modbus RTU equipment connected over a serial interface such as RS485 or RS232.

What is the difference between Modbus TCP and Modbus RTU?

Modbus RTU normally runs over a serial link such as RS485 or RS232. Modbus TCP carries Modbus messages over TCP/IP. A gateway can bridge between the two transports.

Can I connect several Modbus RTU devices to one Teltonika router?

Yes, where the serial bus and field devices are designed accordingly. Multiple RTU devices can have unique server IDs on the same RS485 bus, and the gateway can use the Modbus TCP Unit/Server ID to address the required device.

Should I open TCP port 502 on a public 4G SIM?

Directly exposing Modbus to the public internet is generally a poor security design. Restrict access and use a controlled path such as a VPN or private routed network wherever practical.

Why can I connect but not read the correct register?

Check the device’s register map, function code, server ID, whether the client uses register numbers or zero-based addresses, and the expected data type and byte/word order.

Does every Teltonika router have RS485?

No. Hardware interfaces vary by model. Select a device with the physical serial interface required by the field equipment and verify current RutOS support for the functions you need.

Teltonika Modbus Gateway: Connecting RS485 and RS232 Equipment to IP