I am currently running a program involving mostly 3D scalloping operation generated from Fusion 360 CAM. The program is 9,959 lines of gcode (I’ve successfully run programs with 11-12K lines of gcode in the past). About half way through the program the SPJS Queue goes down to 0 and it stops running. I have tried the following without being able to complete the program:
Active feed hold and cycle start repeatedly
Clear the serial port console and cycle start
Stop G-code, set new start position later in the program and run g-code
Any help on this would be appreciated.
I am using the following:
Browser: Google Chrome
IOS: OS X El Capitan 10.11.6
Grbl: 0.9j
JSON server: Running on raspbian on raspberry pi 3
What are your settings in the cog wheel for Gcode widget? Meaning, how many lines do you send at a time and at what interval? The defaults are usually good. A stop in sending is not going to be SPJS. It will be the browser. In your screenshot you’ve sent 4940 lines and do have 5004 to be sent. If it just stops you could try the pause/unpause button as that would have it keep sending again, but that should not happen. M6 tool change lines also have it stop. A “chilipeppr pause” in a comment also has it stop, but can’t imagine you have that in your comments.
when i was actively trying to mill with grbl (both 0.9x and 1.1x) i saw drop outs the whole time, @jlauer . Possibly an issue with the 'duino (including the usb to serial chip). Whatever the culprit, checking the verbose output of SJPS was definitely a good thing as it showed the disconnects. On a reconnect the widgets clear down the queue and the board is reset (of course) so you’ve lost position anyway.
I had tried pause/unpause during the run seen in the screenshot, but this would allow the program to run for a little bit and would stop again (queue would fill no more than 100 lines then go back down to zero).
I did a dry run of the program since then with verbose mode on; however, too many lines were being filled into the serial port console. So I disabled the console from updating, and the program ran completely without stopping.
When I get back on the computer I will check the cog wheel settings on gcode widget.
Actually, somebody else just reported this. I do think this is the Grbl buffer in SPJS that can possibly deadlock. The best approach is for somebody to take the TinyG buffer and copy it to the Grbl buffer, but change to look for the ok rather than the r:{} that TinyG looks for.
