I have started working with F Engrave a bit and one of the problems I ran into is that the G-Code created by F Engrave contains command lines over 50 characters long. The documentation from F Engrave suggests that changing the #3 value in GRBL from 50 to 80 will fix the command length problem.
I have also run into other programs that generate long command lines (usually comments)
My question is will changing the #3 value to 80 have any negative impact on Easel?
Select the āDisable Variablesā check box in the F-Engrave Settings window
un-select the āEnable Arc Fittingā check box in the F-Engrave Settings window
Use F-Engrave version 1.34 or higher
āError while starting file stream: Command #3 too long: (55 > 50) ā(Settings used in f-engrave when this file was created)ā ā
GRBL Error
This error is generated because the #3 value set in GRBL is 50 and it need to be increased to allow longer g-code lines to be processed. Setting the #3 value in GRBL to 80 should be sufficient to accommodate the g-code generated by F-Engrave. (Thanks to Barry W. for this information)
I donāt think that you should change the grbl value. The recent versions of Grbl use a different settings map. Look at the most recent one here. Configuring Grbl v0.9 Ā· grbl/grbl Wiki Ā· GitHub
You can configure the line length as a compile option in the Grbl source, but I donāt think it can really be increased because the Arduino memory is so limited.
There is no #3 option for Grbl. It has a hard limit of 50 or 70 (79) characters per line due to limitations of the Arduinoās memory capacity. Moreover, Grbl uses $ to indicate its settings options.
Iām getting this error now with UGS nightly build (9/2017) , v1.1f of firmware on a 3d carve. Iāve seen this occasionally, and just retrying it a few times seems to āfixā it, but now I canāt get past it.
The error was a :NULL. I moved from the Platform (.exe) to the .bat script which calls the .java script and itās working. Go figure⦠Platform vs. Classic. Classic works and Platform doesnāt.