Skip to content
Proxus 2.0.0 Proxus 2.0: the largest release in Proxus history Release notes

Drivers

66 protocols, read natively at the edge.

Every driver below runs inside the Proxus gateway. You add a device in the hub, choose its protocol and address, and the gateway reads it. No PLC program changes and no OPC middleware in between; some controllers need a one-time access setting, such as PUT/GET on S7-1200/1500 or an AMS route on Beckhoff. The list comes from the product itself and shows only drivers that are released.

Not sure a machine is covered? List make and model; a Proxus engineer replies within one working day.

PLCs

Over TCP in a name means a serial protocol carried over TCP, through a serial device server or a converter. Proxus does not open serial (COM) ports directly.

Devices that speak MQTT publish straight into the gateway’s built-in broker; HTTP devices can be polled with a function; the Simulator lets you try pipelines, dashboards and rules without a device. Need a protocol that is not here? Tell us which one.

Moving from Kepware

Running Kepware today? Bring its project with you.

Proxus imports channels, devices and tags from a running Kepware server, after you review every change. Siemens, Modbus Ethernet and OPC UA client channels are converted to the matching Proxus protocol; other drivers are listed but not converted. Nothing changes on the Kepware side.

Next step

Send us your equipment list.

List the machines on your lines, with make and model. We confirm which protocol each one uses and what it takes to connect it.

  1. 01

    Scoping call

    Equipment, protocols, sites and the systems the data has to reach.

  2. 02

    Technical walkthrough

    A working demo against a scenario that resembles your plant, not a generic tour.

  3. 03

    Pilot plan

    A defined first line or site, with the deployment and security questions answered up front.

  4. 04

    Roll-out

    The same templates bring the next lines and sites online.