changing bed temp rate of change

Iamturbo1978

Hello all,

I just got my Duet2 WiFi, loaded with RRF 3.2

Everything is going great except my print bed faults out because it is taking to long to heat up because I have a very thick print bed (9mm thick, MIC6, freebee).

Error: Heater 0 fault: temperature rising much more slowly than the expected 1.8°C/sec

I didnt have this kind if problem with RRF 2.0

I did try M570 H0 P30 T15 just to see what would happen. Same thing happened in the same amount of time.

I need to find a way to change the temperature rate of change to a lower value.

Ive reviewed over all the Gcodes, and I couldnt find anything (I could have missed it).

Could someone please point me on how I can change the 1.8c/sec rate of change?

Thank you for any support you can offer.

Phaedrux

You need to PID tune your bed to give the firmware an idea of how long it takes in reality.

M303 H0 Swhatevertemp. When it's done, use M500 to save the results to config-override.g and add M501 to the end of config.g to load those saved values at power on.

The tuning algorithm is changed in 3.2. The process can take quite a while on beds with a lot of mass, so be patient.

https://duet3d.dozuki.com/Wiki/Tuning_the_heater_temperature_control

Iamturbo1978

@Phaedrux wonderful. I will give that a try. I couldn't use PID tuning for my last setup, that is why I didn't even consider tuning it. Thank you for the help.

Pillccia

Hello
I am new, I also bought a duet wifi, and loaded FRW 3.2.
also I have the same problem, I have done the pid several times, asked m307 h0 to follow m500, reset at the next restart I get the same error again.
WRONG I something?
Machine stopped on the table, and I can't get it printed

Phaedrux

@Pillccia M303 H0 S60 to tune the bed to 60c. It may take some time to complete. When finished, then send M500 to save, and add M501 to the end of config.g

Veti

@Pillccia said in changing bed temp rate of change:

m500

do you have a M501 in you config?

Pillccia

@Veti yes I have read various forums, and it is a line that I have added in config.g.
In my stupidity, I doubt that I don't take M500, as every m307 I do, the basic and varied results are identical.

Pillccia

@Phaedrux I tried again to bring the m303 to 60 ° with the command.
with m307 I have the data but as I said, I have always noticed the same, saved and reset.
Same error in normal set (0.4 ° / sec).

or

Phaedrux

@Pillccia Please start a new thread for your issue.

Can you post your config.g?
Can you send M122 and post the results?
Can you send M98 P"config.g" and post the results?

Pillccia

would it be better to go back to FW 2.05? from the mecatronic switch to duet I have not yet printed anything, I'm curious to see how it works