Skip to main content

Connectivity Overview

Overview​

MachineMetrics can connect to virtually any manufacturing equipment, regardless of age, brand, or model. This guide helps you determine the best connectivity method for your machines and understand what's required for a successful connection.

Key Concepts:

  • Protocol: The communication method used to retrieve data from your machine
  • Edge Device: The hardware that collects data from machines and sends it to the cloud
  • Adapter: Software configuration that translates machine data into MachineMetrics format
  • Connection Type: How the Edge device connects to your network (wired, wireless, cellular)

What this guide covers:

  • How to identify the right protocol for each machine
  • What information and hardware you need
  • How to plan your deployment
  • What to prepare before connecting machines

Before You Begin​

Prerequisites​

Before connecting machines, ensure you have:

  • Edge device deployed and activated
  • Network access configured
    • Machines are connected to the network
    • Network drop has been tested and verified that it can ping back to the MachineMetrics Edge Device
    • Use either a laptop or network test device to verify connectivity
    • Firewall rules in place (see Network Requirements Guide)
  • Software options installed and configured
    • Options such as OPC-UA or MTConnect must be installed and configured on machines where required before connecting to MachineMetrics
    • Verify software is running and accessible on the network
  • Machine information gathered
    • Make, model, and control type
    • Network requirements
    • Current IP addresses (if applicable)

What You'll Need​

For each machine:

  • Machine make and model
  • Control type and version
  • Capability information (supports protocols?)
  • Network access information
  • Physical access to the machine control

From your organization:

  • IT support for network configuration
  • Maintenance staff familiar with machine controls
  • Authority to enable protocols or modify settings
  • Budget for any required hardware

Identifying the Right Protocol for Your Machine​

The best way to identify which connectivity protocol to use for your machines is to refer to your Connectivity Tracker or Factory Assessment from MachineMetrics. These documents have been specifically created for your equipment and contain the recommended connectivity methods.

If you have a Connectivity Tracker or Factory Assessment:

  • Follow the protocol recommendations provided by MachineMetrics
  • Reference the specific configuration details for each machine
  • Contact your Solution Delivery Manager (SDM) with any questions

If you don't have a Connectivity Tracker or Factory Assessment:

  • Contact your Solution Delivery Manager (SDM) to request one
  • Or reference the table below for common machine types and controls

Common Control Types and Protocols​

For CNC machines, what control do you have?

Control BrandLikely ProtocolGuide Link
FANUCFOCAS (preferred) or MTConnectFOCAS Guide
MazakFusion Client (Windows-based controls) or MTConnectMazak Guide / MTConnect Guide
OkumaMTConnectMTConnect Guide
HaasMTConnect (Next Gen), Serial (older), or I/OHaas Guide
Siemens CNCOPC-UA (840D sl) or BFC Gateway/I/O (840D PL)OPC-UA Guide
Siemens S7 PLCS7 ProtocolSiemens S7 PLC Guide
Allen BradleyEtherNet/IP (CompactLogix, ControlLogix, GuardLogix)Allen Bradley Guide
Brother D-SeriesOPC-UAOPC-UA Guide
Brother C-SeriesHTTP ConnectorBrother C-Series Guide
HurcoMTConnect (WinMax 10.4.0+)MTConnect Guide
HeidenhainProprietary (TNC 530/640)Heidenhain TNC Guide
Citizen (M700)Citizen M700 adapterCitizen Guide
Citizen (M850)Mitsubishi M70 adapterCitizen Guide
MitsubishiM70/M700 proprietary protocolMitsubishi Guide
DMG MORIDepends on control backendSee options below ↓

DMG MORI Options (check your specific control):

Don't see your control? Contact your Solution Delivery Manager (SDM) or MachineMetrics support with your machine make, model, and control information.

Connectivity Methods​

FANUC FOCAS​

What it is: FOCAS (FANUC Open CNC API Specification) is the standard protocol for FANUC controls.

