If you have a good-working start- and endcode in Cura I see no reason to use the start/endcode in Octoprint.
The only part I use is "After printjob is cancelled" to force Octoprint sending the normal Endsequence when I cancel a printjob ...
-
1
Recommended Posts
tinkergnome 929
UltiGCode uses volumetric e-values, i assume, that you have changed the GCode-Flavor in Cura to "Reprap/Marlin", right?
The remaining problem is, that Octoprint has (obviously) no clue about the temperatures that you have defined in Cura (as Mark Walker said: this part is executed after the start script from Octoprint).
You can add values for M109 and M190 to your Octoprint script, but only with fixed values that you have to change for different materials.
As an alternative: you can (pre-) heat buildplate and nozzle manually with Octoprint before you start the print.
But that's sooo inconvenient..., and i'm still not sure about your intention...?
It's so much easier to use the start/end-code from within the slicer.
Link to post
Share on other sites
Nicolinux 288
Yes I did set to regular Reprap/Marlin.
And you are right - manually heating up defeats the purpose of having a remote device taking care of the print. If I resort to that I could as well walk up to the printer and start the print from the sd card.
Maybe I'll do something in between. Like set a fixed value in OctoPrint and let the gcode heatup value override it when the print begins. It will only break when the difference between my fixed temp and the gcode temp differ greatly, but ok, you can't have it all
Link to post
Share on other sites