Home › Technical articles

Đọc bằng tiếng Việt

N3uron with Siemens S7 PLCs and Modbus devices: Siemens Client, Modbus Client, addressing and PUT/GET

TDL Industrial Automation · Last updated:

From the N3uron Knowledge Base 1.22: the Siemens Client for S7-300, 400, 1200 and 1500, rack, slot and addresses such as db5:01.7, optimized block access and PUT/GET; the Modbus Client with channels, devices, slave ID, offset, swaps, block sizes and auto-demotion; Omron NJ/NX through the EtherNet/IP Client; quality codes and logs.

N3uron reads Siemens S7 PLCs with its Siemens Client module and Modbus devices with its Modbus Client module; Omron NJ and NX controllers are listed under its EtherNet/IP Client. This article follows the N3uron Knowledge Base 1.22, and 1.21 where it says more: what each module connects to, settings and defaults, address syntax, what an S7-1200 or S7-1500 needs changed, and diagnostics. How N3uron itself is built: What is N3uron.

Siemens PLCs, Modbus devices and Omron into N3uronTop row: three groups of devices. A is Siemens S7-300, S7-400, S7-1200 and S7-1500 PLCs; on the S7-1200 and S7-1500 optimized block access must be off and PUT/GET allowed. B is Modbus TCP devices, Modbus RTU on a serial port, or RTU over TCP. C is Omron NJ/NX PLCs, without tag browsing. Middle row: each group goes into one N3uron module: the Siemens Client (device with IP, rack, slot; addresses such as db5:01.7), the Modbus Client (channel and device with slave ID, offset, swaps; addresses such as 400001) and the EtherNet/IP Client (from version 1.22.0, PLC type Omron NJ/NX, variable names). All three feed the N3uron node, where each tag has a value, timestamp and quality and a scan rate of at least 100 ms; from there data delivery modules such as MQTT Client, Sparkplug Client, OPC UA Server, Modbus Server and REST API Server pass the data on. Based on the N3uron Knowledge Base 1.22.Siemens PLCs, Modbus devices and Omron into N3uronA · Siemens S7S7-300, S7-400, S7-1200,S7-1500; on 1200 and 1500:optimized block access off,PUT/GET allowedB · Modbus devicesModbus TCP, Modbus RTU on aserial port, or RTU over TCPC · Omron NJ/NXEtherNet/IP; no tag browsing,variable names typed inS7 over TCP/IPModbusEtherNet/IPSiemens Clientdevice: IP, rack, slot; addressessuch as db5:01.7Modbus Clientchannel and device: slave ID,offset, swaps; addresses suchas 400001EtherNet/IP Clientfrom 1.22.0; PLC typeOmron NJ/NX; variable namesN3uron node · tagseach tag has a value, timestamp and quality; scan rate at least 100 mspassed on byData delivery modulesMQTT Client, Sparkplug Client, OPC UA Server, Modbus Server, REST API ServerBased on the N3uron Knowledge Base 1.22: Siemens Client, Modbus Client, EtherNet/IP Client and Platformpages (read 15 November 2026). No Mitsubishi module found in the 1.22 list. Figure: drawn by TDL.
Figure 1: Siemens PLCs, Modbus devices and Omron into N3uron. On a phone, swipe sideways to see the whole figure.

1. Which module reads which PLC

From the 1.22 module list and module pages:

PLC family N3uron module Protocol What the pages say to set on the PLC
S7-300, S7-400 Siemens Client S7 over TCP/IP nothing listed
S7-1200, S7-1500 Siemens Client S7 over TCP/IP optimized block access off; access level "full"; connection mechanism allows PUT/GET
S7 on MPI, through an Ethernet/MPI converter Siemens Client S7 over TCP/IP to the converter nothing listed; rack and slot in N3uron follow the converter's MPI address assignment
Modbus TCP devices Modbus Client Modbus TCP nothing listed; addresses come from the device's memory map
Modbus RTU devices Modbus Client Modbus RTU on a serial port, or RTU encapsulated over TCP nothing listed; serial settings are set on the channel
Omron NJ, NX EtherNet/IP Client, from 1.22.0 EtherNet/IP (CIP over TCP/IP) nothing listed
Mitsubishi no module named in the 1.22 list not found in the docs not found in the docs

The Modbus Client page says it connects to any Modbus compatible device, so a PLC whose data is offered over Modbus, directly or through a gateway, can be read that way whatever its make.

2. Siemens Client: the device settings

Each PLC is one Device in a Siemens Client instance. Settings on the 1.22 page:

