SCADA and data logging
Earlier articles
Troubleshooting
Troubleshooting a SCADA PC station that reaches only one S7-1500
When every S7-1500 answers ping but SCADA updates only one PLC, ping has proven nothing about the S7 link. Work the checks in order: four distinct MAC addresses on the PLC subnet, the S7ONLINE access point bound to the connected network card, one HMI connection per CPU, and every tag's Connection pointing at its own CPU's connection.
Comparison
Replacing DCS SCADA with a third-party SCADA system
Yes on data, no on engineering. A third-party SCADA reads and writes a PCS 7 controller through an S7 driver or an OPC server, but you rebuild faceplates, symbol links, navigation, alarms and diagnostics by hand - about 1,200 hours for a 500-object unit, which outweighs the license savings. Do it for monitoring layers and small stations; keep the integrated operator station for full process units.
Troubleshooting
Reading M580 I/O in Plant SCADA without mapped memory addresses
Bad I/O on %Q1.1.20 means Plant SCADA is reading a topological M580 channel address that no driver can resolve as a register, and no Modbus table exists to look up. Serve the points through the OFS gateway using PLC tag names, with an XVM export now and the Data Dictionary permanently, and add the missing variables by online change so the 24/7 line never stops.
How-to
How to simulate a Modbus TCP SCADA link on one PC
Yes — one PC can run the SCADA client and a Modbus TCP server simulator at once. Decide which side you are proving, keep exactly one client and one server in the arrangement, prove the server exists with an independent Modbus client, then align object type, offset and word order before trusting any value; a connected link proves transport only.
How-to
How to create a SCADA PLC communication alarm for link loss
Create the SCADA-to-PLC communication alarm from the data server's diagnostic item, not from a PLC bit. Browse to IsPresent under the PLC shortcut's Diagnostic Items folder, create a digital alarm in FactoryTalk Alarms and Events with IsPresent = 0 as the active condition, and it activates about 20 seconds after the link drops; IsPresent(10) shortens that to about 10 seconds. A heartbeat bit cannot do this because it travels over the link it monitors and goes unreadable exactly when the link fails.
How-to
Getting CompactLogix PLC data into Excel over EtherNet/IP
Excel has no EtherNet/IP client, so a CompactLogix reaches a workbook only through a driver layer: an RSLinx edition that documents OPC or DDE support, or a driver library used within its license — RSLinx Classic Lite does neither. Put the PC and controller on one subnet, prove a single controller-scoped tag read, map that one cell, and add writes only against a dedicated test tag the logic validates.
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.
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.
Troubleshooting
Commissioning CP1L Host Link serial reads to SCADA
CX-Programmer going online proves only the programming path, not the SCADA read. Set the CP1L serial port to Host Link, enter its unit number (0 to 31) as the driver's device address, match baud, data bits, parity and stop bits, prove the cable end to end, and free the computer port of other software. Read one known word before adding tags: a timeout means no valid reply arrived; a PLC protocol error proves the link works.
Selection guide
SCADA and PLC platform selection for plant revamps
Judge the whole chain — engineering tool, exact controller, fieldbus role, OPC UA endpoint, SCADA runtime and client — not the IDE alone. Freeze pass-or-fail gates on the license boundary, target hardware, fieldbus, OPC UA and documentation, then pilot one representative plant unit on the real controller. Adopt only after deployment, protocol behavior, diagnostics and failure recovery all pass there; until then the incumbent platform stays the baseline.
How-to
How to learn PLC, SCADA and DAQ from scratch
Learn the three as one project, not three courses: pick one route, wire one real input, program a three-state sequence, exchange one Modbus register, bind SCADA tags and store a timestamped value. Pass the five checkpoint tests on the way; simulation alone never exercises terminals, polarity or reconnection.