Already Have MTConnect? Start Monitoring It Today
If an MTConnect Agent is already answering on your network, you do not need new hardware or a long project. Here is exactly what you need, how to find your endpoint, and how to connect it.
Plenty of shops have MTConnect running and are not using it. A previous monitoring trial left agents behind. A machine dealer turned the option on at install. An ERP or MES project connected a few machines and then stalled. The data is sitting on the network, answering requests nobody sends.
If that is you, connecting FEAI Machine Monitor is a 10-minute job per machine.
An MTConnect Agent that answers on your network is the only hard requirement. Everything else is typing an address into a Windows app.
The requirements
| Requirement | How to check |
|---|---|
| An accessible MTConnect Agent or compatible MTConnect endpoint for each machine | Open http://<ip>:<port>/current in a browser — XML should come back |
| The endpoint address: IP, port, and path | Agent configuration, dealer documentation, or the person who installed it |
| Network reachability from the monitoring PC | Same network or routed VLAN, firewall allows the port |
| Useful data items | /probe lists execution, part count, program, and alarm items |
| A Windows 10 or 11 PC | Office PC or mini-PC near the floor |
Step 1: Find your endpoints
Look in these places, in this order:
- Previous projects. Whoever ran an earlier monitoring or MES trial will have a list of agent addresses.
- The control. Many controls show MTConnect settings, including port, in a network or option menu.
- Your dealer or integrator. They often enable MTConnect at installation.
- An agent PC or gateway. In multi-machine setups, one agent may serve several machines on a single address, each as a separate device.
- Scan LAN. FEAI's read-only network scan probes common ports for MTConnect responses. It helps, but it will not find agents on other subnets or unusual ports.
Port 5000 is the most common default. Some installations use 5001, 5002, 7878, or anything else. The path is usually empty or the device name.
Step 2: Test in a browser
On the PC that will run FEAI, open:
http://<ip>:<port>/probe— describes the devices and their data itemshttp://<ip>:<port>/current— shows the latest values
If both return XML, you are ready. If the page times out or refuses, the problem is network or agent, not software — work through How to Test an MTConnect Connection.
Step 3: Check the data items
In the /probe response, look for these data items on each device:
| Data item | Why it matters |
|---|---|
| Execution | Running vs ready vs stopped vs interrupted — the core of every timeline |
| Availability | Whether the agent can talk to the machine at all |
| PartCount | Production counts for output and OEE performance |
| Program | Which job is running |
| ControllerMode | Automatic vs manual vs MDI |
| Conditions / alarms | Faults and warnings |
Execution and part count are the two that matter most. Missing items usually mean the adapter is not mapping them — a fix for whoever configured the adapter. See What Data Does MTConnect Provide? for details.
Step 4: Connect in FEAI Machine Monitor
- Create a free license and download the Windows app.
- Install, activate with your Installation ID, and open the CONNECT tab.
- Enter the endpoint's IP, port, and path — or use Scan LAN to pick it from a list.
- Confirm the device and watch live data arrive.
- Name the machine the way your floor names it, and set its ideal cycle time so performance and OEE are meaningful.
Repeat for the second machine on the free plan. Leave it running a full week before judging the numbers.
Sharing an agent with another system
MTConnect agents serve read-only HTTP requests and can usually answer multiple clients at once. If your agents were installed as part of another vendor's system, check with them before adding load — but in most cases FEAI can read alongside an existing system without changing anything.
When "we have MTConnect" turns out to be partly true
Common situations and what to do:
- The option is licensed but disabled. Enable it on the control or ask the dealer.
- The agent runs but the adapter is not connected. Availability shows UNAVAILABLE. The adapter needs restarting or reconfiguring.
- Only some machines have it. Start with those. Connect the rest as adapters are added.
- Data items are missing. Execution present but no part count is common. Part counting may need enabling in the control or programs.
- The agent is on a different network. Talk to IT about routing or a firewall rule for the agent port.
Don't have MTConnect yet?
Start with Learn MTConnect and What Is an MTConnect Agent? to understand the options for your controls, then follow the Connect a CNC Machine checklist.
Put your existing MTConnect data to work
Start free — 2 machines. No credit card, no trial clock.
FAQ
How do I know if my machine already has MTConnect?
Check the control's options list or manual, ask your machine dealer, or try opening http://machine-ip:5000/current in a browser on the shop network. If XML with device and data items comes back, an agent is answering.
What port does MTConnect use?
Port 5000 is common, but agents can be configured on any port. Check the agent configuration or ask whoever installed it.
Can FEAI share an MTConnect agent with another system?
Usually yes. MTConnect agents serve read-only HTTP requests and can typically answer more than one client. Check with whoever maintains the agent if it is part of another vendor's system.
Do I need to install anything on the machine?
Not if an accessible agent is already running. FEAI is installed on a Windows PC and connects over the network.
What if the agent answers but data looks incomplete?
The agent may not publish every data item, or the adapter may not be mapping them. Execution state and part count matter most for monitoring. Check the probe response and talk to whoever configured the adapter.
Does connecting FEAI change my MTConnect setup?
No. FEAI only reads from the agent with HTTP GET requests.