Native communication drivers connect the eScada server directly to PLCs and field devices: no gateways, no middleware, no additional software to buy and maintain.
A server can run several communication channels at the same time, each one associated with a protocol; under each channel, several devices speaking that protocol can be configured. Every device exposes its own array oriented tags, and each element of an array can be configured individually with engineering units, notes, scaling and other attributes: vectors for efficiency, fine grained configuration where it matters.
Other kinds of communication drivers are works in progress and are not listed, but in the event your device does not support any of the protocols listed below, do not hesitate to ask for its implementation. We are very pleased to implement communication drivers on request.
- Allen Bradley EIP - Ethernet
- Allen Bradley PCCC - Ethernet
- Allen Bradley DF1 - Serial
- Applicom (Windows x86 OSs only)
- CAN Bus USBTin (fischl.de/usbtin)
- CAN Bus SocketCAN (Classic CAN and CAN-FD)
- General Electric SRTP - Ethernet
- Kernel PLCs TCP - Ethernet
- Kernel PLCs - Serial
- Kunbus (Revolution Pi, revolution.kunbus.com) - Direct I/O
- LTI Servo One - Ethernet
- Mitsubishi FX (PRG) - Serial
- Mitsubishi Computer Link - Serial
- Mitsubishi SLMP1E - Ethernet
- Mitsubishi SLMP3E - Ethernet
- Modbus TCP - Ethernet
- Modbus RTU - Serial
- OMRON CMODE - Serial
- OMRON FINS Serial - Serial
- OMRON FINS TCP - Ethernet
- OMRON EIP (CIP) - Ethernet
- OPCUA Client - Ethernet - TCP transport
- Saia Burgess S-BUS - Serial
- Siemens S7 protocol - Ethernet (even for MPI to Ethernet adapters)
The full documentation for every driver is available in the Documents section.