IMDHMIControls LibraryShop main store

Selection guide

Selecting SCADA software for mixed PLCs and SQL logging

SCADA and data logging Published 8 min read

Short answer

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.

On this page
  1. What the shortlist must prove
  2. The equipment behind the nine paths
  3. Proving a controller path
  4. Bringing serial ASCII devices onto Ethernet
  5. Where the browser client and runtime run
  6. Proving SQL logging through a database outage
  7. Worked example: scoring four candidates over nine paths
  8. Licensing the minimum deployable system
  9. Questions asked

Select by commissioning, not by driver count. Shortlist the packages the field discussion produced — Wonderware, Citect, Schneider ClearSCADA, now sold as Plant SCADA, and InduSoft — then pass or fail each one on the same nine test 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. Each path carries four recorded checks, so a candidate finishes with 36 results, and the package that clears all of them wins the program. A driver named in a brochure is a claim about reach, not a compatibility result, and the S5 and the ASCII devices are where that difference bites.

What the shortlist must prove #

The project brief sets five hard requirements: read ControlLogix, SLC, MicroLogix, FX2N, S7-300, S7-400 and an S5; read the Red Lion G3s; bring serial ASCII devices onto Ethernet; serve browser-based clients; and log to Microsoft SQL Server or MySQL — with most systems deployed single-client on a small touch-panel PC.

Requirement Where it lives in the package What proves it
Mixed-controller reads Native driver catalog, OPC client support A live, correctly scaled read from every family, with quality and timestamp
Serial ASCII over Ethernet Serial transport plus a parser, or a converting gateway One complete transaction parsed to a value, and a visible fault when it fails
Browser-based clients Web client architecture and supported browsers The application running in the intended browser on the panel, touch and all
Single-client deployment Runtime and client licensing The minimum deployable system counted for one site
SQL Server or MySQL logging Database connector and historian configuration One record written once, with the right timestamp, across a database outage

Packages reach multiple brands through native drivers or through OPC, and both are production-grade routes; neither removes the per-path test, because the interface fitted to the specific device, not the family name, decides the connection. This per-project pass and fail exercise is the small cousin of a plant-level platform decision — the broader trade-offs are covered in SCADA and PLC platform selection for plant revamps.

The equipment behind the nine paths #

A family name does not identify a connection: the same family can carry different interfaces that need different drivers or intermediate hardware. Record the details before any test.

Equipment Record before testing The check that passes it
ControlLogix Communication interface, network route, controller tag scope Read the intended tags through the real route
SLC and MicroLogix Exact processor, port, protocol, data-table addresses Read representative data types, then test the required writes
Mitsubishi FX2N Installed interface and supported protocol Confirm the driver matches that interface, not the family name
S7-300 and S7-400 CPU, communication hardware, connection resources, data access configuration Read the intended memory areas with correct interpretation
Siemens S5 Existing port, interface hardware, protocol Prove the complete legacy connection before accepting any driver claim
Red Lion G3 Whether it serves data upstream or touches the controllers itself Identify the server interface it exposes, or bypass it with direct PLC links
Serial ASCII devices Serial settings, wiring, request format, response terminator, checksum One full transaction end-to-end through the chosen transport

Proving a controller path #

Build one evaluation screen and use it for every candidate: a live value, a quality indication, a timestamp, a trend, and one controlled command where the project needs writes. Each controller path then earns four recorded checks:

  • One configured device connection reading a known, changing value.
  • The value compared against the controller's own engineering tool, with data type, signedness and scaling all agreeing.
  • Tag quality, timestamp and driver diagnostics visible while the link runs.
  • A broken connection showing up as bad quality, not as a frozen good value.

Before the first commanded write, make the field side safe — inhibit the real outputs or disconnect the load — so an early or duplicated write cannot move the machine.

If the tag updates correctly but the screen does not, the fault is in the binding or the client path, not the driver. That layered screen is what lets maintenance locate a failure at 2 a.m. without swapping working components.

Bringing serial ASCII devices onto Ethernet #

Putting a serial device on Ethernet changes its transport, not its message. A transparent serial-to-Ethernet server carries bytes; something must still frame the request, parse the ASCII reply, apply any checksum and decide what a timeout means. Two architectures cover it:

  • A transparent server, with the transaction and parsing implemented in the SCADA package itself.
  • A protocol-converting gateway that already speaks the device's format and presents structured values over a protocol the SCADA supports.

Default to the converting gateway when one exists for your device: you buy the parsing once instead of owning it in the SCADA. Use the transparent server when the package's scripting handles the transaction cleanly or no gateway exists. Either way, record the serial settings, request format, response terminator and any checksum from the device documentation, then test the failure modes deliberately: disconnect the device mid-transaction and feed a truncated reply, and confirm the quality changes instead of the last value sitting on screen looking healthy.

