Emergency stop GRBL not working correct in Lightburn

[Bardman (Bart)]

Still not solved by Ligfhtburn, but solved by Neje

Under ​​LaserGRBL​​ and ​​NEJE Win​​ software control:

Pressing the emergency stop button pauses the ongoing operation.Resuming work requires clicking the software’s resume command after releasing the button.

For ​​LightBurn​​ software:
The emergency stop definition does ​​not​​ follow standard GRBL protocol.When controlling devices via ​​USB real-time data streaming​​ (LightBurn’s default mode), pressing the emergency stop button ​​immediately terminates​​ the current project.​​Partially completed work cannot be resumed​​ – this behavior differs significantly from LaserGRBL/NEJE’s pause-and-resume logic.​​
Critical Note:​​
Users must distinguish between these two emergency stop implementations to avoid unintended workflow interruptions.

Please …

[JohnJohn (John Johnson)]

@Bardman

Partially completed work cannot be resumed​​ – this behavior differs significantly from LaserGRBL/NEJE’s pause-and-resume logic.​​

Thank you for reporting this. I will test and confirm shortly.

[misken (Melvin)]

@Bardman

pressing the emergency stop button ​​immediately terminates​​ the current project.

Which button are you talking about? There is a Stop button (that stops the current project) and a Pause button that pauses it, and you can continue afterward.
Emergency stop buttons are usually on the laser device; do you mean a hardware button?

[Bardman (Bart)]

I may be wrong but inside Lightburn are only pauze and stop buttons. No Emergency buttons. So yes i mean a hardware button. The one NEJE sells as working. Yes its working but to lose the rest of your ongoing work. And you need to restart everything to start from zero. And if the error is in the design to find out again …

So i argumented a year ago with Neje, when possible. Its a company with low to none support.

I also bring it up here on the lightburn forum long time ago. And try to connect lightburn and Neje. Nothing happened

So i give it another try.

[gilaraujo (Gil Araújo)]

@Bardman

Yes its working but to lose the rest of your ongoing work.

Emergency stop, by definition, is a non-recoverable state.
Hardware standards-wise, the switch should kill power to all hardware, including the motherboard.
Which, therefore, would imply the buffer is clean and the controller resets.
Again, a non-recoverable state.

Some manufactureres are implementing recovering strategies but this would render the emergency switches to operat as a Hold, not as a emergency stop.

I could be corrected, as I dont know the protocol standards by memory, but if Neje is changing the Emergency stop behaviour, this is mostly firmware and not so much Software.

If you press stop on LightBurn, it is operating as intended; again, it is a non-recoverable state change.

The pause button, on the other hand, is a Hold.
But it might imply a flush of the current operations in the buffer.

[Aaron.F (Aaron)]

@Bardman

Partially completed work cannot be resumed​​ – this behavior differs significantly from LaserGRBL/NEJE’s pause-and-resume logic.​​

The Preview Window can be used to recover from failed jobs.

We made a video on the topic:

How to Restart an Incomplete LightBurn Job

[jkwilborn (Jack Wilborn)]

@gilaraujo

switch should kill power to all hardware

I 100% agree… This is the only feasible e-stop operation.

[Bardman (Bart)]

So as earlier discussed by me , just cut the power. The M8 and M7 in GRBL are useless for emergerncy stop.

But you could be right with you comments on NEJE, They use it as selling point.

[gilaraujo (Gil Araújo)]

@Bardman

The M8 and M7 in GRBL are useless for emergency stop

M7 and M8 are coolant and air assist commands so yes, they would be.
Some manufacturers have creative changes to the firmware, some are great some are not so great ideas. But for sure only they could be definitive on their interpretation of the EmergencyStop procedures.