Skip to main content

MTConnect Connectivity Guide

Overview​

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

Compatible Machines​

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)
  • Mazak - Preview G, Smooth G, 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):

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​

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​

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​

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

Mazak-Specific Setup​

Important: Not all Mazak machines require MTConnect. See the Mazak Connectivity Guide to determine which connection method is appropriate for your machine.

Recommendation:

  • If MTConnect is NOT already installed: Use Mazak Fusion Client instead (recommended)
  • If MTConnect is already installed: You may continue to use MTConnect

Checking for MTConnect:

  1. Access Windows Backend

    • Click Windows Start button on Mazak control
    • The control uses Windows as the OS

  2. Search for MTConnect

    • Click Start → Search
    • Type "MTConnect"
    • Look for MTConnect folder

  3. Verify Installation

    • MTConnect folder should contain:
      • Adapter executable
      • Agent executable
      • Configuration files
    • If not found: MTConnect needs to be installed

Installing MTConnect (if needed):

  1. Contact Mazak

    • Mazak provides MTConnect on a thumb drive
    • Each machine requires individual license file
    • Request one thumb drive per machine
    • Mazak provides installation instructions

  2. Supported Control Models

    • See Mazak-Specific Section for detailed compatibility chart
    • Generally 2010 or newer controls support MTConnect
    • Smooth and Matrix control families

Network Configuration:

  1. Locate Ethernet Port

    • Port usually patched from HMI
    • Cable runs to keystone in main electrical cabinet
    • Connected to shop network

  2. Configure PC IP Address

    • Access Windows network settings
    • Configure Ethernet adapter
    • Set static IP address
    • WARNING: Do NOT change NC IP Address!

  3. Default MTConnect Port

    • Mazak agent typically uses port 5000
    • Mazak adapter typically uses port 7878 (internal)
    • Verify in MTConnect configuration

Starting MTConnect Service:

  1. Access Control Panel → Administrative Tools → Services
  2. Find "Mazak MTConnect" or similar service
  3. Ensure Status = "Running"
  4. If not: Right-click → Start

Okuma-Specific Setup​

Compatibility Check:

  1. Determine Control Type

    • OSP 300: Best MTConnect support
    • OSP 200: Requires THINC API update + MTConnect
    • OSP 100-II: Requires THINC API update + MTConnect
    • Other OSP 100: NOT supported

  2. Use Scout Tool

    • Visit MyOkuma.com
    • Use Scout tool to verify compatibility
    • Tool will indicate if updates are needed

  3. Check Compatibility Chart

Accessing Windows:

  • Press CTRL + /// to access Windows Start button
  • From here you can access File Explorer, applications, etc.

Installing/Updating MTConnect:

  1. Check Current Installation

    • Press CTRL + ///
    • Navigate to Programs → Okuma → MTConnect
    • If not present: needs installation

  2. Install from THINC App Store

    • OSP 300: Install directly from THINC App Store
    • Download MTConnect Agent/Adapter
    • Follow on-screen installation prompts

  3. Update THINC API (if needed)

    • OSP 200 and OSP 100-II require THINC API update first
    • Must be done by Okuma dealer
    • Contact your dealer for this service

Enable Monitoring Tags:

⚠️ Critical Step: Even with MTConnect installed, monitoring must be enabled.

  1. Press CTRL + /// (access Windows)
  2. Select Programs → Okuma → Okuma MTConnect Adapter Application
  3. Enter credentials:
    • Username: Administrator
    • Password: okuma+osp
  4. Select Configuration tab
  5. Click Tags Configuration button
  6. Check "Enable Monitoring Tags"
  7. Verify data items you want to monitor are also checked
  8. Click Save & Close
  9. Restart machine for changes to take effect

Enabling Macro Variable Monitoring:

The Configurations tab also controls which common (macro) variables the adapter exposes over MTConnect. This is required if you need part counting via common variables or any other program-driven variable data.

Okuma MTConnect Adapter Configurations tab showing Common Variable Starting/Ending Index and Enable Monitoring Tags checkbox

  1. On the Configuration tab, locate the Common Variable Starting/Ending Index fields at the top of the screen
  2. Enter the starting index of the variable range you want to monitor (e.g., 500)
  3. Enter the ending index of the range (e.g., 520)
  4. Click Save & Close
