Kepware Server offers more than 150 drivers for controllers from Allen-Bradley, Siemens, Modicon, Mitsubishi, Omron, GE, ABB, Honeywell, Yaskawa and many other manufacturers. The most commonly used driver groups are listed below.

Coverage
150+ device drivers
Driver choice
By controller family and communication interface
Licence
Per driver or as a pack
Current list
On the official product page

The right driver for your device and sector

Energy

Device data flows through drivers to Kepware Server and clients
Velotic
IEC 61850 MMS Client
IEC 60870-5-104 Client
DNP Client Ethernet (DNP3)
KepwareServer
OPC UA
MQTT
SCADA · MES

Substation, protection relay and remote station connections.

Manufacturing

Device data flows through drivers to Kepware Server and clients
Velotic
Siemens TCP/IP Ethernet
Siemens S7 Plus Ethernet
Allen-Bradley ControlLogix Ethernet
KepwareServer
OPC UA
MQTT
SCADA · MES

S7 TCP/IP and S7 Plus are different drivers; select against CPU and firmware.

Infrastructure

Device data flows through drivers to Kepware Server and clients
Velotic
Modbus TCP/IP Ethernet
BACnet/IP
SNMP
KepwareServer
OPC UA
MQTT
SCADA · MES

Bring meter, building automation and network monitoring data into one layer.

Example drivers. Confirm the exact model, protocol role and version support in the manufacturer documentation. Official driver documentation

Major Driver Groups

  • Allen-Bradley: ControlLogix, CompactLogix, MicroLogix, SLC 500, PLC-5
  • Siemens: S7-200/300/400/1200/1500, S5, SINUMERIK CNC
  • Modbus: Modbus TCP/IP, Modbus RTU, Modbus ASCII, Modbus Plus
  • Schneider Electric: Modicon M340, M580, Quantum, Premium
  • Mitsubishi: MELSEC Q, L, FX series
  • Omron: CJ, CS, CP series, FINS
  • GE: 90-70, 90-30, PACSystems
  • ABB: AC800M, AC500, Advant Master, S800 I/O
  • Honeywell: HC900, Experion controllers
  • Example drivers: Modbus TCP/IP Ethernet, Siemens TCP/IP Ethernet, Allen-Bradley ControlLogix Ethernet, BACnet/IP, SNMP, OPC UA Client

The driver list grows with every release; for the current, complete list see the official Kepware product page or contact us.

What to consider when choosing a driver

  1. Controller familyDifferent series from the same vendor usually have separate drivers; the model and the communication interface are considered together.
  2. Connection pathEthernet, serial or a gateway: the driver is chosen by how you will reach the device.
  3. AddressingThe device's memory map and addressing format are verified against the driver documentation.
  4. Load and structureTag count, scan rate and device count determine the load per channel; separating channels by network and protocol makes performance and fault tracing easier.
  5. Device not in the listA generic protocol driver (Modbus, OPC UA client, SNMP) or a custom solution is evaluated.

Frequently asked questions

My device is not in the list; what should I do?

First check whether the device speaks a generic protocol such as Modbus, OPC UA or SNMP. If you are unsure, send us the model and the communication interface and we will work out the right driver together.

Can I mix several brands on one server?

Yes. Each brand or protocol is defined in its own channel; clients see everything through a single OPC UA interface. That is the typical reason for using Kepware Server in mixed plants.

How does the number of drivers affect licence cost?

Drivers are licensed individually or as packs; the options are summarised on the driver packs page.

Kepware ServerAn overview of the platformDriver packsLicence structureChoosing protocols and driversModbus, S7, EtherNet/IP and othersData collection in an existing plantStart small