Omron CipNet Data Collection Guide
1. Protocol Overview
- Protocol Description: CipNet is the term used by Omron for its EtherNet/IP network solution. EtherNet/IP is a widely adopted industrial Ethernet communication protocol that encapsulates the Common Industrial Protocol (CIP) within standard TCP/IP. Unlike protocols based on absolute memory addresses (such as Modbus), CipNet is a tag-based protocol. It retrieves data by accessing pre-defined variable tag names within the PLC, eliminating the need to track specific physical memory addresses.
- Application Scenarios: This protocol is typically used to connect Omron's medium-to-large-scale PLCs, such as the NJ/NX series controllers, to HMIs, SCADA systems, and edge computing platforms like E2C Trinity for efficient data exchange.
- E2C Trinity Support: E2C Trinity supports the Omron CipNet protocol, acting as a Client to read from and write to variables in Omron NJ/NX series PLCs via Ethernet.
2. Prerequisites
Before starting the configuration, please ensure the following:
- Hardware Connection:
- Ensure the E2C Trinity gateway and the target Omron PLC are connected to the same Local Area Network (LAN).
- Ensure the PLC's Ethernet port is configured for EtherNet/IP communication.
- Network Parameters:
- Obtain the IP Address of the target Omron PLC.
- Ensure the E2C Trinity gateway and the target PLC are on the same subnet with no IP conflicts.
- Device Parameters:
- Prepare the PLC project file (Sysmac Studio project).
- Tag List: Identify the "Global Variables" in the PLC that are set to "Network Publish" (Published). Only published tags are accessible via CipNet.
- Identify the Data Type for each tag (e.g., bool, int, real).
3. Configuration Steps
Follow these steps within the E2C Trinity web interface.
Step 1: Create Device
- Log into the gateway management page and navigate to [Data Acquisition].
- Click the "Create Device" button and fill in the information:
| Parameter | Description | Example |
|---|---|---|
| Name | Unique identifier for the PLC device, used to distinguish equipment in the system. | Assembly-Line-NJ-01 |
| Driver | Communication protocol; select [OMRON] - [CipNet] from the dropdown list. | OMRON - CipNet |
| IP Address | The IP address of the target Omron PLC. | 192.168.1.30 |
| Port Number | The EtherNet/IP communication port number (Standard port is 44818). | 44818 |
| Polling Cycle (s) | The frequency of data requests, in seconds. | 5 |
| Connection Timeout (ms) | Max wait time for establishing a network connection (ms). | 1000 |
| Collection Timeout (ms) | Max wait time for the device to respond to a data request (ms). | 1000 |
| Description | Additional information or remarks for the device. | Omron NJ Series Controller |
- Click "Save".
Step 2: Configure Tag (Point Table)
- Select the device and click "Add" to create a Tag.
- Unlike address-based protocols, you must enter the exact variable name defined in the PLC project.
| Parameter Name | Description | Example |
|---|---|---|
| Name | Custom name for the data point for easy identification, used for data reporting. | Temperature, ProcessingCount |
| Tag Type | Select the tag type: + Device Tag: Represents data in the downstream device (PLC). Usually chosen. + Virtual Tag: A virtual tag existing only in the gateway, used as an intermediate variable. |
Device Tag |
| Address | The tag name in the PLC (e.g., temperature, voltage). For array variables, use notation like <font style="color:rgb(68, 71, 70);">voltage[6]</font>. |
temperature, voltage, voltage[6] |
| Data Type | Select based on the actual data type of the tag in the PLC. | short(int16) |
| Read/Write Permission | Access permission of the gateway to this tag in the PLC: + Read Only: Gateway can only read. + Read/Write: Gateway can read and modify. |
Read Only |
| Negation | Effective when data type is bool; if enabled, the read value is inverted before being transmitted. | Enabled/Disabled |
| Decimal Places | Number of decimal places (effective for float(float32) or double(double64)). | 2 |
| Encoding Format | Effective for string; supported: ASCII, ANSI, UTF8, UTF16, UTF16Big, GB2312. | ASCII |
| Length | Effective for string or bcd; number of characters. | 10 |
| Associated Group | [Optional] Select the data group the tag belongs to. | - |
| Unit | The unit of the value, such as °C, pcs, etc. | °C |
| Description | [Optional] Description of the tag. | Real-time temperature of heating zone 1 |
| Data Operation | Mathematical processing of collected data (None, Offset/Scale, Linear conversion, etc.) | - |
- Click "Publish" to apply the settings.
4. Verification & Troubleshooting
Verification
- Check the device list to ensure the status is Online and tags are successfully collected.
- View the Latest Value column to verify data accuracy.
- Test Writing: Click the edit icon in the "Latest Value" column, modify the value, and verify if the PLC accepts the change in the next polling cycle.
Common Troubleshooting (FAQ)
- Issue: Device is online, but tag values are "Bad Quality" or null.
- Check "Network Publish" Status: In Sysmac Studio, ensure the target variable is set to "Publish to Network" (Network Publish: Publish Only or Publish/Subscribe).
- Verify Tag Name: The "PLC Tag Name" in E2C Trinity must match the PLC variable name exactly, including case sensitivity.
- Issue: Device remains offline.
- Ensure the gateway can ping the PLC's IP address.
- Verify that the PLC's internal network settings allow EtherNet/IP connections.
5. Appendix: Data Type Mapping
| E2C Trinity Type | Length / Sign | Omron PLC Type |
|---|---|---|
| bool | 1 bit | BOOL |
| ushort (uint16) | 16 bit, Unsigned | UINT, WORD |
| short (int16) | 16 bit, Signed | INT |
| uint (uint32) | 32 bit, Unsigned | UDINT, DWORD |
| int (int32) | 32 bit, Signed | DINT |
| ulong (uint64) | 64 bit, Unsigned | ULINT, LWORD |
| long (int64) | 64 bit, Signed | LINT |
| float (float32) | 32 bit | REAL |
| double (double64) | 64 bit | LREAL |
| string | N Bytes | STRING |
Revision History
| Version | Date | Author | Changes |
|---|---|---|---|
| 1.0 | 2025-10-9 | Ken Li | Initial document creation. |
Related Articles
Omron HostLink Data Collection Guide
1. Protocol Overview Protocol Description: HostLink is a serial communication protocol developed by Omron for its PLC products, primarily used for data exchange and monitoring between host systems (such as programming software, HMI, or SCADA) and ...Omron FINS TCP Data Collection Guide
1.Protocol Overview Protocol Description: FINS (Factory Interface Network Service) is a communication protocol developed by Omron for its PLC series (e.g., CP, CJ, and CS series) to facilitate data exchange between PLCs and host systems (such as HMI ...Omron HostLink over TCP Data Collection Guide
1. Protocol Overview Protocol Description: HostLink is a serial communication protocol developed by Omron for its PLC products. "HostLink over TCP" is an implementation that encapsulates this serial protocol within TCP/IP, allowing host systems or ...OPC UA Data Collection Guide
1. Protocol Overview Protocol Description: Modbus TCP is a common industrial automation protocol based on TCP/IP network transmission. Application Scenarios: This protocol is widely used for data acquisition and control of devices such as PLCs, ...Modbus TCP Data Collection Guide
1. Protocol Overview Protocol Description: Modbus TCP is a common industrial automation protocol based on TCP/IP network transmission. Application Scenarios: This protocol is widely used for data acquisition and control of devices such as PLCs, ...