tip

Set the range as narrow as possible — only include the variables actually used by your programs. A range like 500–520 is typical for part counting setups.

note

If you are using a common variable for part counting (e.g., VC500), the variable index must fall within this range or MachineMetrics will not be able to read it.

caution

If the Common Variable Starting/Ending Index fields or the Tool Assets checkbox are not visible on the Configurations tab, your version of the Okuma MTConnect Adapter is outdated. Download and install the latest version from MyOkuma.com to access these options.

Port Configuration:

  • Okuma typically uses port 5000
  • Verify in MTConnect configuration utility

Part Counting:

See Okuma Part Counting section for configuring common variables if automatic counting doesn't work.

Okuma OSP-P500 Setup​

The OSP-P500 is a newer Okuma control with a different navigation path than older OSP controls. MTConnect is built in — no THINC App Store installation needed.

Protocol: MTConnect | Default Port: 5000 | URL: http://<machine_ip>:5000/current

Prerequisites:

  • Ethernet cable connected from the machine control to the customer's network
  • Network IP address or DHCP information from the customer's IT team
  • Machine serial number

Step 1: Access the CNC Screen

From the machine homepage (OSP Suite), press CNC in the lower-left Operation panel to open the conventional CNC operation screen.

Okuma OSP-P500 homepage showing OSP Suite with CNC button

Step 2: Open Admin Launcher

  1. On the CNC screen, locate the puzzle piece icon in the lower-right sidebar
  2. Tap it to open the utility menu
  3. Tap the gear icon (⚙) to open settings
  4. Select Admin Launcher

The Admin Launcher window will open with configuration options including Date and Time, Language Change, PLC Monitor, Network Options, DNC-T1 Settings, and Firewall Settings.

Okuma OSP-P500 Admin Launcher showing Network Options

Step 3: Configure the Network / IP Address

  1. In the Admin Launcher, select Network Options (item 4)
  2. Select the Network Interface
  3. The Windows Internet Protocol (TCP/IP) Settings page will appear
  4. Configure the IP address:
    • DHCP: Select "Obtain an IP address automatically"
    • Static IP: Enter the IP address, subnet mask, and default gateway provided by the customer's IT team
  5. Click OK and close the network settings
note

The machine must be on the same network/subnet as the MachineMetrics Edge device, or have a route configured between them.

Step 4: Verify Firewall Settings

The OSP-P500 has a built-in firewall (OSP-FIREWALL) that controls which protocols can communicate with the control. MTConnect must be enabled here.

  1. In the Admin Launcher, select Firewall Settings (item 6)
  2. The OSP-FIREWALL screen will open showing the list of firewall rules
  3. Confirm MTConnect-Agent is checked/enabled in the rules list
  4. If it is not enabled, check the box and press Apply
  5. Press Quit to close

Okuma OSP-P500 OSP-FIREWALL screen showing MTConnect-Agent and OPC UA rules

note

The firewall screen also shows OPC UA (TCP, port 4840) as a separate rule. If you are setting up OPC-UA on the same machine, ensure that rule is also enabled.

Step 5: Open the MTConnect Adapter

  1. Tap the puzzle piece icon again from the CNC screen
  2. From the utility menu on the right side, select MTConnect Adapter
  3. The Okuma MTConnect Adapter window opens on the Configurations tab, showing four sections:
    • System Configuration
    • Device Configuration
    • Tags Configuration
    • Functional Mode Mapping

Okuma MTConnect Adapter — main Configurations screen

Step 6: Update Device Configuration

  1. Select Device Configuration (or press the DEVICE CONFIG. softkey at the bottom)
  2. Update the following fields:
    • Serial Number — Enter the machine's serial number
    • Device Name — Enter a name for the machine
    • Description — Enter a description that uniquely identifies this machine (e.g., make, model, location)
  3. Confirm the changes

Step 7: Configure Monitoring Tags

Critical Step

Without "Enable Monitoring Tags" checked, all tag values will report as UNAVAILABLE.

  1. Select Tags Configuration (or press the TAGS CONFIG. softkey)
  2. ☑ Check Enable Monitoring Tags at the top of the screen
  3. ☑ Optionally check Tool Assets if tool asset data is required — enter the Asset Tool ID if applicable
  4. Set the Common Variable Starting/Ending Index range if the customer's programs use common variables (e.g., 500–520)
  5. Ensure relevant tags are checked. Key tags include:
TagTypeDescription
DRY_RUNOUTPUT_SIGNALDry run status
MACHINE_LOCKOUTPUT_SIGNALMachine lock status
PLC_MONITOR_IO_1–10INPUT_OUTPUT_SIGNALPLC I/O signals
PROGRAM_HEADERPROGRAM_HEADERActive program info
PALLET_IDPALLET_IDPallet identifier
BLOCKBLOCKCurrent block
LINELINECurrent line number
TOOL_NUMBERTOOL_NUMBERActive tool number
TOOL_ASSET_IDTOOL_ASSET_IDTool asset reference
BLOCK_NUMBERBLOCK_NUMBERBlock count
SYSTEMSYSTEMSystem condition

Okuma OSP-P500 Tags Configuration — Enable Monitoring Tags checkbox and tag list

Step 8: Save and Close

  1. Press SAVE & CLOSE (softkey at the bottom right)
  2. The MTConnect adapter reinitializes with the new configuration
  3. Press MINIMIZE TO SYSTEM TRAY — the adapter continues running in the background

Verification

  1. Open a browser on the machine control
  2. Navigate to http://localhost:5000/current
  3. You should see XML output with current machine data items
  4. From a remote machine on the same network, navigate to http://<machine_ip>:5000/current to confirm network accessibility

If all values show as UNAVAILABLE:

  • Confirm "Enable Monitoring Tags" is checked
  • Restart the MTConnect adapter: on OSP-P500, reopen it via CNC → Puzzle Icon → MTConnect Adapter; on Windows-based controls (OSP 300 / 200 / 100-II), close and reopen from Start → Programs → Okuma → MTConnect Adapter
  • If the issue persists, restart the machine control

If the page does not load remotely:

  • Check that Windows Firewall allows inbound traffic on port 5000
  • Verify network connectivity between the Edge device and the machine

Quick Reference — OSP-P500

ItemValue
ProtocolMTConnect
Default Port5000
URL Formathttp://<ip>:5000/current
Admin Launcher PathCNC → Puzzle Icon → Gear → Admin Launcher
MTConnect Adapter PathCNC → Puzzle Icon → MTConnect Adapter
Critical Setting☑ Enable Monitoring Tags

Hexagon CMM Setup​

Hexagon MTConnect Documentation

For full setup instructions from Hexagon, refer to the Metrology Asset Manager MTConnect Guide on Hexagon Nexus.

How It Works

Hexagon's MTConnect implementation uses two components:

ComponentWhat It IsRuns On
MTConnect AdapterBuilt into Metrology Connector. Reads CMM data and sends it to the AgentCMM control PC
MTConnect AgentOpen-source app (cppagent). Receives data from the Adapter and serves it over HTTPCMM control PC or external PC

MachineMetrics connects to the MTConnect Agent HTTP endpoint (port 5001 by default).

Port 7878

In standard MTConnect, port 7878 is the internal TCP port the Agent uses to communicate with the Adapter — it is not an HTTP client endpoint. If you have been connecting MachineMetrics at port 7878, confirm with your MachineMetrics engineer as this may depend on your specific Edge configuration.

Prerequisites:

  • Nexus account (sign up at nexus.hexagon.com)
  • Advanced entitlement (or Local Advanced entitlement) of Metrology Asset Manager
  • Metrology Connector V7.1 or higher installed on the CMM control PC
  • Network access between the Agent PC and MachineMetrics Edge
  • PC-DMIS installed on the CMM PC (optional — only required if you need program name/cycle data)

Setup Steps:

Part 1: Configure the MTConnect Adapter in Metrology Connector

  1. Sign in to your Nexus account, download and install Metrology Connector from User Menu → User Preferences → Downloads
  2. Open Metrology Connector and click the Settings icon (large gear, upper right)
  3. Under Service and interfaces, click the MTConnect Adapter tab
  4. Check the checkbox next to your CMM asset (must already be upgraded to Advanced)
  5. Toggle on Interface Enabled in the Advanced Settings
  6. Note the port number shown — this is what the Agent will connect to (default is typically 7878). It can be changed, but must match the agent.cfg file
  7. Click Save Changes

