Skip to content
SunGeneAgricultural IoT
← All products
Edge IoT Gateway: Measurement point → Available output → Logger or gateway → Customer system.

Edge IoT Gateway — connection diagram.

Edge IoT Gateway

Equipment options & specifications

DIN-rail gateway for collecting Modbus data from farm RS485 / RS232 devices and sending it to MQTT, Modbus or OPC UA systems over Ethernet, optional 4G or Wi-Fi.

Related application hardware: Farm pump & energy monitoring

Farm equipment configurations

Connect existing farm instruments to your monitoring platform

Keep the soil probes, weather instruments and water meters that already work. Choose a gateway by the instruments it must read and the format your receiving system accepts.

Farm data path: RS485 instruments connect to a gateway; the gateway sends readings to the receiving platform. Connection illustration.
Farm data path: RS485 instruments connect to a gateway; the gateway sends readings to the receiving platform. Connection illustration.

Collect readings from a few instruments

A two-port gateway separates devices with different serial settings. Include the register maps and the readings you need.

Bring several farm zones together

A six-port gateway provides more serial branches. Choose it by the number of devices, configured points and required polling interval.

Connect to an existing farm system

Select MQTT for broker delivery, Modbus for a compatible controller, or an OPC UA server for a compatible client. The receiving protocol determines the gateway version.

Compare configurations

Open an equipment type to compare its configurations. The quotation identifies the complete device, interfaces and accessories.

Sensor gateways5 configurations

Two-port Modbus to MQTT gateway

Soil, weather or farm-water instruments sending readings to an MQTT broker.

Request this configuration →

Equipment: 2 RS485/RS232 ports; Ethernet; optional 4G or Wi-Fi.

Include with your request: Device addresses, baud rates, register maps and MQTT message fields.

Six-port Modbus to MQTT gateway

Separate serial branches for several growing areas or equipment groups.

Request this configuration →

Equipment: 6 RS485/RS232 ports; Ethernet; optional 4G or Wi-Fi.

Include with your request: Branch layout, device count, configured points and polling interval.

Two-port multi-protocol gateway

Existing farm controls that need MQTT, Modbus or an OPC UA server connection.

Request this configuration →

Equipment: 2 RS485/RS232 ports; MQTT, Modbus RTU/TCP and OPC UA server roles by configuration.

Include with your request: The required protocol role and the existing controller or platform.

Six-port multi-protocol gateway

Larger instrument groups with different serial settings.

Request this configuration →

Equipment: 6 RS485/RS232 ports; MQTT, Modbus RTU/TCP and OPC UA server roles by configuration.

Include with your request: Serial settings for each branch and the receiving-system interface.

Gateway with Node-RED

Read instruments, scale values and build the agreed data flow to a farm platform.

Request this configuration →

Equipment: Pre-installed Node-RED; Modbus RTU/TCP, MQTT, HTTP and OPC UA connectivity.

Include with your request: Required nodes, flow configuration, payload and software integration scope.

Protocol converters4 configurations

Modbus RTU to TCP gateway

Keep serial farm instruments on a Modbus TCP network.

Request this configuration →

Equipment: Modbus RTU / Modbus TCP to Modbus TCP conversion.

Include with your request: Serial settings, register layout and the network controller.

Modbus to OPC UA gateway

Present instrument readings to an OPC UA client.

Request this configuration →

Equipment: Modbus RTU/TCP input with OPC UA server output.

Include with your request: Client requirements, register maps and node mapping.

Modbus to Wi-Fi converter

Connect a serial instrument group to an available Wi-Fi network.

Request this configuration →

Equipment: Modbus to Wi-Fi communication configuration.

Include with your request: Instrument protocol, site Wi-Fi, power and installation.

PLC to MQTT gateway

Read an existing farm PLC into a receiving MQTT system.

Request this configuration →

Equipment: PLC protocol collection and MQTT data delivery.

Include with your request: PLC make, exact controller, available driver and required data addresses.

  • For the two- and six-port fixed-function gateways, the native-format MQTT outage queue uses RAM. It is lost after power loss or restart; it is not a permanent data logger.
  • Gateway connectivity, sensor power and the outdoor enclosure are separate selections.

Where this equipment fits

SG-RTU-145: Water Level Telemetry Terminal
Pictured: SG-RTU-145 — Water Level Telemetry Terminal.

Bring existing farm equipment into one record

Connect compatible field signals to the selected collector. Start with the sensors and controller already on site, then agree units, timestamps and the destination for each reading.

Connect remote irrigation and weather points

Farm teams can use the same collection approach for remote irrigation and weather points. The required interfaces, power, network and buffering behavior must match the selected device.

Specifications & version options

Serial options
2 or 6 RS485 / RS232 ports
Ethernet
1 × WAN + 1 × LAN, 10/100 Mbps
Data capacity
2-port: up to 10 devices / 512 points; 6-port: up to 50 devices / 4,000 points
Uplink protocols
Model-dependent MQTT, Modbus TCP / RTU and OPC UA server
Network options
Ethernet standard; 4G or Wi-Fi by selected configuration
Power supply
9–36 VDC with reverse-polarity protection
Show 4 more specification rows

Equipment quotation

The quotation lists the selected equipment, accessories, price and delivery terms.

Purchasing and delivery details →

Documents and downloads

Selection guidance and application documents. Wiring, register maps and certificates must match the chosen model and version.

Open family selection sheet

English · Web page · printable
Online selection guide

View application guide (PDF)

Application selection guide
PDF · English

Model-specific documents

Tell us which wiring, protocol or calibration documents you need for the equipment.

