Final configuration is confirmed in the quotation.
Edge IoT Gateway
DIN-rail gateway for collecting Modbus data from RS485 / RS232 devices and sending it to MQTT, Modbus or OPC UA systems over Ethernet, optional 4G or Wi-Fi.
Start with the information you have. Exact model, interface and certificates are confirmed in writing before order.
Image details
Representative industrial gateway family visual derived from a reviewed supplier-family reference and independently de-identified. It is not the final ordered-model photograph; serial-port count, network option, enclosure details, connectors and certificates are confirmed in the quotation.
Related solution: Equipment Monitoring
Where the hardware sits in the monitoring path
A planning view, not a fixed bundle. Signal type, protocol, power, network and the customer endpoint are confirmed before quotation.
Customer system
SCADA, BMS or customer-owned platform
Specifications
- 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
How the model is selected
The written quotation ties the site requirement to one reviewed hardware configuration.
Site requirement
Application, medium, mounting and environment
Hardware configuration
Signal, protocol, power and enclosure
Quote confirmation
Model, quantity, certificates and delivery
Machine monitoring context
Representative site context. Sensors, interfaces, enclosure, power and mounting are confirmed against the actual project before quotation.
What the reviewed outage queue does — and does not do
Use these limits when the project depends on data recovery after a network interruption.
- The queue must be enabled and works only with the supplier-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 reviewed selection notes
Model-selection reference
Industrial Monitoring Hardware Catalog
Use this audited section to compare available hardware configurations. The representative website image is not an exact model photograph; the ordered configuration is confirmed in the quotation.
- Catalog section
- Industrial and modular edge gateways
- SG-coded options
- 6
- PDF pages
- 27
Continue product selection
Compare adjacent hardware families for the same monitoring path. The final combination is checked against the project I/O, protocol, power and enclosure requirements.
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 supplier-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 reviewed supplier-format 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
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 reviewed 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 reviewed volatile MQTT queue for defined network-outage cases
What to include in your quote request
- Connected devices, serial settings, register maps, point count and polling interval
- Required 2-port or 6-port capacity and any need to separate different serial settings
- Ethernet, 4G or Wi-Fi backhaul plus target country / mobile-network details
- MQTT, Modbus or OPC UA role, broker / SCADA endpoint, payload and authentication
- Outage duration, power-loss retention requirement, timestamp / replay acceptance criteria and data-loss alarm
- DC power, mounting space, antenna location, quantity, certificates and project stage
Related selection guides
Related resources
Frequently asked questions
Does this gateway support store-and-forward?
It supports a reviewed MQTT outage queue for the supplier-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 reviewed gateway when power-loss retention is required.
Which MQTT formats support outage replay?
The reviewed replay function is limited to the supplier-format MQTT template. Custom JSON and Sparkplug B do not use the same queue, and OPC UA does not provide equivalent historical replay.
Does replay preserve the original sampling timestamp?
That behavior has not been verified. Projects that depend on original timestamps, strict replay order or end-to-end completeness need a written acceptance test before purchase.
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.
Does OPC UA provide historical replay?
No reviewed OPC UA historical replay is available for this family. OPC UA is provided as a server role on supported models; use the MQTT supplier-format queue or specify another logging path when historical recovery is required.
What should I provide when requesting a quote for the Edge IoT Gateway?
Connected devices, serial settings, register maps, point count and polling interval; Required 2-port or 6-port capacity and any need to separate different serial settings; Ethernet, 4G or Wi-Fi backhaul plus target country / mobile-network details; MQTT, Modbus or OPC UA role, broker / SCADA endpoint, payload and authentication
Where can I compare available model options?
Open the Industrial Monitoring Hardware Catalog linked on this page. It lists audited SG-coded selections; the ordered configuration is confirmed in the quotation.
Will it work with my existing system?
Compatibility is reviewed against your field signals, protocols and upstream platform. Typical pairings include Modbus RTU devices using RS485 or RS232, Ethernet networks and optional 4G or Wi-Fi uplinks, MQTT brokers using the reviewed supplier-format template.