Compatible machines:

  • Any CNC with FANUC control (0i, 16i-B, 18i-B 30i, 31i, 32i series)
  • Requires FOCAS license on the control
  • Compatible with FANUC-controlled equipment

Data available:

  • Machine status (running, idle, stopped)
  • Program name and number
  • Cycle time
  • Part count
  • Alarms and messages
  • Spindle load and override
  • Feed rate and override
  • Axis positions and loads
  • Tool information
  • Tool life
  • Macro variables (custom data)
  • PMC bits
  • Diagnostics data
  • P-CODES

Requirements:

  • Ethernet connection to the control
  • IP address configured on the machine
  • FOCAS option enabled (check with your machine builder if unsure)

Hardware needed:

  • Edge device
  • Ethernet cable

Learn more: FOCAS Connectivity Guide

MTConnect​

What it is: MTConnect is an open, royalty-free standard for manufacturing data exchange.

Important: On most machines, except Haas, you need to contact your machine tool dealer to learn if MTConnect is installed or to learn how to purchase it.

Compatible machines:

  • Mazak (Smooth controls, Matrix controls)
  • Okuma (OSP controls with MTConnect option)
  • Many machine tools with MTConnect agents installed
  • CMMs (Hexagon, Zeiss)
  • Some 3D printers and additive equipment

Data available:

  • Machine status
  • Execution mode
  • Program information
  • Part count
  • Alarms
  • Controller mode
  • Axis data
  • Spindle data
  • Tool data (varies by implementation)

Requirements:

  • MTConnect agent running on the machine or adapter computer
  • IP address of the MTConnect agent
  • Port number (typically 5000 or 7878)
  • Access to the MTConnect data stream

Hardware needed:

  • Edge device
  • Ethernet cable
  • (Sometimes) MTConnect adapter device or computer

Learn more: MTConnect Connectivity Guide

OPC-UA​

What it is: OPC Unified Architecture is a platform-independent, service-oriented architecture for industrial automation.

Compatible machines:

  • Siemens 840D sl controls (with OPC-UA option)
  • Brother D-Series CNC machines
  • Bystronic equipment
  • Many PLCs and industrial controllers
  • Equipment with OPC-UA servers

Siemens 840D PL (Power Line) Controls:

For Siemens 840D PL controls, direct OPC-UA connectivity is not available. These controls require either:

  1. Siemens BFC Gateway (Brownfield Connectivity Gateway) - A scalable middleware solution that bridges devices and protocols, enabling seamless communication between industrial IT and OT systems. The BFC Gateway provides a unified architecture supporting multiple protocols and offers a centralized connectivity hub for managing shop floor equipment. Learn more about BFC Gateway
  2. Digital I/O connectivity - Using sensors and I/O modules to capture machine signals. See Digital I/O Guide

Data available:

  • Varies widely by implementation
  • Typically includes status, cycle data, production counts
  • Custom variables and tags
  • Process parameters

Requirements:

  • OPC-UA server enabled on the machine/controller (840D sl)
  • For 840D PL: BFC Gateway or I/O hardware
  • IP address and port number
  • Data map/tag list from the machine builder
  • Security credentials (username/password or certificate)
  • Understanding of what each tag represents

Hardware needed:

  • Edge device
  • Ethernet cable
  • For 840D PL: BFC Gateway or I/O module

Learn more: OPC-UA Connectivity Guide

Digital I/O​

What it is: Connection via electrical signals and sensors rather than digital protocols.

Compatible machines:

  • ANY machine with electrical outputs or sensors
  • Ideal for older equipment without modern protocols
  • Equipment where direct connection isn't possible or practical

Data available:

  • Machine status (via relay or sensor)
  • Cycle count (via sensor or signal)
  • Part count (via sensor)
  • Custom signals (door open, alarm condition, etc.)
  • Environmental sensors (temperature, vibration, etc.)

Requirements:

  • Access to machine electrical cabinet
  • Identification of available signals (cycle complete, machine running, etc.)
  • Sensor installation points (if counting parts)
  • Electrical schematic understanding (helpful)

