Okuma OSP-P machine monitoring, over Okuma's own adapter
Okuma's OSP-P controls run a full Windows PC internally, and Okuma publishes its own MTConnect adapter for it through the OSP App Store. Newer controls add a factory OPC UA server on top. ThingConnect reads either path the same read-only way it reads everything else.
Why OSP-P connectivity looks different
Okuma's OSP-P control is architecturally unusual among CNCs: it runs on a full Windows operating system, with the control application itself as one program among others on that PC. That's why Okuma can publish an MTConnect adapter and agent as ordinary Windows software rather than shipping it as embedded controller firmware — both pieces run on the machine's own computer, reading from Okuma's THINC API.
MTConnect: Okuma's App Store adapter
Okuma distributes the MTConnect adapter free through the OSP App Store (apps.okuma.com) — an operator or integrator logs in with an Okuma account and downloads the installer matched to the control's OSP version (P300 or P500 builds are separate downloads). Once installed:
| Component | What it does |
|---|---|
| MTConnect Adapter | Reads machine data from the THINC API and converts it to MTConnect's format. |
| Internal link | Adapter feeds the Agent locally on the machine's own PC. |
| MTConnect Agent | Serves the resulting XML data stream over HTTP for any client, including ThingConnect's gateway, to read. |
Newer controls: a factory OPC UA server too
On the current OSP-P500M and OSP-P700A controls, Okuma adds a factory-installed OPC UA server built to the OPC Foundation's standard CNC information model — the same kind of companion specification behind umati-aligned machine-tool servers elsewhere. That's a genuinely separate, newer connection path — it doesn't replace the MTConnect adapter, and across the wider installed base of OSP-P controls, MTConnect via the App Store remains the one path we can confirm broadly.
Our approach:during the fleet survey, we check which OSP-P version each machine is running and confirm whether the MTConnect adapter is installed (it isn't automatic — it has to be downloaded and set up) and whether a newer control's OPC UA server is active, rather than assuming either from the model number alone.
Questions
Frequently asked questions
If it runs an OSP-P control — P200, P300, or newer — yes, using Okuma's own MTConnect adapter, downloaded free from the Okuma App Store for your specific OSP version. It isn't built into the control out of the box the way Haas NGC's agent is, but it's a Okuma-published, Okuma-supported download rather than a third-party bridge.
Because the OSP control runs a full Windows operating system internally, not an embedded real-time OS alone — so the MTConnect adapter and agent can both live on the machine's own PC, reading from Okuma's THINC API directly, rather than needing an external box the way some other brands require.
The newer OSP-P500M and OSP-P700A controls add a factory-installed OPC UA server built to the OPC Foundation's standard CNC information model — a genuine second connection path, not a replacement for MTConnect. Across the wider OSP-P line, MTConnect via the App Store adapter is the one confirmed path; OPC UA is newer-generation-only.
Yes — both are read-only by design for this use. MTConnect has no command channel at all, and an OPC UA monitoring subscription reads the address space without writing back. Machines connect outbound to a gateway inside your firewall; they never reach the internet directly.