How one Omron controller actually talks to another — or to a drive, an HMI, or a different brand entirely. Two messaging worlds: classic FINS and the EtherNet/IP CIP. Build a message and watch it resolve.
A FINS message says where (destination node), what (a service like memory-area read/write), and which (memory area + address). Assemble one and send it.
Assembled frame
FINS
Omron's native command set. Reads/writes memory areas (D, W, H…) by area + address. Rides over Ethernet (FINS/UDP) or serial. The classic way Omron gear talks to Omron gear and SCADA.
CIP (EtherNet/IP)
The open standard. Implicit messaging streams I/O cyclically; explicit messaging does on-demand reads/writes by tag. The bridge to the wider automation world and other brands.
🌍 Crossing boundaries. Both ride the FINS network/node/unit routing you met in the Platform track — a non-zero network number is what lets a message hop to a remote network, another site, or the cloud gateway.
You need cyclic, real-time I/O exchange with a third-party device. Which messaging fits?