Skip to main content

Modules, Boards & Gateways · Hardware

Wireless Gateway / RTU

Coming soon

Connect every LoRa node in the field to SCADA, the cloud and PLCs with a single box.

Request information Specifications
EG-GW-4G gateway: DIN-rail housing with terminals, RJ45, USB-C, SIM, 433 MHz and 4G antennas on top

Overview

The problem. Once wireless nodes are installed in the field, the end that carries data to the control room is rebuilt for every project: a USB converter on a PC, a Raspberry Pi script, a GSM modem and hand-written protocols. This end is the most fragile part on site: it does not restart after a power cut, data is lost when the connection drops, PLC integration needs a separate converter, and updates have to be done on site.

The solution. The Gateway/RTU turns the central end of the Elmes LoRa network into a standard product. The gateway layer forwards LoRa packets to a server over USB-CDC, Ethernet or 4G using a binary/JSON protocol, and to PLC/SCADA over Modbus TCP; the node list, polling interval and alarm acknowledgment are configured on the device. The RTU layer adds local I/O (carrier boards), a time-stamped buffer (no data loss when the link drops), rule-based local logic (threshold → relay, timers) and an RS485 Modbus master. The Edge-AI layer (planned) uses an STM32H7 to detect anomalies in node data on site and sends only events upstream.

Hardware. The device is built by fitting the EM-G0LW-433 module (STM32 + SX1268 + ESP32) onto the EC-GW board of the I/O Carrier Boards family. The RTU version adds local I/O with EC-DIO8 and EC-AIO boards; the 4G version uses the EM-G0C cellular module.

PC + USB converter + scriptRaspberry Pi gatewayCommercial LoRaWAN gatewayElmes Gateway / RTU
Works with Elmes nodesYes (script)YesNo (LoRaWAN)Yes, natively
Power cuts / headless operationWeakFair (SD card risk)GoodGood (MCU, watchdog)
Modbus TCP / MQTTMust be writtenMust be writtenMQTTBuilt in
Local logic / bufferingNoneScriptNoneRTU layer
4GExternal modemExternalOptionModule (EM-G0C)
Price classLow (fragile)LowMedium–highMedium
4G gateway next to a PLC on a DIN rail in a control panel, with RJ45 patch cable and 433 MHz antenna
In use
Gateway / RTU variants: EG-GW-U USB dongle, EG-GW-E, EG-GW-4G, EG-RTU and EG-EDGE
Product family

This product is in development or field testing. Contact us for technical information, pilot use and a preliminary quotation.

Features

  • Three layers on one hardware platform: gateway → RTU → Edge-AI by license and firmware build; same housing and pinout.
  • Elmes node protocol built in: addressing, parameter writes (PARAM_WRITE), broadcast commands, alarm acknowledgment (ACK), status polling.
  • Buffering and retransmission (RTU): lossless time series when the connection drops.
  • Multiple uplinks: USB, Wi-Fi, Ethernet and 4G.
  • Configuration: command-line tool and JSON file import/export.
  • Firesens compatibility: works with the map-based DWIN HMI and PC application of the Wireless Fire Alarm System (Firesens).
  • TargetLocal rule engine (RTU): threshold/timer → relay; local output from a node event (e.g. level → pump).
  • TargetRedundant connectivity: multiple uplinks used as backups for each other.
  • TargetWeb interface: on-device configuration interface running on the ESP32.
  • TargetEdge-AI: anomaly scoring on vibration, meter and level data with an STM32H7, sending only events; predictive maintenance with VibroBal data (Telemetry & Process Intelligence).

Variants

Variants
Model codeLayerModuleUplinkLocal I/OStatusRequest information
EG-GW-UGatewayEM-G0LW-433USB-CDC (PC / Raspberry Pi)—Previous generation in the field (STM32F070 + SX1268, USB)Request information: EG-GW-U
EG-GW-ETargetGatewayEM-G0LW-433Ethernet (EC-GW), Wi-Fi2 DI / 2 DOPlannedRequest information: EG-GW-E
EG-GW-4GTargetGatewayEM-G0LW-433 + EM-G0C4G Cat-1 / NB-IoT + Wi-Fi backup2 DI / 2 DOPlannedRequest information: EG-GW-4G
EG-RTUTargetRTUEM-G0LW-433 + EC-DIO8 / EC-AIO carrier boardsEthernet / 4G8 DI / 8 DO / 4 AI (depending on carrier), RS485PlannedRequest information: EG-RTU
EG-EDGETargetEdge-AI RTUEM-S7L-433 (STM32H7, module series)Ethernet / 4GRTU + on-device modelPlanned (later phase)Request information: EG-EDGE

