G-Code output too long for GRBL and LinuxCNC about hf2gcode HOT 4 CLOSED

Hi koppi,
the line you pasted is just a comment. I can't check it right now but does GRBL and LinuxCNC really fail if a comment (which they just should ignore) is longer than some preset limit? Of course you can call hf2gcode with "-m" (Generate minimalistic g-code, suppress comments) to suppress any comments which should solve your problem.

from hf2gcode.

Both GRBL and the NIST interpreter fail if you send them this long comment. I still like to have all these comments in the G-Code file, so the -m option is a work-around that does however not really solve the problem.

from hf2gcode.

Hi Koppi,
for what purpose do you want to have the ( text=" comments?
I merely added it as debugging feature. How do you expect the line is splitted if it is longer than 50 chars?

( text="123456789012345678901234567890123456789"... )
( "012345678901234567890123456789012345678901234"... )
( "567890123456789012345678901234567890123456789"... )
( "012345678901234567890123456789012345678901234"... )
( "5678901234567890123456789012345678901234567890"... )
( "12345678901234567890123456" )

Do you want to parse the "text" in comments or do you just want to keep them as info?

from hf2gcode.

I just want to keep the text in the comments as info, so a line-split like you showed above would be a good work-around for LinuxCNC and GRBL.

from hf2gcode.