PLC connectivity, across every vendor you run.
One driver framework, not one integration project per PLC brand.
Why a driver framework, not a fixed protocol list
Most plants aren't single-vendor. A framework approach means every protocol — present and future — gets the same reliability characteristics: store-and-forward buffering, automatic reconnection, idempotent delivery, and per-channel diagnostics. Ath Software's engineering team has built device drivers for batch controllers, PLCs, weighbridges, card readers, and more across a 23-year history — that experience underpins the framework's design.
Modbus TCP & RTU
The most widely deployed industrial protocol — Ethernet and serial variants.
EtherNet/IP
Standard for Allen-Bradley/Rockwell and other EtherNet/IP-compatible controllers.
Siemens S7
Connectivity for the S7 PLC family.
Profinet
Real-time industrial Ethernet, common in Siemens-centric plants.
OPC UA & OPC DA
Platform-independent interoperability with any OPC-compliant controller or system.
DNP3 & IEC 60870
Utility and power-sector telemetry protocols.
Frequently asked questions
Our plant has three different PLC vendors — is that a problem?
No — this is exactly what the driver framework is designed for. Each protocol runs through the same acquisition and diagnostics layer.
What happens to a connection during a network blip?
Values buffer and forward automatically on reconnection, with sequence handling to prevent duplicates.
Can you add a protocol that isn't listed here?
Talk to us — the framework is designed for new drivers, and the team has decades of device-driver delivery experience.
Confirm your protocol fit.
Bring your toughest SCADA questions. Our engineers will show you real screens, real alarms, and real trends.
Or talk to us directly: +91 84014 22388 ·sales@scaiq.com