SCADA and data logging
Earlier articles
How-to
Setting the Modbus slave ID for a Citect I/O device
The Modbus slave ID is the Address field of the I/O Device, set in Plant SCADA Studio under Topology. Boards define the server's interface and Ports carry the communication settings; neither holds the station number. Enter the station the device itself is configured to, then compile and deploy, and the #Bad tags clear when the transport already matches.
How-to
Serve generic Modbus devices to SCADA through OFS with the PL7 driver
OFS does serve generic Modbus devices: select the PL7 driver in the device alias, not Unity, because Unity issues Schneider-extended function codes a standard slave rejects while PL7 issues the public read/write set. Import the tag definitions as a .SCY file, make OFS the only Modbus master on the link, and point Citect and every OPC DA or UA client at that one server.
Troubleshooting
Reading a CLICK PLC float over Modbus TCP in an HMI
F428673 is the right address: the F prefix reads the two Modbus registers as the IEEE 754 float the CLICK program wrote to DF1 (24.9645 here), while L returns the raw 32-bit pattern (1103607636) and U returns one 16-bit half (46932). The screen showed 25 because an integer tag or whole-number format rounded it. Move the project to 3.99w and bind F with a decimal format and a floating-point variable.
How-to
Read Citect SCADA 2018 R2 tags from Ignition via OPC DA
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.
How-to
Migrating Modicon SCADA libraries to Plant SCADA 2023
Yes — the Modicon General Purpose libraries for Citect SCADA 2018 reach Plant SCADA 2020 and 2023 by migrating the SGC include file, which their product design allows into any later version. No newer SCADA-side release exists, so migrate the include file with the project and prove each screen by tracing its values back through binding, tag, driver and controller address.
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.
How-to
Connecting Citect SCADA to a Modbus RTU gateway over MODNET
Yes — MODNET is Citect's driver for Modbus over TCP/IP, and a true RTU-to-TCP converter presents standard Modbus TCP on its Ethernet side, so the combination works. Success then rides on two things: the gateway's operating mode, and carrying the RTU slave address and register offsets into Citect correctly, proved by reading one register whose value you can see at the device.
How-to
Connecting Citect SCADA to a CP1W-CIF41 over FINS
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.
How-to
Connect an S7-1500 to SCADA over OPC UA from TIA Portal
The S7-1500 has a built-in OPC UA server from firmware V2.0, deactivated by default. Enable it in the CPU device properties in TIA Portal, select the installed server license, copy the endpoint URL, and download. Paste the opc.tcp address into any OPC UA SCADA client, trust the certificates on both sides, then browse the PLC variables and map them to SCADA tags.
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.
Troubleshooting
Why a SCADA write to a PLC real address fails silently
The link is usually fine. A SCADA write to a PLC REAL address fails over configuration: the ladder compares the double word as a DINT instead of REAL, the SCADA tag type does not match, raw-to-engineering scaling is not 1:1, or the key sequence is shorter than the entry format. Run the four checks in order and re-enter the value.
How-to
Trusting the Citect OPC UA client certificate on a B&R PLC
OPC UA checks certificates in both directions, so a working UAExpert connection only proves the server side. On the B&R CPU Configuration page, open the OPC UA configuration, create the server certificate if there is none, and add the Citect client's public certificate to the trusted clients; then select the same security policy in Citect and the controller.