A Modbus device cannot be browsed, so every SCADA tag comes from the supplier's register map, and a few driver settings decide whether the value on the screen is right. This article compares those settings in Ignition (8.1 and 8.3), Kepware, AVEVA's MBTCP Communication Driver and N3uron's Modbus Client, from each vendor's documentation. The FMCS side of the same work: Bringing AHUs and air compressors into an FMCS SCADA.
1. Register tables and function codes
Ignition's manual lists the four tables of the Modbus specification: coils (read/write bits), discrete inputs (read-only bits), input registers (read-only
| Table | Ignition | Kepware | AVEVA MBTCP | N3uron | Function codes listed |
|---|---|---|---|---|---|
| Coils | C1 | 000001, Output Coils | 1, Output Coils | 000001 | read 01; write 05, 15 |
| Discrete inputs | DI1 | 100001, Input Coils | 100001, Contacts | 100001 | read 02 |
| Input registers | IR1 | 300001, Internal Registers | 300001, Input | 300001 | read 04 |
| Holding registers | HR1 | 400001, Holding Registers | 400001, Holding | 400001 | read 03; write 06, 16; bit write 22 |
Kepware pads short addresses, so 41, 401, 4001, 40001 and 400001 are the same register. N3uron lists neither 15 nor 22, and its function 16 writes one register at a time, like function 6. Each driver can avoid a multiple-write function the device rejects (Kepware: Modbus Function 06 and 05; Ignition: Allow Write Multiple Registers Request; AVEVA: Support multiple register write and Support multiple coil write; N3uron: Enable Modbus function 6). Without function 16, Ignition 8.1 warns that
2. Counting from 0 or from 1
Ignition's 8.1 page notes that the Modbus specification counts addresses from zero. What a typed number means depends on one setting per driver:
- Kepware, Zero-Based Addressing: enabled by default; one is subtracted from the entered address, as on Modicon PLCs. Disable it if the device does not follow that convention.
- AVEVA MBTCP, Use Zero Based Addressing: cleared by default, so item 400001 reaches register 00000 and 400000 is invalid; checked, 400000 reaches 00000.
- Ignition, Zero-based Addressing: checked, each area starts at 0; cleared, at 1 (8.1 page).
- N3uron: the device settings list no zero-based option; a Modbus addresses offset (−65536 to 65536) is added to every address of the device.
With defaults, Kepware and AVEVA send the same request for 400001, although one option is on and the other off, so check what each option does before a tag list is copied to another platform. Ignition's manual suggests creating HR0, HR1 and HR2 by hand and changing the settings until the values are right.
3. Word order, byte order and bits
A float or a
- Kepware: First Word Low is enabled, so the first register is the low word; First DWord Low does the same for
64-bit values; Modbus Byte Order is enabled, and disabling it reads Intel byte order. - Ignition: the 8.1 page puts the high word first; Reverse Word Order puts the low word first.
- AVEVA MBTCP: Use Concept data structures (Longs) and (Reals), checked by default, use the register order of the Concept programming software; Register Order picks one of four orders for
64-bit values; Swap bytes is checked by default. - N3uron: separate switches swap bits, bytes, words in
32-bit values, double words in64-bit values and bytes in strings.
Bits are numbered differently too. N3uron counts 0 to 15; Kepware 0–15 or 1–16, depending on Zero-Based Bit Addressing; AVEVA writes the bit after a colon, 1 to 16, and by default bit 1 is the most significant. In Ignition, HR1024.0 is the first bit, and bit addressing needs a device that supports Mask Write. Kepware uses function 22 only when Holding Register Bit Writes is enabled; otherwise it reads, modifies and writes back the whole register.
4. One point, four syntaxes
The same points in each driver's documented syntax; the device name Dev and unit ID 3 are examples.
| Point | Ignition | Kepware | AVEVA MBTCP | N3uron |
|---|---|---|---|---|
| holding register 1, signed |
[Dev]HR1 | 400001, type Short | 400001 S | 400001, Int16 |
| holding registers 1–2 as a float | [Dev]HRF1 | 400001, type Float | 400001 F | 400001, Float32 |
| one bit of holding register 1 | [Dev]HR1.0 | 400001.0 | 400001:1 | 400001.0 |
| [Dev]HRS1:20 | 400001.20H | 400001:20, String | ||
| unit ID 3 behind a gateway | [Dev]3.HR1 | device ID IP.3 | ModbusPLCRS, PLC unit ID 3 | device, Modbus Slave ID 3 |
Ignition's address mapping and AVEVA's Device Items tab build browsable item lists from such addresses, and both import and export CSV files.
5. Unit IDs and RTU-to-TCP gateways
The drivers describe two kinds of gateway between
Conversion to Modbus TCP. The driver connects to the gateway's IP address, port 502 by default, and the unit ID picks the serial device. Ignition wants one device connection per IP address, with the unit ID in the item path or the address mapping. Kepware's device ID is the host followed by a Modbus server ID from 0 to 255, 0 when no bridge is used. N3uron gives each device a Modbus Slave ID (0 to 255, default 1), several devices to a channel. AVEVA places ModbusPLCRS objects with a PLC unit ID (0 to 255, default 1) under a ModbusBridge object, for the bridges its hardware list names (NR&D Pen-T, Power Logic EGX 100, TSX ETG 100); the direct ModbusPLC connection lists no unit ID.
RTU frames inside TCP. Ignition calls this Modbus RTU over TCP and N3uron RTU encapsulated. Kepware reaches such a terminal server with the Modbus RTU Serial driver and Ethernet Encapsulation, set up as if the device were on a local serial port, up to 255 devices per channel.
Kepware's exception list gives two gateway codes: 10, gateway path unavailable (usually a misconfigured or overloaded gateway), and 11, gateway target device failed to respond (usually a device not on the network). On the serial side, Kepware recommends at most 32 devices per channel without signal amplification, and Ignition's Modbus RTU driver has an
6. Request size, polling and timeouts
| Setting | Ignition | Kepware | AVEVA MBTCP | N3uron |
|---|---|---|---|---|
| holding registers per request | 125 read, 123 write (8.3 defaults) | 1–120, default 32 | up to 122 read, 100 write | 2–240 bytes |
| coils per request | 2,000 | 8–2,000, default 32 | up to 1,976 read, 800 write | 1–2,000 |
| response timeout | Communication Timeout, ms | Request Timeout, usually 1,000 ms | Reply timeout, default 3 s | Request Timeout, default 3,000 ms |
Larger blocks mean fewer requests, but Kepware warns that a block covering addresses the device does not have may be rejected, and by default it stops polling a block that returns exception 2 or 3. Ignition's manual suggests setting Max Holding Registers Per Request to 1 while testing, because one bad address can turn every test tag Bad, and setting it back afterwards, because 1 strains the system once there are hundreds of tags. AVEVA keeps every query and response within the
Poll rates are set per tag group in Ignition (Ignition Logix driver), per device group Update Interval in AVEVA (AVEVA OI Server for ControlLogix) and per tag Scan rate in N3uron, 5,000 ms by default. Kepware and N3uron can take a failing device off scan so it does not slow its channel: Kepware after 3 failed cycles, for 10,000 ms by default, N3uron after 3 failures, for 60,000 ms.
What we check first
This is TDL's practice, not an Inductive Automation, PTC, AVEVA or N3uron requirement.
- We back up the PLC program before any change, and get the register map with the data type, word order and scaling of each point.
- We check the device port (
RS-485 or Modbus TCP), baud rate, parity and station number, and which kind of gateway is used. - We confirm with the plant whether device-side settings, such as a station number, may be changed.
- We test one point of known value per data type with a request size of 1, and settle zero-based addressing, word order and bit numbering before building the tag list.
- We ask how many TCP connections the device or gateway accepts and what else polls it.
- We set poll rates from what screens and historian need, keep slow serial devices on their own channel, and name tags the same way for every unit of one type.
How TDL approaches it
TDL Industrial Automation is a System Integrator in the Rockwell Automation PartnerNetwork, a System Integrator member of the AVEVA Partner Ecosystem, an Ignition Certified Integrator and a Certified Integrator of N3uron. Two of our project pages describe this kind of link:
- Yakult Vietnam ice bank monitoring SCADA (2026): the existing Mitsubishi FX-series PLC stays in control. Its serial port reaches the FactoryTalk Optix SCADA workstation through a Modbus RTU to Modbus TCP gateway and a Stratix switch, and the PLC program was backed up before any change.
- SEHC new air compressor into the FMCS SCADA (2025 to 2026): a Modbus RTU to Modbus TCP converter and KEPServerEX bring the compressor into the FMCS SCADA on AVEVA System Platform, with new tags, objects, graphics, historian and report entries.
Which drivers each platform documents for Siemens, Mitsubishi and Omron PLCs: PLC drivers compared. The services: connecting existing PLCs and equipment to SCADA and facility monitoring (FMCS).
Frequently asked questions
Is 400001 the first register or the second?
With default settings, the first. Kepware subtracts one from the entered address, and AVEVA's MBTCP maps 400001 to register 00000 unless zero-based addressing is checked. Ignition gives HR1 as the equivalent of 40001. If the device's map counts from zero, change the zero-based setting or, in N3uron, the address offset.
Which setting fixes a float that reads wrong?
The word order. It is First Word Low in Kepware, Reverse Word Order in Ignition, the swap of words in
How do I read several RS-485 devices through one Modbus TCP gateway?
Give each device its unit ID. In Ignition, keep one device connection for the gateway and put the unit ID in the item path, such as 3.HR1, or in the address mapping. In Kepware it follows the IP address in the device ID; in N3uron it is each device's Modbus Slave ID; in AVEVA's MBTCP it is the PLC unit ID of a ModbusPLCRS object under a ModbusBridge.
What is the difference between Modbus TCP and Modbus RTU over TCP?
Modbus TCP is the native TCP protocol. RTU over TCP is for devices that put RTU messages inside TCP packets. Ignition and N3uron offer both modes; Kepware reaches a terminal server through the Modbus RTU Serial driver with Ethernet Encapsulation.
Why does one bad register make a whole block of tags go Bad?
The driver reads registers in blocks, and a block that covers an address the device does not have can be rejected. Kepware by default stops polling a block that returns exception 2 or 3; Ignition's manual suggests a request size of 1 while testing, then the normal size again.
Sources
- Inductive Automation, Modbus, Connecting to Modbus Device, Modbus Addressing and Modbus Address Mapping, Ignition 8.3 user manual
- Inductive Automation, Modbus, Connecting to Modbus Device, Modbus Addressing and Modbus Address Mapping, Ignition 8.1 user manual
- PTC, Kepware Drivers help, Modbus TCP/IP Ethernet driver (help version 1.159): Device Properties — General, Device Properties — Ethernet, Device Properties — Settings, Device Properties — Block Sizes, Device Properties — Error Handling, Modbus Addressing and Data Types Description
- PTC, Kepware Drivers help, Modbus RTU Serial driver (help version 1.096): Setup, Device Properties — Settings and Device Properties — Block Sizes; common pages Device Properties — Timing, Device Properties — Auto-Demotion, Device Properties — Ethernet Encapsulation and Modbus Exception Codes
- AVEVA, MBTCP Communication Driver: Get started, Generic modbus controllers, Supported device protocols, Configure a TCPIP_PORT object, ModbusPLC connection, ModbusBridge connection, ModbusPLCRS connection and Supported MBTCP OI server hardware and firmware, Communication Drivers Pack 2026
- AVEVA, MBTCP Communication Driver: Register-number item names, Item names using the Modicon PLC register addresses, Zero- and one-based addressing, Support for
64-bit data types, Controller function codes, Message Optimization, Device group definitions and Device item definitions, Communication Drivers Pack 2026 - N3uron, Modbus Client: Introduction, Configuration and Examples, N3uron Knowledge Base 1.22
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.