Temperatures totally wrong 3.4 RC

Hernicz

@droftarts Yes, that's it.

Hernicz

@achrn I also have 50W heater running at 30V, but Voltage was taken to account.

I'm not the only one with this issue. Are you running on SBC or standalone?

achrn

I'm not claiming you're not having problems, I'm saying the assertions that "If you have a copper heatblock, at initial heatup it way overshots temp" and "when you use copper, heatup just doesn't slow down" are not universally true.

I don't understand why voltage is relevant, if you tune at (near) the voltage you run at (and if you don't, then I think you should).

Hernicz

@achrn I mean after tuning the copper heatblock, heating up from room temp overshot it until triggered a heater fault. Like it didn't know when to slow down heating to reach target temp. It seems like PID tuning doesn't tune for heat up from ambient, only to hold target (yet it cannot even do that if you calibrate tool with cooling fan)

It may not be universally true, but I don't think any PID tuned heater should behave like this. The whole point of PID tuning is to eliminate this (and have a steady target temp).

I had a copper volcano heatblock with a 50W heater and copper nozzle. I don't have issues with aluminium heatblock.

SBC as well. Voltage is just additional info, may not be relevant.

jensus11

I wrote down my values.
What can I do to get rid of these fluctuations?

Bildschirmfoto 2022-03-06 um 22.36.22.png

Bildschirmfoto 2022-03-06 um 22.37.46.png

Bildschirmfoto 2022-03-06 um 22.40.38.png