On this page
Application guide and product-family selection sheet
For your configuration
  • Exact-model datasheet
  • Wiring / pinout
  • Register map, protocol or sample data
  • Model-specific certificates
  • Calibration and measurement evidence
  • Dimensions / installation drawing
Project starter files →
Request an engineering package →
From a product family to your order
  1. Family page

    Compare uses, interfaces and configuration options. These are selection references.

  2. Equipment configuration

    Define the required function, interfaces, power, mounting and accessories for the site.

  3. Written quotation

    Confirm the exact model, configuration, photograph, document revisions, accessories, price, delivery and warranty.

Get selection help

Tell us what you want to measure and where. Send a model number or site photo if you have one.

Text stays in this tab for up to 30 minutes while you browse. Saving across reloads is optional below.

A personal email is welcome.

A country and general site description are enough. If the location is undecided, say so.

Photos, model information or BOM (optional)

Up to 5 files, 10 MB each. PDF, JPG, PNG, WebP, CSV, TXT, DOCX or XLSX.

By submitting this form, you acknowledge the privacy notice.

See where the system fits

Equipment in the system

Example equipment arrangement. Check compatibility and agree who handles software, PLC/SCADA programming and site installation.

Existing field equipment

Confirm the device signals, electrical interface and register map before selecting the gateway.

Data destination

Customer platform or an agreed third-party service

SG-VIB-114: Industrial Accelerometer for Vibration Monitoring

Product photograph

Pictured: SG-VIB-114 — Industrial Accelerometer for Vibration Monitoring.

MQTT buffering during network outages

Use these limits when the project depends on data recovery after a network interruption.

  • The queue must be enabled and works only with the native-format MQTT template.
  • It holds up to 100,000 data points in RAM. Queued data is lost if the gateway loses power or restarts.
  • When the limit is reached, the oldest queued data is deleted.
Show 3 more selection notes

Continue product selection

Compare related equipment and connection options.

How to choose

  • List every RS485 / RS232 device, register map, baud rate, parity setting and required refresh interval before choosing the serial-port count.
  • Use the 2-port version for up to 10 devices / 512 points or the 6-port version for up to 50 devices / 4,000 points, then verify the actual polling workload.
  • Choose Ethernet, 4G or Wi-Fi and define the required MQTT, Modbus TCP / RTU or OPC UA role. Protocol availability is model-dependent.
  • If network-outage recovery matters, decide whether a volatile native-format MQTT queue is sufficient. It does not survive power loss or restart and does not cover custom JSON, Sparkplug B or OPC UA history.
Show 2 more selection checks

Compatible with

  • Modbus RTU devices using RS485 or RS232
  • Ethernet networks and optional 4G or Wi-Fi uplinks
  • MQTT brokers using the native MQTT payload template
  • Modbus TCP / RTU and OPC UA systems, subject to the selected model and protocol role

Typical package

  • Selected 2-port or 6-port gateway
  • 9–36 VDC power, Ethernet patching and antenna accessories for 4G / Wi-Fi versions
  • Serial wiring plan and device register maps
  • MQTT topic, payload and security settings plus an outage-recovery acceptance test when buffering is required

Applications

SG-RTU-157: Industrial Telemetry Remote Terminal Unit

Product photograph. Pictured: SG-RTU-157 — Industrial Telemetry Remote Terminal Unit.

Use this family when several Modbus devices need one DIN-rail gateway for Ethernet, optional 4G or Wi-Fi backhaul. It can collect serial data and hand it to MQTT, Modbus or OPC UA systems. The MQTT outage queue is useful for short network interruptions, but it is not nonvolatile storage.

  • Aggregate Modbus devices across 2 or 6 serial ports
  • Send field data over Ethernet, optional 4G or Wi-Fi
  • Publish selected values to MQTT or expose supported Modbus / OPC UA roles
  • Use the volatile MQTT queue for defined network-outage cases
See related application hardware

Related selection guides

Related resources

Frequently asked questions

Does this gateway support store-and-forward?

It supports an MQTT outage queue for the native-format template. The queue can retain up to 100,000 data points while the network is unavailable, but it is RAM-based rather than nonvolatile storage.

Does queued data survive a power loss or restart?

No. Queued data is held in RAM and is lost if the gateway loses power or restarts. Use external nonvolatile logging or a different gateway with confirmed storage when power-loss retention is required.

Which MQTT formats support outage replay?

The replay function is limited to the native-format MQTT template. Custom JSON and Sparkplug B do not use the same queue, and OPC UA does not provide equivalent historical replay.

What should be specified for outage-data acceptance?

State the required sampling timestamps, replay order and completeness checks in the equipment request and commissioning test.

How do I choose between the 2-port and 6-port versions?

The 2-port version supports up to 10 devices and 512 points. The 6-port version supports up to 50 devices and 4,000 points. The final choice also depends on baud rates, register counts, polling interval, retries and whether devices need separate serial settings.

How should historical recovery be configured?

For historical recovery, select the MQTT native-format queue or a separate logging path. OPC UA is available as a server role on supported models.

Can I keep my existing farm sensors?

Yes, when the sensor interface and protocol match the selected gateway. For RS485 Modbus instruments, provide the register map, address, baud rate and required readings.

Do I need a gateway or a permanent data logger?

Use a gateway to collect and forward readings. The native-format MQTT queue in the fixed-function two- and six-port gateways is held in RAM and is lost on power loss or restart. Select a separate nonvolatile logging path when records must survive loss of power.

Will it work with my existing system?

Use the listed inputs, power and protocol to match the device to your controller. Send its model or an input photo with the equipment request.