Hardware needed:

  • Edge device
  • SeaLevel I/O module
  • Sensors (photo eyes, proximity sensors, etc.)
  • Wiring and connectors
  • Mounting hardware

Typical setup time: 2-4 hours per machine (includes sensor installation and wiring)

Learn more: Digital I/O Connectivity Guide

What it is: MachineMetrics partners with IFM to connect IO-Link conforming sensors for industrial data collection.

Compatible devices:

  • All IO-Link conforming sensors (IFM and other manufacturers)
  • IFM master blocks with IoT data ports (AL1350, AL1352, etc.)
  • Temperature, pressure, flow, vibration, and other smart sensors

Data available:

  • Real-time sensor measurements (temperature, pressure, flow, etc.)
  • Sensor status and diagnostics
  • Process variables
  • Multiple sensors per master block

Requirements:

  • IFM IO-Link master block with IoT port
  • IO-Link sensors
  • Network connectivity to master block
  • M12 cables for sensor connections

Hardware needed:

  • IFM IO-Link master block (with IoT port)
  • IO-Link sensors (IFM or compatible)
  • Edge device
  • Network cable

Typical setup time: 2-4 hours per master block (includes sensor connections and configuration)

Learn more: IFM IO-Link Connectivity Guide

MQTT​

What it is: MQTT (Message Queuing Telemetry Transport) is a lightweight messaging protocol for IoT devices and machines that publish data via publish/subscribe messaging.

Compatible machines:

  • Machines with built-in MQTT support
  • Lincoln Electric welding machines
  • Custom machines with MQTT clients/brokers
  • IoT-enabled equipment

Data available:

  • Depends on machine implementation
  • Typically status, production counts, process variables
  • JSON or raw data formats

Requirements:

  • Machine with MQTT broker or client capability
  • MQTT broker (if machine is client only)
  • Topic structure and data format documentation
  • Network connectivity

Hardware needed:

  • Edge device
  • Optional: External MQTT broker (Mosquitto, HiveMQ, etc.)

Typical setup time: 1-3 hours (varies by machine complexity)

Learn more: MQTT Connectivity Guide

Brother C-Series HTTP​

What it is: HTTP-based connector for Brother CNC machines with C-Series controls, retrieving data from the control's web interface.

Compatible machines:

  • Brother machines with C-Series controls (C00, C-00)
  • Brother Speedio series
  • Brother TAPMATIC series
  • Brother drill/tap centers with web interface

Data available:

  • Machine status and execution state
  • Program information
  • Tool data
  • Spindle speed and load
  • Part count (if available)

Requirements:

  • Brother C-Series control with web interface
  • IP address and HTTP access (port 80)
  • Network connectivity

Hardware needed:

  • Edge device

Typical setup time: 30 minutes - 1 hour

Note: For Brother D-Series controls, use OPC-UA Guide instead.

Learn more: Brother C-Series HTTP Guide

Siemens S7 PLC​

What it is: Direct connection to Siemens S7 PLCs (Programmable Logic Controllers) to read production data from data blocks.

IMPORTANT: Connecting to Siemens S7 PLCs requires an S7 expert who can provide datablock access and information. MachineMetrics does not offer this service. You will need someone with Siemens PLC expertise to configure the datablocks and provide the necessary technical information for connectivity.

Compatible PLCs:

  • S7-300 series (with CP 343-1 Ethernet module)
  • S7-400 series (with CP 443-1 Ethernet module)
  • S7-1200 series (integrated Ethernet)
  • S7-1500 series (integrated Ethernet)

Data available:

  • Machine status and states
  • Part counters and production data
  • Process variables (temperature, pressure, etc.)
  • Cycle times
  • Custom data from PLC data blocks

Requirements:

  • Siemens S7 PLC with Ethernet capability
  • Access to PLC programming (TIA Portal or STEP 7)
  • Data block structure and offsets
  • PUT/GET communication enabled (S7-1200/1500)
  • S7 expert to configure datablocks and provide connectivity information

