Back to overview

Workflow

From a file on your desk to a self-correcting cycle

This is how a part program gets onto a machine with Undrd Control, and how much of the work after that is automatic. Everything happens remotely, except the final press of the button at the control.

Every screen on this page is an illustration built from the dashboard's own views. Names and figures are made up.

01You

Add the program to the machine's library

Upload new referenceIllustrative example

NC file

required

✓shaft_A_rev2.nc

STEP file

optional, for 3D preview

✓shaft_A.step

Upload

Library

O1003

shaft_A_rev2.nc

version 2 of 2
01You

Add the program to the machine's library

Drop in the NC file from your CAM system and, if you have it, the STEP model of the part. The dashboard reads the O-number from the file's first line, so a program is known by the same number the control knows it by.

  • Several files with the same O-number are kept as numbered versions, oldest first.
  • The STEP file is optional. It adds a 3D view of the part with the toolpath drawn over it.
  • Each machine has its own library, so every lathe's programs stay neatly apart.
Upload new referenceIllustrative example

NC file

required

✓shaft_A_rev2.nc

STEP file

optional, for 3D preview

✓shaft_A.step

Upload

Library

O1003

shaft_A_rev2.nc

version 2 of 2
02Automatic

See what the machine already holds

The edge agent reports the control's own program list. The dashboard matches it to your library by O-number, so you can tell at a glance what is loaded, what is missing, and what exists only on the machine.

  • Three counts double as filters: on the machine, in the library, matched.
  • Programs found only on the machine are listed apart, and an administrator can read their code on demand.
  • The counts always reflect what the machine has reported; until it has, they read as unknown.
Machine snapshotIllustrative example

14

On machine

9

In library

8

Matched

  • O1003shaft_A_rev2.ncOn machine
  • O1004flange_B.ncNot on machine

Only on the machine

  • O0042
  • O0107
  • O0230
03You, once

Describe the operations

Open the program in 3D and say what each operation is. This turns a plain NC file into one the closed loop can act on.

  • Set the tolerance for each finishing operation.
  • Mark the probe operation and link it to the operation it measures, so a result lands on the right tool.
  • Duplicate a tool as its twin, so the swap at the wear limit is ready before it is needed.
  • Set a wear limit per tool. The edge agent enforces it before it writes any correction.
OperationsIllustrative example
OpTool 
  • OP10T01Rough turn
  • OP20T02Finish Ø40
    ±0.030Twin T05
  • OP30T08Probe
    Measures OP20
Wear limit · T02
0.100 mm
04You, once

Choose how often to probe

Probing every part costs cycle time. Set “probe every N parts” and the dashboard gates the probe cycle inside the program for you, so only every Nth part is measured.

  • 1 means every part, and the program is sent as it is.
  • The cadence is saved with the program, so every later send uses it.
  • The NC file is adjusted automatically.
Probe everyIllustrative example
5parts
  1. Part 1
  2. Part 2
  3. Part 3
  4. Part 4
  5. Part 5
  6. Part 6
  7. Part 7
  8. Part 8
  9. Part 9
  10. Part 10
  • Probed
  • Cut only
05One click

Send it to the CNC

Press Send to CNC. The dashboard applies the probe cadence, adds the lines that publish probe results, and queues the program for the edge agent. The agent collects it over its own outbound connection, normally within about a second, loads it onto the control and reports back.

  • You follow the delivery live: queued, picked up, uploaded.
  • If the agent is offline the program waits in the queue, and a delivery that runs out of time is flagged straight away.
  • Each command is applied exactly once, even if it is sent twice.
  • On a control that cannot receive files, the agent stages the program and the dashboard tells you to load it at the panel.
  • Sending is reserved for administrator accounts.
Send to CNCIllustrative example
O1003 · shaft_A_rev2.ncSend to CNC

Probe cadence applied · result publishing added

  1. Queued

    Waiting for the agent to collect it

  2. Picked up

    The agent has it and is loading it

  3. Uploaded to the CNC

    Select it at the panel to run

06Automatic

Run, measure, correct

Select the program at the control and run it. From here the loop runs on its own: the probe measures, the agent works out a wear correction and writes it, and the dashboard shows it happening.

  • The dashboard recognises the running program by its content, not by its file name.
  • On a GSK 988TA with the probe on the machine, the agent corrects only when the program on the control is byte-for-byte the one you delivered.
  • At the wear limit the twin tool takes over and its wear count starts again.
  • Alerts fire if a machine goes offline, a delivery gets stuck, or data piles up unsent.
Cycle logIllustrative example

  1. Probe result

    Ø40.026 · nominal Ø40.000 · ±0.030

  2. Correction written

    −0.013 mm on tool 2

  3. Wear checked

    T02 0.078 of 0.100 mm

  4. At the limit

    Twin T05 takes over

Automation

How much is left for you to do

The aim is that you decide things once, per program, and the system carries them out every time after. The one step we deliberately leave to a person is starting a program at the machine.

Automatic

  • Delivering the program and following it to the end
  • Applying the probe cadence and publishing probe results
  • Matching your library against what the machine holds
  • Calculating and writing wear corrections within your limits
  • Swapping to the twin tool at the wear limit
  • Retrying safely, and alerting when something is stuck

You decide once

  • Tolerances for the finishing operations
  • Which operation is the probe, and what it measures
  • How often to probe
  • Wear limits and twin tools

Still done at the machine

  • Selecting and starting the program at the control
  • Everything to do with safety, which stays with certified hardware

Want to see it on your own machines?

Tell us which controls you run and we will walk you through the same flow on your setup.

Talk to usBack to overview