How-to
Connecting Citect SCADA to a CP1W-CIF41 over FINS
Short answer
Yes: a CP1W-CIF41 serves Citect SCADA over FINS once the board holds its IP address, subnet mask and FINS node, and a Citect I/O Device runs the OMFINS FINS-over-Ethernet driver at the same IP, node and port. An NJ301 exposes no addresses, so AT-map the variables you need to CJ-compatible DM words before the driver can read them.
On this page
- Does a CP1W-CIF41 work with Citect SCADA?
- How do you set the IP address and FINS node on a CP1W-CIF41?
- How do you define the FINS I/O device in Citect?
- How do you prove the link with one tag before building the database?
- How do you read an NJ301's variables that have no addresses?
- How do you tell a PLC fault from a network fault when the tag will not read?
- How do you verify the finished link end to end?
- Questions asked
Yes. A CP1W-CIF41 Ethernet option board on a CP1-series Omron PLC serves Citect SCADA as a FINS-over-Ethernet I/O device: give the board its IP address, subnet mask and FINS node, then define a Citect I/O Device with the OMFINS driver on the same values. The one setup that does not go through as-is is an NJ-series CPU: a Sysmac Studio program holds named variables, not addresses, so you AT-map each variable the SCADA needs to CJ-compatible memory such as a DM word, or move to a name-based protocol the firmware supports. This article runs the link from board settings to a proven read and write path, and ends each stage with the pass or fail decision.
Does a CP1W-CIF41 work with Citect SCADA? #
Yes. The board carries Omron's FINS/TCP and FINS/UDP stack, and Citect reaches it through its Omron FINS Ethernet driver, OMFINS, so the pairing needs no gateway, no protocol converter and no custom code — only matching IP, subnet, FINS node and port settings at both ends.
The CIF41 sits in the CP1 option-board slot and gives a CP1E, CP1L or CP1H CPU its Ethernet port. A CP1 CPU keeps its data in addressed memory — CIO, DM, work and holding areas — so the FINS driver addresses words directly, the same way it does on a CJ rack. That is the whole compatibility story: one protocol stack, one addressed memory model, one driver.
If the link already exists and throws FINS errors at runtime, you are past setup; the failure modes then match the ones in Fixing Citect SCADA FINS errors to an Omron NX1P2, which works the same driver against an NX-series CPU. A CP1L that cannot go on Ethernet at all falls back to the serial route in Commissioning CP1L Host Link serial reads to SCADA.
How do you set the IP address and FINS node on a CP1W-CIF41? #
The board ships at 192.168.250.1: put your laptop on 192.168.250.x, ping 192.168.250.1, open the board's setup page in a web browser, and enter the plant address, subnet mask and a unique FINS node — then power-cycle the CPU so the option board restarts with them.
Omron's own setup walkthrough moves the board to 192.168.250.20 with mask 255.255.255.0; on a plant network you take the address from your own plan, but the entries stay the same three. Set the FINS node to the address's last octet — 20 for 192.168.250.20 — so the value you type into Citect later is predictable and easy to check against the board. The browser step also covers the second documented route: write 0.0.0.0 into the address through the browser, then own the address from CX-Programmer. Pick one owner for the address and never mix the two, or the board will answer on different addresses after different power-ups.
Gate this section before Citect is opened: ping the new address from the SCADA server. Replies with no loss earn the next section; a failure is cabling, subnet or switch port, and no driver setting fixes any of those.
How do you define the FINS I/O device in Citect? #
Define one Board, one Port and one I/O Device per CPU: the Port runs the TCP/IP protocol, the I/O Device selects the OMFINS driver with the PLC's IP address as its address, and its FINS network and node fields copy the numbers you set on the board.
- In the project's communication forms, add a Board on the SCADA I/O server and name it for the CPU it reaches.
- Add a Port on that Board with the TCP/IP protocol.
- Add an I/O Device on that Port, choose the Omron FINS Ethernet driver from the driver list, and enter the PLC's address — 192.168.250.20 in the running example — as the device address.
- Set the device's FINS node field to 20 to match the board, and leave the FINS network number at the driver's default unless your plant routes FINS across networks.
- Read the driver's help page once for its address syntax and its list of supported memory areas before you write any variable tags.
- Compile, start the I/O server, and confirm the device shows a running state with an error count of zero.
The Board, Port and device names are yours to choose; the numbers are not. Whatever the driver names its node and network fields, they must equal the board's settings, because a mismatch shows up only as dropped requests.
How do you prove the link with one tag before building the database? #
Build one test variable tag to a DM word you can watch in the PLC tool — D100 in the driver's DM syntax — and gate the project on it: a live value with a zero error count earns the tag database, a timeout sends you back to the board settings.
Choose a word that already moves, a counter or the PLC's clock word, so a correct link shows motion instead of a frozen zero, and watch the same word in CX-Programmer's online monitor while the Citect runtime polls it. Two failure signatures decide your next move. A timeout or a bad-quality tag points at the transport: IP, node, port, firewall. A connected device that rejects the address points at syntax, or at an area this driver cannot reach on this CPU. Fix the one tag before you type another; fifty dead tags hide the single setting that is wrong.
How do you read an NJ301's variables that have no addresses? #
Give every variable the SCADA needs an AT specification to CJ-compatible memory in Sysmac Studio — a DM word is the usual choice — because a FINS driver addresses memory areas and can never resolve a named variable on its own.
Worked example, with the word counts done: an INT occupies one DM word and a REAL occupies two. Reserve D100 for Part_Count (INT): it holds D100 alone. Reserve D101 for Temp_Real (REAL): it holds D101 and D102, so the block is 1 + 2 = 3 words from D100 to D102 and the next mapped variable starts at D103. In Citect, tag Part_Count at D100 as an INT and Temp_Real at D101 as a REAL. Build and transfer the NJ project, read both tags, and compare each against Sysmac Studio's online watch — matching values prove the map. Write a known number such as 123.4 into Temp_Real from Citect as well: a plausible but wrong reading means the driver's word order for multi-word types is reversed, so the tag needs the driver's other word-order setting.
The NJ's built-in Ethernet port carries FINS the same way, so the I/O Device from the earlier section works unchanged once it points at the NJ's IP address with that port's FINS node. Keep an explicit address list as the master document, because changing a variable's type or AT address in Sysmac Studio without updating Citect shifts the data silently. Past roughly a screenful of values, invert the decision and move to a name-based protocol: check which of an OPC UA server or an EtherNet/IP tag service your NJ unit version and firmware expose, per the CPU manual, and attach Citect to that instead — it scales without an address map.
How do you tell a PLC fault from a network fault when the tag will not read? #
Capture packets on the SCADA server's network card for one poll cycle and split the result three ways: requests leaving with no replies incriminate the PLC side, no requests at all incriminate the Citect device, and replies arriving against a bad tag incriminate the driver's address fields.
Omron's FINS default port is 9600, and the UDP variant is connectionless, so a firewall that blocks it produces silence rather than a refusal: allow the port outbound and for return traffic in the SCADA server's firewall before blaming the board. Intermittent rather than constant timeouts point at collisions instead. Check the server's ARP table for a duplicated IP address, and make sure no second device on the segment holds the same FINS node number; either collision shows up as random timeouts that behave exactly like a driver fault, and neither is one.
How do you verify the finished link end to end? #
Close both directions before sign-off: write a test value from Citect into a spare DM word and watch it land in the PLC watch, change the value in the PLC and watch the Citect tag follow, then pull the cable and watch the tag's quality drop and recover.
Recovery timing is part of the test: the tag must come back to good quality within the driver's retry interval after the cable returns, or operators will chase ghost alarms later. After ten minutes of runtime, confirm the driver's error statistics are flat rather than climbing. When the loss state is proven, raise it for operators as an alarm instead of a silent quality flag — how to create a SCADA PLC communication alarm for link loss shows the tag pattern.
One safety note: keep the write list short. Write from Citect only into words that no interlock or sequence logic consumes, because a SCADA write into live control data acts like an operator rewriting the program mid-cycle.
Questions asked
Do I need a separate Citect I/O Device for every client that shows the data?
No. Define the Board, Port and OMFINS I/O Device once on the I/O server that owns the link, and Citect clients read the resulting tags through that server, so each new display client adds no second connection to the PLC. One CPU maps to one I/O Device; clients only load the tag database.
Why does a duplicate FINS node number matter when every IP address is unique?
The IP address gets each frame to the right board, but the FINS network and node numbers travel inside the message and identify the device one layer above IP. Two boards that ping cleanly while sharing a node number answer each other's traffic, which shows up as intermittent timeouts that no driver setting will fix.
Which option board do I fit if the SCADA side speaks EtherNet/IP instead of FINS?
Fit the CP1W-EIP61, Omron's EtherNet/IP option board, when the driver on the SCADA side expects CIP; the CP1W-CIF41 serves FINS and the two are not interchangeable. Decide from the driver first: pick the board that matches the protocol your Citect version will run, then set that board's own address parameters.
Can Citect write into an NJ301 variable that has an AT specification?
Yes. A variable with an AT specification lives at its DM address in both directions, so a Citect write tag to that address changes the variable in the NJ, exactly as it changes a DM word on a CP1 CPU. An unmapped variable stays invisible to writes as well as reads, and operator writes should stay on values the logic treats as setpoints.
How do I find out which memory areas the FINS driver can reach on my CPU?
Read the driver's help page in your Citect version: it lists every supported memory area with its address letter, and the reachable set differs between CPU families. Before an unusual area enters the tag database, point one test tag at it and watch the value in the PLC tool, because a driver that accepts the address string may still read the wrong place.