Setting Meaning Range and default
Rack rack the CPU sits in 0 to 255, default 0
Slot slot assigned to the CPU 0 to 255, default 2
Request Timeout longest wait for a valid response 100 to 1,000,000 ms, default 3,000 ms
Retry attempts retries before the PLC counts as unreachable 0 to 100, default 3
Inter-request delay pause before the next request 0 to 1,000,000 ms, default 0
Block size largest request, in bytes 1 to 1024
Reconnection delay wait before reopening a failed connection at least 1,000 ms

The Examples page uses rack 0 and slot 1 and leaves the other settings at their defaults. Each tag names the device, an S7 address, a data type and a scan rate of at least 100 ms. The data types are Boolean, UInt8, Int8, UInt16, Int16, UInt32, Int32, UInt64, Int64, Float32, Double64, String, DTL and Custom Expression.

3. Writing S7 addresses

An address is an area and a byte offset: db with the block number for data blocks, i for inputs, o for outputs, m for flags. The offset must suit the tag's data type. Examples from the 1.22 pages:

N3uron address In the PLC Type
m:02 %MW2 integer
db5:01.7 DB5.DBX1.7 Boolean
db5:02 DB5.DBD2 Real, read as Float32

A bit is the byte offset, a dot and the bit number from 0 to 7. An array element sits at the array's start offset plus its position times the element size: TestArray[6] of an Int array starting at byte 1024 is 1024 + 6 × 2, so db5:1036 as Int16. The Appendix reads the same from the Offset column of a data block: an Int at 0.0 is db102:00, a Real at 22.0 is db102:22. In a structure, each element's offset is counted with its own size.

The Examples page notes that a Siemens string takes 256 bytes, a maximum-length byte, an actual-length byte, then the characters, and reads one byte by byte as UInt8 tags. For older S7 PLCs behind an Ethernet/MPI converter, the Appendix says most converters turn rack and slot into the MPI address: MPI 2 is rack 0, slot 2, and in the common assignment it tabulates, MPI 32 is rack 1, slot 0. The converter maker's documentation has the exact assignment.

4. What an S7-1200 or S7-1500 needs

The Siemens Client introduction lists two changes in the PLC: optimized block access turned off, and access level "full" with a connection mechanism that allows PUT/GET. The 1.21 version of the page adds that TCP port 102 must be open for S7 communication and that ICMP traffic must be enabled when the driver runs on Windows; the 1.22 page no longer prints that note.

5. Modbus Client: channels and devices

The Modbus Client supports Modbus TCP, Modbus RTU and RTU over TCP, with function codes 01, 02, 03, 04, 05, 06 and 16. Function 16 is supported but, the page notes, cannot do multiple writes and works like function 6.

A Channel is the physical medium; a Device is one slave on it, so several slaves on one serial bus are several devices in one channel. A tag points to Channel/Device.

  • Channel: TCP with host and port (the example uses 502, the default), or serial with port name (COM1 on Windows, /dev/ttyS0 on Linux), baud rate 110 to 115200, data bits, stop bits, parity and flow control. Request timeout 100 to 600,000 ms (default 3,000), retry attempts 0 to 100 (default 3), inter-request delay (default 0). With Auto-reconnect on timeout, the channel reconnects when all its devices stop responding.
  • Device: Modbus Slave ID 0 to 255 (default 1); Modbus addresses offset, added to every address of the device (−65536 to 65536); Enable Modbus function 6, which picks function 6 or 16 for single-register writes; block sizes of 1 to 2000 bits for coils and 2 to 240 bytes for registers.
  • Auto-demotion: after successive failures (default 3), the device is paused for a delay (default 60,000 ms) so it does not hold up the others on the channel.

For a device that accepts only one Modbus connection, the Modbus Gateway module holds that connection and opens TCP servers for other clients, by default on port 3005, each with a priority from 1 to 10.

6. Modbus addresses, data types and byte order

Register type Address example
Coil 000001
Discrete input 100001
Input register 300001
Holding register 400001
Bit in an input or holding register 400001.<bit>, bit 0 to 15
String 400001:<length>, 1 to 250 bytes

The data types are Boolean, UInt16, Int16, UInt32, Int32, Int32-M10K, UInt64, Int64, Float32, Double64 and String; the scan rate is at least 100 ms, default 5,000 ms. The Examples page builds an inverter's tags from its memory map, for example 400106 read as Int16 and scaled.

Byte order is set per device with five swaps: bits in 16-bit types (only for bits read from a word), bytes in 16-bit types (00AA becomes AA00), words in 32-bit types (0000 AAAA becomes AAAA 0000), double words in 64-bit types, and bytes in strings.

For long register maps, tags can be exported to CSV, edited in bulk and imported; imported tags overwrite those of the same name in the target folder.

7. Omron NJ and NX through the EtherNet/IP Client

