INDEX
STG Series WMBus Gateways are designed for industrial-grade Radio Frequency (RF) communication. STG Series WMBus Gateways are tailored to perform various features such as wide temperature range, wide power input range and several connectivity ports. Thus, STG Series WMBus Gateways are the best choice for smart metering, power utility, telecommunication and all other applications that require industrial Wireless MBus Radio Frequency connectivity.
STG Series which have REDZ Broadband Power Line (BPL) link allows devices to communicate with full transparent TCP/IP standard over Low Voltage power lines and allows easy connection between TCP/IP based terminals without use of extra cables.
STG Series WMBus Gateways can create a WMBus RF network and connect Serial and/or ETH based devices with Wireless MBus devices. All communication can be done over Radio Frequency network based on WMBus standard. STG Series WMBus Gateways can operate in 3 main modes: Transparent Mode, WMBus OMS Converter to Modbus RTU packages, WMBus OMS Converter to Modbus TCP packages. STG Series WMBus Gateways can act as TCP to WMBus Gateway as TCP Server, TCP to WMBus Gateway as TCP Client or Serial to WMBus Gateway all in one device. Typical applications: Automated Meter reading, Home – Building – Industrial Automation, Wireless Sensors, Telemetry…
STG Series WMBus Gateways have the versions with and without BPL (Broadband Power Line) Link.
Each device has a Din-Rail kit on rear panel. The Din-Rail kit helps device to fix on the Din-Rail. Slant the switch and mount the metal spring to Din-Rail.
Then Push the switch toward the Din-Rail until you heard a “click” sound.
Standard SMA female Antenna interface, 50 ohm.
Micro USB Console port for LOG in 115200 baud.
Console Tx and Rx Blinks when data transmission occurs.
WMBus Activity LEDs
ALIVE: Keeps ON during normal operation.
WMBus Tx and Rx Blinks when data transmission occurs.
Device Status LEDs
STATUS: Blinks based on device operation.
- When TCP line used blinks during no connection and keeps ON after TCP connection.
- When Serial line used keeps ON.
Device Tx and Rx Blinks when data transmission occurs.
SERVER: Keeps ON after selecting Server from REDZ special design, plug and play Server-Client Operating Modes. Keeps OFF if Client operating Mode selected.
ETHERNET Activity LEDs for port 1, 2 and STG device itself. Blinks during ethernet activity.
5 pin Terminal Block
RS232: Tx, Rx and GND pins
RS485: A, B and GND pins
Can be activated over web interface and baud rate/data type configurable.
10/100Base-T(X) Ethernet ports
Standard SMA female Antenna interface, 50 ohm.
Micro USB Console port for LOG in 115200 baud.
Console Tx and Rx Blinks when data transmission occurs.
WMBus Activity LEDs
ALIVE: Keeps ON during normal operation.
WMBus Tx and Rx Blinks when data transmission occurs.
Device Status LEDs
STATUS: Blinks based on device operation.
- When TCP line used blinks during no connection and keeps ON after TCP connection.
- When Serial line used keeps ON.
Device Tx and Rx Blinks when data transmission occurs.
SERVER: Keeps ON after selecting Server from REDZ special design, plug and play Server-Client Operating Modes. Keeps OFF if Client operating Mode selected.
ETHERNET Activity LEDs for port 1, 2 and STG device itself. Blinks during ethernet activity.
5 pin Terminal Block for Serial Line
RS232: Tx, Rx and GND pins
RS485: A, B and GND pins
Can be activated over web interface and baud rate/data type configurable
7. BPL Status LEDs
ACTIVITY: Blinks during BPL Ethernet activity
LINK: LED Turns ON if the link can be established over BPL
MASTER INDICATION: LED Turns ON if the device is configured and powered as “BPL Master” device
8. 10/100Base-T(X) Ethernet ports
1. Power Input DC: 5-60V DC. Polarity protected so that the power input can be connected in any direction.
2. Power LED: Turns ON when there is power in device.
3. Reset Buttons
RESET TO SERVER: Resets the device to factory setting as Server from REDZ special design, plug and play.
Server-Client Operating Modes
RESET TO CLIENT: Resets the device to factory setting as Client from REDZ special design, plug and play.
Server-Client Operating Modes
Rest can be done at any time by pushing any of the button for 5 seconds.ce to factory setting as Client from REDZ special design, plug and play Server-Client Operating ModesRest can be done at any time by pushing any of the button for 5 seconds.
1. Power Input AC: 90 - 265V AC (100 – 370V DC), 47Hz to 63Hz AC input
2. Power LED: Turns ON when there is power in device.
3. Reset Buttons
RESET TO SERVER: Resets the device to factory setting as Server from REDZ special design, plug and play Server-Client Operating Modes.
RESET TO CLIENT: Resets the device to factory setting as Client from REDZ special design, plug and play Server-Client Operating Modes.
Reset can be done at any time by pushing any of the button for 5 seconds.
1. Power Input AC: 3 phase input, 110V–240V/50-60Hz. It is also ok to connect only single phase to the device such as L1-N connection only.
AC Power supply use L1-N only. Phase 2-3 connections are used to BPL signal transmission.
Best range can be achieved when minimum 2 phases are connected.
2. Power LED: Turns ON when there is power in device.
3. Reset Buttons
RESET TO SERVER: Resets the device to factory setting as Server from REDZ special design, plug and play Server-Client Operating Modes.
RESET TO CLIENT: Resets the device to factory setting as Client from REDZ special design, plug and play Server-Client Operating Modes.
Rest can be done at any time by pushing any of the button for 5 seconds.
STG Series WMBus Gateways have standard Ethernet ports. According to the link type, the switches use CAT 3, 4, 5, 5e UTP cables to connect to any other network device (PCs, servers, switches, routers, or hubs).
| Cable | Type | Max. Length | Connector |
| 10BASE-T | Cat. 3, 4, 5 100-ohm | UTP 100 m (328 ft) | RJ-45 |
| 100BASE-TX | Cat. 5 100-ohm UTP | UTP 100 m (328 ft) | RJ-45 |
With 100BASE-TX/10BASE-T cable, pins 1 - 2 are used for transmitting data and pins 3 - 6 are used for receiving data.
| Pin Number | Description |
| 1 | TD+ |
| 2 | TD- |
| 3 | RD+ |
| 4 | Not Used |
| 5 | Not Used |
| 6 | RD- |
| 7 | Not Used |
| 8 | Not Used |
| CAT5 Based System | BPL Link Based System | |
| Media | CAT5 | Power Line |
| Bandwidth | 100Mbps | Up to 30Mbps |
| Re-Wire | Yes | No, Using existing Power Line |
| Span | <100m | <600m |
| Multiple Nodes | N/A | Up to 10 hops/1000 nodes |
| Encryption | Yes, but difficult to configure | Yes, Plug & Play |
| Installment | Difficult | Easy, simply user power line |
| Installment Cost | High | Low |
| Total Cost | High | Low |
STG Series WMBus Gateways have 1 x RS232 and 1 xRS485 port. Serial line can be connected other serial devices such as RTUs, PLCs, energy meters or any other field device.
| Pin Number | Description |
| 1 | GND |
| 2 | Rx |
| 3 | Tx |
| Pin Number | Description |
| 1 | A |
| 2 | B |
| 3 | GND (Suggested to use) |
Some of the usage scenarios of STG Series WMBus Gateways are described below. Usages are not limited to that examples and user may create their own usage scenario.
STG Series WMBus Gateways can receive WMBus packages and send them to remote or local server over TCP/IP link. This way WMBus packages of many meters can directly be collected on a remote or local Data Server and that data can be used for other applications.
STG act as TCP Client to WMBus Gateway configured in Client Mode, Server device listening the connections and its IP and port must be configured in STG. WMBus configured to operate in Other Mode to listen WMBus packages and all received WMBus packages from the field devices will be transferred to remote server.
STG Series WMBus Gateways can receive WMBUS packages and send them to remote or local clients over TCP/IP link. STG can act as server and up to 20 clients can connect. This way WMBus packages of meters can directly be shared with local or remote devices such as in-home displays.
STG act as TCP Server to WMBus Gateway configured in Server Mode. Field devices can connect to STG device and send WMBus packages. WMBus configured to operate in Meter Mode to send WMBus packages and all received WMBus packages from the connected devices will be transferred field WMBus devices over air.
STG Series WMBus Gateways can receive WMBUS packages and send them to remote or local clients over TCP/IP link. STG can act as server and up to 20 clients can connect. This way WMBus packages of meters can directly be shared with local or remote devices such as in-home displays.
STG can act as client and can regenerate the WMBus received over TCP/IP line. STG server can receive WMBus packages and send to STG client over TCP/IP network and WMBus packages can be regenerated on STG client side. This way WMBus range can be extended over TCP/IP network.
STG Series WMBus Gateways can receive WMBUS packages and send them to local serial devices over RS232 or RS485 serial connection. This way WMBus packages of many meters can directly be shared with local serial devices and that data can be used for other applications.
STG act as Serial to WMBus Gateway configured in Server Mode and listens WMBus packages. WMBus configured to operate in Other Mode to listen WMBus packages and all received WMBus packages from the field WMBus devices will be transferred to field serial devices.
STG Series WMBus Gateways can receive WMBUS messages from local serial devices over RS232 or RS485 serial connection and generate WMBus package based on that messages. This way WMBus packages for WMBus devices can directly be generated by local serial devices over RS232 or RS485.
STG act as Serial to WMBus Gateway configured in Client Mode and listens serial packages. WMBus configured to operate in Meter Mode to be able to send WMBus packages and all received WMBus packages from the field serial devices will be transferred to field WMBus devices.
NOTE: Generated message must be encapsulated in HCI protocol.
HCI protocol:
SOF (Start of Frame): 0xA5
Message Header Field:
Control Field: User may use 0x0 for this part to ignore CRC16 attachment at end
Endpoint ID: It is 0x2
Message ID Field: It is 0x01 for sending data
Length Field: It is the payload length which means data size of framed WMBus package
Example WMBus Message:
| Frame in Hex | Frame in ASCII |
| 0E 06 23 12 67 45 23 01 01 01 80 54 65 73 74 |
..#.gE#...€Te st |
Example encapsulated WMBus Message with HCI protocol:
| Frame in Hex | Frame in ASCII |
| A5 02 01 0E 06 23 12 67 45 23 01 01 01 80 54 65 73 74 |
¥‚...#.gE#...€Te st |
STG Series WMBus Gateways can receive WMBus OMS packages and convert them to Modbus RTU packages. This way WMBus packages of many meters can directly be collected on a remote or local Data Server or RTU device as Modbus registers and can be used for other applications.
STG set in Client mode and Device function set as WMBus – Modbus RTU Gateway. Manufacturing IDs of field devices can be listed with related Modbus addresses. If needed decryption list can be set and White list can be enabled. Received WMBus OMS messages will be converted to Modbus Registers and field or remote Modbus RTU devices can query that data from related Modbus addresses.
STG Series WMBus Gateways can receive WMBus OMS packages and convert them to Modbus TCP packages. This way WMBus packages of many meters can directly be collected on a remote or local Data Server or RTU device as Modbus registers and can be used for other applications.
STG set in Server mode and Device function set as WMBus – Modbus TCP Gateway. Manufacturing IDs of field devices can be listed with related Modbus addresses. If needed decryption list can be set and White list can be enabled. Received WMBus OMS messages will be converted to Modbus Registers and field or remote Modbus RTU devices can query that data from related Modbus addresses.
STG Series WMBus Gateways can be configured over web interface.
Device will get IP from DHCP client when connected to a network. User can use discovery tool to see IP of the device.
Once the IP of the device is set, user may login the device by simply typing the Ip address of device.
NOTE 1: STG default firmware runs with DHCP off and expects an IP lease. If user need static IP or prefers DHCP on during start up, additional firmware is available.
NOTE 2: If there is no DHCP server in LAN, REDZ device will get default 192.168.1.1 IP if it is set as Server Mode. It will get default 192.168.1.100 IP if it is set as Client mode.
Simply write IP of the device to the http client. Google Chrome is suggested to use. Login screen will pop up.
Default user name: admin
Default password: admin
Main screen of device will appear with following information:
From this menu user may select the operating mode and device function of the device. STG has 3 Main Device Function:
1. Transparent Mode ( Sends/Receive WMBus Packages to/from TCP/IP or Serial Side)
2. WMBus OMS to Modbus RTU Converter
3. WMBus OMS to Modbus TCP Converter
“Device ID” field is used to identify device with unique ID number which is also matched with WMBus module of the device.
“Device Name” field is used to identify device and also used during REDZ special design, plug and play Server-Client Operating Modes.
If Device Function is set as WMBus – Modbus TCP Gateway or WMBus – Modbus RTU Gateway, following settings will be shown.
Users may enter Modbus Address that they want to use with field device in this List. They can match the Modbus Address with field WMBus device Manufacturing ID and they can enable the entry they use.
Once the setting has been changed, “Save Configuration” button will be enabled.
After clicking button system will tell if the settings applied successfully or not.
NOTE 1: STG Series WMBus Gateways can keep configuration of 2 different modes in its memory and once the configuration enabled, its already saved settings will be applied. Device can act as Server or Client at a time.
NOTE 2: Settings will be applied once the device is rebooted from web interface or repowered manually.
From this menu user may change the network settings of the device.
Following parameters and static IP settings available for “DHCP Server” setting which is default active for Server operating mode.
Also if the device has Broadband Power Line (BPL) option,
User can select operating mode of BPL either MASTER or NODE.
NOTE: Standard firmware of REDZ BPL supports up to 10 hops and 1000 nodes. Only 1 device can be MASTER in same network.
Once the setting has been changed, “Save Configuration” button will be enabled.
After clicking button system will tell if the settings applied successfully or not.
NOTE 1: STG Series WMBus Gateways can keep configuration of 2 different modes in its memory and once the configuration enabled, its already saved settings will be applied. Device can act as Server or Client at a time.
NOTE 2: Settings will be applied once the device is rebooted from web interface or repowered manually.
NOTE 3: If one of the Serial connections is enabled the device will act as Serial to WMBus Gateway and only following menu items will be available.
NOTE 4: If Device Function is set as WMBus – Modbus TCP Gateway following menu items will be available.
From this menu user may change the network settings of the device.
Following parameters and static IP settings available for “Use Static IP Address” setting:
Also if the device has Broadband Power Line (BPL) option,
User can select operating mode of BPL either MASTER or NODE.
NOTE: Standard firmware of REDZ BPL supports up to 10 hops and 1000 nodes. Only 1 device can be MASTER in same network. If the device is in client mode, it is suggested to use “NODE” as setting.
Once the setting has been changed, “Save Configuration” button will be enabled.
After clicking button system will tell if the settings applied successfully or not.
NOTE 1: STG Series WMBus Gateways can keep configuration of 2 different modes in its memory and once the configuration enabled, its already saved settings will be applied. Device can act as Server or Client at a time.
NOTE 2: Settings will be applied once the device is rebooted from web interface or repowered manually.
NOTE 3: If one of the Serial connections is enabled the device will act as Serial to WMBus Gateway and only following menu items will be available.
NOTE 4: If Device Function is set as WMBus – Modbus RTU Gateway following menu items will be available.
From this menu user may activate RS232 or RS485 connection. Once serial connection enabled, the device will act as Serial to WMBus Gateway and TCP Server and Client options in Network Settings will be disabled. Yet again web interface with basic network settings will be accessible.
Operating Modes and Device Functions affects the usage of WMBus because of default settings of the device
Select “Server” operating mode and set Device Function as “Transparent” to be able to receive data over WMBus network and send to RS232 or RS485
Select “Client” operating mode and set Device Function as “WMBus – Modbus RTU Gateway” to set Modbus RTU serial settings
Select “Client” operating mode and set Device Function as “Transparent” to receive data over RS232 or RS485 serial line and send to WMBus network
When device function set as “Transparent”, user generates WMBus messages and sends to WMBus RF network. In that case HCI protocol must be used
HCI protocol:
SOF (Start of Frame): 0xA5
Message Header Field: 
Control Field: User may use 0x0 for this part to ignore CRC16 attachment at end
Endpoint ID: It is 0x2
Message ID Field: It is 0x01 for sending data
Length Field: It is the payload length which means data size of framed WMBus package
Example WMBus Message:
| Frame in Hex | Frame in ASCII |
| 0E 06 23 12 67 45 23 01 01 01 80 54 65 73 74 |
..#.gE#...€Te st |
Example encapsulated WMBus Message with HCI protocol:
| Frame in Hex | Frame in ASCII |
| A5 02 01 0E 06 23 12 67 45 23 01 01 01 80 54 65 73 74 |
¥‚...#.gE#...€Te st |
Please contact our company if you need full implementation of protocol including CRC16 calculation.
Here are menu options:
Following settings are available for serial line:
Once the setting has been changed, “Save Configuration” button will be enabled.
After clicking button system will tell if the settings applied successfully or not.
NOTE 1: STG Series WMBus Gateways can keep configuration of 2 different modes in its memory and once the configuration enabled, its already saved settings will be applied. Device can act as Server or Client at a time. Lets say TCP Server enabled in Server operating mode and RS232 serial line enabled in Client operating mode on same device, the device can switch between to settings simply by changing the mode.
NOTE 2: Settings will be applied once the device is rebooted from web interface or repowered manually.
NOTE 3: This page has same settings both for Server and Client operating modes and only the texts of serial options will differ based on data package direction.
In Server Operating Mode the text will be “Send WMBus Messages to RS232”.
In Client Operating mode the text will be “Receive WMBus Messages from RS232”.
NOTE 4: This menu is not available when device set to Server and Device Function is set to WMBus – Modbus RTU Gateway.
From this menu user may monitor device status and statistics based on operating mode of device. The page also helps users to check device health.
When device Function is set to WMBus – Modbus TCP Gateway, following page will be available:
When device Function is set to Transparent, following page will be available:
After clicking “Refresh Status” button, system will reload data only and will not reload page. Button will be disabled during reload for an instance. If timeout occurs during the reload, the button will be enabled again with warning of timeout. In normal operation reload of status data will be done immediately.
NOTE: Connected client list will not be visible if one of the serial line is activated and device is set to act as Serial to WMBus Gateway.
From this menu user may monitor device status and statistics based on operating mode of device. The page also helps users to check device health.
When device Function is set to WMBus – Modbus RTU Gateway, following page will be available:
When device Function is set to Transparent, following page will be available:
After clicking “Refresh Status” button, system will reload data only and will not reload page. Button will be disabled during reload for an instance. If timeout occurs during the reload, the button will be enabled again with warning of timeout. In normal operation reload of status data will be done immediately.
The Wireless M-Bus protocol stack implemented on STG is compliant the European standard 13757 part 4: "Communication systems for meters and remote reading of meters". It describes the wireless communication of water, heat, electricity and gas meters with data concentrators. For sake of convenience in this manual such meter devices are called "Meter", the communications partner devices like concentrators are called "Other".
From this menu user may change following WMBus RF parameters:
If Enabled STG supports automatic AES-128 encryption and decryption of radio link messages.
There is the chance to configure up to 16 decryption keys for 16 different devices. The keys can be stored in a RAM table together with the complete WM-Bus device address, Manufacturer ID, Device version and Device Type.
Following table shows the RF channel setup. These channels are available in R-Mode for transmissions from Meter to Other devices. The opposite direction is always done in 868.33 MHz (channel 5).
| Channel | Frequency (MHz) |
| 1 | 868,09 MHz |
| 2 | 868,15 MHz |
| 3 | 868,21 MHz |
| 4 | 868,27 MHz |
| 5 | 868,33 MHz |
| 6 | 868,39 MHz |
| 7 | 868,45 MHz |
| 8 | 868,51 MHz |
Following table shows the possible power level setup:
| Power Level | Tx Power (dBm) | Description |
| 0 | -8 | Minimum Output Power |
| 1 | -5 | |
| 2 | -2 | |
| 3 | +1 | |
| 4 | +4 | |
| 5 | +7 | |
| 6 | +10 | |
| 7 | +13 | Maximum Output Power |
STG is a compact, ultra low power, bidirectional radio device for the 868 MHz frequency band. STG is optimal suited for use in Smart Metering Applications, which are compliant to EN 13757 part 4.
STG supports all link modes according to EN 13757-4:
These four main modes are divided into further sub-modes for dedicated applications. All modes are available in web interface. Following table gives an overview over all WM-Bus modes and their physical parameters.
| Mode | Direction | Data Rate | Coding | Frequency | Preamble + Synchronization |
| S1 | Meter => Other | 32,768 kcps | Manchester | 868,3 MHz | 582 chips |
| S1-m | Meter => Other | 32,768 kcps | Manchester | 868,3 MHz | 56 chips |
| S2 | Meter => Other | 32,768 kcps | Manchester | 868,3 MHz | 56 chips |
| Other => Meter | 32,768 kcps | Manchester | 868,3 MHz | 56 chips | |
| T1 | Meter => Other | 100 kcps | 3 out of 6 | 868,95 MHz | 56 chips |
| T2 | Meter => Other | 100 kcps | 3 out of 6 | 868,95 MHz | 56 chips |
| Other => Meter | 32,768 kcps | Manchester | 868,3 MHz | 56 chips | |
| R2 | Meter => Other | 4,8 kcps | Manchester | 868,03 MHz + n*60 kHz | 104 chips |
| Other => Meter | 4,8 kcps | Manchester | 868,33 MHz | 104 chips | |
| C1 | Meter => Other | 100 kcps | NRZ | 868,95 MHz | 64 chips |
| C2 | Meter => Other | 100 kcps | NRZ | 868,95 MHz | 64 chips |
| Other => Meter | 50 kcps | NRZ | 868,525 MHz | 64 chips |
WM-Bus Mode S: Stationary mode
Mode S1 transmit only, unidirectional, long preamble
Mode S1-m unidirectional, transmission to mobile data collectors, short preamble
Mode S2 bidirectional, short preamble
Operation at 868.3 MHz, chip rate: 32.768 kcps, encoding: "Manchester"
Telegram Format A
WM-Bus Mode T: Frequent transmit mode
Mode T1 unidirectional, frequent operation
Mode T2 bidirectional, frequent operation
Transmission at 868.95 MHz, chip rate: 100 kcps, encoding: "3 out of 6"
Receiving (meter) at 868.3 MHz, chip rate: 32.768 kcps, decoding: "Manchester"
Telegram Format A
WM-Bus Mode R2: Frequent receive mode
Mode R2 bidirectional, meter always available
Transmission at channel 0-9, chip rate: 4.8 kcps, encoding: "Manchester"
Receiving at 868.33 MHz (channel 5), chiprate 4.8 kcps, decoding: "Manchester"
Once a mode is configured the module firmware configures all required physical parameter automatically according to EM 13757-4.
Telegram Format A
WM-Bus Mode C: Compact mode
Mode C1 unidirectional, compact operation
Mode C2 bidirectional, compact operation
Transmission at 868.95 MHz, chip rate: 100 kcps, encoding: "NRZ"
Receiving (meter) at 869,525 MHz, chip rate: 50 kcps, decoding: "NRZ"
Telegram Format A / Telegram Format B
Following table shows the used RF data rates setups. They are configured automatically by the module firmware dependent on the selected Wireless M-Bus mode, the Device Mode and the data direction.
| RF Data Rate (kcps) | Description |
| 4,8 | chip rate, results in a data rate of 2.4 kbps (Manchester coding) |
| 32,768 | chip rate, results in a data rate of 16.384 kbps (Manchester coding) |
| 50 | chip rate = data rate (NRZ coding) |
| 100 | chip rate, results in a data rate of 66.66 kbps (3 out of 6 coding) chip rate = data rate (NRZ coding) |
There are two different telegram formats specified in EN13757-4. Telegram Format A and Telegram Format B. The operating modes S, T and R2 use Telegram Format A. The C-mode supports both telegram formats.
Wireless M-Bus Telegram Format A
Every Wireless M-Bus telegram starts with a preamble sequence followed by a synchronization word. The length of these fields is mode-dependent. The implementation is done according to EN13757-4. The postamble contains normally 8 chips. Only for even packet sizes in T mode (Meter) the postamble consists of four chips.
Wireless M-Bus Telegram Format A, Block 1
The first byte of block 1 is the length byte. It describes the number of the following user bytes including C-Field-, M -Field- and A-Field-Data, but without any CRC byte. C-Field, M-Field and A-fields can be pre-configured (and stored in the non-volatile memory with special firmware version). L-Field and CRC-fields are filled by the firmware at transmission.
Wireless M-Bus Telegram Format A, Block 2
Wireless M-Bus Telegram Format A, Block 3 to Block n (optional blocks)
Wireless M-Bus Telegram Format B
Wireless M-Bus Telegram Format B, Block 1
The first byte of block 1 is the length byte. It describes the number of all following bytes including the CRC bytes. The block 1 in Telegram Format B is the same as in Telegram Format A, only the CRC Field is missing.
Wireless M-Bus Telegram Format B, Block 2
Wireless M-Bus Telegram Format B, Block 3 (optional Block)
STG is able to transmit at RF power levels up to +14 dBm with a low current consumption. In receive mode, the maximum current consumption is of WMBus module is less than 19 mA with a sensitivity down to -116 dBm. With a standby current of less than 0.1 μA for module, the STG is optimal suited for battery powered devices while providing an excellent RF performance.
Receiver RF Characteristics:
| Parameter | Condition | Min | Typ. | Max. | Unit |
| Frequency Range | g1 subband | 868,0 | - | 868,6 | MHz |
| g2 subband | 868,7 | - | 869,2 | MHz | |
| Modulation Techniques : | 2-FSK | ||||
| Sensitivity | BER ≤ 1% 1 kbps, 2-FSK, Deviation: ±30 kHz |
-116 | dBm | ||
| BER ≤ 1% 4,8 kbps, 2-FSK, Deviation: ±7,2 kHz |
-109 | dBm | |||
| BER ≤ 1% 10 kbps, 2-FSK, Deviation: ±20 kHz |
-108 | dBm | |||
| BER ≤ 1% 32,768 kbps, 2-FSK, Deviation: ±80 kHz |
-105 | dBm | |||
| BER ≤ 1% 100 kbps, 2-FSK, Deviation: ±80 kHz |
-102 | dBm | |||
| BER ≤ 1% 256 kbps, 2-FSK, Deviation: ±120 kHz |
-98 | dBm | |||
Transmitter RF Characteristics:
| Parameter | Condition | Min | Typ. | Max. | Unit |
| Frequency Range | g1 subband | 868,0 | - | 868,6 | MHz |
| g2 subband | 868,7 | - | 869,2 | MHz | |
| RF Output Power | Depends on power settings | +12,5 | +13 | +4 | dBm |
| RF Data Rate |
4,8 32,768 100 |
kbps kbps kbps |
|||
| Modulation Techniques : | 2-FSK | ||||
| Modulation Deviation | ±4.8..±7.2 ±40..±80 |
kHz | |||
| TX Frequency Variation vs. Temperature | -20 to +70°C | ±10 | ppm | ||
Here are web menu options:
Following settings are available once Encryption Key Enabled clicked:
Following settings are available once Decryption Key Enabled clicked. User can enter AES Decryption Key, WM-Bus device address, Manufacturer ID, Device version and Device Type. If the setting is ok STG will show as check box under Config OK column ( after restart of device).
Once the setting has been changed, “Save Configuration” button will be enabled.
After clicking button system will tell if the settings applied successfully or not.
NOTE 1: STG Series WMBus Gateways can keep configuration of 2 different modes in its memory and once the configuration enabled, its already saved settings will be applied. Device can act as Server or Client at a time. This way different WMBus settings can be stored in 2 different operating modes.
NOTE 2: Settings will be applied once the device is rebooted from web interface or repowered manually.
NOTE 3: This page has same settings both for Server and Client operating modes.
From this menu user may monitor WMBus status and package details as wel as WMBus OMS parsed datat if available.
WMBus package will be received from WMBus network and shared over to TCP/IP or RS232/RS485 serial line as Modbus TCP or RTU packages when the Device Function is WMBus – Modbus Gateway.
WMBus package will be received from WMBus network and send to TCP/IP or RS232/RS485 serial line when the operating is in Server Mode and Device Function is Transparent.
WMBus package will be received from gateway side comes from either TCP/IP or RS232/RS485 serial line and send to WMbus network when the operating is in Client Mode and Device Function is Transparent.
The page also helps users to diagnose radio communication health.
After clicking “Refresh WMBus Status” button, system will reload data only and will not reload page. Button will be disabled during reload for an instance. If timeout occurs during the reload, the button will be enabled again with warning of timeout. In normal operation reload of status data will be done immediately.
NOTE: This page has same options both for Server and Client operating modes. Only the text for message details will be different.
In Server Operating Mode the text will be “Latest Message Received”.
In Client Operating mode the text will be “Latest Message Sent”.
From this menu user may activate WMBUs RF communication package filter based on White list (accepted packages from Device ID field of WMBus packages) or Black list ( rejected packages from Device ID field of WMBus packages).
Up to 20 entry can be defined for each filter list.
User can get ID of device from “Device Status” menu page.
Following settings are available for any of the list:
In this page user can enter decimal values and page will format it to hexadecimal automatically after cursor is moved out of scope.
Once the setting has been changed, “Save Configuration” button will be enabled.
After clicking button system will tell if the settings applied successfully or not.
NOTE 1: STG Series WMBus Gateways can keep configuration of 2 different modes in its memory and once the configuration enabled, its already saved settings will be applied. Device can act as Server or Client at a time. That means users can configure different configuration settings for different operating modes and switch between each other in an instant.
NOTE 2: Settings will be applied once the device is rebooted from web interface or repowered manually.
NOTE 3: This page has same settings both for Server and Client operating modes.
From this menu user may change parameters or send command to device.
The device restarts itself every 86400 seconds. (Which means every 24 hours.) There are also timeout restart routines in Server mode during listening clients and in Client Mode trying to connect to the server. ( Both preset to 10 minutes which means device will restart system if fails to connect a server in Client mode or a client do not connect in preset time in Server mode.)
After a firmware change old configuration will be used for minor changes. If a major change occurs system will restore to factory default configuration.
User can change the login information.
User can change the log level of the device. REDZ STG WMBus Gateways series has micro USB and gives log in 115200 - 8N1 format.
Any terminal program can be used to listen the LOG over micro USB port of the device which is recognized as Virtual COM port in PC.
User can restore to factory settings and force device to reboot. Factory settings restored for Client if the device in Client mode and factory settings are restored for Server if the device in Server mode.
Firmware upgrade is possible only with files that REDZ supplied. Once the file selected, STG shows selected file:
Then “Upload Firmware” button must be clicked. Then user must wait until page shows the result.
This make take few seconds only. Please wait.
Then system will show the firmware date and version and user can reboot that firmware.
Typical log for the system is shown below.
NOTE: This page has same settings both for Server and Client operating modes.
STG series WMBus Gateways can get WMBus OMS data, can decrypt the data based on OMS decryption mode 5 and share data as Modbus values.
As a first step user should select under Operating Mode page:
Wmbus – Modbus TCP Gateway Device Function (available when device operation mode is server)
Or
Wmbus – Modbus RTU Gateway Device Function (available when device operation mode is client)
Once the device function is set, a list with maximum 20 entries will be shown on Operating Mode page.
Each WMBus device is separate MODBUS device so user should match Manufacturing IDs of field devices with selected Modbus Device Addresses. Then user should enable the entry that STG will expect the WMBus data and share info as Modbus register.
STG can decrypt OMS messages of Up to 16 field devices. If needed user can enter details of Decryption under WMBus Settings page. User can enter AES Decryption Key, WM-Bus device address, Manufacturer ID, Device version and Device Type. If the setting is ok STG will show as check box under Config OK column ( after restart of device).
For example if same details entered in 2 different entyr, STG will not accept and STG will not check Config OK check box.
User can get details such as WM-Bus device address, Manufacturer ID, Device version and Device Type under WMBus Status page if needed.
If there are many WMBus devices in the filed and STG is used to get data of some of them only, user can activate WMBUs RF communication package filter based on White list (accepted packages from Device ID field of WMBus packages) or Black list (rejected packages from Device ID field of WMBus packages).
Up to 20 entry can be defined for each filter list.
User can get ID of device from “Device Status” menu page.
If WMbus – Modbus RTU Gateway is set, user can make serial interface settings under menu Serial Settings.
If WMbus – Modbus TCP Gateway is set, user can change Modbus TCP Port under menu Network Settings.
STG series WMbus – Modbus TCP/RTU Gateway devices can get WMBus OMS data and convert those to Modbus registers. Users or field devices can read WMBus data over Modbus registers. Here are basic rules:
- Each wMBUS device is separate MODBUS slave
Slave ID is possible to configure in STG web page "Operating Mode" in table "Modbus Scheduler Settings" column "Modbus address"
- MODBUS data is stored in two part: Status Block and several Data Blocks depends of number measurements stored in WMBus device
- Without error it is possible read first 6 words or all registers
Number of words needed to read all register is possible after counting length of data blocks. For example, if in status block "data count" value is equal to 2 you have to read 6+2*5 (16) words from address 0
- To restrict number of WMBUS devices it is possible use "White" or "Black" list of WMBus devices
See "Security Settings" in STG web configuration page
- To Decrypt WMBus devices you have to fill "AES-128 Decryption List"
See " WMBus Settings" in STG web configuration page
- Current MODBUS STG status is possible to find in " WMBus Status" page
See " WMBus Status" in STG web configuration page
- Current WMBus device status is possible to find in "Device Status" page
See "Device Status" in STG web configuration page
STG series WMbus – Modbus TCP/RTU Gateway devices convert WMBus OMS data to Modbus Registers in following format:
Frame has 1 Data header, 6 Registers:
- WMbus Device ID: 2 Registers
- WMbus Man ID: 1 Register
- WMbus Version: 1 Register
- WMbus Type: 1 Register
- Total Data Count ( Represents how many data blocks exists)
Data Block, each 5 Bytes total n bytes
- Storage Number: 1 Register
- Function Field: 1 Register
- Data Type: 1 Register
- Data Value: 2 Registers
| Item | Data Structure Name | Register Name | Register Type | Register Address | Data Type Format | Data Length in Words | Data Length in Bytes | Register Description | Example of Register Value in HEX | Sample Register Values | Explanation of Register Values |
| 1 | Data Header | WMbus Device ID | 03 Read Holding Register | 0 | Unsigned Long | 2 | 4 | Device ID from WMbus frame | 0x20218613 | 0x20218613 | WMbus address of device |
| 2 | Data Header | Man ID | 03 Read Holding Register | 2 | Unsigned Integer | 1 | 2 | Manufacturer ID from WMbus frame | 0xB409 | 0xB409 | WMbus device manufacturer code |
| 3 | Data Header | Version | 03 Read Holding Register | 3 | Unsigned Integer | 1 | 2 | Device version from WMbus frame | 0x0001 | 0x01 | WMbus device version |
| 4 | Data Header | Type | 03 Read Holding Register | 4 | Unsigned Integer | 1 | 2 | Device type from WMbus frame | 0x0007 | 0x07 | WMbus device type |
| 5 | Data Header | Data count | 03 Read Holding Register | 5 | Unsigned Integer | 1 | 2 | Number of data block | 0x0004 | 4 | Number of MODBUS data block for WMbus device |
| 6 | Data Block 1 | Storage Number | 03 Read Holding Register | 6 | Unsigned Integer | 1 | 2 | Indicator of stored metering values or historical values of metering data. | 0x0000 | 0 | Current data value |
| 7 | Data Block 1 | Function Field | 03 Read Holding Register | 7 | Unsigned Integer | 1 | 2 | Character of data in data block: instantaneous, maximum, minimum, error state | 0x0001 | 1 | INSTANTANEOUS data value |
| 8 | Data Block 1 | Data Type | 03 Read Holding Register | 8 | Unsigned Integer | 1 | 2 | Data type: energy, volume, weight, unit, time, date | 0x0003 | 3 | Volume, unit in Liters, FLOAT32 data representation |
| 9 | Data Block 1 | Data Value | 03 Read Holding Register | 9 | Depends of Data type | 2 | 4 | Float or Unsigned Long | 0x41B00000 | 22 | Data value |
| 10 | Data Block 2 | Storage Number | 03 Read Holding Register | 11 | Unsigned Integer | 1 | 2 | Indicator of stored metering values or historical values of metering data. | 0x0001 | 1 | Stored data value |
| 11 | Data Block 2 | Function Field | 03 Read Holding Register | 12 | Unsigned Integer | 1 | 2 | Character of data in data block: instantaneous, maximum, minimum, error state | 0x0001 | 1 | INSTANTANEOUS data value |
| 12 | Data Block 2 | Data Type | 03 Read Holding Register | 13 | Unsigned Integer | 1 | 2 | Data type: energy, volume, weight, unit, time, date | 0x0003 | 3 | Volume, unit in Liters, FLOAT32 data representation |
| 13 | Data Block 2 | Data Value | 03 Read Holding Register | 14 | Depends of Data type | 2 | 4 | Float or Unsigned Long | 0x41700000 | 15 | Data value |
| 14 | Data Block 3 | Storage Number | 03 Read Holding Register | 16 | Unsigned Integer | 1 | 2 | Indicator of stored metering values or historical values of metering data. | |||
| 15 | Data Block 3 | Function Field | 03 Read Holding Register | 17 | Unsigned Integer | 1 | 2 | Character of data in data block: instantaneous, maximum, minimum, error state | |||
| 16 | Data Block 3 | Data Type | 03 Read Holding Register | 18 | Unsigned Integer | 1 | 2 | Data type: energy, volume, weight, unit, time, date | |||
| 17 | Data Block 3 | Data Value | 03 Read Holding Register | 19 | Depends of Data type | 2 | 4 | Float or Unsigned Long | |||
| 18 | Data Block 4 | Storage Number | 03 Read Holding Register | 21 | Unsigned Integer | 1 | 2 | Indicator of stored metering values or historical values of metering data. | |||
| 19 | Data Block 4 | Function Field | 03 Read Holding Register | 22 | Unsigned Integer | 1 | 2 | Character of data in data block: instantaneous, maximum, minimum, error state | |||
| 20 | Data Block 4 | Data Type | 03 Read Holding Register | 23 | Unsigned Integer | 1 | 2 | Data type: energy, volume, weight, unit, time, date | |||
| 21 | Data Block 4 | Data Value | 03 Read Holding Register | 24 | Depends of Data type | 2 | 4 | Float or Unsigned Long | |||
| 22 | Data Block n | Storage Number | 03 Read Holding Register | 5 + ((n-1) * 5) + 1 | Unsigned Integer | 1 | 2 | Indicator of stored metering values or historical values of metering data. | |||
| 23 | Data Block n | Function Field | 03 Read Holding Register | 5 + ((n-1) * 5) + 2 | Unsigned Integer | 1 | 2 | Character of data in data block: instantaneous, maximum, minimum, error state | |||
| 24 | Data Block n | Data Type | 03 Read Holding Register | 5 + ((n-1) * 5) + 3 | Unsigned Integer | 1 | 2 | Data type: energy, volume, weight, unit, time, date | |||
| 25 | Data Block n | Data Value | 03 Read Holding Register | 5 + ((n-1) * 5) + 4 | Depends of Data type | 2 | 4 | Float or Unsigned Long |
STG series WMbus – Modbus TCP/RTU Gateway devices shares each data in 5 bytes.
- Storage Number: 1 Register
Shows the historical storage number of data, if it is Instantaneous data t will be 0
- Function Field: 1 Register
There are 4 options
| Item | Function Field description | Function Field Value | Notes |
| 1 | INSTANTANEOUS | 1 | The data in the data block is Instantaneous Value |
| 2 | MAXIMUM | 2 | The data in the data block is Maximum Value |
| 3 | MINIMUM | 3 | The data in the data block is Minimum Value |
| 4 | ERROR STATE | 4 | The data in the data block is Value during error state |
- Data Type: 1 Register
There are 46 types, new values can be added based on user need
| Item | Data Type Name | Data Type Value | Data Lenght in Bytes Stored in MODBUS Register | Data Type Format | Data Type Description | Range |
| 1 | ENERGY_WH | 1 | 4 | FLOAT32 | Energy | 0.001Wh to 10000Wh |
| 2 | ENERGY_J | 2 | 4 | FLOAT32 | Energy | 0.001kJ to 10000kJ |
| 3 | VOLUME_M3 | 3 | 4 | FLOAT32 | Volume | 0.001l to 10000l |
| 4 | MASS_KG | 4 | 4 | FLOAT32 | Mass | 0.001kg to 10000kg |
| 5 | POWER_W | 5 | 4 | FLOAT32 | Power | 0.001W to 10000W |
| 6 | POWER_J_H | 6 | 4 | FLOAT32 | Power | 0.001kJ/h to 10000kJ/h |
| 7 | VOLUMEFLOW_M3_H | 7 | 4 | FLOAT32 | Volume Flow | 0.001l/h to 10000l/h |
| 8 | VOLUMEFLOW_M3_M | 8 | 4 | FLOAT32 | Volume Flow ext. | 0.0001l/min to 1000l/min |
| 9 | VOLUMEFLOW_M3_S | 9 | 4 | FLOAT32 | Volume Flow ext. | 0.001ml/s to 10000ml/s |
| 10 | MASSFLOW_KG_H | 10 | 4 | FLOAT32 | Mass flow | 0.001kg/h to 10000kg/h |
| 11 | FLOWTEMPERATURE_C | 11 | 4 | FLOAT32 | Flow Temperature | 0.001°C to 1°C |
| 12 | RETURNTEMPERATURE_C | 12 | 4 | FLOAT32 | Return Temperature | 0.001°C to 1°C |
| 13 | TEMPERATUREDIFF_K | 13 | 4 | FLOAT32 | Temperature Difference | 1mK to 1000mK |
| 14 | EXTERNALTEMP_C | 14 | 4 | FLOAT32 | External Temperature | 0.001°C to 1°C |
| 15 | PRESSURE_Bar | 15 | 4 | FLOAT32 | Pressure | 1mbar to 1000mbar |
| 16 | ON_TIME_S | 16 | 4 | FLOAT32 | ON time | sec |
| 17 | ON_TIME_M | 17 | 4 | FLOAT32 | ON time | min |
| 18 | ON_TIME_H | 18 | 4 | FLOAT32 | ON time | hour |
| 19 | ON_TIME_D | 19 | 4 | FLOAT32 | ON time | days |
| 20 | OPER_TIME_S | 20 | 4 | FLOAT32 | Operating time | sec |
| 21 | OPER_TIME_M | 21 | 4 | FLOAT32 | Operating time | min |
| 22 | OPER_TIME_H | 22 | 4 | FLOAT32 | Operating time | hour |
| 23 | OPER_TIME_D | 23 | 4 | FLOAT32 | Operating time | days |
| 24 | AVR_DUR_S | 24 | 4 | FLOAT32 | Average duration time | sec |
| 25 | AVR_DUR_M | 25 | 4 | FLOAT32 | Average duration time | min |
| 26 | AVR_DUR_H | 26 | 4 | FLOAT32 | Average duration time | hour |
| 27 | AVR_DUR_D | 27 | 4 | FLOAT32 | Average duration time | days |
| 28 | ACT_DUR_S | 28 | 4 | FLOAT32 | Actuality Duration time | sec |
| 29 | ACT_DUR_M | 29 | 4 | FLOAT32 | Actuality Duration time | min |
| 30 | ACT_DUR_H | 30 | 4 | FLOAT32 | Actuality Duration time | hour |
| 31 | ACT_DUR_D | 31 | 4 | FLOAT32 | Actuality Duration time | days |
| 32 | DURATION_LAST_CUMULATION_H | 32 | 4 | FLOAT32 | Duration since last cumulation | hour |
| 33 | DURATION_LAST_CUMULATION_D | 33 | 4 | FLOAT32 | Duration since last cumulation | day |
| 34 | DURATION_LAST_CUMULATION_M | 34 | 4 | FLOAT32 | Duration since last cumulation | month |
| 35 | DURATION_LAST_CUMULATION_Y | 35 | 4 | FLOAT32 | Duration since last cumulation | year |
| 36 | BATTERY_OP_TIME_H | 36 | 4 | FLOAT32 | Battery operation time | hour |
| 37 | BATTERY_OP_TIME_D | 37 | 4 | FLOAT32 | Battery operation time | day |
| 38 | BATTERY_OP_TIME_M | 38 | 4 | FLOAT32 | Battery operation time | month |
| 39 | BATTERY_OP_TIME_Y | 39 | 4 | FLOAT32 | Battery operation time | year |
| 40 | REMAINING_BATTERY_H | 40 | 4 | FLOAT32 | Remaining battery time | hour |
| 41 | REMAINING_BATTERY_D | 41 | 4 | FLOAT32 | Remaining battery time | day |
| 42 | REMAINING_BATTERY_M | 42 | 4 | FLOAT32 | Remaining battery time | month |
| 43 | REMAINING_BATTERY_Y | 43 | 4 | FLOAT32 | Remaining battery time | year |
| 44 | TIME_POINT_DATE | 44 | 4 | Unsigned Long | 2 bytes date (in 4 bytes register), Data Type G | YY:MM:DD |
| 45 | TIME_POINT_DATE_TIME | 45 | 4 | Unsigned Long | 4 bytes time and date, Data Type F | YY:MM:DD HH:MM:SS |
| 46 | BATTERY_CHANGE_DATE_TIME | 46 | 4 | Unsigned Long | 4 bytes time and date, Data Type F | YY:MM:DD HH:MM:SS |
- Data Value: 2 Registers
Exact value of data, must be parsed based on Data Type Format.
STG series WMbus – Modbus TCP/RTU Gateway devices shares WMBus OMS data as Modbus data and those data can be read by Holding Register command (Function Code 3).
Header Values can be queried individually or as array.
Data Block values can only be queried as Block Data ( 5 bytes).
Frame has 1 Data header, 6 Registers:
- WMbus Device ID: 2 Registers
- WMbus Man ID: 1 Register
- WMbus Version: 1 Register
- WMbus Type: 1 Register
- Total Data Count ( Represents how many data blocks exists)
Data Block, each 5 Registers total n bytes
- Storage Number: 1 Register
- Function Field: 1 Register
- Data Type: 1 Register
- Data Value: 2 Register
This command is requesting the content of meter data holding registers # 40000 to 40031 from the STG series WMbus – Modbus TCP/RTU Gateway device with address 1.
01 03 0000 001F 0402
| 01: | The Slave Address (01 hex = address 1 ) |
| 03: | The Function Code 3 |
| 0000: | The Data Address of the first register requested. |
| 001F: | The total number of registers requested. (read 6 registers in data header and 5 data blocks each 5 registers, total 31 registers) |
| 0402: | The CRC (cyclic redundancy check) for error checking. |
01 03 3E
19012204 2697 0033 0007 0006
0000 0001 002D 19050C9C
0000 0001 0003 455FBFFF
0000 0001 0003 00000000
0000 0001 0007 00000000
0001 0001 0003 455FBFFF
1F91
| 01: | The Slave Address (01 hex = address 1) |
| 03: | The Function Code 3 |
| 3E: | The number of data bytes to follow (6 registers in data header and 5 data blocks each 5 registers, total 31 registers. Each register has 2 bytes and total 62 bytes) |
Data Header:
| 19012204: | Data Header: WMBus Device ID: 19012204 (2 registers) |
| 2697: | Data Header: WMBus Manufacturer ID: 0x2697 |
| 0033: | Data Header: WMBus Version: 0x33 |
| 0007: | Data Header: WMBus Type: 0x07 |
| 0006: | Total Data Block Available in WMBus OMS Parsed Frame |
Data Block 1:
| 0000: | Data Block: Storage Number: 0 |
| 0001: | Data Block: Function Field: 0 |
| 002D: |
Data Block: Data Type: TIME_POINT_DATE_TIME 2 bytes date (in 4 bytes register), Data Type G according to WMBus OMS Standard |
| 19050C9C: |
Data Block: Data Value: 28-12-2020 11:08:00 DST:0 |
Data Block 2:
| 0000: | Data Block: Storage Number: 0 |
| 0001: | Data Block: Function Field: 0 |
| 0003: |
Data Block: Data Type: VOLUME_M3 FLOAT32 data, Range from 0.001 liters to 10000 liters |
| 455FBFFF: | Data Block: Data Value: 3580 liters |
Data Block 3:
| 0000: | Data Block: Storage Number: 0 |
| 0001: | Data Block: Function Field: 0 |
| 0003: |
Data Block: Data Type: VOLUME_M3 FLOAT32 data, Range from 0.001 liters to 10000 liters |
| 00000000: | Data Block: Data Value: 0 liters |
Data Block 4:
| 0000: | Data Block: Storage Number: 0 |
| 0001: | Data Block: Function Field: 0 |
| 0007: |
Data Block: Data Type: VOLUMEFLOW_M3_H FLOAT32 data, Range from 0.001 liters/hour to 10000 liters/hour |
| 00000000: | Data Block: Data Value: 0 liters/hour |
Data Block 5:
| 0001: | Data Block: Storage Number: 1 |
| 0001: | Data Block: Function Field: 0 |
| 0003: |
Data Block: Data Type: VOLUME_M3 FLOAT32 data, Range from 0.001 liters to 10000 liters |
| 455FBFFF: | Data Block: Data Value: 3580 liters |
| 1F91: | The CRC (cyclic redundancy check) for error checking. |
NOTE: This example is given for Modbus RTU Frame. Modbus TCP frame will be similar in following manner :
STG154: 868MHz WMBus – Modbus TCP/RTU Gateway, 2x 10/100 T(x) ETH ports, 1 x RS232 & 1 x RS485, 5-60V DC Power Input
STG254: 868MHz WMBus – Modbus TCP/RTU Gateway, 2x 10/100 T(x) ETH ports, 1 x RS232 & 1 x RS485, 90 - 265V AC (100 – 370V DC), 47Hz to 63Hz AC Power Input
STG655: 868MHz WMBus – Modbus TCP/RTU Gateway, 2x 10/100 T(x) ETH ports + 1 x BPL (Broadband Power Line) Link, 1 x RS232 & 1 x RS485, 3 Phase AC Power Input, 110V–240V/50-60Hz
| Model | 5-60V DC Power Input | 90 - 265V AC (100 – 370V DC), 47Hz to 63Hz AC Power Input | 3 Phase AC Power input, 110V–240V/50-60Hz AC Power Input | 2 x 10/100 T(x) ETH Ports | 1 x RS232 and 1 x RS485 Serial Ports | BPL (Broadband Power Line) Link |
| STG154 | X | X | X | |||
| STG254 | X | X | X | |||
| STG655 | X | X | X | X |
Various types of cookies are used on our website (and on all other digital platforms including mobile applications).
View our new THE INFORMATIVE TEXT ON LPPD AND PRIVACY here.
Google Analytics
Analytical cookies help us to improve our website by collecting and reporting information on its usage.
Google AdWords and Remarketing
We use marketing cookies to help us improve the relevancy of advertising campaigns you receive.
I have read the above articles
download 
