The Shop > Electronics & IC Programing

GRBL questions

<< < (3/3)

geoff_p:
Yes, it does, eventually!  It stops/interupts more calculations but doesn't halt those signals to the drivers that have already been calculated.

At slow feed (Fxx) rates this can take a blooming long time.  In some instances I have had to wait ten-minutes for the steppers to finally stop moving and the positions suggest it has got to near the end of the file anyways.

Thanks also to Gerrit's Wiki, I have been able to follow-along more of the Grbl's Wiki pages and have learned/understood a lot more about that software.  Awesome!

Geoff

gerritv:

--- Quote from: vtsteam on January 15, 2015, 10:20:00 AM ---Hmmmm, stop doesn't stop in Grbl Controller?

--- End quote ---
Stop for most of the GUI's means stop sending Gcode. Which means there might be up to 16 lines of gcode left to execute inside Grbl.
My approach in GrblPanel was to provide access to all of Grbl's features and interface to the GUI . So I have both a Stop sending and a Stop/Feed Hold 'button'
From a safety point of view you should always have a manual E-Stop as well.

Gerrit

vtsteam:
I don't see stop hold implemented on the Grbl Controller, but there is a soft and hard port reset.

The stop hold is a nice feature. Maybe it will be implemented in the next version. I was planning on a hard wired Estop, as well.

Navigation

[0] Message Index

[*] Previous page