IMDHMIControls LibraryShop main store

Troubleshooting

Fixing Citect SCADA FINS errors to an Omron NX1P2

SCADA and data logging Published 6 min read

Short answer

Set the FINS destination unit to 0. Unit 250 returns Generic Error 000012 with Driver Error 0x000016; unit 0 moves the fault to Generic Error 000008 with Driver Error 0x001101, which clears only after the NX1P2 CIO area is enabled and one CIO read succeeds — then DM and every other area reads normally.

On this page
  1. Read the two error pairs as one diagnostic
  2. The configuration that communicates
  3. Capture the exchange before editing anything else
  4. Enable the CIO area and complete one read
  5. What this fault is not
  6. The decision for each state
  7. Questions asked

Your Citect release is not the problem. Citect v7.30 SP1 reads and writes an Omron NX1P2 through the PLC's built-in EtherNet/IP port over the OMFINS3 driver once three settings are right: the FINS destination unit is 0, the [OMFINS] source address is present, and the CIO area is enabled in the NX1P2 memory setup. Unit 250 gives Generic Error 000012 with Driver Error 0x000016, and no other change clears that pair. Unit 0 moves the fault to Generic Error 000008 with Driver Error 0x001101, which clears only after one CIO read succeeds — the driver requests CIO first whatever area your tag addresses. A packet capture on the I/O server proves that in minutes.

Read the two error pairs as one diagnostic #

The kernel logs Generic and Driver errors together; read them as a pair, with the address that produced them, because the step from one pair to the other is itself the finding.

  • Unit 250: Generic Error 000012, Driver Error 0x000016. The destination unit is wrong. The 250 read out of Sysmac Studio is not the FINS destination unit this driver addresses — the CPU answers at unit 0, and both known working NX1P2 configurations use unit 0.
  • Unit 0: Generic Error 000008, Driver Error 0x001101. The route works and the PLC is rejecting the request itself. The driver reference words 0x001101 as: "A correct memory area code has not been used or Expansion Data Memory is not available."
  • Unit status Offline throughout. Generic 000008 means the exchange is established and the I/O device reported a protocol error, so an offline unit with a successful ping and live request traffic is a consistent state: the driver has not completed the one valid read it needs to bring the unit online.

Moving from the first pair to the second proves your requests reach the PLC. Once you see 0x001101, stop editing addresses.

The configuration that communicates #

Setting Working value
Board TCPIP, address 0
Port, special options -I128.1.10.115 -P9600 -T
I/O device protocol OMFINS3
I/O device address 1/115/0/S
citect.ini [OMFINS] Block = 256, IgnoreNonFatalError = 1, Source = 1/1/0

Field by field: 128.1.10.115 is the PLC's IP address, and 9600 is the FINS/TCP port number the built-in port serves. In 1/115/0/S the network is 1, the node is 115 — the PLC's node number on the built-in port, which matched the last octet of the IP in both working setups — the destination unit is 0, and S is the link option; both working setups used S. The option letters (-T, -U, /S, /V) are defined in the installed driver help: -U was tried on the failing setup and changed nothing, and -T sat in the working one — neither option is the cure.

Source = 1/1/0 carries network 1 to match the destination network, node 1 because the PLC already holds 115, and unit 0. A second working installation on an NX1P2-9024DT1 ran destination 0/115/0/S with -I192.168.1.115 -P9600 and [OMFINS] Source = 0/14/0, PollTime = 0, Timeout = 1000, Delay = 20, IgnoreNonFatalError = 0, Watchtime = 30 — so destination network 0 and 1 both reached the PLC. A 0 in that field means the local network to the driver; Sysmac Studio refusing 0 as the PLC's configured local network number is a separate setting and no obstacle.

On the PLC side, the FINS server function on the built-in port is enabled from Configurations and Setup - Controller Setup - Built-in EtherNet/IP Port Settings in the Multiview Explorer, as the NX-series CPU Unit FINS function manual sets out.

Capture the exchange before editing anything else #

Ping the PLC from the I/O server itself, not from the engineering station — ping proves IP reachability and says nothing about FINS addressing or memory access. Then capture on the I/O server with Wireshark, filtered to TCP port 9600.

On this fault the capture shows the driver's read request and the PLC's reply; the reply carries the memory-area rejection while the configured tag pointed at D. That capture is the branch point:

  • Requests and rejected replies both visible — routing is finished and the request content is the fault; go to memory setup.
  • No traffic at all — an IP, port or FINS-server problem; fix that path before touching Citect again.

Enable the CIO area and complete one read #

In the NX memory setup in Sysmac Studio, enable the CIO area even though the application reads only DM. Apply the configuration and confirm the controller is running it. The capture showed why: the OMFINS3 driver sends its read to CIO regardless of whether the tag addresses D, W or H, and the NX1P2 answers with an invalid memory-area code until the CIO area exists. Once the area is enabled and one CIO read completes, reads to DM and the other areas work — that held on both installations.

