TLM Series LoRa Radio Modems with 2 x 10/100Base-T(x) Ports, 1 x RS232 and 1 x RS485 Serial Ports and/or BPL (Broadband Power Line Link) User Manual

The TLM Series LoRa RF Modems build a private radio network between Ethernet devices and RS232 / RS485 serial devices. Two or more modems exchange data over LoRa; each modem connects the radio network to its own Ethernet port or serial port. The data passes unchanged, so any protocol can be carried. For Modbus the modem can also convert between Modbus TCP and Modbus RTU.

All settings are made in the embedded web interface. The same interface shows a health summary, the traffic and counters of the modem, lists the other modems it hears, and offers a remote ping, a link test and remote node information for installation (chapter 11 "LoRa Network Discovery"). This manual describes firmware 3.00.01; what changes for a modem with firmware 3.00.00 is listed in 16.3 "Updating from 3.00.00".

NOTE:

Upgrading a modem from firmware 2.x resets its settings to the factory values. Read 16.4 "Upgrading from 2.x" before you upgrade.

1.1 Models

All models have two 10/100Base-T(X) Ethernet ports, one RS232 port and one RS485 port. TLM154 and TLM254 differ in the power input and the operating temperature range (-25 to +70 C for the AC versions, -40 to +85 C for the DC versions), and so do TLM194 and TLM294. TLM655 and TLM695 add a BPL (Broadband Power Line) link that carries Ethernet over the power line (chapter 7 "System Comparison Between CAT5 and BPL Links"). The power inputs and ports are described in chapter 2 "Hardware Features"; chapter 19 "Ordering Information" and chapter 20 "Product Selection" list the order codes.

NOTE:

The firmware differs by radio band and by BPL. The 868 MHz and 2.4 GHz models show different choices on the LoRa Settings page (see the table below), and only TLM655 and TLM695 show BPL Operating Mode on the Network Settings page.

1.2 What a modem can do

Each modem has one Device Function, chosen on the Operating Mode page. The usual combinations are shown in chapter 9 "Usage Scenarios and Connection Diagrams".

1.3 Radio

A longer message is sent as several packets. All modems of one network must use the same radio settings and, if AES Encryption/Decryption Enabled is used, the same 128-bit Encryption Key. The modems are addressed by a group and a device address on the LoRa Settings page (10.6 "LoRa Settings").

NOTE:

The distance that can be bridged depends on the antennas, their height, the terrain and the radio settings. Check each link on site with the link test on the LoRa Status page (11.4 "Link Test").

The TLM Series LoRa RF Modems are built in versions without and with a BPL (Broadband Power Line) link. TLM154, TLM254, TLM194 and TLM294 have Ethernet, serial and LoRa radio; TLM655 and TLM695 add the BPL link.

2.1 Features

• Two 10/100Base-T(X) Ethernet ports on a built-in Ethernet switch
• One RS232 and one RS485 serial port (one of them is used at a time), 300 to 460800 baud
• Embedded web interface for all settings and for status and traffic information
• Four device functions: LoRa to TCP/UDP Server Gateway, LoRa to TCP/UDP Client Gateway, LoRa to SERIAL Device Gateway and LoRa Repeater; the serial gateway can also convert Modbus TCP to Modbus RTU and Modbus RTU to Modbus TCP
• Further functions: Modbus Unit ID routing and UDP server mode in the server gateway, IEC 62056-21 Mode C baud switching in the serial gateway, NTP time synchronization, Listen Before Talk and acknowledged transmission (C-Data) on the radio, remote ping and link test tools (see chapter 9 "Usage Scenarios and Connection Diagrams" and chapter 10 "Configuration via Web Interface")
• Radio network: point to point, point to multipoint (broadcast) and point to multipoint with a TCP socket to target device list
• Discovery of the other TLM modems of the same LoRa network, with their signal levels, addresses and settings
• 868 MHz or 2.4 GHz LoRa radio, with 128-bit AES encryption of the radio data
• 868 MHz models: LoRa or FSK modulation, LoRa bandwidth 125, 250 or 500 kHz, radio power 5 dBm (about 3 mW) to 20 dBm (100 mW)
• 2.4 GHz models: LoRa or FLRC modulation, LoRa bandwidth 200, 400, 800 or 1600 kHz, radio power -18 dBm (about 0.02 mW) to 13 dBm (about 20 mW)
• Configurable receive and transmit group address and device address
• Up to 10 TCP clients in the server gateway function
• DHCP server
• White list and black list filter for LoRa packets
• Firmware update over the web interface; two firmware images are stored, one of them is active
• AC or DC wide range power input
• Operating temperature -25 to +70 C (AC powered versions) and -40 to +85 C (DC powered versions)
• Rugged metal housing, IP40
• DIN rail mounting

2.2 Extra features of the models with BPL

• Two 10/100Base-T(X) Ethernet ports plus one BPL link
• Wide range three-phase AC input
• Up to 30 Mbps PHY rate on the power line, up to 10 hops and 1000 nodes
• Up to 432 sub-carriers in the 2 to 28 MHz band
• LDPC-C forward error correction with a 128-bit AES core
• Plug and play: the only BPL setting is BPL Operating Mode (MASTER or NODE) on the Network Settings page

2.3 Technical data

2.3.1 LoRa radio

2.3.2 Ethernet

2.3.3 BPL link (TLM655, TLM695)

2.3.4 Power

2.3.5 Physical and environmental

Every modem has a DIN rail kit on its rear panel.

1. Tilt the modem and hook the metal spring of the kit onto the top edge of the DIN rail.
2. Push the modem toward the DIN rail until you hear a click.

Then connect the antenna, the Ethernet and serial cables and the power input as described in chapter 4 "Front Panel Description" and chapter 5 "Top Panel Description". All settings are made in the web interface (chapter 10 "Configuration via Web Interface").

4.1 TLM154, TLM254, TLM194 and TLM294