Specifications

Values marked “Target” are design targets, next-generation values or chip-vendor data; they are updated as measurement and certification are completed.

Current system
Previous-generation hardwareSTM32F070CB + SX1268 radio module, USB-CDC
USB protocolUSB-CDC, binary frame [0x55][cmd][len16][payload][CRC8]
PollingConfigurable interval (JSON configuration); immediate alarm acknowledgment
Host serviceRaspberry Pi service, CSV logging
Radio
Frequency band433.05–434.79 MHz ISM (SX1268)
868 MHz optionSX1262-based 868 MHz versionTarget
Channels8 (200 kHz spacing, 125 kHz BW)
Output power+22 dBm max. (SX1268 datasheet), adjustable
Receiver sensitivity−129 dBm @ SF11/BW125 (datasheet)
Modulation / data rateLoRa SF5–SF12, 0.018–62.5 kbps; (G)FSK
Antenna connectorSMA 50 Ω (on board); 433 MHz antenna (RF antenna series)
Range
Open field≥ 2000 m (SF9, 2 dBi, 2 m)Target
Industrial / indoors≥ 300 mTarget
Communication & security
Packet integrity (previous generation)4-byte address + CRC16
EncryptionAES-128-CCM; NetID + 16-bit addressTarget
Systems on the same siteChannel × NetID; ≥ 8 independent networksTarget
Performance & fail-safe
Number of nodes≥ 100 nodes (depending on the polling interval)Target
Node offline detectionN × polling interval (default N = 3)Target
WatchdogHardware watchdog (IWDG)Target
Interfaces
Ethernet / Wi-FiWi-Fi (ESP32, EM-G0LW-433); Ethernet via the EC-GW boardTarget
4GEM-G0C module (Cat-1 / NB-IoT)Target
ProtocolsModbus RTU (RS485) and Modbus TCP server, MQTT client (JSON), USB binary/JSONTarget
ServiceSWD + UART, USB
Power
Supply9–36 VDC (shared with the EC boards) or USB 5 V (EG-GW-U)
Consumption< 3 W (gateway); < 6 W 4G peakTarget
Inputs / outputs
Local I/OEC-GW: 2 DI / 2 DO; RTU: carrier board chain (8 DI / 8 relays / 4 AI / RS485)Target
Mechanical & environmental
HousingDIN-rail housing, 6 modules wide; IP20Target
Warranty & service
Warranty2 years; service in AnkaraTarget

Applications

  • Fire detection network hub
  • Well/tank and pump telemetry
  • Analog / digital data acquisition
  • Meter reading
  • Irrigation network hub
  • Retrofit telemetry
  • Call system hub
  • Cloud SCADA and predictive maintenance

The Gateway/RTU is the shared central end of Elmes wireless systems:

Compliance & documentation

The Gateway/RTU is under development. Radio compliance is being prepared in stages based on measurements of the fitted module.

  • CE – RED 2014/53/EU and EMC
    In stages, based on module measurements
    Target
  • Product datasheet
    Target
  • External protocol document (USB / Modbus / MQTT)
    Target
  • Installation guide
    Target

Frequently asked questions

Is it LoRaWAN?

No. It uses the proprietary LoRa protocol of Elmes nodes (433 MHz ISM). A LoRaWAN bridge is not on the roadmap.

How many nodes can one gateway handle?

A 24-device network runs in the field on the previous-generation gateway; the target is 100 or more nodes, depending on the polling interval.

How does it talk to a PLC?

Through a Modbus TCP (Ethernet/Wi-Fi) or Modbus RTU (RS485) register map.

Is data lost when the internet connection drops?

In the RTU layer, data is buffered and sent once the connection is back; in the gateway layer, this is the upstream system's responsibility.

What happens to my existing Raspberry Pi setup?

The same USB protocol is kept; the Pi service also works with the new device and will later move onto the device itself.

What is needed for 4G?

The 4G module (EM-G0C), an antenna and a SIM card; MQTT and Modbus TCP work the same way.

When will Edge-AI be available?

It is a planned layer that will come in a later phase with the STM32H7-based EM-S7L-433 module (Elmes Module Series).

Get information about this product

Our engineering team replies within 24 hours.

Request information +90 (312) 395 85 86

Related products