This article answers the following questions:
- What is the difference between PATH, PATH 2, PATH 3, etc?
- Which path signals to MachineMetrics that a part is completed?
- When is a part count signal sent to MachineMetrics?
- When a machine has multiple work counter codes does MachineMetrics increment a part at each code execution point or just one?
This article answers frequently asked questions related to part count, machine paths, and how they are managed within the MachineMetrics application.
What is the difference between PATH, PATH 2, PATH 3, etc?
While this can vary based on the make and model of any given machine, typically Path is related to the main spindle/turret of a machine, while additional, numbered paths indicate sub-spindles and turrets.
Which path signals to MachineMetrics that a part is completed?
MachineMetrics can customize which paths are read for part counts, but by default, all paths are counted. If you need MachineMetrics to ignore certain paths in order to get an accurate part count, please communicate this need to your Customer Success Manager and they will take care of all the necessary configurations.
When is a part count signal sent to MachineMetrics?
MachineMetrics doesn't monitor for a specific M-code's execution, or completion, or part count signal. Rather, MachineMetrics tracks a control's internal part counter. The flow is as follows:
- M-code is run
- A machine's part counter increments
- MachineMetrics detects that the part counter changed
- Part is counted in MachineMetrics.
Most machine controls increment their internal part counter as soon as the M-code is run.
When a machine has multiple work counter codes, does MachineMetrics increment a part at each code execution point or just one?
The internal part counters on most machine controls increment a part whenever any work counter code is listed.
If you have any further questions, please reach out to us directly at firstname.lastname@example.org