Open KenLucke opened 3 years ago
Forgot to say, it's definitely this plugin. Disabling or removing it eliminates the issue, reinstalling or reenabling it causes it to return on the next large file.
I am also seeing a checksum error on N100. I will investigate.
Oh, looks like the virtual printer has a default forced error on N100
! For testing, I guess.
So that's why I have an errors on 100, 105, 110, 115. Funny!
Anyway, your log shows that it was trying to print N100 but N27 had a checksum error and by the time the printer got to N100, N27 was no longer in the buffer. Bummer. I wish that your log went just a little little bit more back so I could see that N27 but it looks like you started at N28.
Another thing worth checking is what if you just lop off the end of the file to see if the size is really the cause.
By the way, the line numbers in the gcode file aren't the same as the line number in the error. The N
prefix is the line number so what the printer called 27 is just the 27th line of gcode that was sent, not counting the lines that needn't be sent because they are just comments.
So gcode file line 33 is N27. Looks like a plain old string, though, so I don't get how the checksum would be wrong in the first place! That's weird. And it looks like the OctoPrint buffer is too small.
If you had even more of the log, that would help. And the test for file size that I mentioned above.
Not sure where the size break point for the file is where this starts. (See the end for what happens).
This is the file for the code below: https://www.dropbox.com/s/n6vaffrzx461o8u/Control%20Box%20Storage%20Unit%20Final.gcode
Here's the relevant lines from the above file (around lines 27), but the whole file is shown above.