Yeah . Ran into this too. For newbies (like David and me) it is annoying that before anything works, you have to delve into the GCODE figure out what G64 is supposed to do determine that it shouldn't matter, and then A) edit the generated GCODE file and then B) find where in the config that command is coming from.
From a usability perspective it would've been better to have the config file sparse, and allow people who know what they need/want add stuff to the config.
Alternatives are to by default output the "sometimes not supported" commands, but commented out. With an additional comment: If you wish to enable this go to options->postprocessor configuration.
An other alternative is to have a 3018 config file that gets selected when at first startup the user answers that he/she has a 3018....
Mine also didn't grok the M8 IIRC....
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Did you try to change the postprocessor to get rid of the G64 code?
Yeah . Ran into this too. For newbies (like David and me) it is annoying that before anything works, you have to delve into the GCODE figure out what G64 is supposed to do determine that it shouldn't matter, and then A) edit the generated GCODE file and then B) find where in the config that command is coming from.
From a usability perspective it would've been better to have the config file sparse, and allow people who know what they need/want add stuff to the config.
Alternatives are to by default output the "sometimes not supported" commands, but commented out. With an additional comment: If you wish to enable this go to options->postprocessor configuration.
An other alternative is to have a 3018 config file that gets selected when at first startup the user answers that he/she has a 3018....
Mine also didn't grok the M8 IIRC....
If you have a working config. i propose to add it to the WIKI. This would help other users to have a working one ...
Ticket will be closed as discussion stopped on that.