INDUSTRIAL NETWORKING

Industrial gateways for field-device and IP integration.

Connect PLCs, meters, sensors and legacy equipment to Ethernet or cellular infrastructure — interface and protocol requirements assessed per project, not assumed portfolio-wide.

  • Field interfaces first
  • Protocol-aware selection
  • Cable and connection coordination
Industrial gateway connectivity concept

SELECT BY REQUIREMENT

Filter gateways by interface and uplink.

Browse productsResults: 15

TELTONIKA PRODUCT PORTFOLIO

15 current gateway models

Industrial gateways selected around interfaces, connectivity and application

CURRENT GATEWAYS

Compare verified differences

Match uplink, Ethernet, field interfaces and cellular options to the filtered gateway range.

AttributeNTP001CurrentTRB140CurrentTRB141CurrentTRB142CurrentTRB143CurrentTRB145CurrentTRB160CurrentTRB236CurrentTRB245CurrentTRB246CurrentTRB247CurrentTRB255CurrentTRB256CurrentTRB500CurrentTRB501Current
UplinkEthernet4G LTE Cat 44G LTE Cat 14G LTE Cat 14G LTE4G LTE Cat 14G LTE Cat 6LTE 4504G LTE Cat 44G LTELTE Cat 1 bisCat 1 / NB-IoTNB-IoT / LTE5G5G
EthernetYes1 × GbE————GbEYesYesYes—YesYes—2.5 GbE
RS232Yes—VariantYes———YesYesYesYesYesYes——
RS485Yes—Variant——Yes—YesYesYesYesYesYes——
M-Bus————Yes——————————
I/OYes—Yes————YesYesYesYesYes———
Cellular—LTE Cat 4LTE Cat 1LTE Cat 14G LTELTE Cat 1LTE Cat 6LTE 450LTE Cat 44G LTECat 1 bisCat 1 / NB-IoTNB-IoT5G5G
RMS—OptionalOptionalOptionalOptionalOptionalOptionalOptionalOptionalOptionalOptionalOptionalOptionalOptionalOptional

Uplink

NTP001Current
Ethernet
TRB140Current
4G LTE Cat 4
TRB141Current
4G LTE Cat 1
TRB142Current
4G LTE Cat 1
TRB143Current
4G LTE
TRB145Current
4G LTE Cat 1
TRB160Current
4G LTE Cat 6
TRB236Current
LTE 450
TRB245Current
4G LTE Cat 4
TRB246Current
4G LTE
TRB247Current
LTE Cat 1 bis
TRB255Current
Cat 1 / NB-IoT
TRB256Current
NB-IoT / LTE
TRB500Current
5G
TRB501Current
5G

Ethernet

NTP001Current
Yes
TRB140Current
1 × GbE
TRB141Current
—
TRB142Current
—
TRB143Current
—
TRB145Current
—
TRB160Current
GbE
TRB236Current
Yes
TRB245Current
Yes
TRB246Current
Yes
TRB247Current
—
TRB255Current
Yes
TRB256Current
Yes
TRB500Current
—
TRB501Current
2.5 GbE

RS232

NTP001Current
Yes
TRB140Current
—
TRB141Current
Variant
TRB142Current
Yes
TRB143Current
—
TRB145Current
—
TRB160Current
—
TRB236Current
Yes
TRB245Current
Yes
TRB246Current
Yes
TRB247Current
Yes
TRB255Current
Yes
TRB256Current
Yes
TRB500Current
—
TRB501Current
—

RS485

NTP001Current
Yes
TRB140Current
—
TRB141Current
Variant
TRB142Current
—
TRB143Current
—
TRB145Current
Yes
TRB160Current
—
TRB236Current
Yes
TRB245Current
Yes
TRB246Current
Yes
TRB247Current
Yes
TRB255Current
Yes
TRB256Current
Yes
TRB500Current
—
TRB501Current
—

M-Bus

NTP001Current
—
TRB140Current
—
TRB141Current
—
TRB142Current
—
TRB143Current
Yes
TRB145Current
—
TRB160Current
—
TRB236Current
—
TRB245Current
—
TRB246Current
—
TRB247Current
—
TRB255Current
—
TRB256Current
—
TRB500Current
—
TRB501Current
—

I/O

NTP001Current
Yes
TRB140Current
—
TRB141Current
Yes
TRB142Current
—
TRB143Current
—
TRB145Current
—
TRB160Current
—
TRB236Current
Yes
TRB245Current
Yes
TRB246Current
Yes
TRB247Current
Yes
TRB255Current
Yes
TRB256Current
—
TRB500Current
—
TRB501Current
—

Cellular

NTP001Current
—
TRB140Current
LTE Cat 4
TRB141Current
LTE Cat 1
TRB142Current
LTE Cat 1
TRB143Current
4G LTE
TRB145Current
LTE Cat 1
TRB160Current
LTE Cat 6
TRB236Current
LTE 450
TRB245Current
LTE Cat 4
TRB246Current
4G LTE
TRB247Current
Cat 1 bis
TRB255Current
Cat 1 / NB-IoT
TRB256Current
NB-IoT
TRB500Current
5G
TRB501Current
5G

RMS

NTP001Current
—
TRB140Current
Optional
TRB141Current
Optional
TRB142Current
Optional
TRB143Current
Optional
TRB145Current
Optional
TRB160Current
Optional
TRB236Current
Optional
TRB245Current
Optional
TRB246Current
Optional
TRB247Current
Optional
TRB255Current
Optional
TRB256Current
Optional
TRB500Current
Optional
TRB501Current
Optional

ENGINEERING

Engineering selection guide

Gateway selection starts with field interfaces, protocol requirements and the upstream connection — assessed per target device, not assumed portfolio-wide.

SIGNAL PATH

Field signal to supervisory layer

  1. Field devicePLC / meter / sensorIndustrial equipment
  2. Field interfaceRS232 · RS485 · M-BusField-side connectivity
  3. GatewayGatewayProtocol / network boundary
  4. UplinkIP / cellularUpstream connectivity
  5. SupervisorySCADA / telemetryMonitoring / control layer

KEY FIELD INTERFACES

Field interfaces in project-selection terms.

Interface availability differs by gateway model. Confirm the required interface against the target device.

  • Ethernet
    IP-native devices and upstream switching
  • RS232 / RS485
    Serial field equipment and buses
  • M-Bus
    Metering and utility interfaces where supported
  • Digital I/O
    Discrete signals — device-dependent

PROTOCOL SUPPORT

Documented protocol support varies by device.

Never assume a protocol is available on all gateway models. Confirm against official documentation for the target device.

  • Modbus RTU/TCPwhere documented
  • MQTTfor telemetry integrations
  • OPC UAon selected devices
  • BACnet, DNP3, DLMSfamily- and firmware-dependent

TYPICAL APPLICATIONS

Where gateway selection is assessed.

Gateway selection depends on the application, field interfaces, upstream connectivity and environment.

  • Smart metering and utility telemetry
  • Machine and PLC serial integration
  • Building and industrial infrastructure
  • Remote asset monitoring

ENGINEERING DISTINCTION

Gateway vs router — complementary roles.

Router

Industrial routers prioritise IP routing, WAN connectivity (Ethernet/cellular) and network resilience between sites and devices.

Gateway

Industrial gateways prioritise field interfaces, protocol handling and data-path integration between legacy equipment and IP/cellular networks.

Some devices combine routing and gateway functions. Selection depends on required interfaces, protocols, port count and topology — not the product label alone.

CONNECTION LAYER

Gateways sit between field wiring and IP infrastructure.

Serial shielding, Ethernet drops, fibre backhaul and power affect gateway projects as much as protocol configuration.

  • Serial and control cable routing
  • Industrial Ethernet to upstream switches
  • Fibre where distance or EMC architecture requires it
  • Connector, surge and cabinet practices

Technical FAQ

Direct answers on selection and scope — without marketing promises.

When do I need RS485 rather than Ethernet?

When field devices only expose serial buses or legacy protocols on RS485/RS232. A gateway translates between those interfaces and IP/cellular uplinks — if devices are already Ethernet-native, a switch or router may suffice.

Can a gateway connect Modbus equipment to MQTT?

Selected Teltonika gateway families document Modbus and MQTT capabilities — confirm per model and firmware. GermanSTS assesses suitability per project; it is not a guaranteed portfolio-wide feature.

Can GermanSTS assess gateway and cable requirements together?

Yes — serial, control and Ethernet cabling can be reviewed alongside gateway interface requirements within the same project enquiry.

Gateway capabilities refer to documented Teltonika Networks devices. GermanSTS does not manufacture gateways or RutOS.

ENQUIRY

Send structured gateway requirements.

Use the Industrial Networking & IoT category in the cable enquiry form.

  • Application
  • Interfaces
  • Ports
  • Environment
  • Quantity
  • Timing