Part 2: Set Up the MTConnect Agent

  1. Download the MTConnect Agent (cppagent) from GitHub: https://github.com/mtconnect/cppagent/releases
  2. Unzip the downloaded archive to a folder on your C drive (for example, C:\Users\Public\Downloads\mtconnect-agent\). The exact folder name may vary depending on the version you downloaded.
  3. Edit agent.cfg in the bin subfolder of the folder you extracted (for example, C:\Users\Public\Downloads\mtconnect-agent\bin\agent.cfg)
    • Ensure the adapter port in this file matches what was set in Step 6 above
  4. Open a command window in the bin folder (type cmd in the folder path bar, press Enter)
  5. Run: agent.exe debug
  6. The Agent is now running

Part 3: Test and Connect

  1. In a browser on the Agent PC, navigate to http://127.0.0.1:5001/current
  2. You should see MTConnect XML data
  3. Provide the Agent PC's IP and port 5001 to MachineMetrics for Edge configuration

Data Flow:

  1. CMM control PC runs Metrology Connector with MTConnect Adapter enabled
  2. Adapter sends CMM data to the MTConnect Agent (internal connection)
  3. Agent serves data over HTTP at http://[Agent-PC-IP]:5001/current
  4. MachineMetrics Edge polls the Agent endpoint and ingests data

Zeiss CMM Setup​

Prerequisites:

  • CALYPSO 7.2+ installed and licensed
  • Zeiss MTConnect Data Interface license
  • Windows 10/11 64-bit PC
  • Network access to MachineMetrics Edge
  • Administrator permissions on controller PC

Installation Steps:

  1. Obtain Installer

  2. Run Installer

    • Execute as Administrator on CMM PC
    • Accept default path: C:\Program Files\Zeiss\MTConnectAdapter

  3. Activate License

    • Open Zeiss License Manager
    • Import MTConnect entitlement file
    • Verify "MTConnect Interface" shows as "Licensed"

  4. Configure Adapter

    • Launch "MTConnect Configuration Utility"
    • Set machine name
    • Set HTTP port (default 5000 or 5001)
    • Configure CALYPSO data path
    • Click "Apply and Start Service"

  5. Test Locally

    • On CMM PC, open browser
    • Navigate to http://localhost:5000/current
    • Should see XML output with MTConnect data

Data Items Available:

  • Machine status (Idle / Measuring / Alarm)
  • Current part program name
  • Measurement count and cycle time
  • Operator ID (if configured)

Hurco-Specific Setup​

Overview:

Hurco machines use the MTConnect protocol to retrieve manufacturing data directly from WinMax on the control. The MTConnect adapter is available for download and installation.

Important: Hurco provides data through the MTConnect protocol but does not provide a GUI interface to display the data. Ensure any third-party applications (including MachineMetrics) check against MTConnect version 1.3 scheme.

Prerequisites:

  • WinMax Version Requirements:
    • Mill: WinMax 10.4.0 or later (MTConnect available without Ultimonitor)
    • Lathe: WinMax 11.3.4 or later (MTConnect available without Ultimonitor)
    • Older versions: Require Ultimonitor option to use MTConnect
  • Administrator access to Hurco control
  • Network connectivity between machine and Edge device

Installing the MTConnect Adapter:

  1. Download MTConnect Adapter

  2. Access Service Menu

    • Select Windows key or Hurco icon button on control
    • Select the Service softkey
    • Enter password: 46268
    • Click OK

  3. Enable Drive Access

    • In Hurco Service Window, select Toggle Drive Access On
    • Button will change to read "Toggle Drive Access Off"

  4. Open File Explorer

    • In Hurco Service Window, select Open Explorer
    • Close the Hurco Service Window (click X in upper right)

  5. Run Installer

    • Search for MTConnect install package in File Explorer
    • Select Run to launch installer
    • Check box to accept License Agreement terms
    • Click Install button
    • Click Finish after successful installation

Verifying Installation:

Method 1: Using Internet Explorer

  1. Access Shell menu (Windows key or Hurco icon)
  2. Select Run softkey
  3. Enter password: 46268
  4. Enter iexplore in Run window and click OK
  5. Enter http://127.0.0.1:5000/current in address bar
  6. Press Enter
  7. Verify: Machine data should display in XML format
    • If data appears, MTConnect adapter is running correctly

Method 2: Using Task Manager

  1. Access Service menu (password: 46268)
  2. Enable Drive Access
  3. Select Task Manager
  4. Close Hurco Service Window
  5. Select Processes tab
  6. Verify: Look for these processes:
    • agent.exe
    • MTConnectAdapter.exe
    • If both are running, adapter is working

Port Configuration:

  • Default Port: 5000
  • Test URL: http://127.0.0.1:5000/current (local)
  • External URL: http://[MACHINE-IP]:5000/current (from network)

Data Items Available from Hurco:

Hurco MTConnect provides the following data:

Data ItemDescription
Status & Control
EStop_StateEmergency stop status
Feed_HoldFeed hold status
Controller_ModeCurrent controller mode
Machine_Mode0=Diagnostic, 1=Idle, 2=Manual, 3=Manual Setup, 4=Auto Prep, 5=Auto Run, 6=Interrupt Cycle
COR_StatusCorner rounding status
Program Info
Program_Name_RunningActive program name
Program_Name_EditingProgram being edited
Program_StatusCurrent program status
Block_NumberCurrent block number
Program_Runtime_SecondsProgram runtime
Part_CountPart counter
Spindle & Feed
Spindle_SpeedCurrent spindle speed
Spindle_OverrideSpindle override percentage
Spindle_TimeTotal spindle run time
S_Axis_LoadSpindle load
Feed_RateCurrent feed rate
Feed_OverrideFeed override percentage
Rapid_OverrideRapid override percentage
Rapid_SpeedRapid traverse speed
Tooling
Current_ToolActive tool number
Positioning
X_Position, Y_Position, Z_PositionAxis positions
A_Position, B_Position, C_PositionRotary axis positions
W_PositionW axis position
Axis Loads
X_Axis_Load, Y_Axis_Load, Z_Axis_LoadLinear axis loads
A_Axis_Load, B_Axis_Load, C_Axis_LoadRotary axis loads
W_Axis_LoadW axis load
Other
Machine_TimeTotal machine time

Troubleshooting Hurco MTConnect:

Problem: Cannot access http://127.0.0.1:5000/current

Solutions:

  1. Verify MTConnect adapter is installed
  2. Check Task Manager for agent.exe and MTConnectAdapter.exe processes
  3. If processes not running:
    • Restart machine
    • Reinstall MTConnect adapter
  4. Check Windows Firewall settings (port 5000 must be allowed)

Problem: Local test works but external access fails

Solutions:

  1. Verify machine IP address
  2. Ping machine from Edge device or computer
  3. Check network connectivity
  4. Verify Windows Firewall allows external connections on port 5000
  5. Check if machine is on same network/VLAN as Edge device

Problem: Wrong WinMax version

Solution:

  • If WinMax is older than 10.4.0 (mill) or 11.3.4 (lathe):
    • Option 1: Upgrade WinMax to supported version
    • Option 2: Purchase and install Ultimonitor option
    • Contact Hurco support for upgrade options

Adding Hurco to MachineMetrics:

After verifying MTConnect is running:

  1. In MachineMetrics, go to Assets → Machines
  2. Click Add Machine
  3. Enter machine details:
    • Machine Name: (e.g., "Hurco VM10i")
    • Make: Hurco
    • Model: (e.g., "VM10i")
    • Edge Device: Select your Edge
  4. Select adapter type: MTConnect Agent
  5. Enter connection details:
    • Connection address: [MACHINE-IP]:5000
    • Example: 192.168.1.100:5000
  6. Click Test Connection
  7. If successful, click Save

Additional Resources:

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​

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.

OEM-Specific Configurations​

Mazak​

Important: Only certain Mazak machines require MTConnect. See the Mazak Connectivity Guide to determine the correct connection method for your specific control type.

Which Mazak controls use MTConnect:

The following controls require MTConnect and cannot use the Fusion Client:

  • Preview G
  • Smooth G
  • Smart

