Okuma machines with OSP-P controls are MTConnect-ready out of the box. Unlike most other CNC brands, the Okuma control runs a full Windows operating system internally, which means the MTConnect Adapter and Agent both live on the machine itself. Setup is largely a software configuration task rather than a hardware one. This guide walks through verifying compatibility, configuring the adapter and monitoring tags, and confirming the XML data stream is accessible on your network.

Note: Okuma is the only major CNC manufacturer that builds the machine, control, drives, motors, encoders, and spindle in-house. Their open-architecture THINC platform is what makes native MTConnect support possible.

Before jumping into configuration, it helps to understand the three software components involved. All three run inside the Okuma control on its embedded Windows PC.

Figure 1: MTConnect architecture on an Okuma OSP-P control

THINC API: This is Okuma’s proprietary interface layer. It sits between the CNC system and any application that wants to read machine data. The MTConnect Adapter pulls data from the THINC API.

MTConnect Adapter: Reads machine data from the THINC API and converts it into the MTConnect format. It communicates with the Agent internally on port 7878.

MTConnect Agent: An HTTP server that makes the machine data available as an XML stream on port 5000. This is what your monitoring software connects to over the network.

The key takeaway is that monitoring software never talks directly to the CNC. It reads from the Agent via a standard HTTP request, which returns XML data that any MTConnect-compatible application can parse.

Not every Okuma control supports MTConnect. It is limited to the OSP-P family, and even within that family, some older models need updates before MTConnect will work.

Figure 2: OSP-P control compatibility with MTConnect

The control model is displayed on the Okuma screen during startup (e.g., OSP-P300A). You can also find it in the system information screen under the SYSTEM menu on the control.

Even on a compatible control, the THINC API version matters. MTConnect requires:

Note: THINC API updates must be performed by an Okuma dealer. You cannot update the API yourself. Contact your dealer to check your current version and arrange an update if needed.

Okuma also provides a tool called SCOUT on MyOkuma.com that can check your exact machine’s compatibility and tell you which adapter version to install.

Since the Okuma control runs Windows internally, all MTConnect configuration happens through the Windows interface rather than the CNC screen. You need to get to the Windows desktop to proceed.

Figure 3: How to access the Windows backend on an Okuma control

Press CTRL + /// (the three-slash key on the Okuma operator panel) to bring up the Windows Start menu. From here you can access File Explorer, the Programs menu, and all standard Windows functions.

When the machine is powered on, the NC software launches automatically. To stay in Windows mode instead:

Note: You should be in Windows mode (NC not running) when installing or updating the MTConnect Adapter software. The NC and the installer cannot run at the same time.

On newer P300 machines, the MTConnect Adapter and Agent are often pre-installed. On P200 and P100 Type II machines, you will likely need to install them yourself.

Look for the Okuma MTConnect icon in the Windows system tray (bottom-left corner of the screen). You may need to hold CTRL and press a button to show the taskbar, then click the left-facing arrows to expand hidden icons. If you see the Okuma icon, the adapter is installed and running.

If the adapter is not installed:

Note: The installer will reject the setup if the THINC API version on the machine is too old. If this happens, you need to contact your Okuma dealer to update the THINC API first.

The installer registers the MTConnect Adapter with the THINC Startup Service so it launches automatically after the NC system boots. If for some reason it does not start automatically, you can configure it manually:

Once the adapter is running, you need to configure two things: the connection settings and the monitoring tags. The monitoring tags step is the one most people miss, and it is the most common reason for data showing as UNAVAILABLE.

Figure 4: The MTConnect Adapter configuration window

Verify the following settings on the Configurations screen:

This is the critical step. Click the Tags Configuration button (or TAGS CONFIG soft key) at the bottom of the configuration screen.

Figure 5: Recommended monitoring tags to enable

Note: If you just installed the adapter and no other applications are using it yet, it is safe to press UNCHECK ALL first, then enable only the tags listed above. You can always add more later.

The Okuma control has a standard Windows network stack. The IP address is configured through Windows Network Connections, not through the CNC interface.

Figure 6: Network setup between the Okuma control and monitoring PC

Note: Coordinate with your IT department for an available IP address. The Okuma control and your monitoring PC must be on the same subnet to communicate.

The MTConnect Agent serves data on port 5000 via HTTP. If the Windows Firewall is active on the control (common on newer machines running Windows 7 or 10), you may need to add an inbound rule:

Once the adapter is configured and the network is set up, verify that the XML data stream is accessible.

Open a web browser on the control (Internet Explorer is typically available) and navigate to:

http://localhost:5000/current

If the page loads and shows XML data with actual values (not UNAVAILABLE), the adapter and agent are working correctly.

On a PC connected to the same network, open a browser and navigate to:

http://192.168.1.50:5000/current

Replace the IP with your Okuma control’s actual address. You should see an XML response like this:

Figure 7: XML data stream from the MTConnect Agent viewed in a browser

If all values show UNAVAILABLE, the agent is running but the adapter is not feeding data. See the troubleshooting section below.

Figure 8: Troubleshooting flow when data shows as UNAVAILABLE

Once your Okuma machine is serving MTConnect data on port 5000, connecting it to Glassdome is straightforward. Glassdome reads the MTConnect XML stream directly and automatically maps the data items to your production dashboards.

The data available through MTConnect on Okuma includes execution state, spindle speed, feed rate, spindle load, active program, alarms, part counts, and common variables. This means Glassdome can provide real-time visibility into machine utilization, cycle times, downtime reasons, and production counts without any additional hardware or sensors.

Learn more: Visit glassdome.com to see how Glassdome integrates with Okuma and other CNC brands for complete shop floor monitoring.

Configuring MTConnect on an Okuma OSP-P control comes down to three things: making sure the adapter is installed, enabling the monitoring tags, and confirming port 5000 is accessible on your network. The architecture is simpler than most CNC brands because everything runs on the Windows PC inside the control. There is no external hardware to install and no special CNC-side configuration needed beyond the adapter software itself.

The most common issue by far is forgetting to enable the monitoring tags after installation. If you see UNAVAILABLE for all data items, that is almost always the reason. Open the adapter configuration, check the Enable Monitoring Tags box, select the tags you need, save, and the data should start flowing immediately.