Omron FINS Ethernet

See purchasing information for more details
Download Free Demo

Product Overview

The Omron FINS Ethernet driver works in conjunction with KEPServerEX to exchange data between OPC clients and Omron FINS protocol-compliant PLCs via UDP/IP. It also supports Sysmac Link operation for accessing additional PLCs via Sysmac Net. KEPServerEX automatically optimizes data acquisition based on client demand and ensures data integrity through extensive error handling.



  • Supports UDP/IP communications
  • Supports FINS Gateway for Sysmac Link and Sysmac Net access
  • Supports Auxiliary Relay


  • Omron FINS over Ethernet

Supported Devices

  • Devices Supporting FINS protocol via Sysmac Way: Host Link Interface

Available Languages

  • English
  • Japanese
  • Simplified Chinese

Application Support

  • DDE Format CF_Text and AdvancedDDE
  • NIO Interface for iFIX
  • OPC .NET Service (OPC .NET) Version 1.00
  • OPC Alarms and Events (OPC AE) Version 1.10
  • OPC Data Access (OPC DA) Versions 1.0a, 2.0, 2.05a, and 3.0
  • OPC Unified Architecture (OPC UA) Clients
  • SuiteLink and FastDDE for Wonderware

Release Notes



  • Added Chinese language support.



  • Added support for Chinese, Japanese, and Korean (CJK) characters.
  • Added Japanese language support.



  • Enhanced error detection to support remote network errors to place the device in error state. This more accurate reporting supports redundancy failover.



  • Corrected an issue where the driver would produce a syntax error during tag validation if the data type was not supported. Some clients add items with a set data type regardless of the address. The driver now responds with bad type, allowing the driver library to validate again with the default type.



  • Increased the maximum channel limit to 512.


  • Added the ability to select the behavior when writes are issued to TS and CS addresses (when the PLC is in Run Mode). Before, these writes would fail and an error would be logged. Options also exist to set the PLC to Monitor Mode and to perform the write, or to set the PLC to Monitor Mode, perform the write, and then reset the PLC to Run Mode.


  • Added support for the CJ2 Model.
  • Added the reporting of device-level error conditions and detection of network relay error frames. We now output the following error messages instead of posting "Device not responding" messages:
  • Modified the driver to handle the relay error frame when a fatal CPU error is present. The error messages were also updated to include "Main, Sub:" and "Net Addr, Node Addr:" in decimal notation: this should make it easier for users to compare to Device Property settings in the server project.

     • Network relay error.[Net Addr, Node Addr: '0x00, 0x3A'], [End Code: '0x8302']

     • Fatal CPU Unit error.[End Code: '0x0080']

     • Non-fatal CPU Unit error.[End Code: '0x83C2']


  • Fixed Address Hints for the C500 IR register.
  • Added 2 new string types:

    • XXX as string with Only the Low Order byte (LSB - least significant 8-bits) of each word is used for

      read/write. , Syntax: XXXaddr.lenE

    • XXX as string with Only the High Order byte(MSB - most significant 8-bits) of each word is used for

      read/write. , Syntax: XXXaddr.lenD


  • Fixed thread synchronization issue which could result in intermittent stale communications for certain channels in multi-channel projects


  • Fixed thread synchronization issue which could result in intermittent stale communications for certain channels in multi-channel projects
  • Consult the manufacturer's website for a current list of models supporting Sysmac Way: Host Link Interface.

What Is a Driver?

KEPServerEX is more than an OPC server—it's a connectivity platform for industrial automation and IoT. Simply download KEPServerEX, and then select from Kepware's library of more than 150 device drivers, client drivers, and advanced plug-ins to fit the communication requirements unique to your industrial control system.

A driver is a software component that enables KEPServerEX to meet the connectivity requirements of a specific device, system, or other data source. The driver handles all proprietary communications to the data source for KEPServerEX; the client interfaces handle all supported OPC, proprietary, and open standards connectivity to applications that monitor or control the devices.

Drivers may be licensed individually or in suites. Additional drivers can be licensed on demand as connectivity needs evolve.