Skip to content
Proxus 2.0.1 Licence and sign-in fixes after the 2.0 upgrade Release notes

Platform · Connectivity

Talk to the equipment you already have.

Native drivers for the controllers, machines and standards on your floor. Pick the protocol, list the values you need: no PLC changes, no middleware.

Connects to
60+ protocols: PLCs, CNCs, robots, meters and OPC UA servers
Configuration
Gateway, protocol, address and tags; no code
Handled for you
Polling, reconnection and per-tag quality

From the wire to a signal

A register number becomes a value people understand.

The gateway reads the raw value; the tag gives it a name, a type and a unit, and the plant tree gives it a place.

  1. On the wire Modbus TCP · 40001 = 118 Holding register on the mixer’s controller
  2. Tag Speed · UShort · rpm Defined once in the device profile
  3. Place Lyon Foods Plant › Processing › Dough › Mixer 3 Enterprise, site, area and cell
  4. Signal Speed 118 rpm · Good What dashboards, rules and targets read

In the product

Connecting a machine, step by step.

Test before you save

Enter the address and test the connection from the gateway itself, before anything is saved.

  • The test runs on the gateway, not the hub
  • Saved, sent to the gateway and reading in one pass

Read every tag once

Paste tags from a datasheet and read each once: a wrong address shows at the desk, not on site.

  • Value or error per tag, before saving
  • Name, address, data type and unit per tag

Browse instead of typing

Find an OPC UA server, browse its address space and add the tags you need.

  • MTConnect, SNMP and Allen-Bradley browse the same way
  • Kepware projects read from a running Kepware server

Model a machine type once

A device profile holds the protocol, connection settings and tags; every identical machine inherits them.

  • Profiles export to a file, without passwords
  • Many devices at once from a CSV or Excel file

Real Proxus screens; the machine data shown is simulated.

Want to see this with your own machines? Check your equipment

Technical details Problems it solves, every capability and the full protocol table

What it solves

What teams run into without it.

  • One driver per destination

    Historians, MES and cloud services each arrive with their own connector to install, secure and keep alive.

  • Vendor lock at the field layer

    A gateway that speaks one vendor well and everything else badly turns every new machine into a project.

  • Nobody owns reconnection

    Scripts collect happily until the switch reboots, and the gap is discovered weeks later in a report.

What you get

Built in, not bolted on.

  • Browse before you configure

    Browse OPC UA, MTConnect, SNMP and Allen-Bradley address spaces, then pick the tags you actually want.

  • Tags with meaning

    Name, address, data type, scaling, unit and read interval per tag, the definition every downstream system inherits.

  • Connection health

    Current status, last update and quality per device, so a silent source is visible before it becomes a data gap.

  • Templates for identical machines

    Define a device profile once and apply it to every identical line, press or cell across sites.

What this enables

What the capabilities add up to, in practice.

  • Onboard a new machine as configuration, not as an engineering project
  • Keep one connection per device no matter how many systems consume it
  • Reuse a device profile across identical lines, cells and sites
  • Know which values are trustworthy right now, per device and per tag

Detail

Protocol coverage

The families teams ask about most. All 60+ protocols, grouped by vendor family, are in the driver list.

See all 60+ protocols
PLC
Siemens S7 (1500, 1200, 300, 200) · Allen-Bradley CIP and PCCC · Mitsubishi MELSEC · Omron FINS and CIP · Beckhoff ADS · Delta · LSIS · Keyence · Panasonic
Standards
OPC UA · Modbus TCP, plus RTU and ASCII over TCP · MQTT (devices publish to the built-in broker) · SNMP
Machines
Fanuc (FOCAS over Ethernet) · KUKA · Yaskawa · Haas · Heidenhain · MTConnect

Questions

What teams ask before the first call.

Ask something else
Do we need to change the PLC program to connect it?

No. Proxus reads from the controller using its native protocol, the same way an HMI or SCADA client would. No blocks are added to the PLC program and no vendor engineering software is required at runtime.

What if a machine speaks a protocol you do not list?

Most equipment exposes at least one of OPC UA, Modbus TCP or MQTT (publishing to the gateway’s built-in broker), which covers the majority of brownfield cases. Where it does not, custom sources can be added through the SDK. Bring the model number to the scoping call and we will tell you which path applies.

How are tags defined: one at a time?

You can define them manually, browse them from the device where the protocol supports it (OPC UA, MTConnect, SNMP, Allen-Bradley), or apply a device profile so an identical machine inherits the whole tag list at once.

What happens when a device goes offline?

The connection state is visible per device, reconnection is handled automatically, and values carry a quality flag so downstream consumers can tell a stale reading from a fresh one.

Can two systems read the same machine without doubling the load?

Yes, that is the point of collecting once. Proxus polls the device on a single schedule and every consumer reads the resulting modelled signal, instead of each system opening its own connection.

Check your equipment

Will it connect to your machines?

Tick what you run. An engineer checks each one against the driver list and replies within one working day.

Which of these do you run?

Controllers, CNCs and robots

Standards and transports

All 60+ protocols

We use your email to answer this check. Marketing emails only if you tick the box; no resale. Privacy notice

Check equipment Live demo