How Mitsubishi CNC collects and connects to the ERP system

• 1
  What you need to know first
• 2
  What Mitsubishi CNC collects and connects from the control
• 3
  Three connection paths and when each one fits
• 4
  Network and security setup before the first tag
• 5
  Common errors and how to avoid them
• 6
  How to build the pipeline in six steps
• 7
  Which connection path fits your shop

Every integration starts with the same question: what can the control actually give you? On Mitsubishi CNC, that depends on the series (M70, M80, M800, M8 series, or older M50/M60) and on which communication options were ordered. The control exposes data in three layers, and you need to know which layer each signal lives in before you write any code.

The first layer is machine status. Run, stop, alarm, feed hold, door open, and cycle-complete flags come straight from the PLC. These are cheap to read and cheap to store. The second layer is production counters, such as part count, cycle time, spindle run time, and tool change count. The third layer is process data: spindle load, axis position, override values, active program number, and offset tables. Process data is where the value is, and also where the polling cost is.

Which signals matter for ERP? In practice, four groups feed almost every work order: start and end timestamps, good versus scrap quantity, active program or work order number, and alarm codes. Everything else is nice to have for dashboards but does not change a production schedule.

A common mistake is trying to collect everything on day one. Engineers wire up 40 tags, the poll cycle slows down, and the ERP starts rejecting records. Start with the four groups above. Add process data later once the pipeline is stable.

• 1
  Control series mattersM70/M80 expose more open interfaces than older M50/M60 controls.
• 2
  PLC tags are not freeEach tag has a read cost. Count them before you set the poll rate.
• 3
  Program number is the keyWithout it, you cannot tie a cycle to a work order.

There is no single correct way for Mitsubishi CNC collects and connects to an ERP. There are three practical paths, and the right one depends on how many machines you have and how much control you have over the control side.

Ethernet with a native protocol is the cleanest path. Modern Mitsubishi controls support MTConnect or OPC UA through an option card or a gateway. MTConnect is read-only and gives you a standard XML schema, which makes the ERP side simple. OPC UA supports subscriptions, so you stop polling and let the server push changes. If your machines are M80 or newer, this is the path to choose.

File and macro output is the low-cost path. The CNC program writes a small text file or CSV to a shared folder at the end of each cycle using macro variables. A service on the network watches the folder and inserts rows into the ERP. This works on almost any control, needs no option card, and is easy to debug. The downside is latency: you get data at cycle end, not during the cut.

Digital I/O and PLC relay is the fallback. A stack light or relay board gives you run, stop, and alarm as dry contacts. You get binary state only, no counters and no program number. Use it when the control is locked down or very old, and accept that the ERP will only know that a machine is running, not what it is making.

• 1
  MTConnect or OPC UABest for M80 and newer, read-only or subscription-based.
• 2
  Macro file dropWorks on nearly any control. Cycle-end latency only.
• 3
  Digital I/OFallback for locked or legacy controls. State only.

Integration projects usually fail on the network, not on the protocol. Put the machine network on its own VLAN. Do not let the CNC controls share a broadcast domain with office traffic, and do not route them to the internet. A gateway or edge device with two network interfaces is the normal pattern: one side talks to the machines, the other side talks to the ERP middleware.

Set static IP addresses on every control. DHCP leases that change after a power outage will silently break your tag addresses. Record the IP, the port, and the protocol version for each machine in a spreadsheet before configuration starts.

Firewall rules should be explicit. The gateway needs to reach the ERP on one port, and the ERP needs to reach the gateway on one port. Nothing else. If your IT team wants deep packet inspection on the machine side, expect timing jitter and plan for a larger buffer.

Time synchronization matters more than most people expect. If machine clocks drift by 30 seconds, cycle records will not line up with ERP shift boundaries, and reports will disagree by a full shift. Point every control and the gateway at the same NTP source.

• 1
  Separate VLANKeep machine traffic off the office network.
• 2
  Static IPsRecord IP, port and protocol per machine.
• 3
  One NTP sourceClock drift breaks shift-level reporting.

The first error is polling too fast. Engineers set a 100 ms poll because it feels more accurate, then the gateway CPU saturates and records arrive late. Match the poll rate to the decision it supports. A production schedule does not need 100 ms data. Tool breakage detection might.

The second error is mapping inside the ladder. When the part number lives in the PLC program, every new job needs a program edit and a download. Put the mapping in a table outside the control and read it by key.

The third error is no buffering. A five-minute network drop during a 90-second cycle wipes out a shift of counts. Local storage and a retry queue cost almost nothing and prevent the argument about whose numbers are right.

The fourth error is writing to the control too early. If you push offsets before the read path is trustworthy, you will chase phantom problems. Run read-only for two weeks, compare counts against the operator's tally, then enable write-back one machine at a time.

• 1
  Pull count reconciliationCompare gateway counts with the operator tally daily for the first two weeks.
• 2
  Alarm code mappingMap control alarm codes to ERP reason codes before go-live, not after.
• 3
  Change logRecord every tag, mapping and firewall change with a date.