Configuration

Note:

This module is available from N3uron version 1.22.0.

Note:

Before starting the configuration, a new module instance must be created. Click here for more information about creating Module instances.

Module Configuration

To create a new EtherNet/IP Client device (or instantiate one from a template), follow the numbered steps in the image:

1. Go to System → Config.

2. In the Explorer panel, expand the Modules section.

3. Select the newly created EtherNet/IP Client module instance, which in this case is named EthernetIP Client.

4. In the Model panel, click the ≡ menu and choose New device.

5. Choose the following options from the dropdown menu:

   • Select device to create a new one from scratch directly in the model.

   • To create a device from a Template, select the new device from the available Templates. In this example, there are two templates for ControlLogix and Omron NJ/NX types of PLCs.

     Tips:

     Using templates is a great idea when working with multiple PLCs of the same type, since you just need to instantiate the template as many times as needed and tweak the settings through Custom properties like IP address, Array block size, Port, Connection Path, etc.

Device Configuration

Array block size guidelines:

• Only applicable when the Struct Type is set to Array.

• The value must be within the range of 100 to 3000.

• Larger block sizes improve performance by reducing overhead, but may increase memory usage and latency.

Request timeout guidelines:

• Enter the value in milliseconds.

• Valid range: 100 to 1,000,000 milliseconds (0.1 to 1000 seconds).

• If the device does not respond within the specified time, the operation will be marked as failed, and the tag will not update.

Retry attempts guidelines:

• Valid range: 0 to 1000

• A value of 0 means no retries; a single failed attempt will be treated as a failure.

• Higher values allow more tolerance for transient network issues but may delay error detection.

Notes:

Array block size

• The array block size should not exceed the actual size of the array in the PLC.

• Choosing a block size that is too large may result in read errors or inefficient communication.

• Adjust the array block size based on the expected array size and performance requirements of the system.

Request timeout

• A lower timeout value may improve responsiveness in detecting communication issues.

• A higher timeout value may be necessary for slow networks or devices that take longer to respond.

• Select a timeout that balances reliability and performance based on your network conditions and PLC behavior.

Retry attempts

• Use higher retry values for unstable or noisy networks.

• Use lower values for time-sensitive applications where fast failure detection is important.

• The retry logic is applied per request and works in combination with the Timeout setting.

Notes:

• The ControlLogix PCCC type is intended for ControlLogix PLCs communicating using legacy PLC/5 protocol (PCCC).

• For CompactLogix PLCs, use ControlLogix.

Guidelines:

• Use standard IPv4 format (e.g., 192.168.1.10).

• The PLC must be reachable from the node's network interface.

• Ensure that firewall rules and network configurations allow TCP communication on the required ports.

Tips:

• 1 typically refers to the backplane port.

• The specific values depend on your network layout and hardware configuration. Consult your system documentation or configuration tools for accurate route information.

Note:

Ensure the port is permitted and not in use by any other application.

Incorrect or missing route paths may result in connection errors or data access failures.

Tag Configuration

Once you’ve created and set up the EtherNet/IP device in the instantiated module, you can create tags and link them to the device either manually or by using the EtherNet/IP Client’s Browser. Select the desired device, then drag and drop the tags you wish to add into the Tag Model.

The Source section links each tag to the EtherNet/IP Client module and defines how the tag value is obtained from or written to the device.

Guidelines Struct type:

• Choose Single element for scalar variables or individual data points.

• Choose Array when you intend to read or write multiple consecutive elements as a block.

• Ensure the data type and element count match the array's actual definition in the PLC.

• Selecting the correct structure is essential for accurate data handling and to prevent communication errors.

Guidelines Scan rate:

• Enter the scan rate in milliseconds.

• Lower values result in faster updates but increase network and CPU load.

• Higher values reduce system load but may delay the detection of value changes.

Notes:

Device name

• If the name of the Device does not match an existing device, the tag will fail to resolve or communicate.

• Changing the name of a device in the module configuration requires updating all associated tags to use the new name.

Scan rate

• The scan rate should be selected based on the priority and frequency of change of the tag's value.

• Critical or fast-changing data may require lower scan rates.

• For infrequently changing values, a higher scan rate can improve performance.

Variable name

• Ensure the name or address matches exactly what is defined in the PLC program.

• Some common abbreviations and shorthand formats are supported automatically.

• Incorrect variable names may result in tag resolution errors or data read/write failures.

Tips:

To replace a Variable name that a tag points to with another variable in the device, use the Browser shortcut in the tag source configuration. Just click the Search icon next to the Config → Source label and select the desired tag.