From 1.22.0, the EtherNet/IP Client has a PLC type Omron NJ/NX next to the Allen-Bradley types. A device needs the PLC's IP address and port, 44818 by default. For CIP-based PLCs, a tag uses the variable name as defined in the controller. Browsing is not supported for Omron PLCs, so names are typed in and must match exactly. A device template lets several PLCs of one type be created at once. The pages do not say what to set in the Omron controller.

8. When a tag goes bad

Every N3uron tag carries a value, a timestamp and a quality, and the Platform Introduction lists the Data Delivery modules that pass tags on, among them MQTT Client, Sparkplug Client, OPC UA Server, Modbus Server and REST API Server. The Tags Overview lists codes such as 8 Bad Not Connected, 24 Bad Communication Failure, 32 Bad Uninitialized and 192 Good; bad tags show in red in the Real-Time view.

Each module instance has its own logger, which records communication problems, errors and warnings; logs are read under System > Diagnostics > File Logs, one file per day. System > Diagnostics > Modules shows whether each module runs, with its CPU, memory, licence state and version.

What is seen What the pages say
tags stay Bad Uninitialized data collection is disabled on the device or channel
SiemensClient or ModbusClient missing from the module type list that driver is not installed on the machine
one slave on a serial channel keeps failing auto-demotion pauses it so the others are still read

What we check first

This is TDL's practice, not an N3uron requirement.

  • We back up the PLC program before any change and note the CPU type, firmware and port.
  • On an S7-1200 or S7-1500, we ask the plant whether optimized block access may be turned off and PUT/GET allowed. Both change the PLC project, so we agree who makes the change and when, and keep backups from before and after.
  • We take rack and slot from the PLC hardware configuration, check the network path and switch to the node, and that port 102, 502 or 44818 is open.
  • For a serial device behind a converter, we check whether the converter translates to Modbus TCP or passes RTU frames over TCP, which decides between Modbus mode TCP and RTU encapsulated.
  • We read one known value from the register map first, then set the offset and word swap until it matches the device's own display.
  • We size the polling load: scan rates, block sizes, inter-request delay.
  • We settle tag names and folders early; the Tags Overview warns that renaming or moving a tag is likely to break references to it.

How TDL approaches it

TDL Industrial Automation is a Certified Integrator of N3uron, listed on N3uron's partner page. We have met these plant situations on other platforms. At Yakult Vietnam a Mitsubishi FX-series PLC stays in service and its data reaches a FactoryTalk Optix SCADA through a Modbus RTU to Modbus TCP gateway. At SEHC a new air compressor joined the AVEVA System Platform FMCS SCADA through a Modbus RTU to Modbus TCP converter and KEPServerEX. On the SEHC VD5 rooftop, Siemens PLCs, HMIs and converters that had stopped working were replaced by a CompactLogix controller; on Vietsovpetro's LP compressor, a Siemens S5 system was replaced by ControlLogix.

Next steps for the data: N3uron to Canary Historian over MQTT Sparkplug B; Modbus with Kepware: Bringing AHUs and air compressors into an FMCS. The same Modbus settings in Ignition, Kepware and AVEVA are compared in Modbus RTU and TCP for SCADA, and the Siemens, Mitsubishi and Omron drivers of other platforms in PLC drivers compared. Services: N3uron integrator in Vietnam and Connecting existing PLCs and equipment to SCADA.

Frequently asked questions

Can N3uron read a Siemens S7-1200 or S7-1500?

Yes, with the Siemens Client module over S7 on TCP/IP. The PLC needs optimized block access turned off, access level "full" and a connection mechanism that allows PUT/GET.

How is a data block bit written in N3uron?

As db, the block number, a colon, the byte offset, a dot and the bit number from 0 to 7. DB5.DBX1.7 in the PLC is db5:01.7 in N3uron.

What are the default rack and slot in the Siemens Client?

Rack 0 and slot 2, each settable from 0 to 255. The Examples page uses rack 0 and slot 1; we take the values from the PLC hardware configuration.

Does the N3uron Modbus Client write with function 16?

Function 16 is supported but works like function 6, one register at a time. The device setting Enable Modbus function 6 chooses which of the two is used for single-register writes.

Can N3uron read Omron or Mitsubishi PLCs?

Omron NJ and NX, through the EtherNet/IP Client from version 1.22.0, with variable names typed in because browsing is not supported for Omron. We found no Mitsubishi module in the 1.22 list; a PLC whose data is offered over Modbus can be read with the Modbus Client.

Sources

Read 15 November 2026. This article paraphrases the sources and does not quote them; read the original documents before designing or working on a system.

Related services:
N3uron (IIoT and DataOps) Connecting existing equipment to SCADA