UM2+ - Wait for Nozzle Heat Up doesn't work

[LePaul 354]

See Github ticket here

 

If you have "Wait for Nozzle heatup" checked in 5.8 and upgrade to 5.9, Cura doesn't tick that setting checkbox for you.

 

Also, if you do tick it off and use gcode flavor Marlin, as I do since I use Octoprint, the print will start after bed is to temperature but not the nozzle.

 

We had this problem a few versions back and it seems to have returned.

 

@Torgeir - I know you're a UM2 guru - letting you know!

 

[Slashee_the_Cow 494]

This seems like one of the times I'd write a single purpose post-processor for as a workaround for a bug. I've already done that... 3 or 4 times.

 

(That's also an offer if you're interested)

[Torgeir 280]

Hi @LePaul,

 

There is one thing we both are using and this is Marlin and Ultimaker 2 -(gcode flavor).

I did use the UM2E+ with the printer controls. However, just made some experimenting with Raspberry pi 4 and Octoprint -about 3 year ago..

Are you using Octoprint from Windows 11 -or? 

Did you upgrade "overwriting" the ver. 5.8?

 

Normally when we look at this setting, the gcode flavor default are: Ultimaker 2.

In this "mode", we can only tick off "Enable Nozzle Temperature Control" in printer menu and enabled Cura to "control" the temperature settings for our model.

(Note, in an UM2 both, bed and nozzle temperature are controlled from printers control panel, not from Cura in gcode.)

If we select gcode flavor to "Marlin", a new line pops up in the printer menu; "Waiting Nozzle Heating" default / cancel and tick off mark present. (Needed cause the nozzle heath level "ready" are not controlled anymore from the printer panel.)

 

(Note: The printer menu are not made by Cura, but made for Cura by @ahoeben. This menu extension can be found at Ultimaker's Marked place found in the right upper corner of Cura. The name of this "plugin" is "Printer Setting" ver. 3.6.0

You'll find this plugin at the "very" bottom of the "plugin" menu.)

 

I've been testing both versions Cura 5.8.1 and 5.9.0. But find no difference between those two versions functionality..

For the record, I'm using Win 10 p and using the D drive for most programs/applications.

Each version of Cura is stored in its own directories and I always want to keep the latest good version as upgrade often can bring a big surprise.  Been there, done that -several times..

 

I would try to install a new version of Cura 5.9.0, but first -you may also want to save and remove the Cura definition file in the C drive as there could be some "issues" in here.  (Cura will make a new file.)

 

Well, -that's all I'll think about so far.

 

Thanks

Torgeir

[LePaul 354]

Hi

 

Octoprint is running on a Pi 3b

 

My frustration is that I am not doing anything different. 

 

Every couple of upgrades breaks this functionality for me.

 

I let the 5.9 install do a "Complete" install, based on the installation wizard.

 

This has been my Ultimaker 2+ machine settings for quite some time...

 

Printer Settings via Machie Tools Plug-in

 

 

 

Edited November 25 by LePaul

[Torgeir 280]

Hi Paul.

 

Okay, I understand.

As I've tried your project settings, starting with another printers setting I've managed to see that Cura did not tick off the check box for you.. So then selected G-code flavor to Ultimaker 2 and find the "default start" G-code was changed to same as used for Marlin.

 

I'd just deleted this start part and then it worked (default verification flag(?). I'm not sure about anything here as there is a fault in the help menu pop up function (for the G-code flavor select "button"), flicker very fast on/off and not possible to see.

 

However, the default start G-code flavor for Ultimaker 2 are:

G0 F3000 Y50 ;avoid prime blob

 

How did it go with the new installation of Cura?

Will the Raspberry Pi work with an old sliced gcode file?

 

I'll think this are  a problem for the Cura team..

 

Maybe revert back to previous version of Cura.

 

Torgeir

[LePaul 354]

Hi,

 

I've been monitoring the Github ticket for updates.  

 

I've rolled back to 5.8.1

 

I need to stop being eager to update to new versions.  Unfortunately every other update seems to blow something up that worked previously.  I've begun to use a competitor's slicer.

 

[Slashee_the_Cow 494]

8 hours ago, LePaul said:

I need to stop being eager to update to new versions.  Unfortunately every other update seems to blow something up that worked previously.  I've begun to use a competitor's slicer.

Please don't leave us 😢

[LePaul 354]

On 11/28/2024 at 1:54 AM, Slashee_the_Cow said:

Please don't leave us 😢

 

Well at some point, when the software repeatedly fails you many times over the years, you have to consider the competition's offerings.

 

I like Cura but it is obvious to me that it is starting to fall behind.  Slicers like Orca, PrusaSlicer and the Bambu Labs version of it are being adopted by new machines out there.   Each has their pros and cons.  

 

I'm not trying hurt any feelings here.  I've been with Cura since I started out in 2013.  I like Ultimaker and the Cura devs.  I'm just finding I have to resort to exploring other software to print reliably, which is the most important thing for me, both at my profession and my hobby printing.

[Slashee_the_Cow 494]

6 hours ago, LePaul said:

I'm just finding I have to resort to exploring other software to print reliably, which is the most important thing for me, both at my profession and my hobby printing.

@Dustin Maybe you need to put the idea in the heads of the higher ups that there should be an LTS version of Cura. Unless there already is one in enterprise-land I don't know about. But "bug fixes and new printer definitions only" updates are a lot less likely to break things (although you do miss out on new features if they're added, but ideally... at least you know it'll slice without problems).

[LePaul 354]

They do have a paid/Enterprise version - I have that at work as were part of their Academy program (maybe that name has changed).