The Hypertherm EDGE Connect runs an MTConnect agent built into its Phoenix software. That agent publishes what the table is doing, run state, active program, cut and pierce activity, and part count, as plain data on your network. Spall reads it and turns it into availability, downtime with reasons, and OEE. Nothing is written back to the CNC. This guide covers the whole setup on the machine.
Before you start You need a Hypertherm EDGE Connect (the Windows-based CNC running Phoenix). In Phoenix 10.21 and later, MTConnect is on by default, older versions take one extra step, covered below. You’ll also need an Ethernet drop at the table, an IP address from whoever runs your network, and the Spall gateway on the same network. The gateway reads only. It never writes to the CNC.
1. Put the EDGE Connect on the network
The EDGE Connect is a Windows PC under the hood, so it gets its IP the Windows way. Give it a static IP (or a DHCP reservation) so Spall always finds it at the same address, and note its host name, which usually looks like edge-000000000. If the CNC isn’t visible to other devices, turn on Network Discovery in Windows so it can be reached over the network.
Set the address in the same range as the Spall gateway, and write down both the IP and the host name. Either one works for the next steps.
2. Make sure MTConnect is enabled
Which way you go depends on your Phoenix version.
- Phoenix 10.21 or later: MTConnect is already on. Nothing to do here, move to Step 3.
- Older than 10.21: from the main screen go to Setups > Password and type
enablemtconnect. That switches the agent on.
3. Confirm the agent is answering
The EDGE Connect’s MTConnect agent listens on port 5134. From any PC on the same network, open a browser and hit the CNC on that port, using either its IP or its host name:
# device definition
http://edge-000000000:5134/probe
# live values right now
http://192.168.1.40:5134/currentIf you see XML, you’re done on the machine. If the page won’t load, the CNC either isn’t reachable on the network (recheck Step 1 and Network Discovery) or a firewall is blocking the port (next step).
4. Open the port on your firewall
MTConnect on the EDGE Connect uses TCP port 5134. If your test PC couldn’t reach the XML, ask IT to allow that port between the CNC and the Spall gateway. On shop networks that’s a one-line rule.
5. Point Spall at the table
In Spall, add the machine, choose MTConnect as the source, and enter the CNC address with the port:
192.168.1.40:5134Assign the Spall gateway on that network and save. Run state, program, and part count start populating within seconds. Start a cut and watch the state flip to ACTIVE and the count move.
What Spall does with this data
Availability. Spall splits the day into cutting, idle, and down straight from the run state. You see true table availability instead of a guess, and where the arc-on hours actually went.
Downtime and reasons. Consumable changes, unloads, and faults all show as stops the moment they happen. Operators tag the reason, and Spall ranks them into a Pareto so you attack the biggest loss first.
Production. Spall reads part count directly over MTConnect for target-vs-actual by shift and job, no counting parts off the table by hand.
Quality and OEE. Availability, performance, and quality roll into one OEE view, each loss ranked in dollars so the number points at an action instead of a score.
One thing worth repeating Spall reads. It never writes. The gateway pulls MTConnect data on your network and sends it outbound over encrypted MQTT. There’s no inbound port opened on your firewall for machine data, no VPN, and no changes to your cut programs or the CNC. Worst case if it can’t reach the table is a gap in the chart. The arc keeps running.
Quick recap
- Static IP and Network Discovery on the CNC
- MTConnect on (10.21+ default, otherwise
enablemtconnect) - Verify
:5134/currentin a browser - Open TCP 5134
- Add the machine in Spall
That’s the whole table in Spall. Repeat per machine, or hand us the addresses and we’ll bring them on together.