Hardware needed:

  • Edge device
  • Network cable

Typical setup time: 1-3 hours (includes PLC data block configuration)

Note: This is for Siemens PLCs, not Siemens CNC controls. For Siemens 840D CNC, use OPC-UA Guide.

Learn more: Siemens S7 PLC Connectivity Guide

Modbus/TCP​

What it is: Modbus is a widely-used industrial protocol for reading and writing data from PLCs and controllers.

Compatible machines:

  • Equipment with Modbus TCP capability
  • Many PLCs (Automation Direct, Allen-Bradley, Siemens, etc.)
  • Process equipment
  • Custom machinery with PLC control

Data available:

  • Depends on PLC programming
  • Typically status, counts, sensor values
  • Custom registers and coils

Requirements:

  • IP address
  • Port number (typically 502)
  • Modbus register map from machine builder
  • Understanding of data types and meanings
  • Knowledge of which registers contain relevant data

Hardware needed:

  • Edge device
  • Ethernet cable

Learn more: Modbus/TCP Connectivity Guide

EtherNet/IP (Allen Bradley)​

What it is: EtherNet/IP is an industrial Ethernet network protocol used to connect to Allen Bradley PLCs.

Compatible machines:

  • Allen Bradley CompactLogix PLCs (1769, 5069 series)
  • Allen Bradley ControlLogix PLCs (1756 series)
  • Allen Bradley GuardLogix safety controllers (1756 series)
  • Not compatible: MicroLogix, SLC500 (use dedicated adapters)

Data available:

  • Status information
  • Production counters
  • Process variables
  • Custom tags from PLC program

Requirements:

  • IP address of PLC
  • Tag list from PLC program
  • Understanding of tag meanings
  • Network access to the controller
  • Backplane slot number (for ControlLogix/GuardLogix)

Hardware needed:

  • Edge device
  • Ethernet cable

Learn more: Allen Bradley Connectivity Guide

MQTT​

What it is: MQTT is a lightweight pub-sub messaging protocol ideal for IoT devices.

Compatible machines:

  • Equipment publishing MQTT messages
  • Custom IoT implementations
  • Some modern equipment with MQTT support

Data available:

  • Depends on MQTT implementation
  • Typically JSON-formatted messages with sensor data, status, etc.

Requirements:

  • MQTT broker address and port
  • Topic structure
  • Message format documentation
  • Authentication credentials (if required)

Hardware needed:

  • Edge device
  • Network connectivity to MQTT broker

Learn more: MQTT Connectivity Guide

Mitsubishi​

What it is: Proprietary connectivity for Mitsubishi CNC controls using the Mitsubishi adapter.

Compatible machines:

  • Mitsubishi M70 / M80 / M800 CNC controls (use M70 adapter)
  • Mitsubishi M700 CNC controls (use M700 adapter)
  • Miyano machines (with Mitsubishi controls)

Data available:

  • Execution state (ACTIVE, READY, INTERRUPTED)
  • Program name and number
  • Tool data and offsets
  • Spindle and feed information
  • Axis positions
  • Alarms and messages
  • Part count (with proper configuration)

Requirements:

  • Ethernet-enabled Mitsubishi control
  • Network connectivity between machine and Edge
  • Static or reserved DHCP IP address

Hardware needed:

  • Edge device
  • Network cable (if not using wireless)

Learn more: Mitsubishi Connectivity Guide

Citizen​

What it is: Proprietary connectivity for Citizen Cincom Swiss-type lathes using the Citizen M700 adapter (for M700 controls) or Mitsubishi M70 adapter (for M850 controls).

Compatible machines:

  • Citizen Cincom L-Series (L20, L32, L220)
  • Citizen Cincom A-Series (A16, A20, A32)
  • Citizen Cincom B-Series (B12, B20, B32)
  • Citizen Cincom K-Series (K16E)
  • Citizen Cincom M-Series (M4xx)
  • Miyano machines (with Mitsubishi controls)

Adapter selection:

  • M700 controls: Use Citizen M700 adapter
  • M850 controls: Use Mitsubishi M70 adapter

Data available:

  • Execution state (ACTIVE, READY, INTERRUPTED)
  • Program name and number
  • Tool data, offsets, and tool life
  • Spindle and feed information (main and sub-spindle)
  • Axis positions
  • Alarms and messages
  • Part count (Work Counter, M-code, or barfeeder signal)
  • Multi-spindle data
  • Guide bushing operations
  • Barfeeder integration

Requirements:

  • Firmware meets minimum requirements (see Citizen guide)
  • Ethernet-enabled Mitsubishi control
  • Network connectivity between machine and Edge
  • Static or reserved DHCP IP address

Hardware needed:

  • Edge device
  • Network cable (if not using wireless)

⚠️ IMPORTANT:

  • Do NOT use MTConnect for Citizen machines unless explicitly instructed by MachineMetrics support
  • Firmware must meet minimum requirements to avoid machine alarms or freezes

Learn more: Citizen Connectivity Guide

Haas (Serial & MTConnect)​

What it is: Multiple connectivity options for Haas machines depending on control generation.

Includes:

  • MTConnect (Next Generation controls, 2016+)
  • Haas Serial MDC/DPRNT (Classic and Next Gen)
  • Digital I/O (pre-2001 machines)

Data available:

  • Execution state and status
  • Program information
  • Tool data
  • Spindle and feed rates
  • Macro and system variables (via serial)
  • Part count

Requirements:

  • Varies by method (see Haas guide)
  • May require Moxa converter for older machines
  • Network connectivity or serial connection

Hardware needed:

  • Edge device
  • Moxa serial-to-Ethernet converter (for classic serial)
  • Current transducers (for I/O method)

Learn more: Haas Connectivity Guide

Network Connection Types​

Wired Connection​

Description: All machines connect via Ethernet cables to a central network switch, which connects to a single Edge device (typically in a server room).

Best for:

  • Facilities with existing network infrastructure
  • Machines in a fixed location
  • When you want to minimize Edge device costs
  • When you have reliable wired network

Advantages:

  • One Edge device can handle 10-50 machines
  • Lower per-machine hardware cost
  • Reliable connection
  • No WiFi signal concerns

Requirements:

  • Network drops (CAT5/CAT6 cable) to each machine
  • Network switch
  • Single Edge device
  • Proper network segmentation

Typical cost: Lower per machine (shared Edge), but requires network cabling

Wireless Connection​

Description: Each machine (or small group) has its own Edge device that connects wirelessly to your facility WiFi.

Best for:

  • Facilities without existing machine network infrastructure
  • Machines that move frequently
  • When running cables is impractical or expensive
  • Environments where wireless is already robust

Advantages:

  • No cabling required
  • Flexible machine placement
  • Quick deployment
  • Each machine has dedicated Edge (more capacity)

Requirements:

  • Strong WiFi coverage on shop floor
  • WiFi-enabled Edge devices
  • Mounting locations for Edge devices (electrical cabinets)
  • WiFi antennas mounted outside electrical enclosures

Typical cost: Higher per machine (individual Edges), but no cabling costs

Cellular Connection​

Description: Edge device connects to the internet via cellular modem, completely separate from your facility network.

Best for:

  • Machines at remote locations
  • When network access is restricted or unavailable
  • Temporary or mobile installations
  • When you want complete network isolation

Advantages:

  • No dependency on facility network
  • Works anywhere with cellular signal
  • Network security concerns eliminated
  • Simple setup

Requirements:

  • Cellular modem or hotspot
  • Data plan from cellular provider
  • Good cellular signal at location

Typical cost: Highest (ongoing data plan costs), but maximum flexibility

Hardware Requirements by Protocol​

