Cura 4.5, Preheat temps are blank.

[cmwoodman 0]

Using a Robo 3D R1+, connected with Octoprint. 

I have updated octoprint to 1.40. 

Connect To Octoprint plugin version is:  3.5.12

 

Just started using 4.5 and noticed 2 things in paticular:

 

1. the preheat box is now blank when i go to the monitor page.

- Previously this was populated by whatever temperatures i had set on my material (i thought) now i have to put it in manually. 

 

2. when i put the desired temp in it will send it to the printer BUT it will not give an accurate reading of the Extruder OR Bed temperatures any more once it has sent the temperature.  it will show what the target temp is but will not give the current temp of the Extruder or the Bed.

 

Am i missing a new config with this new version of Cura to get the preheat and current temps to update correctly?

[ahoeben 1,981]

1. This is a known bug that has been fixed for Cura 4.6

2. This I did not know about, and will look in to.

[dmtrotter 0]

I have this issue with the latest version, 4.10. I also had this issue in the previous version (4.9.1). It doesn't matter if I change from the profile default of 200 or change it to another setting, as soon as the print job is started, only the bed begins heating. I have to manually set my printer to the desired extruder temp. 

 

Are there any steps I can try to resolve this? I am trying to move to this app and away from the in-house app from the manufacturer. So far, that is really the only issue I have had (outside just needing to pick up more knowledge about it in general). 🙂

I don't mean to hijack, and can submit a bug report if needed. I just wanted to bring it up since I was searching this forum for a solution to this issue. Cheers!

 

Thank you!

Edited July 15, 2021 by dmtrotter
Couldn't seem to get the older version typed correctly (twice!)

[ahoeben 1,981]

On 7/15/2021 at 6:04 AM, dmtrotter said:

I don't mean to hijack, and can submit a bug report if needed.

 

That's probably best. Though the problem mentioned in this thread may seem similar to you, it sounds like it is a different underlying problem (especially since the issue in this thread was a very specific bug that was fixed a year ago).

 

When you report the bug, make sure you include both logs and a project file (File -> Save project...).

Edited July 16, 2021 by ahoeben