Mazak MTConnect Machine Monitoring
Mazak was one of the early supporters of MTConnect, and many Mazak machines can publish MTConnect data. Here is how to check yours and get it into a live dashboard.
Mazak was among the early machine builders to back MTConnect, and many Mazak machines in the field can publish MTConnect data. For shops with Mazak turning centers, machining centers, or multi-tasking machines, that often means monitoring is a matter of finding and testing the endpoint rather than buying hardware.
Check the MAZATROL control and its configuration first. That decides whether the machine is ready today.
Mazak controls and MTConnect
| Control family | Typical MTConnect situation | What to check |
|---|---|---|
| Newer MAZATROL controls (for example the Smooth series) | MTConnect capability commonly available | Network connected, MTConnect configured, IP and port |
| Older MAZATROL controls | Varies by control and software | Ask Mazak service whether an adapter or update is needed |
| Machines with non-Mazak controls | Depends on that control | Follow that control's MTConnect path |
Configuration differs between machines even within one control family, so test each one.
How Mazak machines typically publish MTConnect
Depending on the machine, MTConnect may be served:
- from the control's PC side, where an adapter and agent run on the control's Windows environment
- from a separate agent PC that collects from one or more Mazak machines
- through a Mazak connectivity product such as SmartBox, which Mazak offers for secure machine connectivity
Your Mazak service contact or dealer can tell you which applies to your machines.
Step 1: Network the machine
- Connect the machine to the shop network with a cable.
- Set a fixed IP address.
- Confirm the monitoring PC can reach it.
Step 2: Find the MTConnect endpoint
Look in the control's network and MTConnect configuration, or ask whoever set up connectivity. Note the IP address, port, and any device name. Port 5000 is a common default but not universal.
Step 3: Test it
From the monitoring PC:
- Open
http://<ip>:<port>/probe— confirm the device and its data items. - Open
/current— check Execution, Program, PartCount, and ControllerMode have real values. - Run a cycle and refresh — watch Execution change and parts count up.
If something fails, How to Test an MTConnect Connection walks through each cause.
What Mazak MTConnect data is used for
| Data | Monitoring use |
|---|---|
| Execution | Running, idle, stopped time |
| Program | Job-level run time and cycle comparison |
| PartCount | Production and OEE performance |
| ControllerMode | Production vs setup and MDI |
| Conditions | Alarm time and recurring faults |
| Spindle and override data | Cutting activity, slowed programs |
Multi-tasking machines may publish several paths or spindles. Good monitoring handles each path correctly.
Mazak-specific tips
- Multi-path machines — check which path's Execution the monitoring uses for running time.
- Bar feeders and automation — long unattended runs make Mazak cells great candidates for alerts when a machine stops.
- Control PC updates — re-test MTConnect after Windows or control software updates on the control side.
- Part counting — confirm counts increase once per part, not per program loop.
Questions to send your Mazak service contact
Include the machine serial number and ask:
- Which MAZATROL control and software version does this machine have?
- Is MTConnect available on this machine, and is it enabled?
- Where does the MTConnect agent run — on the control, on a separate PC, or through a Mazak connectivity product?
- Which IP address and port does the agent use?
- Which data items are published — execution, program, part count, mode, alarms?
- For multi-tasking machines, which paths and spindles are published?
Keep the answers with your machine records. They save hours the next time a control is updated or someone new takes over the monitoring.
A two-machine pilot plan for Mazak shops
- Choose two machines. A multi-tasking machine and a simpler machining center make a good pair because they test both single-path and multi-path data.
- Confirm MTConnect on each with a browser test.
- Connect them to monitoring and leave them running through at least one full week, including any unattended shifts.
- Check accuracy. Walk the floor a few times and compare what you see with the live status.
- Review the week — utilization by shift, longest stops, setup time, and any alarms that repeat.
- Decide what to do next — expand to more machines, adjust part counting, or fix a network problem first.
Why unattended Mazak cells benefit most
Mazak machines are often set up with bar feeders, pallet changers, or robots for long unattended runs. The cost of a stop is highest when nobody is standing at the machine. Monitoring shows exactly when an unattended run ended and why, and alerts can tell someone the machine stopped instead of finding out at the start of the next shift. For lights-out work, that alone can recover hours each week.
Mazak machines in a mixed shop
Because MTConnect describes every machine the same way, a Mazak turning center and a Haas mill can appear on the same board, with the same status colors and the same utilization math. That makes fair comparisons possible across the whole floor.
Monitoring Mazak machines with FEAI
FEAI Machine Monitor reads Mazak machines that publish MTConnect and shows live status, machine timelines, utilization, OEE, downtime, and shift reports — alongside Haas, Okuma, and FANUC-controlled machines in mixed shops.
It is a read-only client that runs on a Windows PC on your network and stores data locally.
Mazak machine answering on MTConnect? Start free — 2 machines.
FAQ
Do Mazak machines support MTConnect?
Many do. Mazak has supported MTConnect for years, and many MAZATROL controls can provide it. Availability depends on the control, software, and configuration, so check each machine.
Which Mazak controls provide MTConnect?
Newer MAZATROL controls such as the Smooth series commonly provide MTConnect capability. Older controls vary. Your Mazak service team or dealer can confirm a specific machine.
Do I need a Mazak SmartBox to monitor machines?
Not necessarily. SmartBox is a Mazak connectivity product. Many monitoring setups read an MTConnect endpoint directly from the control or an agent PC.
How do I find a Mazak machine's MTConnect endpoint?
Check the control's network settings and any MTConnect configuration, ask your Mazak service contact, then test http://ip:port/current from the monitoring PC.
Can Mazak and non-Mazak machines be monitored together?
Yes. When each publishes MTConnect, one client shows them side by side.
Is FEAI affiliated with Mazak?
No. FEAI Machine Monitor is independent software and is not affiliated with or endorsed by Yamazaki Mazak.