Drivers · MTConnect
MTConnect data collection with Proxus
Proxus reads any MTConnect agent over HTTP. The wizard finds agents on the network, you pick data items from a tree, and the values arrive in your Unified Namespace.
A Proxus engineer replies within one working day.
Protocols and ports
Protocol: MTConnect
The port used when you leave Port empty, browsing the device, and finding servers on the network. The connection test works for every protocol.
-
MTConnect
An MTConnect agent over HTTP. Discovery tries ports 5000, 5001, 5005, 5006 and 7000.
Port when empty: enter it
Browse: Yes
Discovery: Yes
Source: protocol reference
How it works
From the machine to your systems, in four steps.
- 01
Add the device in the hub
Choose MTConnect, enter its address and pick the gateway on the same network. Or let the wizard find servers on the network.
- 02
Browse and pick the tags
The gateway reads the address space, so you choose data points from a tree instead of typing addresses.
- 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.
- 04
Deliver and act
Send the values to databases, brokers, cloud and APIs, and run rules and anomaly detection at the edge.
-
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: MTConnect guide · Add a device · All drivers
Next step
Send us your equipment list.
List your MTConnect models and the other machines on the line. We confirm which protocol each one uses and what it takes to connect it.
- 01
Scoping call
Equipment, protocols, sites and the systems the data has to reach.
- 02
Technical walkthrough
A working demo against a scenario that resembles your plant, not a generic tour.
- 03
Pilot plan
A defined first line or site, with the deployment and security questions answered up front.
- 04
Roll-out
The same templates bring the next lines and sites online.