Protected Website Forms
HTTPS, antiforgery validation, input limits, and reCAPTCHA protect public form submissions. Review the safeguards.
MTConnect Adapter Guide
A practical guide to evaluating controller access, selecting software or appliance delivery, defining an MTConnect model, and validating the resulting machine data.
Where the Adapter fits
- Controller, PLC, API, or signalsThe machine-specific source of observations
- MTConnect AdapterMaps source data into the Adapter protocol for an agreed model
- MTConnect AgentApplies the device model and serves MTConnect documents and streams
- ConsumerMonitoring, analytics, alerts, validation, or manufacturing workflows
The MTConnect information model, Adapter, Agent, and downstream consumer are separate responsibilities. Read the MTConnect Information Model guide for the semantic relationships.
Assess controller and API access first
Start with the exact controller family, firmware, machine options, vendor licenses, and interfaces available at the machine. A similar machine model can expose different data when its controller generation or option package changes.
- Record the controller nameplate, firmware, communication options, and network interfaces.
- Confirm whether the source is a vendor API, OPC UA, Modbus, PLC data, discrete or analog I/O, or an existing MTConnect interface.
- Identify vendor SDK licenses, credentials, certificates, protocol ports, and physical hardware required for access.
- Map desired observations to data that the controller actually exposes; do not infer unavailable values.
- Document machine, cell, and plant network boundaries before deciding where the Adapter and Agent run.
Catalog as the source of current product facts
The public catalog currently contains 10 reviewed Adapter records. Each detail page owns its controller dependencies, delivery options, prerequisites, limitations, and published evidence through the catalog rather than page markup.
Compare current Adapter recordsSelection matrix
| Decision | What to verify | Why it changes the solution |
|---|---|---|
| Data access | Exact API, protocol, signal, license, and firmware | Determines whether the required observations can be collected and which dependencies are needed. |
| MTConnect scope | Devices, Components, Compositions, DataItems, Assets, and expected observations | Defines the model the Agent will publish and what downstream consumers can use. |
| Delivery | Software on approved infrastructure or Edge-Connect local machine integration | Changes hardware, operating-system, network, installation, and support responsibilities. |
| Installation | Remote, onsite, or qualified self-service access | Depends on plant policy, physical access, networking, and the work needed at the controller. |
| Validation | MTConnect version, representative machine states, model review, and evidence requirements | Establishes what was tested and which controller or configuration changes require review. |
Adapter selection and deployment checklist
- Inventory the machine, controller, firmware, options, and available interfaces.
- Define the operational questions and the MTConnect observations needed to answer them.
- Confirm controller access without assuming that a machine brand or model guarantees API coverage.
- Choose software delivery or Edge-Connect based on approved compute, network, and support constraints.
- Define the Device, Component, Composition, DataItem, and Asset scope with the downstream consumers in mind.
- Test representative idle, active, interrupted, alarm, and unavailable states where the equipment permits them.
- Validate documents and streams, record limitations, and retain the reviewed configuration.
- Plan change control for controller firmware, machine options, mappings, Agent versions, and network changes.
For online document checks and ongoing auditing options, use the MTConnect Validation Platform overview and Validator Workflow Guide.
MTConnect Adapter FAQ
What does an MTConnect Adapter do?
An Adapter obtains data from a controller, PLC, sensor, or vendor interface and formats observations for an MTConnect Agent. The Agent applies the device model and serves MTConnect documents and streams to consumers.
Do I select an Adapter by machine brand alone?
No. The controller family, firmware, enabled API or protocol, machine options, desired observations, and site network constraints can all change the integration path.
When should I use Edge-Connect?
Edge-Connect is an appliance option for local machine integration. It contains the applicable Adapter, a local MTConnect Agent, and the Edge-Connect application on the hardware.
Is Shop-Connect an Adapter deployment option?
No. Shop-Connect is a multi-Agent monitoring appliance that consumes data from separately deployed MTConnect Agents. It does not provide upstream machine connectivity.
How should an Adapter be validated?
Validate the device model and representative observations against the agreed MTConnect version and the actual machine configuration. Record what was tested, known limitations, and any changes that require revalidation.
Scope an MTConnect Adapter implementation
- Tailored to your machine connectivity needs
- Flexible deployment and licensing for your environment
- Rapid implementation with expert manufacturing support
