Skip to content
Proxus 2.0.0 Proxus 2.0: the largest release in Proxus history Release notes
Try free Book a demo

Drivers · Modbus

Modbus

Modbus data collection with Proxus

Proxus reads Modbus TCP devices, and Modbus RTU or ASCII devices through a serial device server, with a native driver in the gateway. Enter datasheet addresses such as 40001 and Proxus converts them; the values arrive in your Unified Namespace.

Send us your equipment list Book a demo

A Proxus engineer replies within one working day.

Protocols and ports

3 protocols in this family.

The port used when you leave Port empty, browsing the device, and finding servers on the network. The connection test works for every protocol.

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

  • Modbus RTU Over TCP

    Port when empty: 502

    Browse: No

    Discovery: No

  • Modbus ASCII Over TCP

    Port when empty: 502

    Browse: No

    Discovery: No

  • Modbus TCP

    Datasheet numbers such as 40001 are converted for you.

    Port when empty: 502

    Browse: No

    Discovery: No

Source: protocol reference

How it works

From the machine to your systems, in four steps.

  1. 01

    Add the device in the hub

    Choose the protocol that matches your equipment, enter its address and pick the gateway on the same network.

  2. 02

    Define the tags

    Enter the addresses you need or apply a device profile, so the next identical machine is a matter of applying the profile.

  3. 03

    Name it in the namespace

    Each value gets its place in the Unified Namespace (enterprise, site, area, line or cell, equipment), the same for every protocol.

  4. 04

    Deliver and act

    Send the values to databases, brokers, cloud and APIs, and run rules and anomaly detection at the edge.

Moving from Kepware

Running Kepware today?

Proxus imports channels, devices and tags from a running Kepware server. Siemens, Modbus Ethernet and OPC UA client channels are converted to the matching Proxus protocol; nothing changes on the Kepware side.

Kepware import guide Send us your equipment list

  • Runs at the edge

    The driver runs inside the gateway on the plant network. Data keeps being read when the link to the hub is down.

  • Buffered through outages

    Delivery to the hub and to every outbound target queues at the gateway (48 hours by default, up to 30 days) and is sent in order when the connection returns.

  • Nothing opens inbound

    The gateway connects out to the hub (port 7422, over TLS). Nothing on the plant network has to accept connections from the hub.

  • No per-tag pricing

    Tags, devices and users are not counted. You license gateways and data rate.

    See pricing

Setup details: protocol reference · Add a device · All drivers

Connection guides

Set it up step by step.

All connection guides

Next step

Send us your equipment list.

List your Modbus models and the other machines on the line. We confirm which protocol each one uses and what it takes to connect it.

Send us your equipment list Book a demo
  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.