All other Mazak controls (Fusion 640, Matrix, Nexus, Preview 3, Smooth/SmoothX/SmoothAi) should connect using the Mazak Fusion Client instead. If MTConnect is already installed and working on one of those controls, it is fine to continue using it.

Contact Mazak or refer to your machine documentation if you are unsure which control type you have.

Installation Process:

  1. Check if Installed

    • Access Windows on control
    • Search for MTConnect folder
    • If found: proceed to configuration
    • If not found: contact Mazak

  2. Request from Mazak

    • Mazak provides MTConnect on USB thumb drive
    • Each machine needs individual license
    • Order separate thumb drive for each machine
    • Includes installation files and instructions

  3. Install from Thumb Drive

    • Follow Mazak-provided instructions
    • Installation includes:
      • MTConnect Adapter
      • MTConnect Agent
      • License file (machine-specific)
      • Configuration files

Network Configuration:

  • Configure "PC IP Address" in Windows network settings
  • DO NOT modify "NC IP Address" (internal machine communication)
  • Default agent port: 5000 (or check MTConnect configuration)
  • Default adapter port: 7878 (internal connection)

Service Management:

  • Service name: "Mazak MTConnect" or similar
  • Location: Control Panel → Services
  • Ensure set to "Automatic" startup
  • Verify "Running" status

Common Issues:

Okuma​

Supported Controls:

ControlMTConnectNotes
OSP-P500Built-inSee OSP-P500 Setup for full walkthrough
OSP 300Install from App StoreBest support, easy self-install
OSP 200Install from App Store (after THINC API update)Contact Okuma dealer for API update first
OSP 100-IIInstall from App Store (after THINC API update)Contact Okuma dealer for API update first
Other OSP 100Not AvailableUse I/O integration instead

Compatibility Verification:

Installation for OSP 300:

  1. Access THINC App Store
  2. Search for "MTConnect"
  3. Download and install MTConnect Agent/Adapter
  4. Follow on-screen instructions
  5. Configuration happens automatically

Installation for OSP 200 / OSP 100-II:

  1. First: Contact Okuma dealer for THINC API update
  2. Then: Install MTConnect from THINC App Store
  3. Both steps required for these controls

Enabling Monitoring Tags:

⚠️ Critical: This step is required even if MTConnect is installed.

  1. Press CTRL + /// (access Windows)
  2. Navigate: Programs → Okuma → Okuma MTConnect Adapter Application
  3. Login:
    • Username: Administrator
    • Password: okuma+osp
  4. Click Configuration tab
  5. Click Tags Configuration button
  6. Check "Enable Monitoring Tags"
  7. Select data items to monitor (or select all)
  8. Click Save & Close
  9. Restart machine

Part Counting with Common Variables:

If part count doesn't increment automatically:

  1. Open MTConnect application on Okuma
  2. Go to "Device Configuration"
  3. Select common variable (e.g., VC1)
  4. In CNC program, add near the end:
    • VC1=VC1+1 (increment by 1)
    • VC1=VC1+2 (increment by 2)
  5. Contact MachineMetrics with variable number for configuration match

Default Port: 5000

Accessing Windows: Press CTRL + ///

Hexagon CMMs​

Software Required:

  • Metrology Connector V7.1 or higher (download from Hexagon Nexus)
  • MTConnect Agent — open-source cppagent (GitHub)
  • PC-DMIS (optional — only required for program name/cycle data)

License Requirement:

  • Advanced entitlement of Metrology Asset Manager (obtained via Nexus account)
  • Local Advanced entitlement also supported for non-internet environments

Key Configuration:

  • Enable the MTConnect Adapter tab in Metrology Connector Settings → Service and interfaces
  • Adapter (inside Metrology Connector) runs on the CMM control PC and feeds the Agent
  • MachineMetrics connects to the MTConnect Agent at port 5001
  • Agent can run on the same CMM control PC or a separate PC
  • Adapter port (typically 7878) must match what is set in agent.cfg

Data Available:

  • CMM status (idle, measuring, alarm)
  • Program execution state
  • Cycle data
  • Measurement events

Documentation:

Zeiss CMMs​

Supported Software:

  • CALYPSO 7.2 or newer
  • PiWeb 8.x or newer

License Requirement:

  • Zeiss MTConnect Data Interface license
  • 60-day trial available
  • Trial Download