ProtocolEdge DeviceAdditional HardwareNotes
FOCASRequiredEthernet cable onlySimplest setup
MTConnectRequiredEthernet cable, possibly MTConnect adapterDepends on machine
OPC-UARequiredEthernet cable onlyMay need security setup
Digital I/ORequiredSeaLevel I/O module, sensors, wiringMost hardware-intensive
ModbusRequiredEthernet cable onlyNeed register map
EtherNet/IP (Allen Bradley)RequiredEthernet cable onlyNeed tag list
MQTTRequiredNetwork access to brokerNeed topic structure
SerialRequiredSerial-to-Ethernet converter (MOXA), cablesOlder equipment

Purchase hardware: All hardware should be purchased from MachineMetrics at shop.machinemetrics.com. See the Hardware Buying Guide.

Data Collection Standards​

What Data Can Be Collected?​

Depending on the protocol and machine capabilities, you can typically collect:

Core Metrics:

  • Machine status (running, idle, stopped, alarm)
  • Cycle time (time to produce one part)
  • Part count (total parts produced)
  • Program or job information

⚠️ Important Note on Part Counting (Ethernet Machines):

For Ethernet-connected machines (FOCAS, MTConnect, OPC-UA), MachineMetrics reads the machine's native part counter. The machine itself must be configured to count parts. Without additional scripting or configuration, MachineMetrics relies entirely on the machine's internal part count signal.

Before troubleshooting part counts in MachineMetrics:

  1. Verify the machine's part counter is incrementing on the machine's control screen
  2. If the machine counter isn't incrementing, this is a machine configuration issue (not MachineMetrics)
  3. If the machine counter IS incrementing but MachineMetrics shows zero, then troubleshoot MachineMetrics configuration

See protocol-specific troubleshooting sections (FOCAS, MTConnect, OPC-UA) for detailed steps.

Advanced Metrics (protocol-dependent):

  • Spindle load and speed
  • Feed rate and overrides
  • Axis positions and velocities
  • Tool usage and life
  • Alarms and error codes
  • Coolant and other auxiliary states
  • Temperature, vibration, or other sensor data
  • Custom variables or parameters

Operator Input (via tablets):

  • Downtime reasons
  • Quality/reject information
  • Job start/stop
  • Setup vs production time

Required Information by Protocol​

MTConnect:

  • IP address
  • Port number (typically 5000)

FANUC FOCAS:

  • IP address
  • Confirmation that FOCAS is enabled

OPC-UA:

  • IP address
  • Port number (typically 4840)
  • Data map (list of tags and their meanings)
  • Security credentials (username/password or certificates)

Modbus/TCP:

  • IP address
  • Port number (typically 502)
  • Register map (which registers contain what data)
  • Data types and meanings

EtherNet/IP (Allen Bradley):

  • IP address
  • Tag list and meanings
  • PLC model (CompactLogix, ControlLogix, or GuardLogix)
  • Backplane slot number (for ControlLogix/GuardLogix)

Digital I/O:

  • Available signals (cycle complete, machine run, etc.)
  • Sensor mounting locations
  • Electrical access requirements

Planning Your Deployment​

Single Machine​

Quick Start:

  1. Identify machine protocol (use decision tree above)
  2. Deploy Edge device
  3. Connect machine using appropriate method
  4. Configure data points
  5. Verify data flow

Timeline: Half day to full day

Multiple Machines​

Recommended Approach:

  1. Phase 1: Connect 1-2 "pilot" machines
    • Choose machines with straightforward protocols
    • Learn the process
    • Verify data quality
    • Refine configuration
  2. Phase 2: Roll out to similar machines
    • Use lessons learned
    • Document specific configurations
    • Train internal team
  3. Phase 3: Connect remaining machines
    • Tackle more complex protocols
    • Complete facility coverage

Timeline: 2-4 weeks depending on machine count

Facility-Wide Deployment​

Planning Steps:

  1. Inventory all machines
    • Document make, model, control for each
    • Identify protocol for each
    • Group by connectivity method
  2. Assess network infrastructure
    • Determine wired vs wireless strategy
    • Plan network drops if needed
    • Identify Edge device locations
  3. Calculate hardware needs
    • Number of Edge devices
    • I/O modules for older machines
    • Cables, converters, sensors
    • Tablets for operator input
  4. Order hardware (from shop.machinemetrics.com)
    • Allow lead time (5-14 days typically)
    • Include spares
  5. Schedule deployment
    • Coordinate with production schedule
    • Plan for downtime (15-60 min per machine)
    • Allocate resources (maintenance, IT, MachineMetrics)

