N3uron reads ControlLogix and CompactLogix controllers with its EtherNet/IP Client module, which the N3uron Knowledge Base lists from version 1.22.0. This article follows the Knowledge Base 1.22 pages for that module and the platform pages it relies on: which PLC types it covers, the device settings and connection path, how controller and program tags and arrays are addressed, scan rate and array block size, and where to look when a tag goes bad. How N3uron itself is built is covered in What is N3uron.
1. What the EtherNet/IP Client covers
The module connects N3uron to devices that use EtherNet/IP, which the page describes as CIP over TCP/IP. Its data then reaches other systems through N3uron's Data Delivery modules, such as MQTT Client, OPC UA Server, Modbus Server, DNP Server, Sparkplug Client and REST API Server. The Introduction lists an integrated browser with drag and drop, unlimited tags and devices, manual or browsed tag creation, and an array block size setting that cuts the number of separate reads.
The device setting PLC type decides how the driver formats its requests. The types on the 1.22 page:
| PLC type | What the page says it covers |
|---|---|
| ControlLogix | ControlLogix-class PLCs, CompactLogix included; the page says to use this type for CompactLogix |
| ControlLogix PCCC | A ControlLogix-class PLC that communicates with the legacy |
| The Allen-Bradley |
|
| SLC 500 | The Allen-Bradley SLC 500 series |
| MicroLogix | The Allen-Bradley MicroLogix series |
| Micro800 | The Allen-Bradley Micro800 series |
| Omron NJ/NX | The Omron NJ/NX series, without tag browsing |
The pages name no controller firmware revisions. Siemens and Modbus devices use other N3uron modules: see N3uron with Siemens S7 and Modbus.
2. Module instance and device
A module is used through an instance. Under Config, Modules, a new module is created, its type set to the EtherNet/IP Client and its name chosen; the name cannot contain special characters such as "." or "/". Each instance has Auto-start, with a start delay after the N3uron service starts, and Auto-restart, which restarts the module when it goes offline unless a user stopped it.
A device is one PLC connection. It is added under System, Config: select the module instance in the Explorer panel, open the menu in the Model panel and choose New device, either from scratch or from a template. The page recommends templates when there are several PLCs of the same type, with the IP address, array block size, port and connection path set per instance as custom properties.
| Setting | What it does | Range, as printed |
|---|---|---|
| Enable data collection | Off: no communication with the device, its tags stay Bad – Uninitialized | On or off |
| PLC type | How requests are formatted | The seven types above |
| IP address | IPv4 address of the PLC, required | For example 192.168.1.10 |
| Port | TCP port | 1 to 65535, default 44818 |
| Connection Path | Route to the PLC through a module or bridge | Comma-separated integers |
| Array block size | Elements read per request, for tags whose Struct type is Array | 100 to 3000 |
| Request timeout | Longest wait for a response | 100 to 1,000,000 ms |
| Retry attempts | Retries before the device is marked unreachable | 0 to 1000; 0 means no retry |
Only the port has a default on the page. The PLC must be reachable from the node's network interface, firewall rules must allow TCP on the port, and the port must not be in use by another application.
3. Connection path
The page says a connection path is typically needed when the PLC is reached through a dedicated Ethernet module rather than a built-in Ethernet port, or through another device acting as a bridge. Its example is a ControlLogix gateway used to reach ControlLogix, CompactLogix,
The path is a comma-separated list of integers, read in pairs: a port, then a link address such as a slot number or a remote node. Port 1 typically refers to the backplane.
| Route | Connection path |
|---|---|
| Controller in slot 0 of the backplane | 1,0 |
| Through a DHRIO module in slot 3, channel A, to node 10 | 1,3,2,10 |
The exact values depend on the network layout and hardware, and the page refers to the system's own documentation and configuration tools. A wrong or missing path can cause connection errors or data access failures. How Ignition handles the path to the same controllers: Ignition Logix driver.
4. Tags: controller tags, program tags and arrays
Tags are created in the tag model by hand, or by opening the device in the module's browser and dragging tags into the model. To point an existing tag at another variable, the search icon next to the Source label opens the browser again. The Source section of each tag holds:
| Setting | Meaning |
|---|---|
| Enabled | The module supplies value, quality and timestamp; disabled, the tag acts as a memory tag |
| Module type, Module name | The EtherNet/IP Client and the name of its instance |
| Config – Device | The device name, matching letter case exactly, for example PLC_Main |
| Config – Struct type | Single element for one value; Array for consecutive elements read as a block |
| Config – Scan rate | Refresh time in ms: 1000 is once a second, 100 is ten times a second |
| Source – Variable name | The tag name or memory address in the PLC |
| Source – Value type | Boolean, UInt8, Int8, UInt16, Int16, UInt32, Int32, UInt64, Int64, Float32, Double64, String, String2, Short string |
For CIP-based PLCs, the variable name is the tag name as defined in the controller. A tag inside a program is written as Program:, the program name, a dot and the tag name, so the page's example Program:MainRoutine.MotorSpeed reads MotorSpeed in the program MainRoutine. Names must match the PLC program exactly; the page adds that some common abbreviations and shorthand forms are accepted, without listing them. For PCCC-based PLCs, the variable name is a file address: N7:4 (integer file 7, element 4), B3:4/2 (bit 2 of word 4 in binary file 3), ST18:26 (string file 18, element 26), L20:2 (long integer file 20, element 2) or MG14:6.en (the .en bit of message file 14, element 6).
For arrays, the page's examples are MyArray[0] and N7:0 to N7:9. The value type and element count must match the array as defined in the PLC, and the array block size should not exceed the real array size; a block that is too large can cause read errors. The Struct type list has only Single element and Array, and we found nothing on the pages about reading a user-defined type (UDT) as a whole.
Tag names in N3uron need not match the PLC tag names, and they cannot contain ".", "/" or "\". The Tags Overview warns that renaming or moving a tag that is used elsewhere is likely to break the reference, and the EtherNet/IP Client page adds that renaming a device means updating every tag that uses it. For repeated equipment, a tag template with custom properties builds one structure and many instances. Long lists can be exported to CSV, edited and imported; imported tags overwrite tags of the same name in the target folder, and templates must be imported before their instances.
5. Scan rate, array block size and load
The page gives the trade-offs but no numbers for controller load. A lower scan rate updates faster and raises network and CPU load; it should follow how important a value is and how often it changes. A larger array block size reduces overhead but can increase memory use and latency. A shorter request timeout detects communication problems sooner, a longer one suits slow networks or slow devices, and retries apply per request on top of the timeout: more retries for noisy networks, fewer where fast failure detection matters. If no response comes within the timeout, the operation fails and the tag does not update.
6. When tags go bad
Every N3uron tag carries a value, a timestamp and a quality. Codes on the Tags Overview include 4 Bad Configuration Error, 8 Bad Not Connected, 24 Bad Communication Failure, 32 Bad Uninitialized and 192 Good. Bad tags show in red under Data, Real time.
| What is seen | What the pages say |
|---|---|
| Tags stay Bad – Uninitialized | Data collection is disabled on the device |
| A tag stops updating | The device did not answer within the request timeout |
| Connection errors or data access failures | The connection path is wrong or missing |
| A tag fails to resolve | Its Device name does not match a configured device |
| Resolution errors or read and write failures | The variable name does not match the PLC program |
| Read errors on an array tag | The array block size is too large |
| EtherNet/IP Client missing from the module type list | The module is not installed |
Module logs record startup, runtime activity, communication issues, errors and warnings. Each module instance has its own Logger: enabled by default, level Info, logs kept 7 days. The levels run Error, Warning, Info, Debug and Trace; the Logger page advises Debug or Trace only while collecting evidence, then a return to Info. Under System, Diagnostics, Real Time Logs shows live events per instance with name and message filters, and File Logs loads and exports the log files, which sit in the log folder of the N3uron installation, one folder per module instance and one file per day. Diagnostics, Modules shows whether each instance runs, with its CPU, memory, licence state and version, and can start, stop or restart it.
7. Redundancy
The EtherNet/IP Client pages say nothing about redundant controllers or redundant paths. The Redundancy Agent module switches a TCP connection between a primary and a backup host; its examples are Modbus, DNP3 and Siemens devices, OPC UA servers, databases and N3uron Links, and the page adds virtually any system that offers a primary and a backup connection over TCP. EtherNet/IP is not named among the examples. N3uron's own redundant node pair is covered in What is N3uron.
What we check first
This is TDL's practice, not an N3uron requirement.
- We confirm the node runs 1.22.0 or later, and read the module version under Diagnostics, Modules.
- We find out how the node reaches the controller: built-in port or an Ethernet module in the chassis, the controller's slot, and any bridge on the way. We write the connection path from that, pair by pair.
- We check the network path from the node's interface, the switch port, and that TCP 44818 is open through every firewall.
- We get the tag list from the PLC project, mark which tags are program tags, and copy names exactly.
- We read one known tag first, compare it with the PLC value, then add the rest.
- We set scan rates by how fast each value changes, keep array block sizes within the array lengths, and watch the module's CPU in Diagnostics. The CIP connection counts Rockwell publishes for its Ethernet modules are quoted in the Ignition Logix driver article.
- We settle tag names, folders and templates before the first import, because renaming later breaks references.
How TDL approaches it
TDL Industrial Automation is a Certified Integrator of N3uron, listed on N3uron's partner page. We add N3uron alongside the existing control system, without changing the programs that run the plant. Where the data goes next: N3uron to Canary Historian over MQTT Sparkplug B. The same controllers on other platforms: Ignition Logix driver and AVEVA OI Server ABCIP; other PLC makes in PLC drivers compared. Services: N3uron integrator in Vietnam and Connecting existing PLCs and equipment to SCADA.
Frequently asked questions
Can N3uron read a CompactLogix?
Yes, with the EtherNet/IP Client module from version 1.22.0. The page says to choose the PLC type ControlLogix for a CompactLogix.
What connection path does N3uron need for a ControlLogix?
A path is typically needed when the controller is reached through a dedicated Ethernet module rather than a built-in port, or through a bridge. It is a comma-separated list of port and address pairs; 1,0 reaches a controller in slot 0 of the backplane.
How is a program-scope tag addressed in N3uron?
As Program:, the program name, a dot and the tag name, for example Program:MainRoutine.MotorSpeed. A controller tag uses its name as defined in the controller.
Which port does the N3uron EtherNet/IP Client use?
TCP port 44818 by default, settable from 1 to 65535. Firewall rules must allow TCP on that port between the node and the PLC.
Why do my N3uron tags stay Bad Uninitialized?
The page gives one cause: data collection is disabled on the device, so there is no communication and the tags keep that quality. The module logs under System, Diagnostics show other communication errors.
Sources
- N3uron, EtherNet/IP Client: Introduction and Configuration, N3uron Knowledge Base 1.22
- N3uron, Create a New Module Instance, Creating Tags, Tags Overview, Importing and Exporting Tags, Visualizing Real-Time Values and Templates Overview, N3uron Knowledge Base 1.22
- N3uron, Logger Configuration, Troubleshooting a Module, Real Time Logs, File Logs and Diagnostics: Modules, N3uron Knowledge Base 1.22
- N3uron, Redundancy Agent: Introduction, 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.