Key Configuration:

  • Default port: 5000 or 5001
  • CALYPSO data path must be configured
  • Service runs in background

Data Available:

  • Machine status (Idle / Measuring / Alarm)
  • Current part program name
  • Measurement count
  • Cycle time
  • Operator ID (if configured)

Best Practices:

  • Use static IP for CMM PC
  • Schedule weekly service restart via Windows Task Scheduler
  • Keep CALYPSO and MTConnect adapter versions in sync

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​

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. Review Edge Logs

    • Settings → Edge Devices → Logs
    • Look for MTConnect errors or warnings

Mazak MTConnect Service Issues​

Problem: Mazak MTConnect service won't stay running after reboot

This is a known issue with older Mazak MTConnect adapters.

Diagnostic Steps:

  1. Access Windows on Mazak Control

    • Click Start menu
    • Type "Run" and press Enter
    • Type CMD and press Enter (opens command prompt)

  2. Test MTConnect Locally

    • In command window, type: telnet localhost 7878
    • If you see streaming data: MTConnect is running, likely network issue
    • If telnet doesn't connect: Service not running

  3. Check Service Status

    • Open Control Panel → Advanced Settings → Component Services
    • Find "MTConnect" or "Mazak MTConnect" in services list
    • Check if service is running
    • If not running: Right-click → Start

  4. Verify Again

    • Return to command prompt
    • Retry telnet test: telnet localhost 7878
    • Should now see data stream

Permanent Fix:

  • Contact Mazak dealer and request upgraded MTConnect adapter
  • Newer software versions resolve auto-restart issues
  • Upgrade recommended for production reliability

Okuma Issues​

Problem: MTConnect installed but not reporting data

Check Monitoring Tags:

This is the most common Okuma issue.

  1. Access Windows (CTRL + ///)
  2. Open Okuma MTConnect Adapter Application
  3. Login (Administrator / okuma+osp)
  4. Configuration tab → Tags Configuration
  5. Verify "Enable Monitoring Tags" is checked
  6. If unchecked: Check it, Save & Close, restart machine

Problem: Part count not incrementing

⚠️ CRITICAL FIRST STEP: Verify Machine is Counting Parts

Before troubleshooting MachineMetrics or MTConnect configuration, verify the machine itself is incrementing its internal part counter.

MTConnect (and MachineMetrics) reads the machine's native part counter. If the machine isn't counting parts, MTConnect cannot report them. Without additional configuration, MachineMetrics relies entirely on the machine's internal part count signal provided by MTConnect.

How to spot a bad count on the Timeline

See the Connectivity Validation Guide for a visual guide to identifying healthy vs. problematic part count patterns — including what sporadic counts and sub-second cycle times look like.

Check Machine Part Counter:

  1. Look at the machine's control screen
  2. Find the part counter display (varies by machine/control)
  3. Run a cycle
  4. Verify the counter increments on the machine itself

If the machine counter is NOT incrementing:

  • This is a machine configuration issue, not a MachineMetrics or MTConnect issue
  • Machine is not configured to count parts
  • For Okuma: See Okuma Part Counting section below

If the machine counter IS incrementing but MachineMetrics shows zero:

  • This is a MachineMetrics or MTConnect adapter configuration issue
  • Verify MTConnect adapter is reporting the part count
  • Access MTConnect stream: http://[machine-ip]:[port]/current
  • Look for <PartCount> or similar data item
  • If present in MTConnect but not in MachineMetrics: Data mapping issue

Solution for Okuma Machines:

If Okuma part count not incrementing on machine itself, use Common Variables.

See Okuma Part Counting section for detailed setup.

Problem: THINC API too old

Solution:

  • Contact Okuma dealer for THINC API update
  • Required for OSP 200 and OSP 100-II
  • Cannot self-install API update

Problem: Control not compatible

Solution:

  • Use Scout tool to verify compatibility
  • If not compatible: Use Digital I/O integration instead
  • Contact MachineMetrics for alternative methods

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

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
  • Monitor for adapter errors in Edge logs
  • 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:

Articles:

OEM Resources:

MachineMetrics Resources:

Getting Help​

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: support@machinemetrics.com
  • 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 support@machinemetrics.com with your machine details.