# Low priority CAM feature idea

**URL:** <https://forum.grid.space/t/low-priority-cam-feature-idea/657>\
**Category:** CAM\
**Created:** [May 17, 2022, 1:19am UTC](https://forum.grid.space/t/low-priority-cam-feature-idea/657 "2022-05-17T01:19:33Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![pmc](https://forum.grid.space/letter_avatar_proxy/v4/letter/p/e9c0ed/32.png) [@pmc](https://forum.grid.space/u/pmc)\
**Post date:** [May 17, 2022, 1:19am UTC](https://forum.grid.space/t/low-priority-cam-feature-idea/657/1 "2022-05-17T01:19:33Z")

</div>

Just had a would-be-nice thought – no big deal.

How about a “pause” CAM operation? Move up to “Z clearance” height and pause the job. Next op starts when user resumes the job.  
Possibly with parameters for Z lift then XY move/position – defaulted to “Z clearance” height and no XY move.

---

<div class="post-metadata">

**Author:** ![stewart](https://forum.grid.space/user_avatar/forum.grid.space/stewart/32/21_2.png) [@stewart](https://forum.grid.space/u/stewart)\
**Post date:** [May 17, 2022, 2:49am UTC](https://forum.grid.space/t/low-priority-cam-feature-idea/657/2 "2022-05-17T02:49:28Z")

</div>

I like this idea. It complements the ability to export all operations separately in a zip, which went into a previous release.

---

<div class="post-metadata">

**Author:** ![pmc](https://forum.grid.space/letter_avatar_proxy/v4/letter/p/e9c0ed/32.png) [@pmc](https://forum.grid.space/u/pmc)\
**Post date:** [May 30, 2022, 2:42am UTC](https://forum.grid.space/t/low-priority-cam-feature-idea/657/3 "2022-05-30T02:42:01Z")

</div>

Just had another thought about this. Which might also solve ops/parts ordering.

Maybe generalize “pause” into something like “checkpoint”, which may or may not generate a pause.

The main idea would be that a “checkpoint” forces the end of a block of work to sort. So instead of exposing and adding controls for how K:M sorts work – especially in regard to running all ops for each part vs all parts for each op – only require that all the work to be generated by the ops before a checkpoint gets done before continuing beyond the checkpoint.

A checkpoint could have a switch to generate a pause/hold, or not. Or for greater generality: a free text field to inline into the output – which could default to {lift Z, pause, return Z}.

---

<div class="post-metadata">

**Author:** ![stewart](https://forum.grid.space/user_avatar/forum.grid.space/stewart/32/21_2.png) [@stewart](https://forum.grid.space/u/stewart)\
**Post date:** [May 30, 2022, 2:08pm UTC](https://forum.grid.space/t/low-priority-cam-feature-idea/657/4 "2022-05-30T14:08:53Z")

</div>

I was going to allow for arbitrary gcode in a pause command. The way the code flows currently requires a bit of re-work to allow for op-major ordering. I like the idea, though, since it would also minimize tool changes.