Keep the test tag clean while you do this. D1000.00 is a bit address: the PLC variable needs the AT %D1000 allocation and the tag type must match the driver's bit syntax. Test a word and a bit separately, so a data-type mismatch cannot masquerade as the area fault.

Restart the runtime only with the process in a state that tolerates every driver on that I/O server dropping — the working Schneider units go down with the Omron one.

What this fault is not #

  • The healthy unit 1 on the same server is a Schneider PLC; it proves the server and its network stack, not the Omron driver, the FINS route or the NX memory setup. The mirror image of this trap — one controller updating while another does not — is troubleshooting a SCADA PC station that reaches only one S7-1500.
  • Updated OMFINS and TCPIP driver packs were installed before the fault cleared; the update alone fixed nothing.
  • After 0x001101 appears, further address changes cannot help: the PLC is rejecting the request's memory area, not its route.
  • A driver whose request shape decides the outcome is a Citect pattern, not an Omron quirk — why CitectSCADA cannot read MicroLogix data-table tags with ABCLX is the same lesson on the Allen-Bradley side.

The decision for each state #

  • Generic Error 000012 with Driver Error 0x000016 — change the destination unit to 0 and nothing else; retest.
  • Generic Error 000008 with Driver Error 0x001101 — stop editing addresses; enable the CIO area in the NX memory setup, apply, and complete one CIO read.
  • Capture shows replies carrying rejections — the fault is PLC memory setup, not communications.
  • Capture shows no traffic — fix the IP, port 9600 or the FINS server setting first.
  • One CIO read has succeeded — restart the runtime, confirm each tag individually, and archive the working configuration values.

Questions asked

Why does Citect read the CIO area when the tag points at D1000.00?

The capture on this installation showed the OMFINS3 driver issuing its read against the CIO area whatever the tag addressed — D, W and H tags all produced the same request. With the CIO area disabled in the NX1P2 memory setup, the PLC answers that request with an invalid memory-area code and the unit stays offline. Enable the CIO area, let one CIO read succeed, and reads to DM and the other areas start working. That behavior is specific to this driver and controller combination, observed on Citect v7.30 SP1.

What does Driver Error 0x001101 actually mean?

The driver's error reference words it as: a correct memory area code has not been used, or Expansion Data Memory is not available. In this fault it is not an expansion-memory problem — the PLC received the request and rejected the memory area it named. Treat the code as proof that the FINS route works and the request content does not, and go to the PLC memory setup rather than the addresses.

Can the FINS network number be 0 when Sysmac Studio rejects 0 for the local network?

Yes. A 0 in the destination's network field means the local network to the driver; the local network number configured in Sysmac Studio is a separate setting, and Sysmac Studio refusing 0 there is expected. One working NX1P2 setup used destination 0/115/0/S and another used 1/115/0/S — both communicated. Match the [OMFINS] Source network to whichever destination network you use.

Is Citect v7.30 SP1 too old to talk to an NX1P2?

No. v7.30 SP1 reached full reads and writes to an NX1P2 once the destination unit, the [OMFINS] source address and the CIO area were set. Install the current OMFINS and TCPIP driver packs for that release first: an updated pack alone did not clear the fault, but the working configuration ran with the updated packs installed.

What should the [OMFINS] Source address be?

Use network/node/unit with the network matching your destination network and a node nothing else holds on that FINS network. The working setup used Source = 1/1/0 against destination 1/115/0/S; a second working NX1P2 used Source = 0/14/0 against destination 0/115/0/S. The PLC held node 115 in both. Unit stays 0.

Keep reading

  • Troubleshooting

    Why CitectSCADA cannot read MicroLogix data-table tags with ABCLX

    ABCLX talks to the Logix tag database, and a MicroLogix 1400 programmed with RSLogix 500 has none: its bits live in numbered data files, so an address like PROGRAM:MainProgram.B33{0} can never resolve. Change the I/O device to the ABMLXEIP driver, address the bit by file/element/bit as B33:0/0, and enter the controller's IP as a bare host address (192.168.0.100), never with a /24 suffix.

    SCADA and data logging

  • Troubleshooting

    Fixing CODESYS OPC DA memory growth stopping SCADA reads

    The reads stop because WinCoDeSysOPC.exe, a 32-bit OPC DA server process, climbs to its 2 GB memory ceiling over weeks and then stops serving tags; killing it only resets the clock. The resolution that held was installing the current, licensed CODESYS OPC DA server — 3.5.22.40 in place of the CODESYSV35SP10Patch2 install — and proving it through the old failure window.

    SCADA and data logging

  • How-to

    How to read CompactLogix tags from a C# SCADA application

    Yes: a C# application reads a CompactLogix by acting as an EtherNet/IP client that requests the controller's symbolic tag read and write services over TCP port 44818. For ten tags, build that client directly and skip the OPC server; choose the documented Modbus TCP sample code for 5370 processors only when you need a register interface.

    Industrial networks