![b57d10b4-caa6-4195-a515-255a82b97208-image.png](/assets/uploads/files/1646602950778-b57d10b4-caa6-4195-a515-255a82b97208-image.png) code_text
```3.4-b5

M307 H1
Heater 1 model: heating rate 3.149, cooling time constant 114.7/93.3, dead time 6.85, max PWM 1.00, calibration voltage 24.0, mode PID Computed PID parameters: setpoint change: P8.3, I0.295, D39.7, load change: P8.3, I0.538, D39.7
M307 H1 B0 R3.149 C114.7:93.3 D6.85 S1.00 V24.0

M307 H2
Heater 2 model: heating rate 3.054, cooling time constant 146.3/125.6, dead time 6.25, max PWM 1.00, calibration voltage 24.0, mode PID Computed PID parameters: setpoint change: P9.4, I0.310, D40.9, load change: P9.4, I0.609, D40.9
M307 H2 B0 R3.054 C146.3:125.6 D6.25 S1.00 V24.0

config-override.g
M307 H1 R3.149 C114.677:93.258 D6.85 S1.00 V24.0 B0 I0
M307 H2 R3.054 C146.250:125.643 D6.25 S1.00 V24.0 B0 I0

3.4-rc2

M307 H1
Heater 1: heating rate 3.149, cooling rate 0.525/0.172, dead time 6.85, max PWM 1.00, mode PID, calibrated at 24.0V Predicted max temperature rise 377°C PID parameters: heating P8.3 I0.226 D39.7, steady P8.3 I0.458 D39.7
 M307 H1 R3.149 K0.525:0.172 D6.85 E1.35 S1.00 B0 V24.0

M307 H2
Heater 2: heating rate 3.025, cooling rate 0.524/0.121, dead time 6.38, max PWM 1.00, mode PID, calibrated at 24.0V Predicted max temperature rise 366°C PID parameters: heating P9.3 I0.258 D41.3, steady P9.3 I0.537 D41.3
M307 H2 R3.025 K0.524:0.121 D6.38 E1.35 S1.00 B0 V24.0

config-override.g 
M307 H1 R3.149 K0.525:0.172 D6.85 E1.35 S1.00 B0 V24.0
M307 H2 R3.025 K0.524:0.121 D6.38 E1.35 S1.00 B0 V24.0

Hernicz

@jensus11 First, if you have the values in config.g then remove them from config-override.g

Then simply delete the Kx.xxx:x.xxx parameter with its values.

jensus11

@Hernicz
M307 H1 R3.149 K0.525:0.172 D6.85 E1.35 S1.00 B0 V24.0

you mean like that?

M307 H1 R3.149 D6.85 E1.35 S1.00 B0 V24.0

droftarts

@jensus11 said in Temperatures totally wrong 3.4 RC:

@Hernicz
M307 H1 R3.149 K0.525:0.172 D6.85 E1.35 S1.00 B0 V24.0
you mean like that?
M307 H1 R3.149 D6.85 E1.35 S1.00 B0 V24.0

No, leave in the first K parameter, so like:

M307 H1 R3.149 K0.525 D6.85 E1.35 S1.00 B0 V24.0

Ian

droftarts

@jensus11 Thanks for this info, I've highlighted it for @dc42 's attention. It shows that the PID values are computed pretty much the same in both cases. Just to be clear, did you have heater temperature fluctuations in 3.4-b5?

Ian

jensus11

I don't think that was the case in 3.4-b5. It is not possible for me to print a Temptower. The temperature is just fluctuating. With other parts I noticed that the temperature increases in the first layer of the top layer after the infill part.
If I reduced the Bridges fan speed, it's better. I think when the part fan changes fast and slow the fluctuating start. If the partfan is constant, the temperature is also constant.

Tell me what to do to help.

100% Bridges fan speed in my test print
Bildschirmfoto 2022-03-07 um 13.35.41.png

50% Bridges fan speed in my test print
Bildschirmfoto 2022-03-07 um 13.36.16.png

should i upload the gcodes?

jensus11

It really must be the transition from infill to top layer. If I only print the botton and then the top layer, it's ok. Exactly the same if I only print perimeter.

dc42

@jensus11 please try with the second K parameter in the M307 command missing or set to zero, as @droftarts suggested. This will help me to pin down the problem.

dc42

I am running tests on one of my machines with a new hot end installed, and although the behaviour I am seeing is nothing like as bad as reported in this thread, it is evident to me that the heater feedforward when fan PWM is changed is not working correctly even though the M307 parameters appear to be correct. I will continue investigating tomorrow.

dc42

I just found the bug that is causing this. I will provide updated RRF builds tomorrow or Wednesday. Meanwhile you can set the second M307 K value to zero to disable feedforward.

jensus11

@dc42
I tested it without the second K value. It's better but not good yet. With K0 it looks very good.

dc42

@jensus11 @Hernicz @resam @TheDragonLord I've put 3.4.0rc2+2 binaries at https://www.dropbox.com/sh/amtiizdcylnuaye/AAA4hzXFvU0RMOSDtdT37HFua?dl=0 for testing. These should fix this issue. Although the changes are minor, please test them with care.

A Former User

@dc42 said in Temperatures totally wrong 3.4 RC:

@jensus11 @Hernicz @resam @TheDragonLord I've put 3.4.0rc2+2 binaries at https://www.dropbox.com/sh/amtiizdcylnuaye/AAA4hzXFvU0RMOSDtdT37HFua?dl=0 for testing. These should fix this issue. Although the changes are minor, please test them with care.

@dc42 said in Temperatures totally wrong 3.4 RC:

@jensus11 @Hernicz @resam @TheDragonLord I've put 3.4.0rc2+2 binaries at https://www.dropbox.com/sh/amtiizdcylnuaye/AAA4hzXFvU0RMOSDtdT37HFua?dl=0 for testing. These should fix this issue. Although the changes are minor, please test them with care.

ok, thanks

bberger

Thank you guys for this thread. Up until a few moments ago I was sure it was in my head and been like this forever and expected.

It wasn't as bad as some state here, but at certain temperatures RRF tried to keep the "wrong temperature". It's within a few degrees up until 215C. At 215C and above it tries to hold ~230C - and that quite for quite some time - before going down to 220C. It seems like it tried to over-compensate at that temperature.

For reference here are my tuning params (Rapido hotend, HF configuration, Gdstime 5015 fan - 12V running @24V @100%):
; Heater model parameters
M307 H0 R0.234 K0.184:0.000 D0.80 E1.00 S1.00 B0
M307 H1 R4.502 K0.516:0.459 D5.09 E1.35 S1.00 B0 V23.9

I'll report back it it looks better on the 3.4 RC2+2, but I highly suspect it might.

jensus11

@dc42 Unfortunately I can't test it. I have to wait until gloomyandy releases a new FW.

ÖrjanE

@dc42 I just tested 3.4rc2+2 and can confirm that, at least for me, it behaves much better controlling the hotend temperature.

I have a regular E3Dv6 hotend and a Maestro card. With 3.4rc2 it did overcompensate substantially for the fan and did not return to the target temperature after a fan burst. It often remained over 4 degrees above target.

With 3.4rc2+2 it seems to compensate perfectly for varying fan speeds. I had a slight overshoot (ca 1.5 degrees) at initial heatup, and a slight undershoot (ca 1.5 degrees) when the fan first started. For the rest of the print, it stayed within +-0.2 degrees of target. I have not yet done a new PID tuning with the new firmware,

/Ö