How to Set Up MTConnect on an Okuma OSP

Unlike a Haas, an Okuma doesn’t ship with the MTConnect agent already running. The OSP control is a Windows PC under the hood, so you add MTConnect by installing Okuma’s own free app from the Okuma App Store. Once it’s installed and the control is on the network, that app publishes run state, program, spindle and feed, and part count as MTConnect data. Spall reads it and turns it into availability, downtime with reasons, and OEE. Nothing is written back to the control.

Before you start You need an Okuma OSP-P200 or P300 control, the free MTConnect Agent & Adapter app from the Okuma App Store (Adapter 2.5.0.0 or later), and THINC API 1.18 or later on the control. You’ll also need an Ethernet drop, a fixed IP from your network person, and the Spall gateway on the same network. The gateway reads only. It never writes to the control.

1. Install the Okuma MTConnect app

Get the MTConnect Agent & Adapter app from the Okuma App Store and install it on the OSP control. It bundles both pieces MTConnect needs: the adapter (reads the machine through Okuma’s THINC API) and the agent (serves that data on the network). Make sure the control has THINC API 1.18+, the app needs it to read the machine.

2. Put the OSP control on the network

Because the OSP is Windows-based, it gets its IP the Windows way. Give it a static IP (or a DHCP reservation) in the same range as the Spall gateway so the address never moves. Write it down for the next steps.

3. Confirm the agent is answering

The agent serves MTConnect on port 5000. Check it two ways. First, on the control itself, open a browser to the local address:

# from the OSP control
http://localhost:5000

Then from any PC on the same network, hit the control’s IP with the standard MTConnect endpoints:

# device definition
http://10.0.0.8:5000/probe

# live values right now
http://10.0.0.8:5000/current

If you see XML, the machine is ready. If localhost:5000 works on the control but the IP doesn’t from another PC, it’s the network or firewall (next step), not the app.

4. Open the port on your firewall

The Okuma agent uses TCP port 5000. If a network PC couldn’t reach the XML, ask IT to allow that port between the OSP control and the Spall gateway.

5. Point Spall at the machine

In Spall, add the machine, choose MTConnect as the source, and enter the control address with the port:

10.0.0.8:5000

Assign the Spall gateway and save. Run state, program, and part count start populating within seconds. Run a cycle and watch the state flip to ACTIVE.

Next: make the count right Out of the box the part count over MTConnect may not match the parts you actually make, especially on multi-part cycles. The Okuma way to fix that is a common variable you increment in the program and map in the MTConnect app. That’s its own short guide: How to Set Up Part Counts on an Okuma OSP.

What Spall does with this data

Availability. Spall splits every hour into running, idle, and down straight from the OSP run state. No clipboards, no guesswork, just true availability.

Downtime and reasons. Each stop is caught the instant it happens. Operators tag the reason, and Spall ranks them into a Pareto so you attack the biggest loss first.

Production. With the common-variable count set up, Spall reads real part count over MTConnect for target-vs-actual by shift and job.

Quality and OEE. Availability, performance, and quality roll into one OEE view, each loss ranked in dollars so the number points at an action instead of a score.

One thing worth repeating Spall reads. It never writes. The gateway pulls MTConnect data on your network and sends it outbound over encrypted MQTT. There’s no inbound port opened on your firewall for machine data, no VPN, and no changes to your programs or the control. Worst case if it can’t reach the machine is a gap in the chart. The spindle keeps running.

Quick recap

• Install the Okuma MTConnect app (THINC API 1.18+)
• Set a static IP on the OSP
• Verify localhost:5000 then ip:5000/current
• Open TCP 5000
• Add the machine in Spall

That’s the Okuma on one screen in Spall. Repeat per machine, or hand us the addresses and we’ll bring them on together.