I’m chasing down some gremlins after converting to the SLB and gSender 1.4.12.
Running the Verify Job feature to troubleshoot an Error 1 (per the Sienci suggestions on the grbl Alarms & Errors page) using a 153k gcode file generated in Fusion/grbl post processor and the “warn if invalid line detected” option enabled in gSender.
When I click Verify Job the console quickly runs to the end of the code giving me an OK ( I can scroll up and see the M30 entry) but the visualizer slowly plots the toolpath in yellow then “runs” it realtime to completion (4m 22s) and never closes the process. The Stop Job button is the only active item on the screen, clicking it returns to the normally seen screen.
Can I confidently assume gSender has found no errors when it outputs the [MSG:Pgm end] line and disregard the stuck visualizer display?