Open nebnes opened 7 years ago
Do you know what GCODE commands were sent to GRBL at the time? Could you turn on the "Log communication to serial.log" function in OctoPrint and share what gcode was sent just before the errors, and how far into the gcode it was?
Sounds like some invalid GCODE was received, see the table on this page: https://github.com/grbl/grbl/wiki/Interfacing-with-Grbl
(search for Invalid gcode ID
)
I'm also wondering if it would be possible to upgrade to GRBL 1.1 as well?
The log before the errors :
Send: G2 X201.31 Y326.5246 I77.5788 J-161.7601
Recv: ok
Send: G2 X230.2082 Y331.9844 I43.59 J-151.5111
Recv: ok
Send: G2 X252.0542 Y331.6143 I9.2515 J-98.8446
Recv: ok
Send: ?$G
Send: G2 X270.9935 Y325.0176 I-6.1615 J-48.176
Recv: <Run,MPos:309.852,341.943,0.000,WPos:229.852,331.943,0.000>
Send: G2 X283.9841 Y311.9214 I-19.5485 J-32.3818
Recv: [G2 G54 G17 G21 G90 G94 M0 M3 M9 T0 F3000. S180.]
Recv: ok
Send: G2 X293.0699 Y283.9472 I-57.7185 J-34.2093
Recv: ok
Send: G2 X295.2987 Y219.9787 I-547.4761 J-51.0978
Recv: ok
Send: ?$G
Send: G3 X299.1993 Y199.5613 I49.3397 J-1.1552
Recv: <Run,MPos:354.814,332.369,0.000,WPos:274.814,322.369,0.000>
Send: G3 X305.0305 Y193.3981 I11.1832 J4.7407
Recv: ok
Send: G3 X316.3224 Y191.5788 I8.623 J17.5677
Recv: ok
Send: G3 X329.5573 Y194.9534 I-8.2706 J60.0764
Recv: [G2 G54 G17 G21 G90 G94 M0 M3 M9 T0 F3000. S180.]
Recv: ok
Send: G3 X359.2102 Y207.5437 I-146.468 J386.18
Recv: ok
Send: ?$G
Recv: error: Invalid gcode ID:24
WARNING! Received an error from the printer's firmware, ignoring that as configured but you might want to investigate what happened here! Error: Invalid gcode ID:24\x0d\x0a
Recv: error: Invalid gcode ID:33
WARNING! Received an error from the printer's firmware, ignoring that as configured but you might want to investigate what happened here! Error: Invalid gcode ID:33\x0d\x0a
Send: G3 X371.8407 Y216.7252 I-17.8094 J37.7776
Recv: <Run,MPos:375.454,224.763,0.000,WPos:295.454,214.763,0.000>
Send: G3 X377.4425 Y226.1746 I-18.4217 J17.3059
Recv: error: Expected command letter
WARNING! Received an error from the printer's firmware, ignoring that as configured but you might want to investigate what happened here! Error: Expected command letter\x0d\x0a
Recv: error: Invalid gcode ID:33
WARNING! Received an error from the printer's firmware, ignoring that as configured but you might want to investigate what happened here! Error: Invalid gcode ID:33\x0d\x0a
Recv: error: Invalid gcode ID:33
WARNING! Received an error from the printer's firmware, ignoring that as configured but you might want to investigate what happened here! Error: Invalid gcode ID:33\x0d\x0a
I use grbl 0.9 because I need a servo motor on the z-axis ( https://github.com/robottini/grbl-servo ).
Sounds like the buffers are getting overflowed. It's possible that might be related to the "temperature" poll? Could you try changing the temperature poll interval to be something very large and see if its more stable?
I know I'm resurrecting the dead here, but I was having the same issue, and implemented this solution and it worked. I set the polling interval to 86400 seconds (once per day) and have no issues.
using grbl 1.1e and some random chinese board with arduino nano
The process stops after the following errors in the terminal. I use grbl 0.9 (the cnc works fine with the grbl sender "Rabbit Mill")
Recv: error: Expected command letter
Recv: error: Invalid gcode ID:33 WARNING! Received an error from the printer's firmware, ignoring that as configured but you might want to investigate what happened here! Error: Invalid gcode ID:33\x0d\x0a
Recv: error: Invalid gcode ID:24 WARNING! Received an error from the printer's firmware, ignoring that as configured but you might want to investigate what happened here! Error: Invalid gcode ID:24\x0d\x0a