Mitsubishi CNC machine monitoring, over MTConnect
Mitsubishi Electric publishes its own MTConnect path for its CNC line — the NC Machine Tool Connector, documented in Mitsubishi's own user manual. ThingConnect reads it the same read-only way it reads every MTConnect source.
The NC Machine Tool Connector
Mitsubishi Electric documents its MTConnect path in an official manual — the "NC Machine Tool Connector User's Manual" (doc IB1501634) — describing a software package that captures data from the NC control and hands it to an MTConnect agent, which formats it per the open standard. It's Mitsubishi's own published software for its own CNC line, the same relationship Haas and Okuma have to their respective adapters, not a reverse-engineered third-party tool.
Per that same manual, it's explicitly read-only: the connector captures data outward, with no documented path for a client to change programs, parameters, or machine state through it.
Which Mitsubishi controls it covers
| Control series | Notes |
|---|---|
| M700 / M70 | Covered per Mitsubishi's official NC Machine Tool Connector manual. |
| M700V / M70V / E70 | Covered per the same manual — the V/E designations are Mitsubishi's control-generation variants. |
| M800 / M80 / E80 (incl. M800V) | The current generation covered by the connector. |
Exact data-item coverage — which specific signals the agent publishes per control — is confirmed machine by machine during the fleet survey, the same as every other brand on this site.
The honest gap: OPC UA on the CNC side
We could not verify native OPC UA support on Mitsubishi's CNC controllers from official documentation, so that claim doesn't appear on this page. Mitsubishi Electric's broader e-F@ctory ecosystem covers OPC UA thoroughly — but on the PLC and factory-automation side of the business, a different product line from the M700/M800 CNC series this page is about. Where documentation is ambiguous or where a brand's marketing blends product lines, our standard is to say what we could confirm and stay silent on the rest, rather than assume the capability carries over.
Questions
Frequently asked questions
Yes — the NC Machine Tool Connector, documented in Mitsubishi's own "NC Machine Tool Connector User's Manual" (doc IB1501634). It's Mitsubishi-published software, not a third-party bridge, covering the M700/M70, M700V/M70V/E70, and M800/M80/E80 (including M800V) CNC series.
Yes. Mitsubishi's documentation describes it as read-only by design — it captures NC data and hands it to an MTConnect agent for formatting, with no path back to the control to change programs or parameters.
We could not confirm this from Mitsubishi's own official documentation, so we're not claiming it. Mitsubishi Electric's e-F@ctory initiative covers OPC UA extensively on the PLC and factory-automation side of its business, which is easy to conflate with CNC-side support — but that's a different product line from the CNC controllers this page covers, and we hold the line at what we could actually verify for the CNC.
Yes. MTConnect has no command channel in the standard at all — a client can only read the data an agent publishes, never write to the machine. ThingConnect's gateway reads it the same way it reads every MTConnect source, with machines never touching the internet directly.