FANUC MTConnect Machine Monitoring

FANUC controls run a huge share of the world's CNC machines, but MTConnect is not always switched on out of the box. Here are the common ways shops get FANUC machines onto MTConnect and into a monitoring dashboard.

By Ryan Lenhart · Updated Oct 5, 2026

FANUC controls sit on machines from dozens of builders — mills, lathes, and machining centers that may otherwise share nothing. That makes FANUC machines both the biggest opportunity and the most common question in CNC monitoring: how do I get their data out in a standard way?

Key takeaway

FANUC machines usually reach MTConnect one of two ways: a FANUC MTConnect option on the control, or an adapter that reads the control and feeds an MTConnect agent.

Path 1: MTConnect directly from the control

FANUC offers MTConnect capability for supported controls as an option. When it is available and enabled, the control itself answers MTConnect requests on its network address, and no separate adapter PC is needed.

What to check:

The control series and software version
Whether the MTConnect option is installed and enabled
The IP address and port the control uses for MTConnect

Your machine builder or FANUC service can confirm what a specific control supports and what enabling it costs.

Path 2: A FOCAS-based adapter and agent

When the control does not have the MTConnect option, the most common route is an adapter that uses FANUC's FOCAS library to read the control over Ethernet, then feeds an MTConnect agent. The adapter and agent typically run on a small Windows or Linux PC or gateway on the shop network, and one agent can serve several FANUC machines.

This is how the open-source MTConnect ecosystem and many integrators bring FANUC machines onto MTConnect. Your monitoring software reads standard MTConnect, and never touches FOCAS directly. MTConnect vs FOCAS explains the difference.

Path 3: An existing agent from an earlier project

Many shops already have FANUC machines publishing MTConnect from a previous monitoring trial, MES project, or dealer installation. Try http://<ip>:5000/current against any agent PC on the network before buying anything. See Already Have MTConnect?

Comparing the paths

	MTConnect option on control	FOCAS-based adapter	Existing agent
Extra hardware	None	PC or gateway	Already there
Who sets it up	Builder or FANUC service	Integrator or in-house	Already done
Cost	Option price, if not installed	Adapter software and PC	None
Data depth	Defined by the option	Defined by the adapter	Varies
Machines per setup	One per control	Many per agent	Varies

Prerequisites for any path

Ethernet enabled on the control and connected to the shop network
A fixed IP address for each control so the adapter or monitoring software can find it
Network access from the agent or monitoring PC to the control
Someone to own it — usually a builder, dealer, or integrator for setup, and someone in-house for day-to-day checks

What data to expect from FANUC MTConnect

Most setups publish the essentials for monitoring:

Data item	Used for
Execution	Running, idle, and stopped time
ControllerMode	Automatic vs manual and MDI
Program	Which job is running
PartCount	Production and OEE performance
Conditions / alarms	Fault time and recurring alarms
Spindle speed, load, feed override	Cutting activity and overrides

Exactly which items appear depends on the option or adapter. Check /probe for each machine.

Testing a FANUC machine's MTConnect feed

Open http://<ip>:<port>/probe on the monitoring PC and confirm the device appears.
Open /current and check Execution, Program, and PartCount have real values.
Run a cycle and refresh — Execution should go ACTIVE and PartCount should increase if counting is enabled.

How to Test an MTConnect Connection covers every failure mode.

Questions to ask your builder or integrator

Which FANUC control series and software does this machine have?
Is the FANUC MTConnect option installed, or available, and what does it cost?
Is Ethernet enabled on the control, and which IP address does it use?
If you supply an adapter, which data items does it publish, and where does the agent run?
Who supports the adapter PC when it needs updates or a restart?

Common FANUC MTConnect problems

Ethernet not enabled on the control, or plugged into a different network.
Adapter PC turned off or asleep, so every machine it serves goes offline at once.
Part count not incrementing because the program does not trigger the counter.
Wrong path on multi-path lathes, so running time looks too low.

Monitoring FANUC machines with FEAI

Once a FANUC machine publishes MTConnect, FEAI Machine Monitor reads it like any other: live status, timelines, utilization, OEE, downtime, and shift reports. Mixed fleets show FANUC machines side by side with Haas, Mazak, and Okuma machines.

FEAI is a read-only MTConnect client. It does not use FOCAS directly, does not install adapters, and does not configure controls.

Compatibility note. FEAI Machine Monitor is designed to monitor supported FANUC-controlled machines when the required data is available through MTConnect. Compatibility depends on the control, options, adapter configuration, available data items, and network access.

Important limitations. FANUC and FOCAS are trademarks of FANUC Corporation. FEAI Machine Monitor is independent software and is not affiliated with or endorsed by FANUC or the MTConnect Institute.

FANUC machine publishing MTConnect? Start free — 2 machines.

FAQ

Do FANUC controls support MTConnect?

Many FANUC controls can provide MTConnect, typically through a FANUC MTConnect option or through an adapter that reads the control and feeds an MTConnect agent. Availability depends on the control series, software, and options.

Can I monitor FANUC machines without FOCAS?

Yes, if the control provides MTConnect directly. Otherwise most adapters use FOCAS to read the control and publish MTConnect, so FOCAS is used underneath while your monitoring software reads standard MTConnect.

What do I need to monitor a FANUC machine with FEAI?

An accessible MTConnect Agent or compatible endpoint for that machine, reachable from the Windows PC running FEAI. FEAI does not use FOCAS directly.

Do FANUC machines need Ethernet for monitoring?

Yes in practice. Both the MTConnect option and FOCAS-based adapters communicate over the control's Ethernet connection, which must be enabled and on the shop network.

Can FANUC and non-FANUC machines be monitored together?

Yes. Once each machine publishes MTConnect, a single client shows them side by side.

Who sets up a FANUC MTConnect adapter?

Usually your machine builder, dealer, or an integrator. FEAI reads the resulting agent and does not configure controls.