One integration layer for every controller on your plant floor
AXLink bridges Siemens S7, Mitsubishi FX, Unitronics and Advantech ADAM controllers — and is built to keep adding more — into a single Modbus TCP / OPC UA interface. Point any SCADA or HMI at it, legacy or modern, and stop writing one integration per device.
What AXLink Delivers
- Unified Modbus TCP / OPC UA output
- Isolated, independent polling per device
- Zero-downtime configuration changes
- Built-in diagnostics and live signal monitoring
Mixed-vendor plants, no common language
Most industrial sites run controllers from several vendors, wired over MPI, RS-485 or a bare programming port — and rarely does one SCADA driver cover them all natively. Meanwhile, plants standardized on an older SCADA platform face a separate problem: migrating to something newer usually means re-writing every driver again.
AXLink sits in between: it speaks every field protocol directly to the device, and exposes all of it as plain Modbus TCP / OPC UA — the two interfaces essentially every SCADA and HMI on the market can read, from legacy platforms like InduSoft Web Studio to modern ones like Ignition. Swap the SCADA later without touching the field wiring or the PLC programs.
Field protocol in, standard interface out
Field Controllers
S7, ADAM, Unitronics, Mitsubishi FX today — more vendors added as separate driver modules
AXLink
One independent polling channel per device, mapped automatically into a shared register table
Modbus TCP / OPC UA
One standard interface, ready for legacy or modern SCADA/HMI/historian software
Built for continuous operation, not a demo booth
Isolated Channels
Every protocol keeps its own connection, retry logic and timer — one device going offline never affects another.
Zero-Downtime Configuration
Editing settings restarts only the affected channel — never the polling engine or the Modbus/OPC UA server.
Live Monitor
Every mapped signal in real time, with a text filter and a pinned/favorites list for the tags you check most often.
Built-in Diagnostics
Per-device connection status, retry counters and last-poll timestamps — real data quality, not just a SCADA link check.
Modular Driver Architecture
Each protocol is one self-contained driver module — adding a new one never touches the engine or existing drivers.
Growing protocol coverage, one driver at a time
AXLink's driver architecture is built so a new protocol is a single module, not a rewrite. Today's coverage, plus what's next.
Available Today
Siemens S7
AvailableOver MPI (PRODAVE6, official Siemens stack) or a built-in Ethernet alternative (S7comm/TCP), switchable per site.
Advantech ADAM
AvailableRS-485 I/O modules — digital in/out, analog input — already running in active field deployments.
Unitronics
AvailableV-series PLCs via the official Unitronics driver — inputs, outputs, memory bits, integers and timers.
Mitsubishi FX
AvailableProgramming-port serial protocol (X/Y/M/D/T/C) — verified line-by-line against Mitsubishi's own official protocol manual.
On the Roadmap
Not built yet — listed here because the driver architecture makes each one a scoped, standalone addition. Tell us which protocol matters most for your site.
Not locked to legacy platforms
Because AXLink's output is plain Modbus TCP and OPC UA, it works with essentially any SCADA, HMI or historian that speaks either standard — from decades-old installs to today's web-based platforms.
Listed for compatibility by protocol (Modbus TCP / OPC UA), not vendor partnership. Still on a legacy platform like InduSoft? AXLink lets you migrate the SCADA layer later without re-wiring the field side.
Also Relevant For
Running a mixed-vendor plant on a SCADA that's starting to show its age?
Tell us what's on site and we'll tell you honestly whether AXLink fits — including what's still in progress.
Contact Us