On the gateway route, also verify how a dead downstream device is reported — stale data behind a healthy-looking status is the failure that gets missed. The same selection questions arise when a controller is the serial client rather than the SCADA, as in connecting ControlLogix to RS232 and RS485 serial devices.

Where the browser client and runtime run #

A browser client still needs a runtime service behind it: something has to poll the controllers and serve the application. For these single-client systems, host the runtime on the touch-panel PC itself — one computer, one license footprint, no panel-to-server link to lose — and move to a separate server only when the combined load test pushes the panel past responsiveness or site availability demands it. At the point the machine is chosen, specify it as an industrial panel PC rated for cabinet-door duty rather than a repurposed office box, then prove it:

  • Launch the application in the intended browser on the panel and exercise touch response, screen fit, navigation, login and command confirmation.
  • Run polling, trends, alarms and database logging together while watching processor, memory and storage.
  • Restart the panel and interrupt the client-to-runtime link; the operator must be able to tell a disconnected browser session from a device-level tag fault.

Proving SQL logging through a database outage #

A database connection proves credentials and a network path; it proves nothing about logging. The historian test: start logging a changing tag, stop the database service or pull its network link, watch whether the SCADA buffers or discards, then restore and count. Records buffered during the outage must appear exactly once with correct plant-time timestamps; gaps or duplicates disqualify the configuration. Run it against whichever database the project ships — SQL Server or MySQL — because the connector, not the concept, is what you are buying.

Duplicate rows have a second life as a query failure: a client that expects one record and receives two rejects the result set, the failure behind fixing the Ignition more-than-one-record result set error, so if Ignition joins the shortlist, test for it deliberately.

Worked example: scoring four candidates over nine paths #

Inputs. The project list names nine equipment categories: one ControlLogix platform, two legacy Allen-Bradley lines (SLC and MicroLogix), one FX2N, two S7 lines (S7-300 and S7-400), one S5, the Red Lion G3s, and the serial ASCII devices. Grouped by the connection each needs, that is six controller paths plus three non-controller paths — the ASCII transaction, the browser session on the panel, and the SQL record across the outage. The field replies put four packages on the shortlist. Every path earns the same four recorded checks defined earlier, adapted to the path: a configured connection, a correct value or rendering, visible quality or diagnostics, and a visible failure.

Rule. A candidate is acceptable only when every mandatory path passes all four checks. A failed path converts to conditional only when a specific gateway or OPC route is named for it and added to the test plan; a failed path with no named route rejects the candidate for this program.

Arithmetic. 6 controller paths + 3 non-controller paths = 9 mandatory paths. 9 paths × 4 checks = 36 recorded results per candidate. 4 candidates × 36 results = 144 recorded results for the program.

Result and decision. Accept at 36 of 36. A candidate at 35 of 36 with the S5 read failing stays on the list only with a named S5 route — a protocol gateway or an OPC server — that is then tested; the same 35 of 36 with the database outage check failing is a rejection, because nothing external substitutes for the historian's own buffering. Two or more failed paths ends the candidacy outright: at that point the integration risk is the package. Where a controller is not yet on the bench, rehearse the SCADA side first by simulating a Modbus TCP SCADA link on one PC; it proves the method, not the path, so the field test still counts.

Licensing the minimum deployable system #

Most of these projects ship single-client, so compare packages on the smallest system one site can legally run: development seat, runtime, the served browser client, any per-driver or per-connection licenses, and the database connector. Count those components per package before comparing anything else. The minimum deployable system differs between packages far more than the feature matrices do, and the package with the smallest true minimum usually wins single-client work even when its enterprise story is thinner. Confirm in writing that the license allows the runtime and the served client together on one machine — the panel PC is the deployment, not a workstation.

Questions asked

Can one SCADA package really talk to all these PLC families at once?

Yes. Packages reach mixed brands through native drivers or through OPC, and both routes run production plants every day. The limit is never the number of families; it is the interface on each device, because the communication option fitted to the FX2N or the port on the S5 decides the driver or gateway. Give every family its own commissioned path and the count stops mattering.

Why not just pick the package with the longest driver list?

Because a listed driver is matched to specific interfaces, addressing schemes and firmware, not to family names. The S5 and the ASCII devices are exactly where a brochure claim and a working connection part ways. Nine commissioned paths with recorded pass and fail results rank candidates better than any driver count can.

What does a transparent serial-to-Ethernet server leave undone?

It moves bytes, not meaning. The SCADA, or a gateway behind it, still frames each request, parses the ASCII reply, applies any checksum and decides what a timeout means. If keeping that parser alive in the SCADA package looks like permanent work, that is the signal to buy the converting gateway instead and let it present structured values.

Does single-client licensing change which package wins?

Often it decides the whole contest. Count the smallest system one site can legally run, including development seat, runtime, served client, driver licenses and the database connector, before comparing features. Two packages that look identical on an enterprise feature matrix can need very different component counts for a single-client box, and the smaller true minimum usually wins that work.

Keep reading

  • 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.

    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 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.

    SCADA and data logging