Closed Triodes closed 3 days ago
I just tested it locally and it does not fix the issue with the other plugin (PrintTimeGenius). But it might still be a good idea to use an existing valid GCODE command instead.
Oh boy :D My idea was that these commands are filtered out and don't reach the printer.... So the M117 still doesn't solve the issue with the PTG plugin? How come? It should be able to process a M117, right?
I can rewrite it to use M118 (serial print), needs a bit more than your change, but if PTG can't handle that I'm not sure what to do
Closing in favor of #84
Since the latest update it seems that the plugin adds several commands to the uploaded GCODE files with the preprocessor hook.
Commands I have found are:
These are not valid GCODE commands and it seems they cause other preprocessing plugins to fail. One of them is the PrintTimeGenius plugin which completely screws up its estimates because of these commands. This PR uses the M117 Command with a message that starts with the original command. I.e.:
From what I could tell this should not impact the functionality of the plugin.
Lemme know if you agree!
Kind regards, Aron (Triodes)