How to Read Data From CNC Machine Controls and Networks

• 1
  Key takeaways
• 2
  What You Can Actually Read From a Control
• 3
  Reading Data From CNC Machine Files: USB, RS-232, and Ethernet
• 4
  Network Protocols: MTConnect, OPC UA, and FOCAS
• 5
  Matching Control Data to Inspection Results
• 6
  What to Check Before You Trust the Numbers
• 7
  How to Read Data From CNC Machine: 6 Steps
• 8
  Which Data Method Fits Which Job

Every CNC control exposes a fixed set of live values. On a Fanuc, Siemens, Heidenhain, or Mazak panel, the position display shows absolute and relative coordinates, the active work offset, and the remaining distance to go. The program screen shows the block being executed. The offset page shows wear and geometry values for each tool. The alarm page shows the last fault and the time it occurred.

These five screens answer most questions a buyer has. If a feature measured 0.03 mm oversize, the wear offset history tells you whether the operator compensated. If a surface finish came out rough, spindle load and feed override tell you whether the tool was pushed too hard. If a part was scrapped, the alarm log tells you whether the machine stopped or kept cutting.

The panel is a live view. It does not store history beyond a shift unless someone writes it down or the control saves it. That is the main limit. For anything longer than one shift, you need files or a network connection.

• 1
  Position and offsetsAbsolute position, work offset number, and tool wear values.
• 2
  Program blockThe exact line running now, plus feed and speed override percentages.
• 3
  Load and alarmsSpindle and axis load, plus the last 10 to 50 alarms with timestamps.
• 4
  Tool lifeRemaining life counters on controls that support tool management.

Most controls from the last 20 years can export files. The simplest path is a USB port on the front of the control. On a Fanuc 0i or 31i, you press the System key, then All I/O, then select the program directory and copy to USB. On a Siemens 840D, the same job runs through the Services menu. The files come out as plain text or a proprietary format.

Older machines use RS-232 serial. Set the baud rate to match the control, commonly 9600 or 19200, 7 data bits, even parity, 2 stop bits. Get one of these wrong and you get garbled characters or nothing at all. This is the most common setup error. Check the cable is a null modem type before blaming the control.

Ethernet is now standard on new machines. You can pull programs, tool lists, and alarm logs over FTP or a shared folder. On a Heidenhain TNC, the file manager lets you copy the whole program folder to a network drive. Speeds are fast enough to back up a full program library in minutes.

• 1
  USB firstWorks on most controls built after 2005. Check the file extension before opening.
• 2
  RS-232 settings9600 or 19200 baud, 7-E-2, null modem cable, hardware handshake on.
• 3
  Ethernet backupUse FTP or a mapped drive. Confirm the control clock is set correctly first.

If you need live data across a shop floor, point-to-point file transfer will not scale. MTConnect is the most common open standard. It streams values like spindle speed, feed rate, execution state, and part count as XML over HTTP. A machine agent runs on a small box or PC next to the control and publishes the data.

OPC UA does the same job with a different data model. It is stronger on security and works well when the same network also carries PLC and robot data. Fanuc's own FOCAS library gives direct access to control registers over Ethernet. It is fast and detailed, but it is vendor-specific and needs a licensed application to read it.

For most job shops, MTConnect is enough. It answers the questions buyers ask: was the machine running, what was it cutting, and how long did the cycle take. OPC UA makes sense when you are already running it elsewhere in the plant.

• 1
  MTConnectOpen XML standard. Good for machine state, cycle time, and part counts.
• 2
  OPC UAStrong security and a shared data model with PLCs and robots.
• 3
  Fanuc FOCASDeep access to control registers. Vendor-specific and needs a license.

Control data tells you what the machine intended to do. Inspection data tells you what the part actually measures. You need both. A program can run clean with no alarms and still produce a part 0.02 mm out of tolerance if the tool wore or the material moved.

Pull the tool offset history for the feature in question. If the wear value changed during the run, the operator saw a drift and compensated. If it did not change, the part was cut once and never checked until final inspection. That is a process gap worth asking about.

Compare timestamps. The log time, the inspection time, and the shipment time should line up. A gap of several hours between cutting and inspection is normal. A gap of several days usually means the parts sat in a queue, and any rework happened off the record.

At GreatLight, a 100% inspection step runs before shipment. Raw material checks, in-process monitoring, and final inspection are logged, and reports are available on request. That gives you a second data source to set against the control log.

• 1
  Offset historyShows whether the operator adjusted for tool wear during the run.
• 2
  Alarm logShows stops, spindle faults, and servo errors with timestamps.
• 3
  Inspection reportShows measured values. Ask for the report on the specific feature.

The control clock is the first thing to verify. If it is off by hours or days, every timestamp downstream is wrong. Ask the shop to sync it to a network time source. This takes two minutes and saves arguments later.

Check the units. A Fanuc control can display in metric or inch, and the setting is easy to change by accident. A value that reads 25.4 could be millimeters or thousandths of an inch depending on the mode. Confirm the unit before you compare anything.

Look for gaps. A clean log with no entries for three hours during a shift is suspicious. Either the machine was idle, or the logging stopped. Ask which one. A shop that can explain an idle gap is more credible than one that claims the machine ran nonstop.

Finally, ask what the data is not. Control logs do not capture manual deburring, hand polishing, or bench work. They do not capture rework. They show the CNC cycle, not the whole manufacturing route.

• 1
  Clock syncVerify the control time against a known reference before reading logs.
• 2
  Unit modeConfirm metric or inch display. 25.4 mm and 0.001 in are easy to confuse.
• 3
  Log gapsIdle time is fine. Unexplained silence in the log is not.