Devices in the App's menu is the single list of the machines added to MTConnect Server. A Device only needs its source, an MTConnect Agent or an SHDR Adapter. The Agent Hub and Collection are optional for each Device, and can be turned on or off at any time.
| What the Device Does | Result | License |
|---|---|---|
| Nothing (neither turned on) | The Device is kept to organize machines, store their connection details, and send them requests. It's shown as Not monitored. | None |
| Serve through the Agent Hub | The Device is served from the Agent Hub's port, with its own MTConnect Agent. | None |
| Collect data | The Device's data is sent to its Profiles. | One seat |
Add Devices from an MTConnect Agent
- Go to Devices and click Add Device.
- Enter the Agent's Address and Port (default
5000), and click Find Devices. Path is only needed when the Agent is served under a path. - Choose the Devices to add from the ones the Agent reports. Devices that were already added are marked Already added. To type a Device in instead, use Enter a Device manually.
- On Review, optionally change the Description values (UUID, Name, Manufacturer, Model, Serial #, and Station), which override what the Agent reports.
- Optionally enter a Group, and choose what the Devices do: Serve through the AgentHub, Collect data, or neither. For collected Devices, choose the Profiles their data goes to, in addition to their Group's Profiles.
- Click Add Device.
| Setting | Default | Description |
|---|---|---|
| Address / Port / Path | port 5000 | The MTConnect Agent's HTTP address |
| Device | The name or UUID of the Device on the Agent | |
| Stream Interval | 100 ms | How often the Agent sends data |
| Stream Heartbeat | 10000 ms | How often the Agent sends a heartbeat when there's no new data |
| UUID, Name, Description, Manufacturer, Model, Serial #, Station | Optional values that override what the Agent reports |
Add a Device from an SHDR Adapter
An SHDR Adapter sends data over a TCP stream (usually on port 7878), but doesn't describe the Device, so it needs a Device model.
Go to Devices > Add Device and choose SHDR Adapter:
- SHDR Adapter - Enter the Adapter's Address and Port.
- Device Model - Choose a saved Model, upload a Device file, copy the model from an Agent's probe, or paste the XML. The Adapter's keys are matched to the IDs and Names of the model's DataItems.
- Review - Choose what the Device does, and click Add Device.
- Set Availability to AVAILABLE while connected - For Adapters that don't send Availability.
- Use the time data is received - Replaces the Adapter's timestamps.
- Reconnect Interval - How long to wait (in milliseconds) before connecting to the Adapter again after the connection is lost.
- Data sent while the Adapter is disconnected is lost, and the Device's values become
UNAVAILABLEuntil it reconnects.
Collection reads an SHDR Device through its Agent at the Agent Hub, so there's a single connection to the Adapter. Turning on Collection also serves the Device, and it can't stop being served while it's collected. This doesn't work while the Hub uses TLS.
The Devices List
The list shows each Device's source and its Agent Hub and Collection status, under its Group when Devices have Groups. Groups can be collapsed, and the filter searches every Device.
| Status | Meaning |
|---|---|
| Not monitored | Neither the Agent Hub nor Collection is on, so nothing connects to the Device. |
| No License | The Device is collected, but doesn't have a License yet. The Collection Worker notices a new License within about 30 seconds. |
| No Profile | The Device is read and its Connection Status is shown, but its data isn't stored or published anywhere until it has a Profile. |
A Device's Page
Open a Device to see and change it. Each Device has these tabs:
| Tab | Shows |
|---|---|
| Details | The Device's source and status. Check Connection checks the source now, which happens automatically when opening a Device that reads from an Agent. |
| Requests (Agent Devices) | Sends probe, current, and sample requests to the Device's Agent, the same as the Request Browser. |
| SHDR (SHDR Devices) | The last 500 Lines and the latest Value of each Key. It only connects when you click Connect, and reads the Agent Hub's connection while the Device is served, so no other connection is made to the Adapter. |
| AgentHub | The Device's Hub metrics, its connection to the source, its URLs with links to probe, current, sample, and assets, and its buffer. Add to AgentHub or Remove from AgentHub. |
| AgentHub Data | What the Hub serves for the Device, as clients see it: current values, samples (including Live), and the Device model. |
| Collection | The Device's License (Manage Licenses), its Profiles, and its position in the Agent's buffer. Reset Position reads the Device again from the Agent. Add to Collection or Remove from Collection. |
| Logs | The Device's entries from the Workers' logs. |
| Configuration | The Description and source settings, the Device Model, and Delete Device. Changes are kept while moving between tabs, and applied with Save Changes. |
- Removing a Device from the Agent Hub or Collection keeps it in Devices.
- A Device keeps its License when its Address, Port, or Device is changed, and its seat is released when it's deleted.
- The Request Browser, SHDR Browser, and Device Validation Tools can fill in a saved Device.