Skip to content

Long G-code String Problem #1431

Answered by neophyl
UD551 asked this question in Q&A
Jul 20, 2021 · 1 comments · 1 reply
Discussion options

You must be logged in to vote

Those look like your start/end gcode blocks. If you open up the output gcode at the end of the gcode after all the print moves etc Slicer/PS/Super Slicer stores a copy of all the settings used. Its a pretty handy function that allows you to load /import all the settings from any output gcode.
Your printer firmware should NOT be parsing those as they are after the end and besides they are commented out. Sounds like the firmware on the printer could do with a bug fix. As Slicer has always done this with gcode files it seems strange that its only recently started though.

As this is causing you an issue I can see a couple of possible ways to address it.
-Open an issue here and supply the proj…

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@UD551
Comment options

Answer selected by UD551
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants