IMDHMIControls LibraryShop main store

How-to

Read Citect SCADA 2018 R2 tags from Ignition via OPC DA

SCADA and data logging Published 7 min read

Short answer

Citect SCADA 2018 R2 ships a built-in OPC DA server: enable it under the Topology activity in Citect Studio, connect Ignition's OPC DA module to it, and the Citect variable tags appear for browsing and import with no OFS, no CtAPI and no project rewrite. OPC UA exists only in later Citect releases. When Ignition and Citect run on different PCs, configure DCOM security for the account the Ignition service runs under.

On this page
  1. Why OPC DA is the 2018 R2 route
  2. Enable the OPC DA server in Citect Studio
  3. Connect Ignition and prove the link locally
  4. Worked case: Ignition gateway on a second PC on the same LAN
  5. Configure DCOM between the two PCs
  6. Tell a tag fault from a connection fault
  7. The decision for each case
  8. Questions asked

Yes, a stand-alone Citect SCADA 2018 R2 server can publish its variable tags to an Ignition gateway across the site LAN with no project rewrite, no OFS and no CtAPI. The route is the OPC DA server built into 2018 R2: enable it under the Topology activity in Citect Studio, then point Ignition's OPC DA module at it. Keep the Ignition gateway on the Citect PC and there is nothing else to configure; put it on a second PC, as most sites do, and the only extra work is DCOM security for the account the Ignition service runs under. OPC UA is not a 2018 R2 option — it arrives in later releases — so every other route costs more than this one. The steps below assume that layout: a 2018 R2 server talking Modnet to its I/O devices, read by Ignition over the same LAN.

Why OPC DA is the 2018 R2 route #

Citect SCADA 2018 R2 ships an OPC DA server inside the product. Enabling it is a configuration change on the Citect server that owns the variable tags; the Modnet links to the I/O devices keep running exactly as configured, and the OPC server republishes the tags the runtime already holds. OPC DA is the COM-based member of the OPC classic family, so this link behaves like any Windows COM client talking to a Windows server. The alternatives all cost more:

Route Change to Citect What it costs you
Built-in OPC DA server + Ignition OPC DA module Enable it under the Topology activity in Studio DCOM configuration when the two systems sit on different PCs
OPC UA Not available in 2018 R2; later releases only A Citect upgrade before any connection work
CtAPI None to the project A client you write yourself; ctapi.dll is a native library that does not load cleanly into a Java-based gateway
Protocol gateway at the devices None Device data only, no Citect variable tags; Ignition rebuilds the tag and alarm database Citect already owns

Where OPC UA does exist — the later releases — publishing tags to a client and consuming UA from a PLC are different directions, and trusting the Citect OPC UA client certificate on a B&R PLC covers the certificate step in the second direction.

Enable the OPC DA server in Citect Studio #

  1. Open the project in Citect Studio on the server PC.
  2. Go to the Topology activity, where the project's servers are defined.
  3. Enable the OPC DA server on the Citect server that owns the variable tags Ignition needs.
  4. Apply the change; if the OPC server does not register, restart the Citect runtime.
  5. Prove the Citect side before any network work: from an OPC DA client on the Citect PC itself, browse the server and confirm the variable tags appear with Good quality and live values.

The OPC server publishes the variable tags, not the devices behind them. An empty browse usually means the server was enabled on the wrong machine in the Topology, or the runtime is not running.

OPC DA rides COM, so the Ignition gateway that opens the connection must run Windows; a Linux gateway cannot host the OPC DA module. If the link calls for a new host in the cabinet beside the Citect server, an industrial mini PC is the class of machine meant for gateway duty there.

  1. Install the OPC DA module in the Ignition gateway and restart the gateway.
  2. In the gateway's OPC connections, add a new OPC DA server connection and point it at the Citect OPC DA server on the Citect PC.
  3. Check the connection status on the gateway's status page before reading any tag.
  4. Open the OPC browser, select the Citect variable tags in bulk, and import them instead of retyping item paths.
  5. Read one imported tag: a live value with Good quality proves the server, the module and the connection in one step.

With the gateway on the Citect PC, DCOM is out of the picture entirely; that is the fastest way to separate Citect-side faults from network faults.

Worked case: Ignition gateway on a second PC on the same LAN #

Inputs, and where each comes from:

  • PC A: the Citect SCADA 2018 R2 server, stand-alone, no OFS, Modnet to its I/O devices — the installation in question.
  • PC B: the Ignition gateway with the OPC DA module, elsewhere on the same site LAN.
  • One test variable tag created in the Citect project; the value written into it is your choice, and 12345 below is an example value, not a setting.

The rule, in words: a COM client on the server's own PC uses local COM, which needs no DCOM configuration; across two PCs the client's activation crosses exactly one DCOM boundary, and Windows denies launch, activation or access unless the server's DCOM settings admit the client's service account.

The arithmetic:

  • DCOM boundaries = 0 if the client PC equals the server PC, otherwise 1.
  • This site: PC B and PC A are different machines, so boundaries = 1, and DCOM configuration is required before the remote test can pass.
  • Proof round trip: 12345 written into the test tag in the Citect runtime must read back as 12345 at the Ignition tag with Good quality.
  • Fault split over the imported group: every tag bad at once = 1 connection fault; one tag bad among good ones = 1 item fault.

Expected result: locally, at 0 boundaries, the browse lists the variable tags with Good quality; remotely, at 1 boundary, the connection sits faulted until DCOM grants PC B's service account its rights, then moves to connected with the same values.

Decision: two PCs — configure DCOM first, and read any remote-only failure as a binding fault; one PC — skip DCOM altogether.

Configure DCOM between the two PCs #

Grant the rights to the one service account the link needs and nothing broader; blanket Everyone access on a control-network DCOM server is an open door.

  1. On PC A, open Component Services (dcomcnfg) and expand DCOM Config.
  2. Find the OPC DA server application the Citect install registered; on a 2018 R2 machine it shows as AVEVA SCADA OPC DA Server.
  3. Under launch and activation permissions, add the account the Ignition service runs under and allow local and remote launch and activation.
  4. Under access permissions, allow the same account, local and remote.
  5. On a workgroup network, the usual layout for a stand-alone site, create a matching local account on PC A and run the Ignition service under an account with the same name and password on PC B; on a domain, use a domain account both machines accept.
  6. Re-test from PC B: the connection moves from faulted to connected, and the tag that read Good locally reads Good remotely.

AVEVA's Tech Notes and knowledge base document these DCOM steps per Windows version; follow the one matching the Windows build on PC A, because the permission dialogs moved between Windows releases.

Tell a tag fault from a connection fault #

What you see Likely cause Where to look
Browse finds no server OPC DA server not enabled, or the runtime stopped Topology activity in Studio; runtime state on PC A
Works only while someone is logged on Server identity set to the interactive user Identity setting of the server application in dcomcnfg
Connection faulted, every tag bad DCOM binding across the two PCs Launch, activation and access rights; the Ignition service account
Connected, one tag bad Item path wrong, or the tag is not in the running project Compare the path against the browse result
Connected, values frozen The Citect variable stopped updating from its device Check the variable inside the Citect runtime; the OPC server republishes what Citect holds

Read the table as one rule: a fault hitting every tag at once lives in the connection, and a fault hitting one tag lives in that tag. A link that ran clean for weeks and then degrades has a documented cousin on other OPC DA servers, OPC DA memory growth that stops SCADA reads; a runtime restart that clears the slowdown points at server-side resources the same way.

The decision for each case #

  • Citect and Ignition on one PC: the local proof above is the whole job — enable, connect, browse, import. No DCOM, no OFS, no CtAPI, no change to the project.
  • Two PCs on one LAN: the same steps, then DCOM launch, activation and access rights for the Ignition service account, with the account named however the network requires.
  • OPC UA required: not on this release — upgrade Citect or fund a CtAPI-to-OPC UA gateway as a development project, and skip the device-level protocol gateway for the reasons in the table above.

Questions asked

What happens to the Ignition link when the Citect runtime restarts?

Expect the OPC DA connection to drop and the Ignition tags to go bad for the length of the restart, then recover on their own once the runtime and its OPC DA server register again. Prove it once at commissioning: stop and start the Citect runtime, and confirm the connection returns to connected and quality returns to Good without touching the gateway. If it stays faulted after the runtime is up, the OPC server did not re-register — check the Topology activity setting on the server.

Why does the Citect OPC server vanish when nobody is logged on?

Because the server's DCOM identity is set to the interactive user, it only runs while that user holds a desktop session. Open the identity setting for the server application in dcomcnfg and run it as a fixed service account instead, giving that account the launch, activation and access rights. After the change the server registers at boot, and the Ignition connection stops depending on anyone staying logged in.

Which Citect versions would give me OPC UA instead?

OPC UA support begins in the releases after 2018 R2, where the product continues as AVEVA Plant SCADA; 2018 R2 has no UA server to connect to. On the old release, plan on the built-in OPC DA server. If the site later upgrades and Citect itself becomes an OPC UA client of a PLC, certificate trust becomes its own task, separate from publishing tags to Ignition.

Can I avoid DCOM by keeping the Ignition gateway on the Citect PC?

For a test, yes, and it is the fastest proof: a client on the server's own PC talks over local COM, which needs no DCOM configuration. As a permanent layout it is rarely wise, because the gateway then competes with the SCADA runtime for the same machine's resources. Prove the Citect side locally, then move the gateway to its own PC and configure the DCOM rights once.

Do Citect tag names survive the trip into Ignition?

Yes. The OPC DA server publishes the Citect variable tag names as its item names, so browse-and-import keeps Ignition's tag names identical to the Citect project. That also means a variable renamed in Citect stops matching the imported item after the next deployment, and the affected Ignition tag reads bad until you re-import it.

Keep reading

  • 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

  • Troubleshooting

    Getting Citect SCADA talking to a Mitsubishi iQ-R PLC

    Fix the transport before anything else: the Citect MELSECQ port on TCP_BOARD must match the iQ-R's SLMP connection module exactly — protocol, port number and IP address. If tags above device 65,535 fail, that is the MELSEC Q protocol's 16-bit address ceiling, and no setting fixes it; move to Mitsubishi's OPC MX UA server with a Citect OPC client driver.

    SCADA and data logging

  • Troubleshooting

    Fixing Citect SCADA FINS errors to an Omron NX1P2

    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.

    SCADA and data logging