MTConnect Connectivity

Overview

Jump to: What is MTConnect? · Why MTConnect is Preferred · Who This Guide is For

What is MTConnect?

MTConnect is an open-source, royalty-free standard for collecting data from manufacturing equipment. Developed and maintained by the MTConnect Institute, this standard enables manufacturing equipment to provide data in structured XML format rather than proprietary formats.

MTConnect is one of the most commonly encountered standards that MachineMetrics uses to connect to machines worldwide.

Key Characteristics:

• Open and standardized protocol
• XML-based data format
• Industry-wide adoption
• No licensing fees
• Supported by major machine tool builders

Why MTConnect is Preferred

When a machine supports MTConnect, it's typically the preferred connectivity method because:

1. Standardized: Consistent data format across different manufacturers
2. Rich Data Set: Comprehensive machine status, alarms, programs, and production metrics
3. Simple Setup: Often requires only network configuration
4. No Additional Hardware: No serial converters or I/O modules typically needed
5. Fast Deployment: Can usually connect in 20-45 minutes
6. Industry Support: Continuously evolving with industry needs

Who This Guide is For

This guide is for:

• Manufacturing engineers connecting MTConnect-capable equipment
• IT personnel configuring network access for machines
• Maintenance staff enabling MTConnect on controls
• Quality engineers connecting CMM equipment
• Anyone responsible for machines with MTConnect capability

---

Machine Setup Guides

How MTConnect is enabled varies by manufacturer — some controls ship with an agent, others need one installed. Each guide below covers a vendor end to end: checking for an existing installation, enabling the agent, configuration, and vendor-specific troubleshooting.

Machine / Control	Setup guide
Mazak (only if MTConnect is already installed)	Mazak
Okuma, including OSP-P500	Okuma
Hexagon coordinate measuring machines	Hexagon CMM
Zeiss coordinate measuring machines	Zeiss CMM
Hurco	Hurco
3D Systems DMP 350 Flex	3D Systems DMP 350 Flex

Machines not listed here can still connect if they expose an MTConnect agent — see Other MTConnect Machines for the general approach.

---

Compatible Machines

Jump to: Machine Tool Brands · Control Systems · CMM Equipment

Machine Tool Brands

Many well-known machine tool brands now include MTConnect as a standard or optional feature:

Common MTConnect-Enabled Brands:

• DMG MORI - Various controls
• Haas - Next Gen controls (port 8082)
• Hexagon - CMM and metrology systems
• Hurco - WinMax 10.4.0+ (mill) or 11.3.4+ (lathe)
• Kitamura - Arumatik-Mi via AnyWhere Remote; Arumatik-Jr via the Mitsubishi IMA adapter (see Kitamura Connectivity)
• Mazak - Preview G, SmoothEZ, and Smart controls (other Mazak controls use Fusion Client)
• Okuma - OSP-P500, OSP 300, OSP 200, OSP 100-II
• Sodick - EDM and grinding machines
• Zeiss - CMM and metrology systems
• Many others - Check with your machine manufacturer

Control Systems

Mazak Controls (MTConnect only):

• Preview G, SmoothEZ, and Smart controls require MTConnect
• Other Mazak controls (Matrix, Nexus, Smooth including SmoothG, Preview 3, Fusion 640) use Mazak Fusion Client instead
• See Mazak over MTConnect for supported control models

Okuma Controls:

• OSP-P500 (newer control, see OSP-P500 Setup)
• OSP 300 (best support)
• OSP 200 (requires THINC API update)
• OSP 100-II (requires THINC API update)
• Other OSP 100 controls: NOT supported

Hurco Controls:

• WinMax 10.4.0 or later (mills) - MTConnect included
• WinMax 11.3.4 or later (lathes) - MTConnect included
• Older WinMax versions - Requires Ultimonitor option
• Uses MTConnect version 1.3 schema
• Port 5000 (default)

Others:

• Varies by manufacturer
• Check machine documentation
• Contact MachineMetrics for verification

CMM Equipment

Hexagon CMMs:

• Metrology Connector V7.1 or higher (download from Hexagon Nexus)
• MTConnect Agent — open-source cppagent (GitHub)
• Advanced entitlement of Metrology Asset Manager (via Nexus account); Local Advanced entitlement supported for non-internet environments
• PC-DMIS (optional — only required for program name/cycle data)

Zeiss CMMs:

• CALYPSO 7.2 or newer
• PiWeb 8.x or newer
• Requires MTConnect Data Interface license

Other CMMs:

• Contact CMM manufacturer for MTConnect support
• May require software updates or licenses

---

Prerequisites

Before connecting your MTConnect machine, ensure you have:

Hardware:

• Machine with MTConnect capability (verified)
• MachineMetrics Edge device (deployed and activated)
• Ethernet cable (CAT5/CAT6)
• Network access between machine and Edge device

Network:

• IP address for the machine
• Knowledge of MTConnect agent port (typically 5000, or 8082 for Haas)
• Firewall access for MTConnect agent port
• Ability to test connectivity (ping, browser)

Access:

• Physical access to machine control
• Permission to enable MTConnect (if not already enabled)
• Administrative access to Windows backend (for Mazak, Okuma)

Information:

• Machine make, model, and control type
• Control software version
• Current network configuration

For CMMs:

• MTConnect license (Hexagon or Zeiss)
• CMM software version
• Administrator permissions on CMM PC

---

How MTConnect Works

Jump to: Architecture · Data Flow · Ports and Endpoints

Architecture

MTConnect uses a client-server architecture:

Machine Control
     ↓
MTConnect Adapter (converts machine data to SHDR format)
     ↓
MTConnect Agent (serves XML data via HTTP)
     ↓
MachineMetrics Edge Device (ingests and processes data)
     ↓
MachineMetrics Cloud

Components:

• Adapter: Translates machine-specific data to SHDR (Simple Hierarchical Data Representation)
• Agent: HTTP server that provides XML data streams
• Client: MachineMetrics Edge device that consumes the data

Data Flow

1. Machine control generates operational data
2. MTConnect Adapter reads this data
3. Adapter converts data to SHDR format
4. Agent receives SHDR and converts to XML
5. Edge device polls the Agent's HTTP endpoint
6. Edge processes and sends data to MachineMetrics Cloud

Ports and Endpoints

Common MTConnect Ports:

• 5000: Agent port (most common default)
• 7878: Adapter port (Mazak and some others)
• 8082: Agent port (Haas Next Gen)
• Custom: Some implementations use different ports

Note: MTConnect uses two types of ports:

• Agent ports (e.g., 5000, 8082) - External HTTP endpoint for data collection - Test with web browser
• Adapter ports (e.g., 7878) - Internal connection between adapter and agent - Test with telnet

Testing Adapter Ports:

To test if an adapter is running on port 7878, use telnet (not a web browser):

telnet <machine-ip> 7878

Example:

telnet 192.168.1.100 7878

If the adapter is running, you should see streaming data. If it doesn't connect, the adapter service is not running.

Common Endpoints:

• /probe - Returns agent configuration and available data items
• /current - Returns current values for all data items
• /sample - Returns historical time-series data
• /assets - Returns asset information (tools, fixtures, etc.)

Example URLs:

• http://192.168.1.100:5000/probe
• http://192.168.1.100:5000/current
• http://192.168.1.100:8082/sample (Haas)

---

Verifying MTConnect Support

Jump to: Quick Test Method · Control-Specific Checks

Quick Test Method

Follow these steps to check if your machine produces MTConnect data:

Step 1: Ensure Network Connection

1. Connect machine to network via Ethernet
2. Configure static IP address on machine
3. Note the IP address (e.g., 192.168.1.100)

Step 2: Test Connectivity

1. From a computer on the same network
2. Open Command Prompt or Terminal
3. Ping the machine: ping 192.168.1.100
4. Verify you receive replies

Step 3: Test MTConnect Endpoint

