That startup code doesn't have code for warming up the bed or the hot end - but Cura should insert that into output gcode automatically if it isn't. As @GregValiant said, it could be an UltiMaker thing.
Could you post a gcode file which has the problem so we can have a look at it?
Hello, first post here for me,
I have the exact same problem, with the same printer (Ultimaker 2+) using Octoprint instread of the stock firmware.
But I've only been having it for the last few days. Everything has been working flawlessly before that.
I can't really remember when I updated my Cura version but I think it could be related.
Here's a snippet of the beginning of a failing print (i.e. waiting for bed temperature but not printhead), sliced yesterday :
M118 E1 OCTOAPP_DISABLE_LAYER_MAXIC ;FLAVOR:Marlin ;TIME:223 ;Filament used: 0.0419893m ;Layer height: 0.15 ;MINX:93.116 ;MINY:93.117 ;MINZ:0.27 ;MAXX:129.884 ;MAXY:129.884 ;MAXZ:1.17 ;TARGET_MACHINE.NAME:Ultimaker 2+ ;Generated with Cura_SteamEngine 5.8.1 M140 S90 M105 M190 S90 M104 S235 M82 ;absolute extrusion mode G21 ;metric values G90 ;absolute positioning M82 ;set extruder to absolute mode M107 ;start with the fan off G28 Z0 ;move Z to bottom endstops G28 X0 Y0 ;move X/Y to endstops G1 X15 Y0 F4000 ;move X/Y to front of printer G1 Z15.0 F9000 ;move the platform to 15mm G92 E0 ;zero the extruded length G1 F200 E30 ;extrude a few mm of feed stock G92 E0 ;zero the extruded length again G1 E-1 F500 ;Retract a little (etc etc etc)
I think the lien to blame is the one near the beginning that reads :
M104 S235
The 235 (°C) in the S235 message is the temperature I configured my hotend to heat to but according to Marlin docs, the M104 message tells it to heat-up and then continue analyzing GCode without waiting for it to get to that temperature. According to me this is not the ways things should go. And this is not the ways things used to go.
Here's a snippet of GCode I sliced a few weeks back, that is working perfectly :
M118 E1 OCTOAPP_DISABLE_LAYER_MAXIC ;FLAVOR:Marlin ;TIME:4444 ;Filament used: 0.659027m ;Layer height: 0.1 ;MINX:72.11 ;MINY:17.47 ;MINZ:0.27 ;MAXX:150.89 ;MAXY:56.25 ;MAXZ:2.37 ;TARGET_MACHINE.NAME:Ultimaker 2+ ;Generated with Cura_SteamEngine 5.7.1 M140 S90 M105 M190 S90 M104 S235 M105 M109 S235 M82 ;absolute extrusion mode G21 ;metric values G90 ;absolute positioning M82 ;set extruder to absolute mode M107 ;start with the fan off G28 Z0 ;move Z to bottom endstops G28 X0 Y0 ;move X/Y to endstops G1 X15 Y0 F4000 ;move X/Y to front of printer G1 Z15.0 F9000 ;move the platform to 15mm G92 E0 ;zero the extruded length G1 F200 E30 ;extrude a few mm of feed stock G92 E0 ;zero the extruded length again G1 E-1 F500 ;Retract a little G1 Y50 F9000 (etc etc etc)
In this one, the same message appears, but it is (nearly) immediately followed by a M109 S235 whichs instructs (again) the hotend to get to 235°C but this time telling it wait until it gets to the specified temperature before proceeding with the rest of the code.
I don't know why this actually change. But the only serious thing I can suspect is the different Cura version.
But then other people should be witnessing this buggy behavior.
Yours,
Jérôme
30 minutes ago, JeromeT said:think the lien to blame is the one near the beginning that reads :
M104 S235
The 235 (°C) in the S235 message is the temperature I configured my hotend to heat to but according to Marlin docs, the M104 message tells it to heat-up and then continue analyzing GCode without waiting for it to get to that temperature. According to me this is not the ways things should go. And this is not the ways things used to go.
You are correct. Without an M109 line it won't actually wait for the hot end to heat up. I'm not sure why it sticks the M105s (report temperature over serial/USB connection) in there. Or why it doesn't just use an M109/M190 (wait for temperature) without bothering with the M104/M140 (set target temperature) immediately before it.
You should probably submit a bug report to make sure the developers are aware (or annoy @GregValiant if someone's already reported it and he has to mark it as a duplicate, either works 😄). Just make sure to include at least all the information you have in your post.
The easiest fix is probably just to modify your startup gcode to include the heating commands. The simple way (which emulates the previous behaviour) would just be to put this at the start of your startup gcode (before everything else):
M190 S{material_bed_temperature_layer_0}
M109 S{material_print_temperature_layer_0}
I could have a guess as to the cause and probably be wrong: 5.7.2 had a bug where it inserted those temperature lines (including the correct M109) even when it shouldn't because the startup gcode already had temperature commands in it, so this might be collateral damage from the fix for that?
@JeromeT an alternative to Slashee's suggestion is that you can also access the setting that is affecting the prepend codes that Cura is inserting.
Go to the MarketPlace (button at the right top corner of the Cura workspace) and load the "Printer Settings" plugin.
After re-starting Cura the new "Printer Settings" group will be at the bottom of the Custom Settings list.
Check "Wait for nozzle heatup". Cura should then add an M109 to the temperature prepends instead of that M104 you are getting now.
1
Yes, I had a Github ticket a little while ago about this same issue. That check box fixed it
The StartUp and Ending Gcodes have been getting a make-over. There was also the bug in 5.7.2 that caused the "Wait for (bed/hot end) heatup" settings to be ignored. That one affected a lot of users.
There is also a lack of consistency in the StartUp and Ending Gcodes that the definition files provide.
For example, Creality will have temperature lines in the StartUp and so the Prepend temperatures aren't required. AnyCubic printers need the prepend heating temperatures. or the print will start with a cold nozzle and bed.
So are the settings handled in the definition file over-rides? Not all the time. It makes it tough on a new user to try to figure out why the "stock" prints work but when they slice with Cura it won't print.
Thank you guys. It indeed looks like a recent and "not totally resolved" issue.
@Slashee_the_Cow : the tip you give here :
20 hours ago, Slashee_the_Cow said:I could have a guess as to the cause and probably be wrong: 5.7.2 had a bug where it inserted those temperature lines (including the correct M109) even when it shouldn't because the startup gcode already had temperature commands in it, so this might be collateral damage from the fix for that?
Is the closest results Google was throwing back at me when trying to solve my issue before posting here. It sounds related to me too. But I can't check it neither.
I might go back to that 5.7.1 version instead of installing a plugin to "solve" that issue. Thanks for the suggestion though @GregValiant.
Yours,
Jérôme
You should seriously consider installing at least a couple of AHoeben/FieldOfView's plugins.
In particular - "Mesh Tools", "Printer Settings" and "Material Settings" are extremely helpful.
1 hour ago, JeromeT said:I might go back to that 5.7.1 version instead of installing a plugin to "solve" that issue. Thanks for the suggestion though @GregValiant.
No need for plugins for it to be fine in 5.8 - just add the lines of gcode I posted earlier to your startup gcode. Though I will second @GregValiant on recommending @ahoeben's plugins.
You would actually be fine on 5.7.2. The bug in that version only affects printers which have temperature commands in their startup gcode, which you don't.
(I do, and because I have too much free time I fixed it by writing a post-processing script that removed the added lines.)
MariMakes posted a topic in UltiMaker Cura,
ArunC posted a topic in UltiMaker 3D printers,
Recommended Posts
GregValiant 1,359
UM printers are different and I don't know the answer here, but maybe @Torgeir knows what the problem is?
Link to post
Share on other sites