How to Find, Test, and Fix an MTConnect Connection
A step-by-step checklist to locate an MTConnect endpoint, prove it answers, confirm the data is usable, and troubleshoot the problems that stop most connections.
Most MTConnect problems are not software problems. They are an address typed wrong, a firewall in the way, or an adapter that stopped talking to the machine. A browser and ten minutes can tell you which.
Work through these steps in order on the same PC that will run your monitoring software.
Test from the monitoring PC, not your laptop. "It works from my desk" means nothing if the shop-floor PC is on a different network.
Step 1: Find the endpoint
An MTConnect endpoint has three parts:
| Part | Example | Where to find it |
|---|---|---|
| IP address | 192.168.10.41 | Control network settings, agent PC, IT records |
| Port | 5000 | Agent configuration (5000 is the common default) |
| Path | empty, or a device name | Agent configuration — often blank |
Places to look, in order:
- Documentation from earlier projects — monitoring trials, MES pilots, or integrators.
- The control — network settings and MTConnect option screens often show the port.
- Your machine dealer — they may have enabled MTConnect at installation.
- An agent PC or gateway — one agent may serve several machines from one address.
- A network scan — FEAI's read-only Scan LAN probes common ports for MTConnect responses. It will not find agents on other subnets, non-standard ports, or behind firewalls.
Common ports besides 5000 include 5001, 5002, and other values set by integrators. If you are guessing, try 5000 first.
Step 2: Test reachability
Open a browser on the monitoring PC and go to:
http://<ip>:<port>/current
| Result | Meaning | Next step |
|---|---|---|
| XML appears | The agent is reachable | Go to Step 3 |
| Page times out | Wrong IP, different network, or firewall | Check IP, network, and firewall |
| Connection refused | Right machine, nothing listening on that port | Check port and that the agent is running |
| Error page from another service | Wrong port | Try other ports |
You can also use the command line: ping <ip> checks basic reachability (some networks block ping), and curl http://<ip>:<port>/current returns the XML in a terminal.
Step 3: Check the device description
Open http://<ip>:<port>/probe. You should see one or more Device elements, each with components and DataItem entries. Look for these types:
- EXECUTION — running vs stopped
- PART_COUNT — production counts
- PROGRAM — active program
- CONTROLLER_MODE — automatic, manual, MDI
- AVAILABILITY — connection to the machine
- Condition items — alarms
If one agent serves several machines, note each device's name — you will select it when connecting.
Step 4: Confirm live values
Back in /current, check that the important items have real values, not UNAVAILABLE. Then run a cycle (or watch one) and refresh:
- Execution should change to ACTIVE during the cycle
- PartCount should increase at the end of the cycle, if counting is enabled
- Program should show the running program
If values change, the connection is good and ready for monitoring.
Step 5: Connect your monitoring software
In FEAI Machine Monitor, open the CONNECT tab, enter the IP, port, and path (or pick a Scan LAN result), select the device, and confirm data arrives. Built-in diagnostics confirm reachability and show which data items the agent publishes.
Troubleshooting common MTConnect problems
The page times out
- Confirm the IP address on the control or agent PC
- Check the monitoring PC is on the same network or a routed VLAN
- Ask IT whether a firewall blocks the port between the two networks
- Check the Windows firewall on an agent PC allows inbound connections
Connection refused
- The agent is not running — restart the agent service
- Wrong port — check the agent configuration file
- MTConnect option is not enabled on the control
Availability is UNAVAILABLE
- The agent is running but the adapter is disconnected
- Restart the adapter service and check its connection to the control
- The machine may simply be powered off
Execution or PartCount missing from /probe
- The agent's device configuration does not define them
- Ask whoever configured the agent and adapter to add the mapping
PartCount never changes
- Part counting is not enabled in the control or the program does not trigger it
- Multiple-part fixtures may need counter configuration
Data stops after a while
- Adapter crashes or loses its connection to the control — check adapter logs
- Network drops — check cabling and switches near the machine
- Machine sleep or power-saving modes
History has gaps
- The client polled less often than the agent's buffer covers
- Network outages longer than the buffer
Works from one PC but not another
- Different network segments or firewall rules — always test from the monitoring PC
When to call for help
If the agent and adapter were installed by a dealer or integrator, they are the fastest fix for adapter mapping and control-side settings. For network routing and firewall rules, involve your IT provider. FEAI Machine Monitor reads data. It does not configure controls, agents, or adapters.
Endpoint answering? Start free — 2 machines and watch the timeline fill in.
FAQ
How do I find my MTConnect endpoint?
Check previous project documentation, the control's network or option settings, your dealer, or an agent PC on the network. Then test candidate addresses with http://ip:port/current in a browser. Port 5000 is the most common default.
How do I test an MTConnect connection?
From the PC that will run monitoring, open http://ip:port/probe and http://ip:port/current in a browser. Both should return XML. Then run a cycle and refresh current to see values change.
Why does my MTConnect agent show UNAVAILABLE?
Usually the agent is running but its adapter is not connected to the machine, or the machine is powered off. Check the adapter service and its connection to the control.
Why is my MTConnect connection timing out?
Wrong IP, the agent is not running, the PC and machine are on different networks, or a firewall is blocking the port.
Can I test MTConnect without monitoring software?
Yes. A web browser is enough for basic tests, and command-line tools like curl work too.
Does FEAI help diagnose connections?
Yes. FEAI Machine Monitor includes connection diagnostics and a read-only Scan LAN tool to help locate and check MTConnect endpoints.