1. Open a web browser
2. Try these URLs (replace IP with your machine's IP):
   • http://192.168.1.100:5000
   • http://192.168.1.100:8082 (Haas only)
3. Add /current to the URL for current data
4. If you see XML data, MTConnect is working!

Step 4: Verify on Control (Windows-Based)

For machines with Windows backend (Mazak, Okuma):

1. Access Windows backend on the machine control
2. Open browser on the control
3. Navigate to http://127.0.0.1:5000 or http://127.0.0.1:7878
4. Or try http://localhost:5000/current
5. If data appears here but not from external PC: firewall issue

What Success Looks Like:

You should see XML output similar to:

<?xml version="1.0" encoding="UTF-8"?>
<MTConnectStreams ...>
  <DeviceStream name="Machine1">
    <ComponentStream component="Controller">
      <Samples>
        <Execution>READY</Execution>
        ...

If No Data Appears:

• MTConnect may not be enabled
• Port may be different
• Firewall may be blocking access
• Software upgrade may be needed

Control-Specific Checks

For Mazak:

1. Access Windows backend (click Start button)
2. Search for "MTConnect"
3. Look for MTConnect folder with associated files
4. If found: MTConnect is installed
5. If not found: Contact Mazak for installation files

For Okuma:

1. Access Windows backend (press CTRL + ///)
2. Use Scout tool at MyOkuma.com to check compatibility
3. Navigate to Programs → Okuma → MTConnect
4. If present: MTConnect is installed
5. Check THINC API version (may need update)

For Hexagon CMMs:

• Confirm Metrology Connector V7.1+ is installed on the CMM control PC
• Verify the Advanced entitlement of Metrology Asset Manager is active in your Nexus account
• Confirm the MTConnect Agent (cppagent) is running and listening on port 5001

---

Physical Connection

Jump to: Network Setup · Wired vs Wireless

Network Setup

Step 1: Connect Ethernet Cable

• Plug cable into machine's Ethernet port
• For Mazak: Port typically patched from HMI to electrical cabinet
• For Okuma: Port on control panel or in cabinet
• For CMMs: Network port on CMM PC

Step 2: Configure IP Address

Static IP (Recommended):

• Access network settings on machine or control PC
• Set static IP address
• Example: 192.168.1.100
• Subnet: 255.255.255.0
• Gateway: 192.168.1.1 (if needed)

⚠️ For Mazak:

• Configure "PC IP Address" (Windows Ethernet settings)
• DO NOT change the "NC IP Address" - this is for internal machine control communication

For Okuma:

• Press CTRL + /// to access Windows
• Configure Ethernet adapter settings
• Set static IP

For CMMs:

• Standard Windows network configuration
• Use static IP for reliability

Step 3: Verify Network Access

• Ensure machine IP and Edge device are on same subnet
• Test with ping from Edge device or computer
• Verify firewall allows MTConnect port

Wired vs Wireless

Wired Connection (Typical):

• Direct Ethernet cable from network to machine
• Most reliable for MTConnect
• Lower latency
• Preferred for production environments

Wireless Connection:

• Edge device with WiFi in machine cabinet
• Edge connects via Ethernet to machine
• Edge communicates to cloud via WiFi
• Useful when cabling is impractical

---

Enabling MTConnect

Generic MTConnect Setup

For machines that already have MTConnect installed:

Step 1: Locate MTConnect Service

• Access Windows backend on control
• Search for MTConnect application or service
• Common locations:
  • Start Menu → Programs → MTConnect
  • Windows Services → "MTConnect Agent" or similar

Step 2: Verify Service is Running

• Open Services (services.msc)
• Find MTConnect service
• Status should be "Running"
• If not running: Right-click → Start

Step 3: Configure Network Port

• Open MTConnect configuration utility
• Verify HTTP port (typically 5000 or 7878)
• Ensure port is not blocked by firewall

Step 4: Test Locally

• On the machine control, open browser
• Navigate to http://localhost:5000/current (or your port)
• Verify XML data appears

Step 5: Test Externally

• From another computer on network
• Navigate to http://[machine-ip]:5000/current
• If this fails but local test works: firewall issue

---

Adding the Machine in MachineMetrics

Once MTConnect is enabled and verified:

Step 1: Log into MachineMetrics

• Navigate to Assets → Machines
• Click Add Machine

Step 2: Enter Machine Details

• Machine Name: Descriptive name (e.g., "Mazak-Mill-1")
• Make: Manufacturer (e.g., "Mazak", "Okuma")
• Model: Machine model
• Select Edge Device: Choose your Edge from dropdown

Step 3: Configure Adapter

• Adapter Type: Select MTConnect
• IP Address: Enter machine's IP address
• Port: Enter MTConnect agent port
  • 5000 (most common agent port)
  • 8082 (Haas agent port)
  • Note: 7878 is typically the adapter port, not the agent port
• Device Name: Leave blank unless multi-machine agent (see below)
• Click Test Connection

Step 4: Verify Connection

• Test should return "Connected" or success message
• If test fails:
  • Verify IP address is correct
  • Verify port is correct
  • Test endpoint in browser first
  • Check firewall settings
• Click Save when test succeeds

Step 5: Configure Data Collection

• Machine will appear in Machines list
• Initial data items collected automatically
• Configure part counting if needed
• Map additional data items as required

---

Configuring Data Collection

Jump to: Available Data Items · Part Counting · Multi-Machine Agents

Available Data Items

MTConnect provides rich data depending on machine implementation:

Status & Mode:

• Execution state (READY, ACTIVE, INTERRUPTED, STOPPED)
• Controller mode (AUTOMATIC, MANUAL, MDI, etc.)
• Emergency stop status
• Door state

Program Information:

• Program name
• Active block
• Line number

Production Metrics:

• Part count (varies by implementation)
• Cycle time
• Run time
• Idle time

Machine Parameters:

• Spindle speed (actual and override)
• Spindle load
• Feed rate (actual and override)
• Axis positions
• Axis loads

Alarms & Messages:

• Active alarms with codes
• Warning messages
• Operator messages

Tool Data (if available):

• Tool number
• Tool life
• Tool changes

Quality Data (CMMs):

• Measurement results
• Part program execution
• Inspection cycle data

Part Counting

Automatic Part Counting (Most Machines):

• MTConnect often provides part count automatically
• Counted based on program execution cycles
• No additional configuration needed
• Verify count is incrementing correctly in MachineMetrics

Manual Configuration (If Needed):

For Okuma (Common Variables):

If automatic counting doesn't work:

1. On Okuma Control:

   • Open MTConnect application
   • Navigate to "Device Configuration" page
   • Select common variable for part count (e.g., VC1)

2. In CNC Program:

   • Add common variable increment near end of program
   • Example: VC1=VC1+1 (increments by 1)
   • Example: VC1=VC1+2 (increments by 2 parts)

3. Notify MachineMetrics:

   • Contact support with variable number used
   • Configuration will be matched on our end

For Other Machines:

• Check MTConnect documentation for part count data item
• May be labeled "PartCount", "GoodCount", or similar
• Configure in MachineMetrics data mapping if not automatic

Multi-Machine Agents

Some MTConnect Agents report data for multiple machines over the same IP address and port.

Identifying Multi-Machine Setup:

• Browse to http://[IP]:[PORT]/probe
• Look for multiple <Device> entries in XML
• Each device will have a unique name

Configuration:

To collect data from a specific machine in a multi-machine agent:

1. In MachineMetrics, when adding the machine
2. Append device name to Connection Address
3. Format: [IP]:[PORT]/[DeviceName]
4. Example: 192.168.1.100:5000/Machine_1

In XML, look for:

<MTConnectDevices>
  <Devices>
    <Device name="Machine_1" ...>
    <Device name="Machine_2" ...>

Use the exact name from the XML, including underscores and capitalization.

---

Other MTConnect Machines

Generic Setup:

• Most MTConnect machines follow similar process
• Verify MTConnect is enabled
• Determine correct port (test with browser)
• Configure static IP
• Add to MachineMetrics using MTConnect adapter type

Common Ports:

• 5000 (most common agent port)
• 8082 (Haas agent port)
• Note: 7878 is typically an adapter port (internal)

If Unsure:

• Contact machine manufacturer
• Contact MachineMetrics support with machine details
• Test endpoint with browser first

---

Troubleshooting

Adapter vs. Agent: Testing Each One

MTConnect typically runs as two components, and either one can be the thing you're connecting to:

• Agent — port 5000 (or 8082 on Haas). The HTTP server that serves XML. Often runs on the control, but may run on a separate PC.
• Adapter — port 7878. Feeds raw data to the agent. Nine times out of ten the adapter is running directly on the control, even when the agent lives elsewhere — it is frequently the more reliable component to find on the machine itself.

Testing the Agent (ports 5000 / 8082) — Use a Browser

1. From a computer on the same network, navigate to http://<ip-address>:5000 (or http://<ip-address>:8082 for Haas).
2. Append /current to the URL to see live data.
3. If you see XML, the agent is up.

See demo.mtconnect.org/Mazak/current for an example of a healthy agent response.

Testing the Adapter (port 7878) — Use Telnet or PuTTY

The adapter does not serve a web page — a browser will not work here. Use either of the following:

Option 1: Telnet

telnet <ip-address> 7878

note

Telnet is disabled by default in Windows. Enable it under Control Panel → Programs and Features → Turn Windows features on or off → check Telnet Client.

Option 2: PuTTY

1. Download PuTTY from putty.org (no installation needed).
2. Set connection type to Raw.
3. Enter the machine IP address and port 7878.
4. Click Open.

If you can connect to port 7878, MTConnect is very likely installed. If you see machine data on either test, you are good to go.

---

Connection Issues

Problem: Machine won't connect or test connection fails

Diagnostic Steps:

1. Verify Physical Connection

   • Ethernet cable securely connected
   • Link lights on network port active
   • Cable not damaged

2. Test Network Connectivity

   • Ping machine IP from Edge device or computer
   • If ping fails: network/routing problem
   • If ping succeeds: MTConnect or firewall issue

3. Test MTConnect Endpoint

   • Open browser on computer
   • Navigate to http://[machine-ip]:[port]/current
   • Try different ports: 5000, 7878, 8082
   • If XML appears: MTConnect is working, check MachineMetrics configuration
   • If no response: MTConnect not running or wrong port

4. Check Firewall

   • Windows Firewall on control may block MTConnect port
   • Temporarily disable to test (be sure to re-enable)
   • Or add firewall rule for MTConnect port
   • Common ports to allow: 5000, 7878, 8082

5. Verify MTConnect Service

   • Access Services on machine control
   • Find MTConnect service
   • Verify Status = "Running"
   • If stopped: Start the service

No Data Appearing

Problem: Connection succeeds but no data in MachineMetrics

Solutions:

1. Wait for Initial Sync

   • Allow 5-10 minutes for first data
   • MTConnect polls periodically
   • Refresh browser/app

2. Check Machine Status

   • Verify machine is powered on
   • Machine may need to be in certain mode
   • Run a program to generate data

3. Verify Endpoint Returns Data

   • Browse to http://[machine-ip]:[port]/current
   • Ensure XML contains actual values
   • If XML is empty or has no values: MTConnect configuration issue on machine

4. Check Data Mapping

   • Assets → Machines → [Your Machine] → Data Mapping
   • Verify data items are mapped
   • Look for unmapped items

5. Request Edge Logs

   • Edge device logs are not viewable in the app
   • Contact MachineMetrics Support to have them pulled and checked for MTConnect errors

---

Network Problems

Problem: Can access MTConnect locally but not from network

Cause: Firewall blocking MTConnect port

See Also: Network Requirements Guide for Edge device network and firewall requirements.

Solutions:

1. Check Windows Firewall

   • On machine control, open Windows Firewall
   • Check if MTConnect port (5000, 7878) is blocked
   • Add inbound rule to allow port

2. Test from Control First

   • On machine, open browser
   • Go to http://localhost:5000/current
   • If this works but external access doesn't: firewall

3. Create Firewall Rule

   • Windows Firewall → Advanced Settings → Inbound Rules
   • New Rule → Port → TCP → Specific Port (5000 or 7878)
   • Allow the connection
   • Apply to all profiles

4. Network Routing

   • Verify machine and Edge are on same subnet
   • Or proper routing is configured
   • Check with IT team if needed

Missing or Unavailable Data Items

Sometimes a machine connects successfully and reports data, but a specific data item you expect is either absent from the stream or shows a value of UNAVAILABLE.

In MTConnect, the individual pieces of information a machine publishes are called data items (each is a DataItem in the agent's structure). A status of UNAVAILABLE means the data item exists in the machine's MTConnect structure — the control is advertising it — but the control is not populating it with an actual value.

info

MachineMetrics relies on the machine control vendor to output the data items they are supposed to. MachineMetrics reads what the control's MTConnect agent provides; it cannot create a value the control is not supplying.

What to do when a data item is missing or reports UNAVAILABLE:

1. Confirm the data item is genuinely expected for that machine and control — not all controls expose every data item.
2. Contact the machine tool builder or control manufacturer and ask:
   • Is this behavior expected for this machine and control version?
   • Do they have a standard data item list to check the machine against?
3. Ask whether an MTConnect software update from the builder or control vendor resolves the issue — this is the most common fix.

When a control advertises a data item but does not populate it, the fix is in the hands of the builder or control vendor and is outside MachineMetrics' control to resolve. Contact MachineMetrics Support if you need help identifying the affected data items or routing the issue to the right party.

---

Best Practices

Network Configuration:

• Use static IP addresses for all machines
• Document IP addresses and ports
• Keep machine IPs in dedicated range
• Example: 192.168.1.100-199 for machines

MTConnect Service:

• Set services to "Automatic" startup
• Monitor service health periodically
• Keep MTConnect software updated
• Request latest versions from machine manufacturer

Data Quality:

• Verify part counting works correctly
• Map all relevant data items
• Test data accuracy against machine display
• Review data regularly for anomalies

Maintenance:

• Check service status weekly
• Watch reporting status and buffer levels in Assets → Edge Devices → Edge Management
• Keep machine control software updated
• Document any configuration changes

For CMMs:

• Use static IPs
• Schedule service restarts weekly (Task Scheduler)
• Keep measurement software and MTConnect versions in sync
• Validate XML output against MTConnect schema

Documentation:

• Record machine IPs and ports
• Document MTConnect version installed
• Keep notes on any special configurations
• Maintain list of common variable usage (Okuma)

Security:

• MTConnect uses HTTP (not HTTPS)
• Use dedicated machine network
• Limit access to MTConnect ports
• Don't expose MTConnect to public internet

---

Additional Resources

MTConnect Institute:

• Official website: www.mtconnect.org
• Standards documentation
• Reference implementations
• Community forums

MTConnect GitHub:

• github.com/mtconnect
• Sample adapters for various machines
• Reference agent implementations
• Tools and utilities

Wikipedia:

• MTConnect Wikipedia Page
• Overview and history
• Industry adoption information

Articles:

• Modern Machine Shop - MTConnect Overview
• Control Design - MTConnect Guide

OEM Resources:

• MyOkuma MTConnect Page
• Hexagon MTConnect Setup Guide
• Zeiss CMM Observer

MachineMetrics Resources:

• Machine Connectivity Overview
• Quick Start Checklist

---

Getting Help

Jump to: Before Contacting Support · Contact Options

Before Contacting Support

Gather this information:

1. Machine Details

   • Make, model, serial number
   • Control type and version
   • MTConnect version (if known)

2. Network Configuration

   • Machine IP address
   • MTConnect port
   • Can you ping the machine?
   • Can you browse to MTConnect endpoint?

3. Test Results

   • Browser test result (XML output or error?)
   • Local test on control (if Windows-based)
   • Telnet test result (for Mazak)

4. Error Details

   • Exact error messages
   • Screenshots helpful
   • When problem started
   • What changed recently

Contact Options

MachineMetrics Support:

• Email: MachineMetrics Support
• Include all information listed above
• Attach screenshots
• Describe troubleshooting steps attempted

Machine Manufacturer:

• For MTConnect installation files
• For software upgrades
• For control-specific questions
• For THINC API updates (Okuma)

Solution Delivery Manager (SDM):

• Configuration guidance
• Deployment planning
• Best practices

MTConnect Institute:

• Protocol questions
• Standards documentation
• Community support

---

Ready to connect your MTConnect machine?

1. Verify MTConnect support
2. Enable MTConnect if needed
3. Configure network
4. Test endpoint in browser
5. Add machine in MachineMetrics
6. Verify data flow

Questions? Contact MachineMetrics Support with your machine details.