Basically looking through the past posts on the forums it seems that there isn't a clear solution to this problem quickly stopping smoothie and then being able to resume . However in my case i think i have a few things that might make this a little easier. I am using a smoothie board 1.0b to control a 2d gantry however the motion is never faster than 100mm/min and most of the time under 25mm/min. It seems realistically i will have to use suspend and resume triggered by button pushes and it will be a sd card print. I tried to drop the queue size to a small number and the planner mm_per_line_segment also to a short distance. however it still seems to finish out the g move before stopping. Does anyone have any idea for how to create a quick feed hold button? I don't need this to be a kill switch as i already have one on the power in. Thanks
You are going the right way about this : you should make sure the queue only contains small blocks, and then it should stop very fast.
With blocks that are 0.1mm, a 32block queue should stop in about 3.2mm. That could easily be made much smaller.
I'm not sure what's going on if you tried this and it doesn't work. It definitely shouldn't be "waiting for the gcode move before stopping", that's not at all how it works.
Are you using the latest version of the firmware ?