Okuma MTConnect Machine Monitoring

Okuma's PC-based OSP controls make MTConnect a natural fit, and many Okuma machines can publish MTConnect data. Here is how to check yours and get it into live monitoring.

By Ryan Lenhart · Updated Oct 5, 2026

Okuma's OSP-P series controls run on a Windows-based PC platform, which makes it practical to run MTConnect software directly on the control. Okuma has supported MTConnect for years, and many Okuma lathes, machining centers, and multi-tasking machines can publish MTConnect data with the right application installed.

Okuma controls and MTConnect

Your Okuma distributor is the best source for what a specific machine supports.

How Okuma MTConnect typically works

On OSP-P controls, an MTConnect adapter reads data through Okuma's application interface on the control, and an agent serves it over the network — often both on the control itself. One external agent can also serve several Okuma machines. What Is an MTConnect Agent? explains the two pieces.

Step 1: Network the machine

1. Connect the control's Ethernet port to the shop network with a cable.
2. Set a fixed IP address on the control.
3. Confirm the monitoring PC can reach the machine.

Step 2: Confirm the MTConnect application

Check that the MTConnect application is installed and set to start with the control. If it is missing, your Okuma distributor can advise on the right package and installation. Note the port the agent uses.

Step 3: Test the endpoint

From the monitoring PC:

1. Open http://<ip>:<port>/probe — confirm the device and data items appear.
2. Open /current — check Execution, Program, PartCount, and ControllerMode have values.
3. Run a cycle and refresh — Execution should go ACTIVE and parts should count.

How to Test an MTConnect Connection covers what to do when it fails.

What Okuma MTConnect data is used for

Multi-tasking and twin-spindle machines may publish several paths. Make sure monitoring uses the right one for running time.

Okuma-specific tips

• The app must start with the control. If MTConnect stops after a restart, check the application's startup settings.
• Windows updates on the control can affect the MTConnect application. Re-test after updates.
• Control PC firewall. The control's Windows firewall may need to allow the agent's port.
• Multi-path machines. Confirm which path is used for running time and part counts.

Questions to send your Okuma distributor

Copy this into an email for each machine, with the serial number:

1. Which OSP control and software version does this machine have?
2. Is an MTConnect application installed, and is it licensed and enabled?
3. If not, which package do you recommend, and what does it cost to install?
4. Which port does the agent use, and does it start automatically with the control?
5. Which data items are published — execution, program, part count, mode, alarms?
6. Are there any Windows firewall or network settings we need on the control?

The answers turn a vague "does it support MTConnect?" into a clear plan, and you can keep them with your machine records for the next time someone asks.

A two-machine pilot plan for Okuma shops

1. Pick two machines — ideally your bottleneck and one typical machine.
2. Confirm MTConnect on both using the steps above.
3. Connect them to monitoring and leave them running for a week.
4. Compare with the floor. Ask the operators whether the timeline matches what they remember — long setups, waiting for material, tool changes.
5. Review the first week. Look at utilization by shift, the longest stops, and how often the machines sat idle between jobs.
6. Decide on expansion based on what you learned, not on a sales pitch.

Two machines is enough to prove whether the data is accurate and whether your team will actually use it.

Okuma machines in a mixed shop

Many shops run Okuma lathes next to machining centers from other builders. Because MTConnect describes every machine the same way, an Okuma lathe and a FANUC-controlled mill can show the same status colors, the same utilization math, and the same shift reports. That makes it fair to compare machines and to see where work is piling up — something that is hard to do when each brand has its own separate software.

Monitoring Okuma machines with FEAI

FEAI Machine Monitor reads Okuma machines that publish MTConnect and shows live status, timelines, utilization, OEE, downtime, and shift reports — side by side with Mazak, Haas, and FANUC-controlled machines.

It is a read-only client running on a Windows PC on your network, with data stored locally. It does not install applications on Okuma controls.

Okuma machine answering on MTConnect? Start free — 2 machines.