My build runs beacon on the shuttle which I have been unable to get to work with the default tool_probe cfg. I wrote some macros using gcode_button I had hoped to use at the end of the drop off/ pickup gcodes to pause if a error was detected. It worked at first then automatically resumed do to what I assume is because of the running tool change script.
I believe the after_change_gcode should work for what I need on the pick up side once I figure out how to call up a specific macro according to the selected tool. However, that just has me wishing for that section to be available in each tool ideally with both a after drop off and after pickup sections. I have no clue beyond some theory how coding works and in turn how difficult it would be to add something like this. Either way thanks for all the work you have already done.
Disregard... Never crossed my mind that I needed to be testing this in a print to see that actual behavior of the pause instead of just doing tool changes.
My build runs beacon on the shuttle which I have been unable to get to work with the default tool_probe cfg. I wrote some macros using gcode_button I had hoped to use at the end of the drop off/ pickup gcodes to pause if a error was detected. It worked at first then automatically resumed do to what I assume is because of the running tool change script.
I believe the after_change_gcode should work for what I need on the pick up side once I figure out how to call up a specific macro according to the selected tool. However, that just has me wishing for that section to be available in each tool ideally with both a after drop off and after pickup sections. I have no clue beyond some theory how coding works and in turn how difficult it would be to add something like this. Either way thanks for all the work you have already done.