• Antenna: standard SMA connector, 50 ohm; female on TLM154 and TLM254 (868 MHz), male on TLM194 and TLM294 (2.4 GHz).
• Console port for the log output only, 115200 baud - micro USB on earlier hardware, USB Type-C on current hardware; the modem does not read input on it. The USB serial chip is made by FTDI; the driver is on the Driver page under Support on redz-sc.com (https://redz-sc.com/en/support/driver). Its Tx and Rx LEDs blink while data passes.
• LoRa LEDs: ALIVE, Tx and Rx (see the LED table below).
• Device LEDs: STATUS, Tx, Rx and SERVER (see the LED table below).
• Ethernet activity LEDs for port 1, port 2 and the modem itself.
• 5 pin terminal block for the serial line, from the top: A, B, GND, RX, TX - RS485 uses A, B and GND, RS232 uses GND, RX and TX (the GND contact is shared, see chapter 8 "Serial Cables"). The port, the baud rate and the data format are selected on the Serial Settings page, which appears in the menu only when Device Function is LoRa to SERIAL Device Gateway.
• Two 10/100Base-T(X) Ethernet ports (RJ-45).

4.2 TLM655 and TLM695

The front panel of the BPL models has the same connectors and LEDs as above, plus three BPL LEDs. The SMA antenna connector is female on TLM655 (868 MHz) and male on TLM695 (2.4 GHz).

• ACTIVITY: blinks while Ethernet data passes over the BPL link.
• LINK: on when a link over the power line is established.
• MASTER: on when the modem is the BPL master (BPL Operating Mode = MASTER).

4.3 LED indicators

NOTE:

In these cases the STATUS LED keeps blinking although the modem works normally: in the server gateway when Enable Modbus Unit ID to Target Device Matching List is on, or while only UDP peers are served; in the client gateway when all its targets are UDP targets.

NOTE:

The console port prints the log only when Log Level is not NONE and Log Output is CONSOLE; the factory default is NONE, so a new modem prints nothing there. Open the port with 115200 baud, 8 data bits, no parity, 1 stop bit. See chapter 18 "Logs and Troubleshooting".

WARNING:

Changing Log Level or Log Output with Change Log Level and Reboot restarts the modem.

5.1 TLM154 and TLM194

1. Power input: 5 - 48 V DC (60 V maximum), protected against reverse polarity.
2. Power LED: on while the modem is powered.
3. Reset buttons, marked RESET TO SERVER and RESET TO CLIENT. With firmware 3.00.01 both do the same: held for more than 5 seconds, either one restores the factory settings and restarts the modem (see below).

5.2 TLM254 and TLM294

1. Power input: 100 - 240 V AC (120 - 370 V DC), 50 / 60 Hz.
2. Power LED: on while the modem is powered.
3. Reset buttons, marked RESET TO SERVER and RESET TO CLIENT. With firmware 3.00.01 both do the same: held for more than 5 seconds, either one restores the factory settings and restarts the modem (see below).

5.3 TLM655 and TLM695

1. Power and BPL terminal block: three-phase AC, 110 - 240 V, 50 / 60 Hz, or 9 - 36 V DC on the DC version.
2. Power LED: on while the modem is powered.
3. Reset buttons, marked RESET TO SERVER and RESET TO CLIENT. With firmware 3.00.01 both do the same: held for more than 5 seconds, either one restores the factory settings and restarts the modem (see below).

5.3.1 Power connection

The terminals are marked L3, L2, L1 and N. The modem is powered over L1 and N only; L2 and L3 are data terminals. The order of the terminals on the panel is not the same on every hardware version: connect by the marks, not by the position. The AC versions take 110 - 240 V, 50 / 60 Hz; the DC version takes 9 - 36 V DC.

5.3.2 Data connection

The AC powered version is made with the P-N or the P-P data connection, the DC powered version with the P-P data connection. The order codes are listed in chapter 19 "Ordering Information".

5.4 Reset Buttons

The two buttons are marked RESET TO SERVER and RESET TO CLIENT. With firmware 3.00.01 both do the same: held for more than 5 seconds while the modem is running, either one restores all settings to the factory values and restarts the modem.

WARNING:

A reset with the buttons erases every setting, including the network settings, the web password and the LoRa radio settings (frequency, addresses, AES encryption): after the reset the modem no longer reaches the rest of its LoRa network until those are set again. After the restart the modem is a LoRa to TCP/UDP Server Gateway (also after RESET TO CLIENT) and asks for its address by DHCP; without a DHCP server it uses 192.168.1.1 / 255.255.255.0. Keep a copy of the settings with Download Current Configuration on the Management page.

NOTE:

The same factory reset can be started from the web interface with Restore Factory Configuration on the Management page; Reboot Device there only restarts the modem. See 10.9 "Management".

The modem has two standard 10/100Base-T(X) Ethernet ports with RJ-45 connectors. Use Cat. 3, 4, 5 or 5e UTP cables to connect PCs, servers, switches or routers.

The two ports belong to a small Ethernet switch inside the modem; the modem itself is connected to that switch. Either port can be used, and the second port can connect a further Ethernet device. Because the modem sits behind the switch, it does not notice when a cable is unplugged from a port.

6.1 Cable type and specifications

6.2 Pin assignments

With 100BASE-TX and 10BASE-T, pins 1 and 2 transmit data and pins 3 and 6 receive data.

TLM655 and TLM695 carry Ethernet over the low voltage power line. Devices on the power line network talk TCP/IP to each other as over a cable, without new cabling. The only setting is BPL Operating Mode on the Network Settings page: MASTER or NODE (factory default: NODE). The modem applies it to its BPL link when it starts, so a new setting takes effect after the modem is restarted (10.9 "Management").

NOTE:

BPL Operating Mode shows the stored value only after the BPL link has confirmed it; until then the field shows NODE. Check the field before you save the Network Settings page, otherwise a modem set to MASTER is saved as NODE.

Set one modem of a power line network to MASTER and all others to NODE.

7.1 CAT5 and BPL compared

NOTE:

The power and data connections of the BPL models (P-N, P-P and DC versions) are described in chapter 5 "Top Panel Description".

WARNING:

Connect a TLM655 or TLM695 to a network over one path only: over the power line or over an Ethernet cable. If it reaches the same network over both, the network has a loop and packets are lost or delayed.

The modem has one RS232 port and one RS485 port on a 5 pin terminal block. They connect serial devices such as RTUs, PLCs and energy meters.

Only one of the two ports works at a time: tick Enable RS232 or Enable RS485 on the Serial Settings page (the page always keeps exactly one of them ticked) and choose Baud rate (300 to 460800) and Line Control (8_NONE_1, 9_NONE_1, 8_EVEN_1, 8_EVEN_2, 8_ODD_1, 8_ODD_2, 8_NONE_2, 9_NONE_2, and 7_EVEN_1 when no Modbus conversion is enabled). The serial port is used only when Device Function is LoRa to SERIAL Device Gateway; in every other function both ports are off and the Serial Settings page does not appear in the menu. If that function is saved with neither port enabled, the modem enables RS485 with 19200 baud and 8_NONE_1. A new serial setting takes effect after the modem is restarted (10.9 "Management").

8.1 RS232 pin assignments

3 wire RS232 connection: TX, RX and GND. TX is the modem's output and RX its input: connect TX of the modem to RX of the device, RX of the modem to TX of the device, and GND to GND. The picture numbers the RS232 pins 1 to 3; they are contacts 3 to 5 of the terminal block.

8.2 RS485 pin assignments

2 wire RS485 connection (A, B) and GND. The modem switches the RS485 line between sending and receiving itself.

A TLM network is built from two or more modems that talk to each other over LoRa. Each modem has one Device Function, chosen on the Operating Mode page; the function decides what the modem does with its Ethernet or serial side. The scenarios below show the usual combinations. They are examples - any TCP/IP or RS232 / RS485 device can be connected in the same way.

9.1 Addresses

Every modem has its own address (Group Own Address and Device Own Address) and a target address (Tx Group Address and Tx Device Address) on the LoRa Settings page. Data from the gateway side is sent to the target address, unless one of the matching lists described below or Reply only to sender names another target. Tx Device Address 65535 means all devices of the target group. A factory modem has the own address group 1 / device 1 and the target group 1 / device 65535.

A modem receives the packets sent to its own group and device address and the packets sent to device 65535 of its group. All modems of one network must use the same radio settings (frequency, modulation, bandwidth, spreading factor, error coding) and, if AES encryption is used, the same key.

9.2 Message size

One LoRa packet carries at most 229 bytes of user data on the 868 MHz models (TLM154, TLM254, TLM655) and 109 bytes on the 2.4 GHz models (TLM194, TLM294, TLM695). In the transparent functions the modem closes a message after a pause in the incoming data (Idle Timeout (ms, 0=off), 100 ms from the factory), at Max Length (0=off) or at the Delimiter Enable character - and at the packet size at the latest. Modbus frames and UDP datagrams longer than one packet are sent as several packets.

NOTE:

A message received over LoRa is held for each connected TCP client in a slot of 512 bytes. If all connected clients are still busy with the previous message, the new message waits in the queue. If at least one client is free, the message goes to the free clients and is dropped for the busy ones. UDP output does not join packets again: a payload longer than one LoRa packet reaches the UDP receiver as several datagrams.

WARNING:

After you save a new Device Function, or switch a conversion option, a matching list, Reply only to sender or Mode C baud switching on or off, the modem keeps working with its old settings until it restarts; its traffic is not stopped. The message after saving lists which settings work at once and which only after a restart. Restart the modem with Reboot Device on the Management page or switch it off and on.

9.1 TCP/IP devices over LoRa

An application on the central side (a SCADA, a PC program, a PLC with a TCP client) reaches a TCP device in the field. Modem A next to the application works as LoRa to TCP/UDP Server Gateway; modem B next to the field device works as LoRa to TCP/UDP Client Gateway and connects to the field device itself.

• Data from the application is collected by A into a message and sent to the target address of A.
• B writes every message it receives to all enabled targets in its list.
• The answer of the field device goes from B to the target address of B. With Reply only to sender checked, B answers the modem the request came from instead; until B has received a request it uses its target address.
• A passes every message it receives to all connected clients.
• The bytes are not changed. Any protocol - Modbus TCP, IEC 60870-5-104, a vendor protocol - passes as it is.

Point to multipoint: set the Tx Device Address of A to 65535 and give every field modem its own device address. Each request then reaches all field modems, so the protocol itself must make sure that only the addressed device answers (for example by the Modbus Unit ID).

NOTE:

Before B connects to a target it checks the target with a ping. A target that does not answer a ping (or a router that blocks it) is shown as HOST UNREACHABLE and is not connected. With UDP Enable (server mode) on A, A also receives UDP datagrams on its UDP Listen Port (5001 from the factory), and every UDP sender takes one of the Maximum Number of Clients places; a UDP sender that stays silent for 5 minutes frees its place. With Maximum Number of Clients 1, the first UDP datagram takes the only place: no TCP client can connect until that UDP sender has been silent for 5 minutes.

9.2 Serial devices over LoRa

RS232 or RS485 devices exchange data over LoRa. Every modem that has a serial device works as LoRa to SERIAL Device Gateway with Enable RS232 or Enable RS485, Baud rate and Line Control set like the device. The central side can also be a TCP application on a LoRa to TCP/UDP Server Gateway modem - the data is the same byte stream.

• The serial master is connected to modem A, the serial slaves to modems B, C, ... With the Tx Device Address of A set to 65535 every request reaches all slave modems; each slave modem sends its answers to the address of A.
• Serial data is collected into a message by the Data Packing rules and written unchanged to the serial port of the receiving modem.
• With Line Control 7_EVEN_1 the parity bit is removed before the radio and created again on the receiving serial port.
• If neither serial port is checked when the function is selected, the page checks Enable RS485.

9.3 Modbus TCP master to Modbus RTU slaves

A Modbus TCP master (SCADA, HMI) reads Modbus RTU slaves in the field. Modem A next to the master works as LoRa to TCP/UDP Server Gateway and passes the Modbus TCP frames unchanged. The field modems work as LoRa to SERIAL Device Gateway with Enable Modbus TCP to RTU Conversion and convert between Modbus TCP and Modbus RTU on their serial line.

1. The master sends a Modbus TCP request to modem A. A sends it over LoRa to its target address - one field modem, or 65535 for all field modems of the group.
2. The field modem turns the request into a Modbus RTU frame: the Unit ID becomes the slave address, function code and data are kept, the CRC is added. The frame is written to the serial line.
3. The modem waits for the answer for Timeout (ms) (100 to 60000 ms, 1000 ms from the factory). An answer with the right slave address, function code and CRC is turned back into Modbus TCP with the transaction ID of the request and sent to the target address of the field modem - set it to the address of A. An exception answer of the slave (for example illegal data address) is passed on the same way, with the exception code of the slave.
4. A passes the answer to the master.

• A field modem handles one request at a time; further requests wait in its queue until the answer or the timeout.
• If no answer comes in time and Exception (0x0B) Enable is checked, the field modem answers with Modbus exception 0x0B (gateway target device failed to respond). Unchecked (the factory setting), it sends nothing.
• Data Packing does not apply and 7_EVEN_1 is not offered in this mode; the page switches the line control to 8_NONE_1. A Baud rate of 300 is raised to 19200 when the page is saved.

NOTE:

If A sends to 65535 and several field modems receive the request, every modem whose slaves do not answer produces its own exception 0x0B when Exception (0x0B) Enable is checked. Use the exception only when each request reaches a single field modem - for example with the routing by Unit ID described next.

NOTE:

The field modem finds the end of an answer from its function code: by the byte count for the function codes 1, 2, 3, 4, 12, 17, 20, 21 and 23 (24: by its two-byte count), as a fixed answer of 8 bytes for 5, 6, 11, 15 and 16, of 10 bytes for 22 and of 5 bytes for 7 and for an exception answer. For function codes without a length field (for example 8 and 43) the answer ends when the serial line has been silent for 35 ms. Every answer must pass the CRC check.

9.4 Modbus routing by Unit ID

Modem A next to the Modbus TCP master sends each request only to the field modem that serves the addressed slave. A works as LoRa to TCP/UDP Server Gateway with Enable Modbus Unit ID to Target Device Matching List. Its Server Listening Port then serves Modbus TCP requests instead of transparent data. With the option checked the page hides UDP Enable (server mode), Maximum Number of Clients and Data Packing, and shows the Modbus Routing Table (Modbus ID to LoRa target) and the Modbus Response Timeout card. The field modems are set up as in the previous scenario.

• The table has 5 rows. A request is sent unchanged only to the LoRa address of the matching row.
• No matching row: A answers at once with exception 0x0A (gateway path unavailable).
• The answer of the field modem is matched by transaction ID and Unit ID and returned to the master. An answer longer than one LoRa packet arrives as several packets; A joins them and returns the complete answer.
• No answer within Timeout (ms) plus a radio margin (4 x 0.5 s at SF5 to SF7, 4 x 2 s at SF8 and SF9, 4 x 4 s at SF10 to SF12): with Exception (0x0B) Enable checked, A answers with exception 0x0B. The checkbox is unchecked from the factory: A then sends nothing and the master runs into its own timeout. Either way A takes the next request.
• A serves one Modbus TCP client and one request at a time; the next request waits in the TCP buffer.

A field modem can also work as LoRa to TCP/UDP Client Gateway connected to a Modbus TCP slave: it passes the request unchanged to its target and the answer back to A, and A returns it to the master. Enable only one target on that modem and set its Tx Group Address and Tx Device Address to the address of A. The first request after a start can take several seconds longer while the field modem opens the connection to its target (about 7 seconds in our measurement); after that a read of 5 registers took about 1.1 seconds at the factory radio settings.

NOTE:

This list and Enable TCP Socket to Target Device Matching List exclude each other: checking one clears the other. At least one row must stay enabled (At least one routing line must be enabled!). The Buffer Status line of the LoRa Status page counts the routed requests and their timeouts.

9.5 Modbus RTU master to remote slaves

A Modbus RTU master on a serial line (a PLC, an HMI, a data logger) reads slaves that sit behind other modems. Modem A next to the master works as LoRa to SERIAL Device Gateway with Enable Modbus RTU Master to TCP Conversion and uses the same Modbus Routing Table (Modbus ID to LoRa target) as the routing by Unit ID.

1. A closes a request when the serial line is silent for 35 ms and checks its CRC (4 to 256 bytes).
2. A finds the routing row for the slave address, wraps the request into Modbus TCP and sends it to the LoRa address of that row. No row: A answers the master at once with exception 0x0A.
3. The remote modem - a LoRa to SERIAL Device Gateway with Enable Modbus TCP to RTU Conversion and RTU slaves - answers. Its target address must be the address of A.
4. A turns the answer back into Modbus RTU with CRC and writes it to the master.
5. No answer within Timeout (ms) plus the radio margin: exception 0x0B to the master if Exception (0x0B) Enable is checked, otherwise nothing.

NOTE:

If the master repeats a request before the answer has arrived, the new request replaces the old one. This option excludes Enable Modbus TCP to RTU Conversion and Mode C baud switching on the same modem.

9.6 TCP socket to target device mapping

Several applications on the central side each talk to their own field device, with a protocol that has no address of its own. Modem A works as LoRa to TCP/UDP Server Gateway with Enable TCP Socket to Target Device Matching List. Every row of the TCP Socket to Target Remote Device List opens its own listening TCP port and belongs to one LoRa target.

• The list shows as many rows as Maximum Number of Clients on the Network Settings page, up to 10. Each row accepts one client. Server Listening Port is not used while the list is on.
• Data received on the port of a row is sent only to the LoRa address of that row.
• An answer from the LoRa address of a row is passed only to the client of that row. An answer from an address that is not in the list goes to all connected clients.
• The field modems are LoRa to TCP/UDP Client Gateway or LoRa to SERIAL Device Gateway modems whose target address is the address of A.

NOTE:

If a row uses another group than the Group Own Address of A, the page shows a yellow GROUP MISMATCH band: answers from that group only come back if the field modem is set up for it. The list works only with the server function; with any other function it is switched off when the settings are saved.

9.7 Extending the range with a LoRa Repeater

A modem in the middle extends the distance between two modems that cannot hear each other. The middle modem R works as LoRa Repeater; it has no Ethernet or serial function.

• R sends every data packet it receives again, unchanged, to its own target address (Tx Group Address / Tx Device Address). Repeated packets are always sent unacknowledged.
• A payload that R has repeated is not repeated again if the same payload arrives within 5 s (SF5 to SF7), 20 s (SF8, SF9) or 40 s (SF10 to SF12). This stops packets from circling between repeaters. A master that sends exactly the same request again within this time gets the second copy dropped by R. Buffer Status counts these drops.
• Discovery, ping, link test and remote node frames are not repeated: these tools reach only the modems in direct radio range.

NOTE:

R has one target address (Tx Group Address / Tx Device Address) for both directions. Plan the addresses so that requests and answers both reach their destination.

9.8 Joining two LoRa networks over Ethernet

Two LoRa networks far apart exchange data over a LAN or WAN. Modem A in network 1 works as LoRa to TCP/UDP Server Gateway; modem B in network 2 works as LoRa to TCP/UDP Client Gateway with the IP address of A as Target IP and the Server Listening Port of A as Target Port.

• Data that A receives over LoRa goes over the TCP connection to B, and B sends it over LoRa to its target address in network 2. The other direction works the same way.
• Each network keeps its own radio settings and addresses; only the IP path joins them.
• B pings A before it connects: firewalls and routers between them must let the ping and the TCP connection through.

9.9 Meter reading with IEC 62056-21 Mode C

A meter reading program on the central side reads electricity meters through an optical probe or a serial meter port. Modem A next to the program works as LoRa to TCP/UDP Server Gateway; modem B at the meter works as LoRa to SERIAL Device Gateway with Enable IEC 62056-21 Mode C Baud Switching. B follows the Mode C handshake and changes its serial baud rate to the speed the meter offers.

1. When you save the Operating Mode page with the option newly switched on, the modem sets the serial settings once to 300 baud, 7_EVEN_1 and the delimiter rule off. These values stay editable. Like the option itself, they work after a restart.
2. The program sends the sign-on request; B writes it to the meter at the base baud rate.
3. B reads the speed code (the fifth character) of the identification line of the meter: 0 to 6 mean 300, 600, 1200, 2400, 4800, 9600 and 19200 baud.
4. When the program sends the acknowledgement with the same speed code, B switches the serial port to that speed as soon as the acknowledgement has left the port. The readout follows at the new speed.
5. B returns to the base baud rate on the next sign-on request, or when the line has been silent for Mode C Idle Revert (s) (2 to 255 s, 10 s from the factory).

NOTE:

The sign-on request and the acknowledgement must each reach B as one LoRa message; the idle timeout of Data Packing on A normally ensures this. Keep the delimiter rule off for meter reading: with it on, every line of the readout becomes a separate radio message. Mode C works only with plain transparent serial and cannot be combined with the Modbus options.

10.1 Connecting to the Web Interface

All settings of the modem are made with a web browser over the Ethernet port. Every page of the interface is protected by a user name and a password.

10.1.1 Factory network state

A factory modem asks for its address by DHCP: Use Static Address for Device and DHCP Server Enabled are both off. The stored address fields are used as the fall-back address:

If no DHCP server answers, the modem uses the stored address as its fall-back address. In this state it has no gateway: Server Gateway Address is the gateway of the modem only with a static address (as DHCP server the modem uses its own address as gateway and hands the field to its clients), so the modem can then be reached only from its own network. With the factory address 192.168.1.1 and the cable connected it waits up to one minute for a DHCP answer before its data services start on the fall-back address. With another stored Server IP Address the data services start on that address without this wait.

NOTE:

A modem that started on the fall-back address and receives a DHCP address later restarts once by itself and then works with the new address. The same happens when the DHCP server hands out a different address.

10.1.2 Find the address with the abcZ Network Tool

The abcZ Network Tool lists the REDZ devices of a network with their address, MAC address, product and firmware version, so the modem can be found without knowing its address.

1. Connect the PC to the same network as the modem. Start the abcZ Network Tool and open the Discovery tab.
2. Type the network in IP range, for example 192.168.0.0/24 for the addresses 192.168.0.1 to 192.168.0.254. Leave User and Password at the factory values (admin / admin) unless the password of the modem was changed.
3. Click Scan (HTTP). Each modem that answers appears as a row, with its address in IP and its MAC, Product and Version.
4. Find your modem by its MAC address and double-click the row: the web interface of the modem opens in the browser. The same MAC address is shown in the header of every page of the web interface.

A modem with another password is listed with "auth required (password?)" in Product - type its password and scan again. Discover (UDP) is a faster alternative inside the same subnet. The tool is described in full in chapter 17 "Software - abcZ Network Tool".

10.1.3 Login

1. Type the address of the modem into the address line of the browser, for example http://192.168.1.1.
2. The browser asks for a user name and a password. The user name is always admin; the factory password is admin.
3. The Operating Mode page opens.

WARNING:

Change the password after the first login: page Management, card Change Password.

10.1.4 Page header and menu

The header of every page shows the product name, the firmware version, the build date of the firmware and the MAC address of the modem.

The menu on the left has eight entries. Seven are always present; Serial Settings appears only when the Device Function is LoRa to SERIAL Device Gateway.

• On a narrow screen the menu is hidden behind the menu button at the top.
• Many field names show a short help text when the mouse pointer rests on them.

10.1.5 Saving and the answer of the modem

The Save Configuration button of a page is disabled until a value on that page has been changed. After a click a waiting window is shown while the modem stores the settings, then a message window with an OK button reports the result. The success message appears only after the modem has stored the values and answered.

WARNING:

Restart the modem after every save on Operating Mode, Network Settings and Serial Settings: open Management and press Reboot Device, or switch the power off and on. The device function, the serial interface, baud rate and line control and the network addresses are used only after the restart. Some other values (for example Data Packing, Modbus Response Timeout, the routing table and the list targets) are used at once, so until the restart the modem runs with a mix of old and new settings.

NOTE:

A save made while the modem is already restarting is refused and nothing is stored. Wait until the modem is back and save again.

NOTE:

A value the modem does not accept (for example a number out of range) is not stored; the modem keeps its previous value and stores the other values of the page, and the success message adds the warning shown in the table. If every value sent was rejected, the page reports that the save failed ("Rejected: all ... value(s) out of range - nothing saved") and nothing was stored. The page keeps showing the rejected value until it is reloaded.

10.1.6 Reset buttons

Holding one of the reset buttons of the modem for more than 5 seconds restores the factory settings and restarts the modem, see 5.4 "Reset Buttons". After the restart the modem is in the factory network state described above and the password is the factory password (admin).

10.2 Operating Mode

On this page you choose what the modem does (the device function) and set the options of that function. Cards that do not belong to the selected function are hidden. The cards and the menu follow the function selected on the page at once, before you save and before the restart. The Device Status page always shows the function the modem is running.

10.2.1 General fields

10.2.2 Device functions

NOTE:

The Serial Settings menu appears only for LoRa to SERIAL Device Gateway. The server port fields on Network Settings appear only for LoRa to TCP/UDP Server Gateway.

10.2.3 LoRa to TCP/UDP Server Gateway

Two check boxes choose how data from the network side is addressed on LoRa. Only one of them can be on; checking one clears the other. With both off, everything goes to the target set on the LoRa Settings page.

10.2.4 TCP Socket to Target Remote Device List

The list has 10 rows. Only as many rows are shown and used as Maximum Number of Clients on the Network Settings page; save that page and reload this one to see more rows.

Data from a client connected to the port of a row is sent to that row's target. A LoRa message coming back from that target is delivered only to the client of the same row. A LoRa message from a device that is not in the list is delivered to all connected clients.

NOTE:

If a row uses a group address different from the modem's own group address (set on LoRa Settings), an amber GROUP MISMATCH band appears at the top of the page. It is a warning only: answers from another group reach this modem only if the remote side is set up for it.

10.2.5 Modbus Routing Table (Modbus ID to LoRa target)

Used with Enable Modbus Unit ID to Target Device Matching List (server gateway) and with Enable Modbus RTU Master to TCP Conversion (serial gateway). Each of the 5 rows sends the requests for a range of Modbus Unit IDs to one remote modem. The remote modem serves its local Modbus RTU devices with Enable Modbus TCP to RTU Conversion.

Factory content of row 01: Unit IDs 1 to 247 to group 1, device 1. When the routing is switched on and no row is enabled, row 01 is enabled automatically. At least one row must stay enabled; the page refuses to save otherwise ("At least one routing line must be enabled!").

A request whose Unit ID matches no enabled row is answered at once with Modbus exception 0x0A (gateway path unavailable). If the ranges of enabled rows overlap, the first matching row (lowest number) is used.

10.2.6 Modbus Response Timeout

In all three modes exception 0x0B is sent only when Exception (0x0B) Enable is checked. With the check box cleared, a request that is not answered in time gets no answer from the modem; the master then runs into its own timeout.

10.2.7 Data Packing

Data arriving from the network or serial side is collected and sent over LoRa as one packet. These rules decide when a packet is closed and sent. A value of 0 switches a rule off. A packet is always closed at the size of one radio fragment: 229 bytes on 868 MHz models, 109 bytes on 2.4 GHz models.

NOTE:

If you switch all three rules off, the modem sets Idle Timeout (ms, 0=off) back to 100 ms when the page is saved; otherwise short messages would wait in the buffer for ever. The page still shows 0 until it is reloaded.

10.2.8 TCP/UDP Client Settings

Shown for LoRa to TCP/UDP Client Gateway. The modem opens the connections to the targets in this table itself.

Reply only to sender (check box at the top of the card): data from the targets goes back over LoRa to the modem that sent the last request, instead of the fixed target on the LoRa Settings page. Until the first request has been received, the LoRa Settings target is used. Use it when more than one master polls through this modem. A change is used after the restart. Factory default: off.

NOTE:

Data received over LoRa is sent to every enabled target. The connection state of each target is shown on the Device Status page under TCP Client Status.

10.2.9 LoRa to SERIAL Device Gateway options

With all three check boxes off the serial gateway is transparent: bytes pass unchanged between the serial line and LoRa. Each check box adds a special function; only one of them can be on.

Mode C Idle Revert (s): idle time after which the serial line returns to the base baud rate, 2 to 255 seconds, factory default 10. Shown only when Mode C is checked.

NOTE:

When Mode C is switched on and saved, the modem sets the serial port once to the usual Mode C base values: 300 baud, 7_EVEN_1, and Delimiter Enable off. You can change them afterwards; your values are kept. Keep the delimiter off for meter reading: with it on, every line of the readout becomes a separate radio message. The pages show the new values only after they are reloaded: reload the browser page before you save again, otherwise the next save writes the old values back (for example Delimiter Enable on).

NOTE:

With one of the two Modbus options, 7_EVEN_1 is not available on the Serial Settings page. If the serial line was set to 7_EVEN_1 it is changed to 8_NONE_1, and a baud rate of 300 is changed to 19200, when the page is saved. Reload the browser page to see the changed values.

10.2.10 Saving the Operating Mode page

1. Change the values. Save Configuration becomes active.
2. Press Save Configuration. The page shows "Saving Operating Mode..." and sends all fields of the page, including the hidden cards, to the modem.
3. The modem stores the values and the page reports "Operating Mode saved.". The message lists what is used at once - Data Packing, Modbus Response Timeout with its exception check box, the routing table, Mode C Idle Revert (s) and the target group and device addresses of the list - and what is used only after the restart: the device function, the mode check boxes, Reply only to sender, the TCP/UDP Client Settings table and the Device Name as network host name. The Device Name itself is stored at once. A changed list TCP Port can be used before the restart when its listening port is opened again. If the modem refused the request, the page reports "Operating Mode Change Failed!" with the reason.
4. Restart the modem with Reboot Device on the Management page.

WARNING:

The modem does not restart by itself. Until it is restarted it keeps working, without a pause in the traffic, with the device function it started with, although the page already shows the new selection. Restart the modem soon after saving.

NOTE:

When you save the page with LoRa to SERIAL Device Gateway and no serial interface is enabled - always the case when you come from another device function - the modem selects RS485, 19200 baud and 8_NONE_1. After the restart, open Serial Settings and check the interface, baud rate and line control before connecting the serial device.

10.3 Network Settings

This page sets the address of the modem, the time server and, for the server gateway, the listening port. Some fields appear only for certain device functions or models.

10.3.1 NTP Settings

NTP Server IP or URL: the time server the modem asks for the time (UTC). Enter an IPv4 address or a host name. The field takes up to 63 characters and must not be empty; use a name of 30 characters or less, because the time client of the modem uses only the first 30 characters. Factory default: pool.ntp.org. A new name takes effect after a restart.

The modem compares its clock with the time server 10 minutes after start-up and then every hour. If the difference is 5 seconds or more, the clock is corrected without a restart. The modem needs a working gateway and DNS server to reach a time server given by name. With a static address, set Server Gateway Address and the DNS addresses (Primary DNS Address, Secondary DNS Address) on this page; the modem uses both DNS addresses. In DHCP address mode the DHCP server of the network supplies them. While the modem runs the DHCP server it cannot reach a time server outside its own network.

NOTE:

The modem clock runs in UTC: the time server gives UTC, and there is no time zone setting. Set Device Time on the Management page sends the local time of the PC; while a time server answers, the modem sets its clock back to UTC at the next check.

10.3.2 Device Network Settings

Each address is entered as four numbers of 0 to 255.

The two boxes exclude each other. If the stored settings (for example after a firmware update) or a configuration file have both set, the modem keeps the static address and switches the DHCP server off.

10.3.3 DHCP server

With DHCP Server Enabled the modem serves the network it is connected to:

• Addresses are handed out upwards from DHCP Server Range Start Address. The start address must lie in the network given by Server IP Address and Server Net Mask and must be higher than Server IP Address (for example modem 192.168.1.1, start 192.168.1.100).
• Up to 15 clients are served. A lease lasts 20 minutes.
• The clients receive Server Net Mask as their mask, Server Gateway Address as their gateway and Primary DNS Address as their DNS server; an address set to 0.0.0.0 is not handed out. These values are taken at start-up. The modem itself does not forward traffic and does not answer DNS queries: give the address of a router of this network as gateway if the clients must reach other networks.
• The modem itself still uses its own address as gateway in this mode, so it cannot reach devices outside this network (for example a time server elsewhere); Server Gateway Address only goes to the clients.

WARNING:

Run only one DHCP server on a network. Do not enable the DHCP server when the modem is connected to a network that already has one, for example behind a router.

NOTE:

The page notes that UDP output does not keep message boundaries: data larger than one radio fragment (229 B on the 868 MHz models, 109 B on the 2.4 GHz models) arrives as several datagrams.

10.3.4 Saving the Network Settings page

1. Change the values. Save Configuration becomes active.
2. Press Save Configuration. The page shows "Saving Network Settings..."; after the modem has stored the values it reports "Network Settings Changed." with the request to reboot the modem, or "Cannot change Network Settings.".
3. Restart the modem with Reboot Device on the Management page.

WARNING:

Restart the modem after saving this page. The new address is used only after the restart; some other values, such as Server Listening Port and Maximum Number of Clients, can already be used before it when connections are opened again. Write the new address down before you restart: if the modem moves to another network or address, the browser has to be pointed to the new address, and the PC may need an address in the new network. If the address is lost, the abcZ Network Tool finds the modem on the network (chapter 17 "Software - abcZ Network Tool").

10.4 Serial Settings

This page appears only when the device function is LoRa to SERIAL Device Gateway. It sets the serial port of the modem.

Baud rates offered: 300, 600, 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200, 230400, 460800.

Line control choices: 7_EVEN_1 (7 data bits, even parity, 1 stop bit; first in the list when it is offered), 8_NONE_1, 9_NONE_1, 8_EVEN_1, 8_EVEN_2, 8_ODD_1, 8_ODD_2, 8_NONE_2, 9_NONE_2. 7_EVEN_1 is offered only for the transparent serial gateway, not with the Modbus options.

NOTE:

Saving Operating Mode with another device function clears both interface check boxes in the stored settings. Saving it with LoRa to SERIAL Device Gateway while no interface is enabled selects RS485, 19200 baud and 8_NONE_1. The check boxes on this page show the stored interface.

1. Change the values. Save Configuration becomes active.
2. Press Save Configuration. The page shows "Saving Serial Settings..." and then "Serial Settings Changed." with the request to reboot the modem, or "Cannot change Serial Settings.".
3. Restart the modem with Reboot Device on the Management page.

WARNING:

The serial port is set up only at start-up. The new interface, baud rate and line control are used after the restart.

10.5 Device Status

This page shows the state of the modem and its traffic counters. The values are read each time the page is opened from the menu and each time Refresh Status is pressed; they are not updated by themselves.

Which counters and connection tables are shown depends on the device function the modem is running, that is the function it had at its last start, not on the selection on the Operating Mode page.

Under the page title a line shows the time of the last refresh, taken from the clock of the PC.

NOTE:

A red band at the top of the page means the LoRa addresses of the modem are still at their factory values ("FACTORY DEFAULTS - device not configured!" or "LoRa addresses are at FACTORY values"). Two modems with factory addresses disturb each other: set the addresses on LoRa Settings. The band can be hidden with the cross at its right end until the page is reloaded.

10.5.1 Health summary

Below the title four boxes summarise the state of the modem. A coloured dot in each box shows the result: green = normal, amber = worth a check, red = fault, grey = no data yet or not used.

10.5.2 IP Address and App Status

Several of these texts can appear at the same time.

10.5.3 Automatic restarts

The modem restarts itself in the following cases; the radio module checks are listed in chapter 18 "Logs and Troubleshooting". The counters on this page start from 0 again after such a restart.

NOTE:

The count of repeated restarts is cleared when a client connects or a target is reached (service cases), when the gateway answers again (gateway case) or when a serial Modbus device answers correctly (serial cases, with Enable Modbus TCP to RTU Conversion). Reboot Device on the Management page clears every count and lets the modem try again. A modem in DHCP address mode that has not yet received any DHCP address since its start (for example a factory modem on a direct cable) does not run the gateway check. See chapter 18 "Logs and Troubleshooting" for the complete list of self-checks and the log messages they write.

10.5.4 Communication Counters

Log Counter and Log Status are shown only when logging is switched on (Log Level other than NONE on the Management page). Log Counter is the number of log lines sent to the console or the UDP log server; Log Status is the internal state of the log output, for support.

NOTE:

For LoRa Repeater the page shows the module counters, N. of LoRa Messages Received Correctly and N. of Gateway Messages Sent Correctly; the latter stays 0 because a repeater has no network or serial output. The repeated messages are counted, but the counters for them are not shown. Copies dropped by the repeater are counted on the LoRa Status page.

10.5.5 TCP Connections

Shown while the modem runs as LoRa to TCP/UDP Server Gateway. One row per connected client; with Modbus Unit ID routing one row for the Modbus TCP client. The table is read again with every refresh.

Without a connection the table shows "no client connected" (with Modbus Unit ID routing: "no Modbus client connected").

10.5.6 TCP Client Status

Shown while the modem runs as LoRa to TCP/UDP Client Gateway. One row per enabled target of the TCP/UDP Client Settings table, read from the modem with every refresh: Target (address and port), Type (TCP or UDP), State, Last activity, and the bytes sent to the target (Bytes out) and received from it (Bytes in) since the last start. Without an enabled target the table shows "no target enabled". The states:

The targets are brought up one after the other, so with a long list it takes a while until every row shows CONNECTED. A target that drops is retried automatically; a retry can take a few minutes.

10.5.7 System Diagnostics

The System Diagnostics card (memory figures, start-up diagnostics and recovery counters) is a service display and is hidden in the standard firmware.

10.5.8 Buttons

NOTE:

All counters start from 0 after every restart of the modem.

10.6 LoRa Settings

The page LoRa Settings holds the radio settings of the modem: its own LoRa address, the default target address, the radio parameters and the AES encryption. The settings are stored with Save Configuration. The own addresses, the radio parameters, Listen Before Talk and the AES encryption are used by the radio after the next restart of the modem. Tx Group Address, Tx Device Address and Acknowledged Transmission (C-Data) take effect as soon as they are saved.

NOTE:

Some labels show a short help text when the mouse pointer rests on them: Listen Before Talk, C-Data, AES encryption and key on this page, and Buffer Status, Link Test and Remote Node on the page LoRa Status.

NOTE:

Some radio parameters are kept at their factory values and are not shown on the page: the radio mode (standard mode with address filtering), the receiver control (receiver always on), the LED control, the packet format (received packets carry signal strength, signal-to-noise ratio and a time stamp) and the power saving mode (off). The values shown on LoRa Status rely on this packet format.

10.6.1 Address Settings

NOTE:

Do not use 255 as Group Own Address or 65535 as Device Own Address: these values are reserved as broadcast addresses. The page accepts them, but they are not valid own addresses.

A modem is reached over the radio by the pair group address / device address. Two modems that exchange data point at each other: the Tx addresses of one modem are the own addresses of the other. The target lists on the page Operating Mode can select another target for some connections; without such a list every message goes to the Tx addresses set here.

NOTE:

When Tx Device Address is changed from 65535 to a single modem and saved, the modem also turns on Acknowledged Transmission (C-Data) once. Whenever C-Data is turned on, by this rule or by hand, the 868 MHz models also turn on Listen Before Talk (LBT) once. Both can be turned off again afterwards. The page does not show these automatic changes at once: the boxes stay unchecked until the page is reloaded, although they are stored as checked.

10.6.2 Radio Settings

The radio card differs by frequency band. The 868 MHz models (TLM154, TLM254, TLM655) and the 2.4 GHz models (TLM194, TLM294, TLM695) show different fields and different value ranges. The fields that set the radio channel must be the same on all modems that talk to each other.

The fields marked "LoRa only" are shown when Modulation is LoRa; when another modulation is selected they are hidden and the fields of that modulation appear instead.

A frequency outside the range of the model is not accepted: the page shows a message and puts the previous value back.

Listen Before Talk (LBT) makes the radio check that the channel is free before it transmits and wait while another device is sending. It is useful when several devices share the channel or at high spreading factors, where one frame occupies the air for a long time. The threshold is -90 dBm and is not shown on the page. On the 2.4 GHz models the row is not shown: their radio module listens before talk by itself and has no setting for it.

With Acknowledged Transmission (C-Data) the receiving radio confirms every frame sent to a single modem, and a frame that is not confirmed is sent again, up to 3 attempts in all. If the third attempt is not confirmed either, the whole message is dropped and counted as "LoRa TX fail-drop" under Buffer Status. Messages to 65535 (broadcast) are always sent without confirmation, and in the LoRa Repeater function the option is not used. A receiving modem accepts both kinds of frames, so modems with and without this option work together.

NOTE:

If only the confirmation is lost, the frame is sent again and arrives twice. An application that cannot accept a repeated message must filter repeats itself.

10.6.3 AES Encryption

With AES Encryption/Decryption Enabled the payload of every LoRa frame is encrypted with a 128-bit key. The field Encryption Key appears when the box is checked. Type the key as 32 hexadecimal digits; a leading 0x and the separators - or : are ignored, and a shorter value is filled up with leading zeros. The page shows the key as 16 pairs of digits separated by -.

All modems that must read each other's traffic need encryption turned on and exactly the same key. Frames encrypted with another key are received by the radio but cannot be decrypted and are dropped. Encryption keeps the content secret; it does not decide which modems may send: a modem with encryption on still accepts unencrypted frames from other modems. Use the lists on the page Security Settings for that.

WARNING:

Every modem leaves the factory with the same key. When you use encryption, enter your own key. The key can be read by everyone who can log in to the web interface and is part of the downloaded configuration file.

10.6.4 Saving

1. Change the values. Save Configuration becomes active as soon as a value differs from the stored one.
2. Click Save Configuration. The page shows LoRa Settings Changed. and the note that a reboot is required: the modem keeps working with the previous radio settings until it is restarted.
3. Restart the modem (Reboot Device on the page Management). The radio is set up with the new values during the start.

NOTE:

Only the settings of the radio module wait for the restart: own addresses, radio parameters, Listen Before Talk and AES encryption. New Tx addresses and the C-Data setting are used at once, although the page asks for a restart after every save on this page. The card Module Information on the page LoRa Status shows the own addresses the radio is really using.

NOTE:

A save that arrives while the modem is already restarting is refused and nothing is stored: the page shows Cannot change LoRa Settings. followed by the reason given by the modem. Wait until the modem has started again and save once more. If the modem refuses only some of the values, the confirmation adds a warning that names how many values kept their previous setting; the other values are saved.

10.7 LoRa Status

The page LoRa Status shows what the radio receives and offers test tools for the radio link. The values are read when the page is opened and each time Refresh LoRa Status is clicked; they are not updated on their own. The time of the last update is shown under the page title.

10.7.1 Module Information

10.7.2 Latest Message Received - LoRa Side

10.7.3 Latest Message Received - Gateway Side

The last message the modem received on its Ethernet or serial side for transmission over the radio, in hexadecimal (Payload in Hex) and as text (Payload As ASCII). The card is not shown in the LoRa Repeater function.

10.7.4 Buffer Status

10.7.5 Device Connections over LoRa

A table with one row for each remote modem heard over the radio, up to 32 modems. Its columns are the signal strength and signal-to-noise ratio of the last packet (RSSI, SNR), their running averages (R-avg, S-avg), the number of packets received (RX), the group and device address of the remote modem, the seconds since its last packet (Age) and Details. Details shows, for modems that answered a connection request, the radio module ID, the device function of the remote modem and the IP addresses connected to it.

Request LoRa Connections sends a connection request over the radio to every modem of the group set in Tx Group Address (not to other groups). The request is sent several times. The page waits 25 seconds (Request LoRa Communication List in Progress) and then refreshes the table with the answers. The modem also sends such a request once by itself about one minute after it was switched on or restarted by the user (Reboot Device, Reboot Alternative Firmware, a configuration upload, a change of the log settings or a factory reset), as soon as it is in normal operation, no data is waiting to be sent and no radio frame has been received for 10 seconds. After any other restart (for example one ordered over the radio with Reboot from another TLM, or one the modem made on its own) it does not send this request; click Request LoRa Connections when you need the Details column.

10.7.6 Remote Ping (device on remote TLM network)

Checks a device on the Ethernet network of a remote TLM. Enter the group and device address of the remote TLM and the IP address to ping in Target IP, then click Ping. The remote TLM pings that IP address on its own network and sends the result back over the radio. The result line shows:

NOTE:

When the modem refuses Request LoRa Connections, a Remote Ping, a Link Test or a Remote Node request, the page shows Request Failed. followed by the modem's reason in brackets, and for the last three the result line shows Not sent. Reasons: an invalid group or device address, the radio out of service, a link test already running. If Target IP is not a valid IP address, the reason shown speaks of "no recognized field in request"; check the Target IP. If the modem does not answer at all, the result line shows No confirmation from the device.

10.7.7 Link Test (site survey)

Measures the radio link to a remote TLM. Enter its group and device address and the number of test frames in Probe Count (1 to 50), then click Start. The modem sends the test frames one after the other; the remote TLM answers each one with the signal values it measured. A frame without answer counts as lost after 3 seconds (SF5 to SF7), 12 seconds (SF8, SF9) or 24 seconds (SF10 to SF12).

For Remote Ping and Remote Node the page stops asking for a result after 3 minutes; for Link Test it waits the number of probes x 24 s + 30 s, but at least 3 minutes, whatever the spreading factor. It then shows "No result - polling stopped (timeout)." in the result line.

NOTE:

For a fair loss figure, run the test with Acknowledged Transmission (C-Data) turned off on both modems: with it on, lost frames are repeated by the radio and the test shows fewer losses than the link really has.

10.7.8 Remote Node (remote TLM management)

Reads the identity of a remote TLM or restarts it over the radio. Enter its group and device address.

NOTE:

Read Info reports the device function the remote TLM is running; the other values are its stored settings, so settings saved there but not yet applied by a restart already appear. With a long device name the end of the summary is cut off.

With the device address 65535 or the group address 255, Reboot is a group restart: every TLM of that group (65535), every TLM with that device address in all groups (255), or every TLM in reach (both) receives the request, acknowledges it and restarts. The page then asks a second time and names the case, for example This will restart ALL modems in ALL groups that hear the broadcast. Continue? Only after the second confirmation is the request sent. Before it asks, the page checks the two addresses: the group must be a number from 1 to 255 and the device a number from 1 to 65535.

WARNING:

Reboot restarts the remote TLM: its data connections are interrupted until it has started again; a group restart interrupts every TLM it reaches at the same time. A remote TLM carries out these requests from any TLM that can reach it over the radio; no password is asked. The only protection is the White List / Black List of the remote TLM (page Security Settings), which applies to Remote Ping, Link Test, Read Info and Reboot as well. Remote configuration changes are not possible.

NOTE:

For Remote Ping (device on remote TLM network), Link Test (site survey) and Read Info enter the address of one TLM. With 65535 every TLM of that group in reach answers, and the results of several modems are mixed. Enter group addresses from 1 to 255 and device addresses from 1 to 65535 only. For these three tools the page does not check the fields; the modem refuses a value that is not a number or is above 255 / 65535: nothing is sent and the page shows Request Failed. with the reason. Group 0 and device 0 are not refused.

10.8 Security Settings

The page Security Settings limits which remote modems this modem accepts radio data from. The filter compares the device address of the sender of every received LoRa frame with a list of up to 20 addresses; the group address is not compared.

Only one list can be active: checking one box clears the other, and the table of the checked list appears. Enter each device address as a number; the page converts it to the hexadecimal form 0x0000 to 0xFFFF. Unused rows stay at 0x0000.

Click Save Configuration. The page confirms with Security Settings Changed. The lists are applied at once; no restart is needed. If the save fails, the page shows Cannot Change Security Settings. followed by the reason given by the modem.

NOTE:

Enter the Device Own Address of the remote modems. Because only the device address is compared, a listed address counts for that address in every group.

NOTE:

The password of the web interface is changed on the page Management, card Change Password.

10.9 Management

The page Management sets the clock, updates the firmware, saves and loads the configuration, changes the password, sets the log output and restarts or resets the modem.

10.9.1 Set Device Time

Time At Start shows the clock of the modem as the modem last read it; Current Local Time shows the clock of the PC when the page was opened. Set Device Time sends the local time of the PC at the moment of the click to the modem and sets its clock while the modem keeps running; it does not restart. The page confirms with Device time has been set. Time At Start shows the new time after the page is reloaded.

If the time cannot be set the page shows Set Device Time Failed! followed by the reason given by the modem, for example "Rejected: reboot in progress - time NOT set" when the modem is just closing down for a restart. The date of the PC must lie in the years 2000 to 2063.

NOTE:

The modem has no time zone setting. When a time server is set on the page Network Settings and reachable, the modem compares its clock with it once an hour and corrects it when the difference is 5 seconds or more. The time server gives UTC, so a local time set with this button is changed back to UTC at the next check. Without an answer from the time server a time set by hand stays as it is.

10.9.2 Live Firmware Update

The modem holds two firmware images: the running one and an alternative one. A firmware update loads a new image into the alternative area while the modem keeps working with the running firmware; the modem changes over only when you click Reboot Alternative Firmware.

WARNING:

The modem does not check which model a firmware file was made for. It also accepts the file of the other frequency band or of the model with or without BPL. Always select the file of your model from the table above.

1. Click Select Firmware File and choose the .binimg file of your model. Its name appears in Firmware file to upload.
2. Click Upload Firmware. A window shows the upload in percent and then Checking... while the modem writes and checks the image. The running firmware is not changed and the modem does not restart.
3. Wait for the result "Firmware Uploaded" in the bar and press Close. Alternative Firmware Version and Alternative Firmware Date now show the new image and Reboot Alternative Firmware becomes active.
4. Click Reboot Alternative Firmware and confirm Reboot into the ALTERNATIVE firmware? The device will switch firmware banks. The modem restarts with the new firmware (see the warning below).

In our measurement on a TLM154 (868 MHz) the upload took about 12 seconds. After Reboot Alternative Firmware the modem stopped answering after about 8 seconds and the web page answered again about 11 seconds after the click. Reload the page yourself about 15 seconds after the click and check the firmware version.

After a failed or interrupted upload the alternative area is marked as invalid; Reboot Alternative Firmware is then refused with Alternate Firmware Boot Failed! and the reason given by the modem. Upload the file again.

Alternative Firmware Version and Alternative Firmware Date show the firmware in the alternative area; they stay empty while that area holds no valid image. Reboot Alternative Firmware is active only while that area holds a valid image.

WARNING:

Reboot Alternative Firmware restarts the modem a few seconds after the confirmation and starts the other firmware; all connections are interrupted during the restart. The page shows Rebooting... and reloads itself after 5 seconds; if it still shows the old firmware, reload it again once the modem answers. The current settings are taken over only when the first two numbers of the two firmware versions are the same (for example 3.00.x); otherwise the other firmware starts with its own stored settings. The firmware that ran before stays in the modem as the alternative firmware, so you can switch back the same way.

10.9.3 Download / Upload Configuration

Download Current Configuration saves all settings of the modem in a file named ZTG_<device name>_v<firmware version>.zcfg. The file starts with an identification block that names the product, the firmware version and the device name.

WARNING:

The configuration file contains the password of the web interface and the AES key in plain text. Keep it in a safe place.

Upload Configuration File opens a file dialog. The upload starts as soon as a file is selected; there is no further question. Settings that are not in the file keep their current values. A radio carrier frequency in the file outside the range of the model is replaced with the factory frequency. While the file is being read the modem sends nothing over LoRa; if the upload breaks off, sending starts again after at most 60 seconds. Before anything is stored the modem checks the identification block and the content of the file; a file that is refused is not stored at all, and the modem keeps its settings:

The page does not reload by itself after the answer: press Close and reload the page after the restart.

WARNING:

An accepted configuration file restarts the modem about 1.5 seconds after the answer. If the file contains other network settings or another password, the modem is reached at the new address and with the new password afterwards (to find the address of a modem, see chapter 17 "Software - abcZ Network Tool").

10.9.4 Change Password

Change Password becomes active when all three fields are filled and the confirmation matches. The new password is valid at once, without a restart; the page confirms with Password Changed, Next time you login, please use new password. From the next request on, the modem accepts only the new password; when the browser asks for the login, enter the new password.

If the change is refused the page shows Error! Cannot change password. with the reason: "Rejected: current password is incorrect - password NOT changed", "Rejected: new password is empty - password NOT changed" or "Rejected: new password and confirmation do not match - password NOT changed".

WARNING:

Change the factory password after the first login. A forgotten password is set back to admin by a factory reset; without the password use the reset buttons of the modem (5.4 "Reset Buttons"), which do the same as Restore Factory Configuration. The password is also part of the configuration file: uploading a configuration file sets the password stored in that file.

10.9.5 LOG

The log records what the modem does, for troubleshooting. ERROR writes only errors, INFO adds normal events, DEBUG writes everything. With NONE the output fields are hidden. UDP Server Port and UDP Server IP are shown only with UDP SERVER; the modem then sends every log line as a UDP message to the given address and port.

The page checks the entries: a wrong address is answered with You have entered an invalid IP address! and a wrong port with UDP Port should be a number between 1 and 65535; the field then returns to its previous value. How to receive and read the log (console settings, UDP listener and firewall, line format) is described in chapter 18 "Logs and Troubleshooting".

WARNING:

Change Log Level and Reboot stores the log settings and restarts the modem about 1.5 seconds later; connections are interrupted during the restart. The page shows Rebooting... and reloads itself after 5 seconds. If the stored values do not change (for example the same address typed in another form), the page reports Log settings unchanged - no reboot needed. and the modem does not restart.

10.9.6 Restore / Reboot

WARNING:

Reboot Device starts the restart about 1.5 seconds after the confirmation, in every operating state of the modem (also while it waits for a network or for its targets); all connections are interrupted until the modem has started again. The page reloads itself after 5 seconds; if the modem is not back yet, the browser may show an error - reload the page a little later.

WARNING:

Restore Factory Configuration erases ALL settings - operating mode, network, serial, LoRa, security lists, log settings and the password (back to admin). After the restart the modem asks for its IP address by DHCP; a static address that was set before is gone, and without a DHCP server it uses 192.168.1.1. The page reloads itself after 5 seconds at the old address and may not find the modem there: find it by its MAC address with the abcZ Network Tool (chapter 17 "Software - abcZ Network Tool"). Download the configuration first if you may need it again.

The factory reset does not change the firmware: the running firmware and the alternative firmware stay as they are.

If the modem is just closing down for a restart the command is refused and the page shows "Restore to Factory Failed! (Rejected: reboot in progress - factory restore NOT applied)". Repeat it after the restart.

The LoRa Status page shows which modems a TLM hears and offers four tools to check a network during installation: the connection list with Request LoRa Connections, Ping of an IP device behind a remote modem, a link test and remote node information. All of them work over LoRa between modems with the same radio settings.

11.1 Device Connections over LoRa

Every modem keeps a list of the modems it has received packets from. Each received packet updates the row of its sender; no request is needed for this. The list appears in the card Device Connections over LoRa and is read again with Refresh LoRa Status.

NOTE:

RSSI, SNR, their averages and RX are shown when the radio module reports the extended packet format (the factory setting). Otherwise these columns show a dash.

• The list holds up to 32 modems. When it is full, the modem heard longest ago is replaced.
• The list starts empty after every restart.
• Rows are kept by the sender's LoRa address (group / device), not by Device ID. When the address of a modem is changed, the modem appears in a new row under its new address; the row under the old address stays, with a growing Age (s), until the modem showing this page restarts or the row is replaced when the list is full. If another modem starts using the old address, that row shows the other modem instead.
• A modem whose packets are blocked by the White or Black List on the Security Settings page does not appear and is not answered.

11.2 Request LoRa Connections

Request LoRa Connections asks all modems in radio range for their status. The page shows Request LoRa Communication List in Progress for 25 seconds and then reloads the status data. If the modem does not accept the request, the page shows Request Failed. with the reason in brackets instead, for example a radio module out of service.

1. The modem sends a status request to its Tx Group Address with device address 65535 (all devices of the group). The request carries the device addresses of the modems already listed with their details: modems that answered before, and modems whose own status request it heard, for example the automatic one after their start.
2. Every modem that receives the request and whose device address is not in that list answers with its module ID, its Device Function and its TCP connections. The list holds device addresses only: a modem of another group with the same device address stays silent too. The answer goes to the answering modem's own Tx Group Address with device address 65535; the requesting modem receives it only if that group is its own group. Every modem that hears the answer updates its list.
3. The requesting modem sends the request again about 5 seconds later, each time with the updated list. After five requests without an answer it stops. Each answer that arrives makes it send another request at once, so with many modems more than five requests go out.
4. Status requests and answers are handled by the modems themselves and never reach the Ethernet or serial side. Buffer Status counts them as REDZ consumed.

NOTE:

Each modem also starts one round of five status requests by itself about one minute after it has been switched on or restarted (for example from the web page, after a configuration import or a firmware update), as soon as no data is waiting and it has received no LoRa packet for 10 seconds. Answers do not extend this round. The Details column therefore fills without a click shortly after the network has started. After the daily restart, after a restart ordered over the radio by another modem, and after a restart that the modem makes by itself to recover from a fault, this automatic round is not sent.

• While a discovery runs, every modem that sends a status request or answer holds its own LoRa data for about 5 seconds after it (6 seconds for a modem that is already in the list). Run the discovery while the data traffic can wait.
• A LoRa Repeater does not pass status requests or answers on: the list shows only modems in direct radio range of the modems that take part.
• Only modems in the target group of the requesting modem receive the request.

NOTE:

If no modem is found, check that all modems use the same radio settings and target group, raise Radio Power Level, and mount the antenna of the central modem high, for example on a pole.

11.3 Remote Ping

Remote Ping (device on remote TLM network) checks an IP device behind another modem without leaving the web page. Enter the LoRa address of the remote modem (Group Address, Device Address) and the IP address of the device behind it (Target IP), then click Ping.

1. The modem sends a ping request over LoRa to the remote modem.
2. The remote modem sends an ICMP echo request (ping) to the target IP address on its own Ethernet port and returns the result over LoRa.
3. The result line under the button is read every 2 seconds until the result is in.

NOTE:

The remote modem handles one ping at a time; a second request arriving meanwhile is ignored and ends with NO RESPONSE. The remote modem must be in direct radio range - a repeater does not pass these frames. If Target IP is not a valid IP address, no ping is started: the page shows Request Failed. with a reason that speaks of "no recognized field in request", and the result line shows Not sent. Check the Target IP.

11.4 Link Test

Link Test (site survey) measures the radio link to one remote modem in both directions. Enter the LoRa address of the remote modem and a Probe Count from 1 to 50 (10 from the factory), then click Start.

1. The modem sends the probes one after another. The remote modem answers each probe at once with the signal strength and SNR at which it received the probe.
2. The next probe follows when the answer has arrived, or when no answer has come within 3 s (SF5 to SF7), 12 s (SF8, SF9) or 24 s (SF10 to SF12); the probe then counts as lost.
3. During the test the result line shows RUNNING with the probes sent and the answers received.

At the end the line shows DONE with the number of probes sent, the answers received and the success rate, followed by the average RSSI / SNR measured here (answers from the remote modem) and remote (probes received by the remote modem). Without the extended packet format the averages show a dash.

NOTE:

For an honest loss figure run the test with Acknowledged Transmission (C-Data) switched off: acknowledged transfer repeats lost frames and can hide losses. The page follows the result for the number of probes x 24 s + 30 s, at least 3 minutes. A second Start while a test runs (for example from another browser) is refused. The remote modem must be in direct radio range.

11.5 Remote Node

Remote Node (remote TLM management) reads the settings summary of a remote modem or restarts it. Nothing can be changed remotely. Enter the LoRa address of the remote modem and click Read Info or Reboot.

Read Info returns one line, for example OK - N:LORA_LM_SERVER DF:0 FW:3.00.01 IP:192.168.1.1 G:1 D:1 TxG:1 TxD:65535 SF:12 RX:<n> TX:<n>. If the remote modem does not answer within 15 seconds the line shows TIMEOUT - no response.

WARNING:

Reboot restarts the remote modem. After you confirm Reboot the remote device? the remote modem acknowledges (OK - Reboot acknowledged - remote device is restarting) and restarts shortly after; its connections and LoRa traffic stop until it is up again. No password is asked: any modem of the network with the same radio settings can restart another one. Use the White List on the Security Settings page to accept packets only from known modems.

WARNING:

Do not enter 65535 as Device Address in Remote Ping, Link Test or Remote Node unless you mean it: 65535 addresses every modem of that group in radio range. Reboot then restarts all of them at once, and the results of the other tools cannot be assigned to one modem. For Reboot with device address 65535 or group address 255 the page asks a second time and names the modems that will restart, for example This will restart ALL modems in ALL groups that hear the broadcast. Continue? The other tools do not ask.

11.6 Limits of the diagnostic tools

• Ping, link test and remote node frames are sent to exactly the address you enter and are answered only by a modem in direct radio range; a LoRa Repeater does not pass them.
• Enter a group from 1 to 255 and a device address from 1 to 65534 of an existing modem. Only Reboot checks the fields on the page. In the other tools a value that is not a number, a group above 255 or a device address above 65535 is not taken by the modem: the tool then works with the address of its previous request, without a message. An address where no modem answers ends with a timeout; 65535 reaches every modem of the group (see the warning above).
• A link test that is running ignores a new Start.
• The diagnostic frames never reach the Ethernet or serial side of the remote modem.

This chapter sets up the most common Modbus case step by step: a Modbus TCP master (a SCADA or a PC program) reads a Modbus RTU slave (for example an energy meter) over LoRa. The general description is in 9.3 "Modbus TCP master to Modbus RTU slaves".

The example slave has the Modbus address 5 and communicates at 9600 baud, 8 data bits, no parity, 1 stop bit. The master reads 5 holding registers (function code 3) from register address 7. Use the values of your own slave where they differ.

12.1 Wiring

1. Connect modem A to the network of the master with an Ethernet cable (chapter 6 "Ethernet Cables").
2. Connect the RS485 terminals A and B of modem B to the RS485 terminals of the slave, A to A and B to B, and connect GND when the slave has a ground terminal (chapter 8 "Serial Cables").
3. Mount the antennas and power both modems (chapter 3 "Installation").

12.2 Settings of modem A (Modbus TCP side)

Open the web interface of modem A (10.1 "Connecting to the Web Interface") and set the pages below in this order. Click Save Configuration on each page before you go to the next.

12.2.1 Operating Mode

1. Device Function: LoRa to TCP/UDP Server Gateway.
2. Leave Enable TCP Socket to Target Device Matching List and Enable Modbus Unit ID to Target Device Matching List unchecked.
3. Data Packing: keep the factory values (Idle Timeout (ms, 0=off) 100, Max Length (0=off) 0, Delimiter Enable unchecked). A request of the master is sent over LoRa when no further byte has come for 100 ms.
4. Click Save Configuration.

NOTE:

Keep Delimiter Enable unchecked for Modbus: Modbus frames are binary and may contain the delimiter byte, which would split a request into two radio messages.

12.2.2 Network Settings

1. Server Listening Port: 502 (the factory default and the usual Modbus TCP port).
2. Maximum Number of Clients: 1 for one master. Raise it if more masters connect at the same time. Every connected master then also receives the answers to the other masters' requests (with their transaction IDs); the master must ignore answers whose transaction ID it did not send.
3. Give modem A an IP address that the master can reach (10.3 "Network Settings").
4. Click Save Configuration.

12.2.3 LoRa Settings

1. Group Own Address: 1, Device Own Address: 1.
2. Tx Group Address: 1, Tx Device Address: 2 - the own address of modem B.
3. Leave the radio settings at their factory values, or set them exactly as on modem B.
4. Click Save Configuration.

NOTE:

Because the Tx Device Address changes from 65535 to a single modem, saving the page also checks Acknowledged Transmission (C-Data) once, and with it Listen Before Talk (LBT) on the 868 MHz models. Both stay editable. The same happens on modem B.

12.3 Settings of modem B (Modbus RTU side)

Open the web interface of modem B and set the pages below in this order.

12.3.1 Operating Mode

1. Device Function: LoRa to SERIAL Device Gateway.
2. Check Enable Modbus TCP to RTU Conversion. The page now shows the Modbus Response Timeout card and hides Data Packing.
3. Leave the other two options, Enable Modbus RTU Master to TCP Conversion and Enable IEC 62056-21 Mode C Baud Switching, unchecked.
4. Timeout (ms): the time modem B waits for the answer of the slave after it has written the request to the RS485 line. 1000 (the factory default) suits most slaves; the allowed range is 100 to 60000.
5. Check Exception (0x0B) Enable (it is unchecked at the factory). If the slave does not answer within the timeout, modem B then sends Modbus exception 0x0B (gateway target device failed to respond) to the master, so the master learns at once that the slave is silent. Unchecked, modem B sends nothing.
6. Click Save Configuration.

NOTE:

Set the Serial Settings page after the Operating Mode page. When neither serial port is enabled yet (as on a factory modem), saving Operating Mode with LoRa to SERIAL Device Gateway enables RS485 at 19200 baud, 8_NONE_1; change it to the values of the slave on the Serial Settings page (10.4 "Serial Settings").

12.3.2 Serial Settings

1. Check Enable RS485 and leave Enable RS232 unchecked.
2. Baud rate: 9600, Line Control: 8_NONE_1 - the same as the slave. With Modbus conversion, 7_EVEN_1 is not offered, and 300 baud is changed to 19200 at the next start.
3. Click Save Configuration.

12.3.3 LoRa Settings

1. Group Own Address: 1, Device Own Address: 2.
2. Tx Group Address: 1, Tx Device Address: 1 - the own address of modem A. Modem B sends every answer to this address.
3. Radio settings: the same as on modem A.
4. Click Save Configuration.

12.4 Restart both modems

The new Device Function, the Modbus conversion, the serial settings and the LoRa settings take effect only after a restart. On the Management page of each modem click Reboot Device and confirm Reboot the device now?.

WARNING:

Reboot Device restarts the modem. The page shows Reboot Device Command has been sent. and the modem cannot be reached for a short time; its connections and LoRa traffic stop until it is up again. Open the page again afterwards.

12.5 Settings of the master

LoRa is slow compared with a cable. The answer time is the sum of 100 ms collection time on modem A, two radio transfers, up to about 100 ms on each modem before a received radio message is passed on, the acknowledgement time when Acknowledged Transmission (C-Data) is on, and the answer time of the slave; the radio transfers grow with the LoRa Spreading Factor and the message length. Set the response timeout of the master longer than Timeout (ms) of modem B plus the two radio transfers, and leave a pause between polls. Start with generous values and shorten them after watching the real answer times. In our measurement with this example at the factory radio settings (SF12; C-Data and, on 868 MHz, LBT switched on by the save), a poll every second left about one request in five unanswered: the request did not reach the slave. With a poll every 3 seconds, a pause of 1 second between polls and a response timeout of 10 seconds in the master, all 118 requests were answered.

• Modem B handles one request at a time. Requests that arrive while it waits for the slave are queued and answered one after the other.
• Every answer carries the transaction ID of its request. A late answer that arrives after the master has given up is therefore recognised by the master as old.

12.6 Checking the communication

Start polling in the master. Then check both modems.

12.6.1 Modem A: Device Status

• The health summary at the top of the page shows in the Connections box one client, with the address of the master, and in the LoRa Radio box how long ago the last radio frame came and from which group / device (modem B).
• The TCP Connections table lists the master with its Ip Address/Port, the Local port 502 and the bytes received from and sent to the master since it connected.
• N. of Gateway Messages Received Correctly and N. of LoRa Messages Sent Correctly rise with every request of the master.
• N. of LoRa Messages Received Correctly and N. of Gateway Messages Sent Correctly rise with every answer that comes back from modem B.
• The page does not update by itself: click Refresh Status to read the values again.

12.6.2 Modem B: Device Status

• The health summary shows Not used in the Connections box (modem B has no TCP clients) and No serial errors in the Serial / system box.
• N. of LoRa Messages Received Correctly rises with every request from modem A, N. of Gateway Messages Sent Correctly with every request written to the slave.
• N. of Gateway Messages Received Correctly and N. of LoRa Messages Sent Correctly rise with every answer sent back to modem A (an exception answer of the slave and an exception 0x0B after a timeout count too).
• N. of Gateway Incorrect Modbus Characters Received should stay at 0. If it rises, the slave answers with a wrong slave address, a wrong function code or a wrong CRC, or a request arriving over LoRa is not a valid Modbus TCP frame - see the limits below. Reset Logs does not clear this count, so the Serial / system box shows Serial errors until the next restart.
• N. of Serial UART Errors rises when the baud rate or Line Control do not match the slave.

12.6.3 LoRa Status

The LoRa Status page of each modem shows the last radio message it received (10.7 "LoRa Status"):

Latest Message Received - Gateway Side shows on modem A the last request from the master. On modem B it shows the Modbus TCP answer that modem B made from the answer of the slave (7 header bytes, function code, byte count and data), the exception answer of the slave, or the 0x0B exception frame; it is not the raw RTU answer, and answers that modem B dropped do not appear. To list the other modem with its signal values under Device Connections over LoRa, click Request LoRa Connections: the automatic request after a start waits for a quiet radio and is not sent while the master polls (chapter 11 "LoRa Network Discovery").

12.7 Limits in this example

12.7.1 Size of an answer

In this example modem A passes the radio data on unchanged, so keep every answer within one LoRa packet:

A longer answer is sent by modem B in several packets, and modem A passes each packet to the master as it arrives. If a later packet is lost, the master receives an incomplete frame. Split larger blocks into several requests. With routing by Unit ID on modem A (9.4 "Modbus routing by Unit ID"), modem A instead collects the packets of an answer and passes it to the master only when it is complete; if a packet is lost, the master gets no answer, or exception 0x0B when Exception (0x0B) Enable is checked on modem A.

The same packet size applies to write requests of the master. A write of more than 108 registers (868 MHz models) or 48 registers (2.4 GHz models) with function code 16 is split by modem A into several radio packets. Modem B joins them before it writes the request to the slave, but each part travels as its own radio packet. Keep large writes within one packet as well.

12.7.2 Supported function codes

Modem B passes every function code of the master to the slave. It finds the end of the answer of the slave from the function code:

Modem B then checks the CRC of the answer before it sends it to modem A.

12.7.3 Exception answers of the slave

Modem B passes a Modbus exception answer of the slave (for example 02, illegal data address) on to the master as a Modbus TCP exception answer with the exception code of the slave. The master therefore learns the reason at once and does not wait for a timeout. An exception answer is a valid answer: it does not add to N. of Gateway Incorrect Modbus Characters Received.

An answer with a wrong slave address, a wrong function code or a wrong CRC is dropped. Modem B then keeps waiting until Timeout (ms) runs out; the master sees a timeout, or exception 0x0B when Exception (0x0B) Enable is checked, and further requests wait in the queue that long. The bytes of the dropped answer are added to N. of Gateway Incorrect Modbus Characters Received.

WARNING:

When more than 500 incorrect characters arrive without a valid answer of the slave in between, modem B restarts. Every valid answer, also an exception answer, starts this count again; N. of Gateway Incorrect Modbus Characters Received itself is a running total. A wrong baud rate, a noisy RS485 line or a second device answering with another slave address can therefore restart modem B. After two such restarts in a row modem B stops restarting and keeps running: App Status and the Serial / system box show SERIAL NOISE PARKED. A valid answer of the slave or Reboot Device ends this state. Check the wiring, Baud rate and Line Control and watch this counter during commissioning.

12.7.4 More than one field modem

To read slaves behind several field modems, either set the Tx Device Address of modem A to 65535 so that every field modem receives every request, or let modem A route each Unit ID to its field modem (9.4 "Modbus routing by Unit ID"). With 65535, leave Exception (0x0B) Enable unchecked on the field modems: otherwise every field modem whose slaves do not answer sends its own exception.

With routing by Unit ID, modem A also shows the Modbus Response Timeout card. Modem A answers a Unit ID without a matching routing line at once with exception 0x0A. When no answer comes back in time, modem A sends exception 0x0B only if Exception (0x0B) Enable is checked on modem A; it is unchecked at the factory, and the master then sees a timeout.

Recordings of the web interface of a modem with firmware 3.00.01. The videos have no sound; each step is described in the chapter named above the video.

13.1 Firmware update

The Management page of a modem: the image file is chosen with Select Firmware File, sent with Upload Firmware and checked by the modem (Checking..., then "Firmware Uploaded"); afterwards Alternative Firmware Version shows the uploaded version. The switch to the new firmware with Reboot Alternative Firmware is not part of the recording. Steps, limits and the upgrade from 2.x: 10.9.2 "Live Firmware Update" and chapter 16 "Firmware Update and Upgrading from 2.x".

13.2 Reading a Modbus RTU slave over LoRa

The example of chapter 12 "Modbus Communication Example": the settings of modem A and modem B, then a Modbus TCP master program on a PC reading the slave through both modems and, while the master polls, the Device Status pages of both modems and the LoRa Status page of modem B. In the recording the slave is a Modbus RTU slave program on the same PC, connected to the RS485 terminals of modem B through a USB-RS485 adapter, with the slave address and serial settings of the example.

An I/O mirror links two HUR Series Modbus TCP remote I/O devices over a TLM LoRa network: the outputs of one HUR device follow the inputs of the other one.

NOTE:

Pair devices of the same kind: analog with analog, digital with digital.

Between the two HUR devices the TLM modems work as described in 9.1 "TCP/IP devices over LoRa". Both modems use the same radio settings, and each one has the other one as its target address on LoRa Settings.

The first video shows an analog pair on the bench: the current fed into the analog input HUR is set on the analog output HUR through the TLM modems.

The second video shows the configuration of the HUR devices and the TLM modems. It was recorded with firmware 2.x: the TLM pages in it look different and have other names; the names in this manual are those of firmware 3.00.01.

A Modbus TCP program on a PC reads two HUR Series Modbus TCP remote I/O devices in the field over a TLM LoRa network. The TLM modems pass the Modbus TCP frames unchanged.

1. Modem A next to the PC works as LoRa to TCP/UDP Server Gateway. The Modbus program connects to the IP address of modem A at its Server Listening Port (502 from the factory).
2. The modem next to a HUR device works as LoRa to TCP/UDP Client Gateway with the IP address and the Modbus TCP port of the HUR device as Target IP and Target Port, and modem A as its target address on LoRa Settings.
3. With the two HUR devices behind two field modems, set the Tx Device Address of modem A to 65535 so that each request reaches both field modems.

The two videos below were recorded with firmware 2.x. The TLM pages in them look different and have other names; the names in this manual are those of firmware 3.00.01.

The first video shows the Modbus program reading the two HUR devices.

The second video shows the physical set-up of the same example: three TLM modems, the two HUR devices and the PC with the Modbus program.

16.1 Firmware files

There is one firmware file for each radio band, with and without BPL. Use the file whose name contains your model:

WARNING:

The modem does not check which model a firmware file was made for. It also accepts the file of the other frequency band, or of the model with or without BPL, and then runs firmware that does not fit its radio module. Check the file name against the table above before every update.

16.2 Updating the firmware

The modem holds two firmware images: the running one and an alternative one. An update loads the new file into the alternative area while the modem keeps working; the modem changes over only when you start the alternative firmware. The buttons and messages are described in 10.9 "Management".

1. Download the configuration with Download Current Configuration and note the settings of every page (see the section on upgrading from 2.x below for why notes are needed).
2. On the page Management, card Live Firmware Update, click Select Firmware File and choose the file of your model.
3. Click Upload Firmware and wait until the window reports that the firmware is uploaded. The modem keeps working during the upload.
4. Check that Alternative Firmware Version shows the new version, then click Reboot Alternative Firmware and confirm.
5. When the page is back, check the version line at the top of the page. If no answer came or the page does not come back, do not click Reboot Alternative Firmware again: wait for the restart and check the version first. If the first request was carried out, a second click switches back to the old firmware.

WARNING:

Reboot Alternative Firmware restarts the modem about 1.5 seconds after the answer, whatever the modem is doing at that moment. All connections and the radio traffic stop until the new firmware has started.

NOTE:

The firmware that ran before stays in the modem as the alternative firmware. Reboot Alternative Firmware switches back to it. If both versions have the same first two numbers, the firmware you switch back to takes over the current settings, including changes you made since the update. Otherwise it starts with the settings it had when you left it.

NOTE:

An interrupted or failed upload does not touch the running firmware. The alternative area is then marked invalid and the change-over is refused; upload the file again.

The page files of the web interface carry the firmware build in their address, so the browser loads the new pages after an update. If a page still looks like the old interface, reload it with Ctrl+F5.

16.3 Updating from 3.00.00

A modem with firmware 3.00.00 is updated as described above. The settings, the LoRa addresses and the password are taken over; the modem stays in its radio network and needs no new configuration. A stored value that is outside the range of the model is set back to its factory value at the first start and logged with a CFG norm line - for example Max Length (0=off) above 109 on a 2.4 GHz model.

NOTE:

If your Modbus TCP master relies on exception 0x0B with the routing by Unit ID, check Exception (0x0B) Enable on Operating Mode after the update.

16.4 Upgrading from 2.x

A modem that runs a 2.x firmware is updated the same way: upload the 3.00.01 file of its model and start it with Reboot Alternative Firmware. The 2.x settings are not taken over: firmware 3.00.01 starts with factory settings.

WARNING:

After the upgrade the modem is out of its radio network until it is configured again. Plan one visit per modem for the update and the configuration, and keep the notes of the 2.x settings at hand. If some modems are reached only through the radio link of other modems, update the farthest modem first; otherwise a modem in the middle that is back at factory settings cuts off the modems behind it.

Do not upload a configuration file saved by a 2.x firmware. Firmware 3.00.01 refuses a file it cannot read, but a 2.x file whose entries it happens to know is accepted without any identity check and stored with the settings it does not contain left as they are. Configure the first upgraded modem by hand, download its configuration and use that file for the other modems of the same model.

NOTE:

The 2.x device function "LoRa to Serial Device Gateway with Modbus TCP/RTU Conversion" is no longer a separate entry of Device Function. Select LoRa to SERIAL Device Gateway and tick Enable Modbus TCP to RTU Conversion. A configuration file that still holds the old function is converted to this setting when the modem starts.

16.4.1 Upgrade checklist

16.4.2 What is different after the upgrade

16.5 Configuration file and model check

A configuration file downloaded from firmware 3.00.01 starts with an identification block. It names the product, the radio variant, the firmware version and build, the size of the settings block and the device name:

"_meta": { "product": "REDZ TLM Series 868MHz LoRa Based RF Modem", "variant": "868", "fw": "3.00.01", "build": "...", "cfg_bytes": ..., "device": "..." },

Before anything is stored, the modem compares the block with itself. The size of the settings block (cfg_bytes) must match, otherwise the file is refused with "Rejected - layout mismatch: file <n>, device <n>". The product name and the variant must be exactly its own: a file of the other frequency band, or of the model with or without BPL, is refused with "Rejected - product mismatch: file '...', device '...'" and nothing changes. A file of another firmware version with the same settings block size, for example a file saved by firmware 3.00.00, is accepted with a warning: "Configuration Uploaded (warning: file from fw <x>, device runs 3.00.01) - device will restart". The full list of answers is in 10.9 "Management".

A file with a fault in it is refused as a whole and nothing is stored; the answer names the line and the position of the fault. A file without identification block (for example one edited by hand without it) is accepted without the check above; the answer then says "Configuration Uploaded (legacy config - no _meta) - device will restart".

WARNING:

An accepted configuration file restarts the modem about 1.5 seconds after the answer. If the file holds other network settings or another password, the modem is reached with them afterwards.

17.1 What the tool does

The abcZ Network Tool is our Windows program for REDZ devices on an Ethernet network. With TLM Series modems it finds them and shows their address, product, firmware version and MAC address, reads the identity of one modem, gives a modem a static address, restarts or resets a modem, and updates the firmware of one modem or of many modems at once. This chapter describes version 1.1.0 and only what you need with a TLM Series LoRa RF modem. Download the tool and its own user guide from the Support page of redz-sc.com (https://redz-sc.com/en/support).

The tool talks to the modem the way a web browser does. Type the password of the modem's web interface in Password on each tab; leave User at admin, because the modem accepts only that user name. The factory password is admin. A modem with another password is listed with "auth required (password?)" in the Product column.

From firmware 3.00.01 on, the modem confirms every command of the tool: it answers whether it carried the command out or why it refused it, and the tool shows that answer. The tool decides by the firmware version it read from the modem; for the commands on the Discovery tab this is the version shown in the Discovery list, so scan again after you have updated a modem. A modem that still runs 3.00.00 does not confirm commands; the tool then reports only that the request reached the modem.

17.2 Find the modem

Open the Discovery tab. In IP range type the addresses to search: a network such as 192.168.0.0/24, a range of the last number such as 192.168.0.1-254, a range such as 192.168.0.10-192.168.1.50, or one address. Click Scan (HTTP): the tool reads the start page of every address in the range, so it also finds modems behind a router. Each modem found appears as a row with IP, MAC, Series, Product, Device (the device name), Version, Build date and Status (the result of the last right-click command on that row).

NOTE:

Timeout (s) is the wait per address (2.5 s by default; raise it when modems behind a router are missed) and Parallel the number of addresses asked at once (24 by default). The modem serves at most 7 web connections at a time. Very high Parallel values together with scans repeated one after the other can use up these connections: every modem then looks offline for about a minute and recovers by itself. Raise Parallel only for large ranges and do not repeat scans back to back.

The Series column shows TLM-LM for a TLM Series LoRa RF modem. The tool takes it from the product name: a TLM product whose name contains "LoRaWAN" is shown as TLM-LW. That is the TLM Series LoRaWAN end node, another product with its own firmware; never give a TLM-LW device a modem image or the other way round.

Discover (UDP) is faster: it asks with a broadcast on UDP port 30303, which the modem answers. A broadcast does not cross routers, so it finds only modems in the same subnet as the PC. The modems that answer are then read in the same way as with Scan. A modem that answered the broadcast but could not be read (for example a wrong password or a timeout) shows only its name followed by "(UDP)" in Product; check the password and scan it with Scan (HTTP).

Double-click a row, or right-click it and choose Open Web Page, to open the modem's web interface in your browser; Copy IP copies its address. Series filter (for example TLM-LM) and Find narrow the list. Export CSV saves the selected rows (or all rows shown) as a list for Fleet Update.

A modem that is not found may still be at its factory address 192.168.1.1 in a network without a DHCP server; see 10.1 "Connecting to the Web Interface". Assign Address at Factory IP... on the Discovery tab gives such a device a new address from a PC in another network; its steps are in the tool's own user guide.

17.3 Read the identity of one modem

On the Single Device Update tab, type the modem's address in Device IP and click Read Identity (safe). The panel Device identity (last read) shows the product name, firmware version, build date, MAC address and device name. Nothing is changed on the modem. If Expected product is empty, the tool fills it with the product name it read; this name protects the firmware update (below). Read Identity is also the way to check a modem after a restart, a new address or a firmware update: the version and build date it shows are the ones the modem runs now. Open Web Page opens the web interface of the modem at Device IP in your browser.

17.4 Give the modem a static address

On the Discovery tab, right-click the modem's row and choose Set IP / Subnet / Gateway (one device).... The tool first reads the modem's network settings; the window "Set network - <address>" then shows IP address, Subnet mask and Gateway as they are stored for the static address (Server IP Address, Server Net Mask and Server Gateway Address in 10.3 "Network Settings"). A modem that has its address from a DHCP server shows these stored values, not the address it uses now; a modem that never had a static address shows the factory values 192.168.1.1, 255.255.255.0 and 192.168.1.1.

Type the new values, click Apply and type SET to confirm. If another task of the tool (for example a fleet update) is still running, nothing is written and the log asks you to wait or use Stop. Otherwise the tool turns on Use Static Address for Device, saves the three values (the other network settings are kept) and waits for the modem's answer. With firmware 3.00.01 the log says "network settings confirmed by device (REQ=SAVE_NET, reboot required); rebooting to apply...". If the modem refuses the change, for example because it is restarting at that moment, the log and the Status column show "REFUSED by device:" with the modem's reason, and the tool stops there: nothing was saved and the modem keeps its address. After a confirmed save the tool restarts the modem and looks for it by its MAC address at the new address. It searches the 256 addresses around the new address (for 192.168.5.20: 192.168.5.0 to 192.168.5.255). When it finds the modem there, the log says "now reachable at" with the new address. When it does not, the log warns that the modem was not found by its MAC address, and the Status column shows "IP set? not found at" with the address you typed. While a scan or an update is running, the tool refuses this command; wait until the task ends.

NOTE:

A modem that still runs 3.00.00 does not confirm the save: the log then says only "accepted (HTTP 200; device gives no acknowledgement on this firmware)", which means that the request reached the modem, not that the modem saved it. For such a modem the search by MAC address is the only check.

NOTE:

The tool can find the modem only if the PC can reach the new address. With a subnet mask wider than 255.255.255.0 it still searches only the 256 addresses around the new address. If the modem is not found after the change, look for it at the new address with Scan (HTTP), Read Identity (safe) or your browser, and also at the OLD address: the new address takes effect only when the modem restarts, and the tool does not check that the restart command arrived. A wrong subnet mask or gateway can make the modem unreachable.

17.5 Restart or reset the modem

Select one or more rows on the Discovery tab, right-click and choose Reboot Device (selected)... or Restore Factory Configuration (selected)..., then confirm; for the factory reset you also type RESTORE. The Status column shows the result for each modem. With firmware 3.00.01 a restart shows a check mark and "reboot: confirmed by device (REQ=REBOOT, reboot required)"; the words "reboot required" only repeat that the modem restarts. "REFUSED by device:" is followed by the modem's reason. "NOT SENT" means the request did not reach the modem; "FAILED (HTTP 401 - password?)" means the modem refused it because of a wrong password. A modem that still runs 3.00.00 gives no confirmation: the column shows a warning sign and "accepted (HTTP 200; device gives no acknowledgement on this firmware)" or "sent, response lost", which is not proof that it restarted. To be sure, wait until the modem is back and click Read Identity (safe) for it, or scan again.

NOTE:

Tool 1.1.0 and a modem with firmware 3.00.01: after Restore Factory Configuration (selected)... the Status column shows a cross and "REFUSED by device: device acknowledged a different request: RESTORE_FACTORY", although the modem accepted the command and resets itself. Check the modem after the reset (see the warning below) instead of repeating the command.

WARNING:

Both commands restart the modem, and every connection through it is dropped until it is back. Restore Factory Configuration (selected)... deletes every setting of the selected modems, including the password, the radio settings and the static address; afterwards a modem takes its address from a DHCP server or stays at 192.168.1.1. Check the number of selected rows before you confirm.

17.6 Update the firmware

Each TLM Series model has its own firmware image. Use the image of your model:

On the Single Device Update tab:

1. Clear Expected product, type the modem's address in Device IP and click Read Identity (safe); the tool fills Expected product with this modem's product name. (A name left from another modem is not replaced, and the update would then stop.)
2. Click Browse... and choose the firmware image (.binimg) of your model from the firmware package (see chapter 16 "Firmware Update and Upgrading from 2.x"). If the package contains a RELEASE_v3.00.01.json file, keep it next to the image: the tool then also checks the image file against it.
3. Click Update and confirm.

Before it writes, the tool stops when the product name read from the modem is not the expected one (this cannot be overridden), skips a modem that already runs the version in the file name (tick Force (flash even if version matches) to write it anyway) and compares the image with the modem: the product family (an image of the TLM Series LoRaWAN end node is caught the same way), the frequency band (868 MHz or 2.4 GHz) and BPL or no BPL. When they differ it asks in the window Image / device mismatch; answer No and the modem is not touched.

WARNING:

The modem itself accepts the image of every TLM Series model: an 868 MHz modem takes a 2.4 GHz image and a modem without BPL takes a BPL image, and the other way round. The tool's comparison is the only protection. Never answer Yes in Image / device mismatch unless you are sure of the model, and in Fleet Update keep Stop on image/device mismatch ticked.

The image is written into the modem's alternative firmware bank; the running firmware is not touched by the upload. The tool then sends the command to start the new firmware once. Whether the modem confirms this command depends on the firmware it runs before the update: a modem at 3.00.01 answers, and the log shows "confirmed by device (REQ=REBOOT_ALT_FW, reboot required)"; if it refuses (for example because the uploaded image is not valid), the update ends at once with BANK SWITCH REFUSED and the modem keeps its old firmware. A modem that still runs 3.00.00 (the first update to 3.00.01) gives no confirmation: the log says "accepted (HTTP 200; device gives no acknowledgement on this firmware)" and that the version and build stamp decides the outcome. In both cases the tool waits for the restart and compares the version and build date the modem reports with those of the uploaded image; when the modem does not answer at its address, it looks for it by its MAC address in the 256 addresses around it and at the factory address 192.168.1.1. The log ends with "RESULT:" and SUCCESS when the modem reports the version and build date of the uploaded image. If you write an image with the same build date as the one the modem already runs, this check cannot tell whether the modem switched. When the modem did not switch or did not come back in time, the result is NOT CONFIRMED. In that case wait a little and click Read Identity (safe): the version and build date show which firmware the modem runs.

WARNING:

The modem restarts at the end of the update, and every connection through it is dropped until it is back.

With Upload only (no reboot) ticked, the tool writes the image into the alternative bank and stops there: the modem keeps running its current firmware and the result is UPLOADED (no reboot). To start the new firmware later, use Reboot Alternative Firmware on the modem's web interface (see 10.9 "Management"); this restarts the modem.

The result of an update is one of these texts (in the log after "RESULT:", and in the Status column of Fleet Update):

NOTE:

Stop (or Esc) cancels the modems and addresses that are still waiting; the step in progress finishes or times out, and an upload in progress is not aborted (it only writes the alternative bank). A modem whose start command was already sent may restart with the new firmware: check it later with Read Identity (safe).

NOTE:

Factory reset after update deletes every setting of the modem after the update, and its address may change. Leave it off unless you want the factory settings. When the factory reset was sent, the result line reads "SUCCESS (factory reset)"; check the modem afterwards (it now uses the factory settings and may be at another address, see above). When the modem was updated but the factory reset could not be sent or was answered with an error, the result is UPDATED, FACTORY RESET FAILED; as the pilot of a fleet update this result stops the fleet. With tool 1.1.0 this also happens when the modem already ran 3.00.01 before the update: the modem then resets as requested, but the tool reads its confirmation as a refusal (see 17.5 "Restart or reset the modem"). Check such a modem with Read Identity (safe) after the reset.

17.7 Update many modems

The Fleet Update tab updates a list of modems from a CSV file with the columns ip, expected_product and image_path (the image path is relative to the CSV file). Export CSV on the Discovery tab writes such a list with the image column empty; fill in the image of each modem's model from the table above. Validate CSV (dry-run) checks the list without writing, and Run Fleet Update starts the update. With a Pilot IP (opt.) the tool updates that modem first and leaves all the others untouched if it fails; the rest are then updated Parallelism (jobs) at a time. Choose a pilot that does not yet run the new version: a skipped pilot counts as a success, and a pilot whose image does not match stops the fleet. With Stop on image/device mismatch ticked, a modem whose image does not match its band or BPL is skipped and the others continue. The other options of this tab (images assigned in the table, Write report CSV, Save CSV...) are described in the tool's own user guide.

18.1 Getting the log

The modem writes what it does as text lines. The log is off at the factory. It is switched on in the card LOG of the page Management (10.9 "Management"):

WARNING:

Change Log Level and Reboot stores the log settings and restarts the modem when a value has changed. Connections and radio traffic stop during the restart.

The video below shows the same steps with a REDZ CKL Series device and the program Packet Sender as the UDP receiver. The names of the fields and of the button in the LOG card are the same on the TLM modem; their order on the page can differ, and the log lines of the CKL device look different from those of the TLM modem described below.

Each line starts with the date and time of the modem clock (day-month-year), then ERR-, INF- or DBG- for the level, then the message. Where a message carries a number, the number follows the text directly:

16-10-26 14:03:12 ERR-NETWD: gateway unreachable, consecutive failures2
16-10-26 14:05:40 INF-NETWD: gateway reachable again (step=0 fail=2 park=0)

NOTE:

A line that is too long for the log is cut and ends with the character ~.

18.2 Start-up lines

After every start the log contains, near its start, two lines that tell why the modem started. They are written only when the log is on.

BOOT rcon=0x... POR rbt=FRESHBOOT-POR
diag streak=0 wdt=... ps=... wc=0x... norm=0

The second line (diag ...) holds service values for REDZ support.

18.3 Log messages

The table lists the messages a user is most likely to meet, with the level at which they appear. <n> stands for a number, <ip> for an address.

18.4 Automatic restarts and parking

The modem restarts itself when a fault does not clear by itself. For the faults that can come back after every restart, it counts the restarts: the third time in a row it stops restarting ("parked") and keeps working with what is left. The App Status line of the page 10.5 "Device Status" then shows the parked state. After a self-restart (also the daily one) the parked text is gone until the fault comes back; the count is kept, so the modem then parks again without restarting. Serial line noise is the exception: its parked text stays after a self-restart.

NOTE:

If several cases are parked at the same time, App Status shows all their texts one after the other.

NOTE:

While the gateway check is parked, the modem still renews and requests its DHCP address every 15 minutes or so; during each request the network connections of the modem are interrupted for a moment.

NOTE:

The Ethernet port of the modem sits behind an on-board switch, so the modem sees a link even when the cable is unplugged. An unplugged cable therefore shows up as an unreachable gateway or missing clients, not as a lost link.

NOTE:

If the modem sees no Ethernet link at the start in LoRa to TCP/UDP Server Gateway or LoRa to TCP/UDP Client Gateway with DHCP address mode, it waits for the link without restarting; App Status shows (NO LINK - waiting, no reboot).

18.5 Known behaviours and limits

18.5.1 The modem restarts again and again

• Symptom: the modem restarts again and again; connections and radio traffic stop at every start.
• Cause: one of the cases of the table in "Automatic restarts and parking" above.
• What to do: switch the log on at INFO and look for the last lines before each start and for the BOOT line; the table names the case.

18.5.2 App Status shows a parked state

• Symptom: App Status on Device Status shows a text in brackets such as (GATEWAY UNREACHABLE - parked).
• Cause: the same fault asked for a restart the third time in a row; the modem stopped restarting for it. Only the gateway check still restarts the modem about every 30 minutes to try again; the planned daily restart also runs.
• What to do: remove the cause (client, target, gateway, cable, radio module, serial line), then use Reboot Device for a fresh start; see 10.5 "Device Status".

18.5.3 No radio traffic after an upgrade from 2.x or a factory reset

• Symptom: the modem does not reach the other modems of its network.
• Cause: the LoRa addresses and radio settings are at their factory values.
• What to do: enter LoRa Settings again and restart the modem.

18.5.4 The modem is not found at its old address

• Symptom: the web interface does not open at the address the modem had before.
• Cause: the modem is in DHCP address mode, or at 192.168.1.1 after a factory reset.
• What to do: find it as described in chapter 17 "Software - abcZ Network Tool". If it cannot be found at all, hold one of the reset buttons (RESET TO SERVER or RESET TO CLIENT, 5.4 "Reset Buttons") for 5 seconds: both restore the factory settings and restart the modem, also when the web interface does not work. All settings are lost.

18.5.5 App Status shows (NO LINK - waiting, no reboot)

• Symptom: App Status shows (NO LINK - waiting, no reboot).
• Cause: the modem saw no Ethernet link at the start.
• What to do: check the cable and the switch.

18.5.6 The UDP log stays empty

• Symptom: the UDP receiver program on the PC shows no lines.
• Cause: a wrong port or address, the firewall of the PC, or a modem and PC that cannot reach each other.
• What to do: check UDP Server Port and UDP Server IP, the firewall of the PC, and that the modem and the PC are in the same network.

18.5.7 Planned restart every 24 hours

• Symptom: once a day the modem restarts; its connections are closed.
• Cause: by design the modem restarts after 24 hours of running time, counted from its last start. The log line, at Log Level INFO or DEBUG, is "RESTART_SYSTEM_TIMEOUT: (S)<n>".
• What to do: nothing. A TCP client must be able to connect again by itself.

WARNING:

Holding a reset button for 5 seconds restores all factory settings and restarts the modem at once. The LoRa addresses, network settings and password are lost.

When you contact REDZ support, send the log lines around the problem, including the two start-up lines after the restart, and the firmware version shown at the top of the page.