OMRON — FINS and EtherNet/IP CIP in one driver
From classic OMRON PLCs to modern NJ/NX controllers. MergenHub unifies FINS/TCP and symbolic CIP access in a single driver, tested against real PLCs.
| Tag | Address | Value | Quality |
|---|---|---|---|
| LineSpeed | Line_Speed | 145.0 | |
| BoxCount | Box_Count | 8213 | |
| Vacuum_OK | Vacuum_OK | 1 | |
| Temp_Zone1 | Temp_Zone1 | 181.4 | |
| Alarm_Active | Alarm_Active | 0 |
The MergenHub interface — CIP access to OMRON NJ/NX symbolic variables; FINS key format and Siemens alias.
What is OMRON communication?
OMRON's classic CJ/CS/CP series communicate over the FINS protocol (via memory areas). The newer NJ/NX controllers use CIP over EtherNet/IP, accessing program variables by symbolic name. MergenHub supports both.
Where is it used?
Machine automation, packaging, production lines and OMRON-based control panels in water/energy plants. Facilities that want to manage both legacy and new OMRON fleets from one platform.
Feature coverage
Classic FINS memory areas and NJ/NX symbolic variables are supported together.
EtherNet/IP CIP
Symbolic variable read/write via ForwardOpen + Multiple Service Packet + UCMM (including the CIP class 0x6B tag list).
FINS / TCP
FINS/TCP for the CJ/CS/CP series; access to DM, CIO, WR, HR and other memory areas.
Standard key format
Compatibility with common OMRON address keys (e.g. the FirstWordLow fix) and Siemens alias mapping.
Symbolic tag generation
Auto-generate tags by discovering program variables from NJ/NX controllers.
Nagle-off
Nagle's algorithm is disabled for low latency; many tags in one round-trip via multiple service packets.
Structured types
Symbolic access to integers, floats, strings and array/structure members.
MergenHub