SCADA and data logging
SCADA software, alarms, data logging and historians.
Latest articles
Selection guide
Where to install Historian alongside Citect SCADA
Put the Wonderware Historian on a separate server sized for its history files and leave the connector on the Citect SCADA host. The connector only pushes data out, adding no Historian client functions to Citect, and events need their own acceptance test.
Explainer
Reading ctrlX CORE variables without an OPC UA server
A SCADA server app running on ctrlX OS, SpiderControl is the documented case, reads the variables of its own ctrlX CORE directly through the ctrlX Data Layer, so the local path carries no OPC UA server app. Variables on any other controller still arrive through the server's drivers, one session per source: OPC UA, Modbus or ISO-on-TCP. The server license includes unlimited local access and unlimited HTML5 browser clients, and a 10-day trial is issued automatically.
Troubleshooting
Fix ControlLogix tags missing from Ignition OPC UA browse
Restart the OPC-UA module, delete the stored /data/drivers/.tags file on the Ignition server, then refresh the browse from the device page — not the OPC Browser. The Logix driver resolves only addresses present in its browse results, so a hand-typed tag for a missing address stays Stale until the stored browse data is rebuilt.
Troubleshooting
Replacing a KoyoNet Citect link with Do-more Modbus TCP
Use the H2-DM1E as a Modbus TCP server and point Citect's ModNet driver at it, mapping measurements into MIR, setpoints into MHR, and status and command bits into MI and MC. The working KoyoNet link stays only as a temporary read bridge, because its octal addressing, integer-only V-memory and reported 768-word window are exactly what you are leaving.
Troubleshooting
Connect SCADA to an SLC 5/03 and MicroLogix 1500
None of the three listed drivers will work: ControlLogix and CompactLogix are different controller families, and the MicroLogix 1100/1400 connection is Ethernet to models that have an Ethernet port. Your SLC 5/03 and MicroLogix 1500 LRP are serial-only, so connect through an OPC server with a serial DF1 or DH-485 driver, or a protocol-aware gateway. Put both controllers on one DH-485 network and bridge it once.
Selection guide
Sizing one Ignition gateway for 100,000 OPC UA tags
A 100,000-tag OPC UA application fits one Ignition gateway at the published large-project benchmark of 8 cores, 16 GB RAM and SSD storage, which assumes at most 10% of tags changing into history and up to 75 concurrent clients. Qualify that server against your changed-value rate, historian load and client activity with a representative test, and distribute gateways on measured limits, not on tag count.
How-to
How a SCADA system reads EtherNet/IP adapter sensor data
A tag-based SCADA client cannot browse an EtherNet/IP adapter, because an adapter publishes fixed I/O assemblies and has no tag server. Run a scanner-class client on the gateway and configure the EDS-declared assembly instances and RPI, or let a PLC own the Class 1 connection and read that PLC's tags.
Selection guide
Selecting SCADA software for mixed PLCs and SQL logging
Shortlist the candidates, then pass or fail each one on nine commissioned paths: a live read from every PLC family in the mix, one parsed serial ASCII transaction, a browser client session on the target touch-panel PC, and one logged record in SQL Server or MySQL verified across a database outage. Accept a package only when every path passes all its checks; a failed path keeps a candidate alive only with a named gateway or OPC route.
Troubleshooting
Why PLC symbol changes break SCADA tags in OFS
The tags drop because OFS resolves symbolic item names through a symbol source that no longer matches the downloaded PLC application. Replace the stale XVM symbol file with a fresh export, or move to OFS 3.63 SP3 with "Using Data Dictionary", "No Communications Break" and the PLC build's preload option so the server reads the updated dictionary before scanning.
Troubleshooting
Fixing Machine SCADA Expert Modbus TCP reads to a TM221
Matching IP and port do not prove the read path is right: with MOTCP selected, Machine SCADA Expert must use that driver's station and address syntax, and the number after 4X must resolve to MW0. Rebuild the station and I/O address from the MOTCP manual example, then prove it with known values in MW0 and MW1: the wrong convention reads MW1, exactly one register off.
Troubleshooting
When Aveva Edge cannot browse S7-1500 OPC UA tags
AVEVA Edge connecting but showing no S7-1500 tags is a browse fault, not a comms fault: UAExpert reading the same server proves the tags are exposed. Match Edge's endpoint and security settings to the working client, verify the CPU's X1 Ethernet addresses, put a virtual machine on the PLC subnet, and check the browse timeout before rebuilding the datasheet.
How-to
Starting an OPC UA client connection from PLC code
As of OPC UA Client app version 1.16.0, a configured connection stays Disconnected until something requests a start. PLC code does that job: run cyclically, read the client state, and issue the start request only when the state is Disconnected and no request is pending, gated so it fires once per attempt. Import the PLCOpenXML example into ctrlX PLC Engineering and give the PLC sole ownership of automatic starts.