Timeline: 4-12 weeks for 20-50 machines

Pre-Connectivity Checklist​

Before connecting each machine, verify:

Network Readiness​

  • Edge device deployed and online
  • Firewall rules configured (see Network Requirements Guide)
  • Network connectivity verified to machine location
  • IP addresses allocated for machines (if static IPs)

Machine Preparation​

  • Machine make, model, control documented
  • Protocol identified
  • Required information gathered (IP, data maps, etc.)
  • Physical access to machine available
  • Maintenance staff available to assist

Hardware Availability​

  • All required hardware on-site
  • Cables correct length and type
  • Sensors and mounting hardware (for I/O)
  • Tools for installation

Coordination​

  • Production schedule allows for connection time
  • Machine operator informed
  • IT/Network team available if needed
  • Backup plan if connection takes longer than expected

Getting Hardware​

Purchase from MachineMetrics: All connectivity hardware should be purchased from shop.machinemetrics.com

Why buy from MachineMetrics:

  • Pre-configured and tested
  • Guaranteed compatibility
  • Full support coverage
  • Faster troubleshooting

Required for ordering:

  • Purchase order OR full payment
  • Shipping cannot proceed without one or the other

See the Hardware Buying Guide for complete details.

Next Steps​

After reading this overview:

  1. Identify your machines' protocols
    • Use the decision tree in this guide
    • Document findings for each machine
  2. Determine network approach
    • Wired, wireless, or cellular
    • Coordinate with IT team
  3. Order hardware
  4. Read protocol-specific guides
  5. Begin with pilot machines
    • Start small to learn the process
    • Verify data quality before scaling

Common Scenarios​

Scenario: Mixed Machine Shop (Various Ages/Types)​

Situation: 15 machines including newer FANUCs, older Haas, and some manual equipment.

Approach:

  • Newer FANUC CNCs → FOCAS protocol
  • Older Haas → Haas Serial or Digital I/O
  • Manual machines → Digital I/O with sensors
  • Wired network (one Edge in server room)

Hardware needed:

  • 1 Edge device
  • Ethernet cables for FOCAS/Serial connections
  • 3-5 SeaLevel I/O modules for manual machines
  • 1-2 MOXA serial converters for older Haas
  • Sensors, wiring, mounting hardware

Scenario: Single Machine Type (Mazak shop)​

Situation: 12 Mazak CNC machines, all with Smooth controls.

Approach:

  • All machines → MTConnect protocol
  • Wireless network (one Edge per machine or per small group)

Hardware needed:

  • 12 Edge devices with WiFi capability
  • Ethernet cables
  • WiFi antennas and mounting hardware

Scenario: Remote Job Shop​

Situation: 5 machines in a location with no IT support or network infrastructure.

Approach:

  • Mixed protocols based on machine type
  • Cellular connection (complete network independence)

Hardware needed:

  • 1 Edge device
  • Cellular modem with data plan
  • Protocol-specific hardware as needed

Getting Help​

Before You Connect​

Questions about which protocol to use?

Need help with network planning?

  • Contact your CSM for deployment planning assistance
  • Involve your IT team early in the process

Hardware questions?

During Connection​

Technical support:

Protocol-specific guides:

  • See the comprehensive guides for each protocol (coming in this section)

After Connection​

Data not appearing?

  • See protocol-specific troubleshooting sections
  • Check Edge device status
  • Verify machine settings

Need optimization?

  • Work with your CSM on data quality
  • Review part counting configuration
  • Fine-tune machine settings

Ready to connect your first machine? Select the appropriate protocol guide from the list below:

Questions? Contact support@machinemetrics.com or your Solution Delivery Manager (SDM) during onboarding.