Describe the machine
Choose the machine manufacturer, model, controller series, production year and required data points.
- Main
- Connection
Check if you can collect data from your machines
Machine connectivity checker
Can I connect this machine?
Get the exact answer.
Select the machine, CNC and required data. MDCplus will identify the protocol, connection architecture and monitoring scope before you start a pilot.
✓No installation for the first check ✓Read-only connection ✓Controller-specific result
Step 1 of 1
Check machine compatibility
Connection supported Standard MDCplus architecture is available.
Recommended protocolFANUC FOCAS 2
Connection methodEthernet to local MDCplus edge connector
Estimated complexityStandard
Monitoring scopeStatus, program, alarms, counters, overrides and loads
From model to live data
Know the connection path before the project starts
The checker translates machine and controller data into a practical integration route. You get the protocol, network requirements, available signals and the next action.
Get the technical route
See the recommended protocol, connection type, supported signals and likely integration complexity.
Move to live monitoring
Choose the protocol library or a complete connection service with commissioning and monitoring setup.
Connected to MDCplus
From raw controller signals to production monitoring
A successful connection is not the finish line. MDCplus normalizes machine data and turns it into a live production view for operators, engineers and managers.
Real-time machine statesProcessing, idle, setup, alarm, maintenance and offline states.
Unified data modelDifferent CNC and PLC sources are converted into one production data structure.
Production analyticsOEE, utilization, downtime, cycle time, plan completion and maintenance signals.
Shop Floor OverviewLine 1 - Shift A
● LIVE
OEE78.4%+4.2%
Utilization84.1%+2.8%
Plan92%On track
Downtime31m-12m
DMG MORI CTX 310PROCESSING
GROB G550IDLE
MAZAK VARIAXISPROCESSING
Legacy turning centerALARM
Illustrative dashboard with sample data.
Controller and protocol coverage
Modern CNC, PLC and legacy equipment
The final connection method depends on the exact controller version, installed options and available interfaces. The checker narrows that route before an engineering review.
FFANUC FOCAS
SSiemens Sinumerik
HHEIDENHAIN
OOPC UA
MMTConnect
PPLC and legacy
Connection route by controller
| Controller | Recommended protocol | Connection method | Complexity | Monitoring scope | What to confirm |
|---|---|---|---|---|---|
| FANUC 0i / 30i / 31i / 32i | FANUC FOCAS 2 | Ethernet to local MDCplus edge connector | Standard | Status, program, alarms, parts count, overrides, spindle and feed data | A standard MDCplus connection route is available. |
| Siemens Sinumerik 840D / ONE | Sinumerik OPC UA or native CNC interface | Industrial Ethernet to MDCplus edge connector | Standard to extended | Status, program, alarms, axis and spindle data, counters and variables | Controller options must be confirmed before commissioning. |
| HEIDENHAIN TNC 320 / 640 | HEIDENHAIN LSV2 / DNC | Ethernet through a local connector | Standard to extended | Status, current program, alarms, execution data and machine variables | The exact route depends on TNC generation and enabled DNC options. |
| Mazatrol Smooth / Matrix | Mazatrol native interface, MTConnect or PLC route | Ethernet or PLC-based data collection | Engineering review | Machine status, program, alarms, counters and selected process values | Controller generation and installed communication options need verification. |
| Okuma OSP | Okuma OSP interface or MTConnect | Ethernet to MDCplus edge connector | Engineering review | Status, program, alarms, counters and selected CNC variables | OSP version and API availability need verification. |
| Haas NGC / Classic | MTConnect or Haas data interface | Ethernet to MDCplus edge connector | Standard | Status, active program, alarms, spindle, feed and parts count | NGC machines usually provide a direct Ethernet route. |
| PLC / legacy machine | OPC UA, Modbus TCP, S7, discrete I/O or external sensors | PLC or industrial gateway to MDCplus edge connector | Extended | Machine state, cycle, alarms, counters, energy and selected process signals | Legacy equipment can be connected through PLC, signals or additional sensors. |
| Other controller | To be identified after controller review | Direct CNC, PLC or gateway-based architecture | Survey required | Depends on controller interfaces and available machine signals | The machine may still be connectable through a native protocol, PLC or gateway. |
Questions about connecting machines
Frequently asked questions
Short answers about protocols, legacy equipment and what the checker does with your data.
Can I connect my CNC machine to MDCplus?
It depends on the controller, its version and the installed options. The checker marks FANUC, Siemens Sinumerik, HEIDENHAIN and Haas as supported, Mazatrol and Okuma as likely supported once the version and options are verified, and legacy equipment as connectable through a PLC, signals or additional sensors.
Which controllers and protocols does the checker cover?
FANUC (FOCAS 2), Siemens Sinumerik (OPC UA or the native CNC interface), HEIDENHAIN (LSV2 / DNC), Mazatrol (native interface, MTConnect or a PLC route), Okuma OSP (OSP interface or MTConnect), Haas (MTConnect or the Haas data interface), and PLC or legacy machines (OPC UA, Modbus TCP, S7, discrete I/O or external sensors).
Can old or legacy machines be connected?
Yes, a route is available. Legacy equipment can be connected through a PLC, machine signals or additional sensors. The checker rates this route as extended complexity.
Is the connection read-only?
Yes. All connection routes shown in the checker are read-only.
Do I need to install anything for the first check?
No. The first check needs no installation, and no equipment data is transmitted during it.
What machine data can be monitored?
It depends on the controller and the installed options. The scope can include status, current program, alarms, counters such as parts count, and selected values such as overrides, spindle and feed data and loads. The result of the checker lists the scope for your controller.
What if my controller is not on the list?
Choose Other controller. The checker then returns an engineering check: the machine may still be connectable through a native protocol, a PLC or a gateway, and the protocol is identified after a controller review.
How does the machine data reach MDCplus, and can it run on premise or in the cloud?
Machines connect over Ethernet, or through a PLC or industrial gateway, to a local MDCplus edge connector. MDCplus converts data from different CNC and PLC sources into one production data structure, and is available on premise and in the cloud.
What happens after the check?
You can use the MDCplus protocol library in your own product, or MDCplus engineers can connect the equipment and launch live production monitoring.
Choose the next step
Get the protocol or connect the machine end to end
Use the MDCplus protocol library in your own product, or let our engineers connect the equipment and launch live production monitoring.
