[FluidNC Issue#1569] Feature: Implement M66 not-immediate modes About GRBL HAL

Issue #1569 | 状态: 进行中 | 作者: tomaszglinski | 创建时间: 2025-09-19

标签: enhancement

Machine Context

I have a DYI pen-plotter and I’m building a pen lifting mechanism with sensors. I want to pause gcode execution until my sensor says “ok”.

Feature Description

Unfortunately docs say FluiNC supports now only M66 mode 0, which means it will not block the execution until signal comes. Any chance for fix for that?

Other Approaches

added:
In the mean time I will try using M0 + cyclestartpin

deleted:
In the mean time I will try to workaround it with loops (https://linuxcnc.org/docs/html/gcode/o-code.html), not sure if that will work, but for sure it will be ugly….

How I Can Help

You tell me. I have programming background but not in your tech

#1 – MitchBradley 于 2025-09-19

We are unlikely to add blocking M66 because it requires looping inside the GCode interpreter. There are some instances of that already, but they are complicated due to the need to perform other real-time operations while waiting, and to handle various error exit conditions. We are disinclined to add more such loops, when the functionality can be achieved by other means that are already well-established and debugged.

Either of your two alternative approaches should work.

原始Issue: https://github.com/bdring/FluidNC/issues/1569

Machine Context

Feature Description

Other Approaches

How I Can Help

评论 (1)