Overview

Serve every machine from a central server with the free Agent Hub and Tools, and add per machine licensed Data Collection when you need it.
MTConnect Server Docs Menu

MTConnect Server runs on a central server and connects to the MTConnect Agents and SHDR Adapters on the shop floor. It serves every machine from a single MTConnect port, and can collect their data into a database or an MQTT broker. It's configured and monitored from a web App, and its data is available to other applications through a REST API.

Start with the free Agent Hub and Tools to set up your machines, then add Data Collection when you're ready. The two features can be used together or on their own:

FeatureWhat It DoesLicense
Agent HubReplaces an existing MTConnect Agent by reading SHDR Adapters directly, or serves Devices from many existing Agents and Adapters from a single port as a central hub. Each Device runs its own MTConnect Agent.Free, no License required
Data CollectionReads the same Devices, stores their data in Tables (SQLite, PostgreSQL, or SQL Server), and publishes it as Messages (MQTT). Add it to the machines you already serve.One seat for each Device that's collected

MTConnect Server is designed to run on a central server. The MTConnect.NET Agent is designed to run on the machine, and the Agent Hub can serve those Agents, or replace them.

The App's Tools (Network checks, the Request Browser, Device Validation, the SHDR Browser, and the Definition Browser) are also free, so MTConnect Server can be installed just to troubleshoot machine connections.

MTConnect AgentsProbe, Current, and Sample over HTTP (port 5000)
SHDR AdaptersTCP stream (port 7878), with a Device model
MTConnect Server
Data CollectionTables in SQLite, PostgreSQL, or SQL Server, and Messages to an MQTT broker
Agent Hubhttp://{server}:5001/{deviceUuid}/current for any MTConnect client
App & REST APIhttp://{server}:8490/ and /api
Collection and the Agent Hub read from the same list of Devices, and either can be turned on for each Device.
The App's Home page: what MTConnect Server is set up to do, and how it's running
The App's Home page: what MTConnect Server is set up to do, and how it's running

Concepts

TermDescription
DeviceA machine, read from one Device on an MTConnect Agent or from an SHDR Adapter. Every Device is in one list, and the Agent Hub and Collection are turned on or off for each one.
GroupA named set of Devices, such as a plant or a cell. A Group's Profiles apply to each of its Devices.
ModelA saved MTConnect Device model, used to serve an SHDR Adapter or to change the model an Agent reports.
ProfileA rule for which data goes where: Tables (a database) or Messages (MQTT), with its own Filter and destinations.
Service & RouterA database or MQTT broker connection (a Service), and the Router with the same name that a Profile sends data to.
FilterThe DataItems a Profile includes, and how often their values are sent.
Retention RuleHow long a Tables Profile keeps Observations before deleting them.
License CodeA code for this computer with one or more seats. Each collected Device uses one seat.
WorkerA background process. The Collection Worker collects data, and the Agent Hub Worker serves Devices.

How It's Built

MTConnect Server is built on the TrakHound Framework and the MTConnect.NET Agent. The installer sets up a TrakHound Instance that runs as a Windows Service, with the MTConnect Server App, Api, Workers, and the database and MQTT Services already configured. The MTConnect Server Packages can also be installed on an existing TrakHound Instance (see Installation).

Explore the Docs

The Agent Hub and Tools are free. Data Collection is licensed at $30 per machine per month. Get a free 2-hour trial License instantly after installing, with no sales call. See Pricing and the Licensing Guide.