Omron FINS TCP Data Collection Guide

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 or SCADA). FINS TCP is an implementation that encapsulates the FINS protocol within TCP/IP for Ethernet communication.
  • Application Scenarios: This protocol is widely used in industrial automation scenarios requiring remote monitoring, data acquisition, and control of Omron PLCs via Ethernet.
  • E2C Trinity Support: E2C Trinity supports the standard Omron FINS TCP protocol, acting as a Client to read from and write to Omron 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) and can communicate.
    • The debugging PC must be connected to the gateway via Ethernet to log into the E2C Trinity web interface.
  • Network Parameters:
    • Obtain the IP Address of the target PLC and the FINS TCP Port Number (Default is 9600).
    • 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 or the Data Point List.
    • Identify key parameters:
      • Unit Number: The unit node number of the target PLC.
      • Tag Addresses: Register addresses to be collected (e.g., D100, W10.01, CIO1500).
      • Data Type: Data type for each point (e.g., int16, float32/REAL, bool, etc.).
      • Byte Order: Determine the storage order for 32-bit or larger data types within the PLC.

3. Configuration Steps

Follow these steps within the E2C Trinity Web interface.

Step 1: Create Device

  1. Log into the gateway management page. Navigate to [Data Acquisition] to enter the E2C Trinity configuration page.


 

2. Click the "Create Device" button and fill in the connection information in the pop-up window.

Parameter Description Example
Name Unique identifier for the PLC device. Packaging-Line-A-Machine-02
Driver Select [OMRON] - [FINS TCP] from the dropdown list. OMRON - FINS TCP
IP Address The IP address of the target PLC. 192.168.1.20
Port Number FINS TCP communication port; default is 9600. 9600
Unit Number The unit node number of the target PLC. 0
Polling Cycle (s) Frequency of data requests (Seconds). 5
Byte Order (32-bit int) Specifies the byte sequence for 32-bit data. BADC
Byte Order (String) Specifies whether to reverse the string byte order. False
Connection Timeout (ms) Limit for establishing a TCP connection (ms). 1000
Collection Timeout (ms) Limit for the device to respond to requests (ms). 1000
Description Additional info for user reference. Workshop A Line, Machine 02

3. Click "Save" to complete the device creation.

Step 2: Configure Tag (Point Table)

  1. Select the newly created device from the device list on the left.
  2. Click "Add" to create a single data acquisition Tag. Fill in the tag information.

Parameter Description Example
Name The tag name used in data reports. Temperature
Tag Type Device Tag: Data from the PLC. Virtual Tag: Gateway-side variable. Device Tag
Address Type PLC register type (e.g., D, C, W, H, A, E0~EF). + For example, if the point address in the PLC is D100, configure the "Address Type" as "D" and the "Address" as "100".
+ For example, to read the 3rd bit of the D100 register in the PLC, configure the "Address Type" as "D", the "Address" as "100", and the "Bit Offset" as "3".
Address Specific register address in the PLC.
Bit Offset Required for 'bool' types; specifies the bit index.
Data Type Must match the PLC's data format. short (int16)
Read/Write Permission Read Only or Read/Write (for remote modification). Read Only
Decimals Number of decimal places (for float/double). 2
Unit Engineering units (e.g., °C, pcs). °C
Associated Group Assign the tag to a specific data group. -
Description Brief explanation of the tag's purpose. Heat Zone 1 Real-time Temp
Data Operation Mathematical processing (Scaling, Offset, etc.). None

Repeat the steps to add all necessary tags. Once finished, click the "Publish" button in the top right corner to apply the configuration.

4. Verification & Troubleshooting

Verification

  1. Check the device list to ensure the status is Online and tags are successfully collected.

2. View the Latest Value column to verify data accuracy.

3. 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 remains offline.
    • Verify physical cable connections and link lights.
    • Use the Ping tool in [System -> Tools] to check network reachability.
    • Verify the IP, Port, and protocol settings against the PLC configuration.
    • Check PLC Ethernet module settings; ensure a connection or port is configured for the host (E2C Trinity).
  • Issue: Connected, but values are null or incorrect.
    • Verify Address and Data Type: Ensure the "Address Type" and "Address" match the PLC program exactly.
    • Ensure the addressed register exists and the PLC program is running.
    • Check [Debug Logs] to filter by device and identify specific error details (e.g., address out of range, permission denied).

5. Appendix: Data Type Mapping

When configuring tags in E2C Trinity, use the following mapping:

E2C Trinity Type Length / Sign Omron PLC Equivalent Example Address Notes
bool 1 bit BOOL D100.0, W10.05 Reads a bit from a word address.
ushort (uint16) 16 bit (Unsigned) UINT, WORD D200, W30 Standard 16-bit word.
short (int16) 16 bit (Signed) INT D201, C100 Standard 16-bit signed integer.
uint (uint32) 32 bit (Unsigned) UDINT, DWORD D300, W50 Occupies 2 consecutive words. Byte order is critical.
int (int32) 32 bit (Signed) DINT D302 Occupies 2 consecutive words. Byte order is critical.
ulong (uint64) 64 bit (Unsigned) ULINT, LWORD D400 Occupies 4 consecutive words. Byte order is critical.
long (int64) 64 bit (Signed) LINT D404 Occupies 4 consecutive words. Byte order is critical.
float (float32) 32 bit (IEEE 754) REAL D500 Occupies 2 consecutive words. Byte order is critical.
double (double64) 64 bit (IEEE 754) LREAL D502 Occupies 4 consecutive words. Byte order is critical.
string N Bytes STRING, ARRAY D600 Parses consecutive words as characters.

​

Revision History

Version Date Author Changes
1.0 2025-09-22 Ken Li Initial document creation.

    • Related Articles

    • 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 ...

    • 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 ...

    • 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, ...

    • Inovance TCP Data Collection Guide

      1. Protocol Overview Protocol Description: The Inovance TCP protocol is a communication method that allows direct TCP/IP network connection to Inovance PLCs (such as H3U, AM/AC series). It supports efficient data exchange by reading tags or register ...

    • 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 ...