Controller · Okuma
Connect Okuma OSP-P200, OSP-P100-II and older OSP
OSP 200 and OSP 100-II support MTConnect after a THINC API update from the Okuma dealer; other OSP 100 controls do not and are connected through discrete I/O (integrator guidance).
At a glance
| MTConnect | Yes after THINC API update (P200, P100-II) |
|---|---|
| Other OSP 100 | Not supported; use I/O |
Connection paths
MTConnectRecommended
After the dealer's THINC API update.
Discrete I/OFallback
Licences and options
| Item | Option / part number | Paid? | Note |
|---|---|---|---|
| THINC API update | Dealer | Free per Okuma | |
| Okuma MTConnect Agent | MyOkuma | Free |
Software versions
- OSP 200 and OSP 100-II need a THINC API update first
Data you can read
- As P300 once MTConnect runs
Setting it up
- Call the dealerRequest the THINC API update.
- Install the agentFrom MyOkuma.
- Enable monitoring tags
Connectors that support this control
| Product | Vendor | Type | Outputs |
|---|---|---|---|
| MTConnect cppagent | MTConnect Institute (Apache-2.0) | Open source | MTConnect REST, MQTT |
| Predator MDC | Predator Software | Monitoring software | SQL / MES / ERP |
| MachineMetrics Edge | MachineMetrics | Monitoring software | Cloud |
Sources
Facts on this page come from these documents, opened on 27 October 2026.
Last verified 27 October 2026 against vendor documentation. OPC UA Connect is an educational resource published by TEEPTRAK; it is not affiliated with the OPC Foundation, the MTConnect Institute or any control maker.