DMG Mori builds MTConnect into every new machine running its CELOS operating panel, free of charge, as part of the standard IIoT interface. That’s the good news, and it’s real. The part worth knowing before you start is that “standard” doesn’t mean “already on,” and it doesn’t mean identical from machine to machine, because CELOS itself runs on top of a back-end CNC that’s either FANUC or Siemens depending on the machine, and that back-end changes what step one actually is. Get that part right and the rest is the same MTConnect setup as any other control.
Before you start This covers CELOS-equipped DMG Mori machines. Older, non-CELOS DMG Mori controls aren’t covered here, check with DMG Mori or your service rep if you’re not sure which generation you have. You’ll need to know your machine’s back-end control (FANUC or Siemens, it’s on the machine’s spec sheet or ask your DMG Mori contact), the MTConnect agent enabled in CELOS, an Ethernet drop, a fixed IP, and the Spall gateway on the same network. The gateway reads only. It never writes to the control.
1. Know your back-end control before you start
This is the step that actually differs by machine, and skipping it is the most common reason MTConnect setup stalls on a DMG Mori.
- FANUC back-end. MTConnect typically comes pre-installed and ready to enable, since FANUC’s own connectivity story lines up cleanly with what CELOS already exposes. Move straight to step 2.
- Siemens back-end. MTConnect is not installed by default here. DMG Mori sells it as a separate IoT Connectivity package on Siemens-based CELOS machines, and it has to be purchased and installed before there’s anything to enable. Contact your DMG Mori sales or service rep if you’re not sure whether that package is already on your machine.
Getting this backwards, assuming a Siemens-back-end machine already has MTConnect because a FANUC-back-end sister machine did, is the single most common reason a DMG Mori MTConnect setup stalls before it starts.
2. Enable MTConnect in the Machine Data menu
Once the adapter is present (pre-installed on a FANUC back-end, or added via IoT Connectivity on a Siemens back-end), turn it on from CELOS itself: open the Machine Data menu, set Application Output to MTConnect, and set MTConnect Agent to Enabled. Note the MTConnect Agent Machine ID shown on that screen, you’ll need it, since a DMG Mori agent can serve more than one device definition and Spall needs to know which one is this machine.
3. Put the control on the network
Give the machine a static IP, or a DHCP reservation, in the same range as the Spall gateway. Write it down for the next step.
4. Confirm the agent is answering
MTConnect agents conventionally serve on port 5000. From any PC on the same network:
# device definition, confirms the Machine ID from step 2
http://10.0.6.14:5000/probe
# live values right now
http://10.0.6.14:5000/currentIf /probe shows a device matching the Machine ID from step 2 and /current returns live XML, the machine is ready. If nothing answers, double check step 1 and step 2 rather than assuming a network fault, on a Siemens back-end machine, the most common cause is the IoT Connectivity package not actually being installed yet.
5. Open the port on your firewall
If a PC elsewhere on the network couldn’t reach the XML, ask IT to allow TCP 5000 between the DMG Mori and the Spall gateway.
6. Point Spall at the machine
In Spall, add the machine, choose MTConnect as the source, and enter the control’s address, port, and the Machine ID from step 2:
10.0.6.14:5000 (device: DMU50-A114)Assign the Spall gateway and save. Run state, program, and part count start populating within seconds.
What Spall does with this data
Availability. Every hour splits into running, idle, and down straight from the standard MTConnect Execution and ControllerMode items, no clipboards, and identical whether the machine’s back-end is FANUC or Siemens once the data is flowing.
Downtime and reasons. Each stop is caught the instant it happens. Operators tag the reason, and Spall ranks them into a Pareto.
Production. Spall reads part count directly over MTConnect for target-vs-actual by shift and job, once the DataItem is present in your machine’s device definition.
Quality and OEE. Availability, performance, and quality roll into one OEE view, each loss ranked in dollars.
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 programs or the control. Worst case if it can’t reach the machine is a gap in the chart. The spindle keeps running.
Quick recap
- Check whether your machine’s back-end is FANUC (usually just needs enabling) or Siemens (may need the IoT Connectivity package first)
- Enable it in CELOS: Machine Data > Application Output: MTConnect, MTConnect Agent: Enabled
- Note the Machine ID, you’ll need it
- Set a static IP, verify
ip:5000/probeandip:5000/current - Open TCP 5000, then add the machine (and Machine ID) in Spall
Backend and package differences aside, once the agent answers, a DMG Mori behaves like any other MTConnect machine from here. Bring us your machine list, FANUC or Siemens back-end noted, and we’ll tell you exactly what each one needs.