Minor Bug: Autotune missing Phase 2 report
-
Running 3.3beta2.
Screen grab from autotuning the bed:
14/04/2021, 09:05:26 Auto tuning heater 0 completed after 3 idle and 5 tuning cycles in 1659 seconds. This heater needs the following M307 command: M307 H0 R0.133 C686.2 D3.30 S1.00 V12.1 Send M500 to save this command in config-override.g 14/04/2021, 08:54:16 Auto tune starting phase 4, tuning with fan off 14/04/2021, 08:44:14 Auto tune starting phase 3, heating system settling 14/04/2021, 08:37:52 Auto tune starting phase 1, heater on 14/04/2021, 08:37:47 M303 H0 S60 Auto tuning heater 0 using target temperature 60.0°C and PWM 1.00 - do not leave printer unattended
For the record previous autotune with the v0.6 was "M307 H0 A142.0 C810.5 D3.5 S1.00 V0.0 B0"
-
@doctrucker its always been like that I think.
It also tells you the fan is now off, even though that plays no part in the bed tuning process -
@jay_s_uk maybe on RRF2/3 but not 1:
M303 H1 S200 22:33:58 Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 473C. Auto tune heater 1 completed in 119 sec Use M307 H1 to see the result, or M500 to save the result in config-override.g 22:32:52 Auto tune phase 3, peak temperature was 211.4 22:32:45 Auto tune phase 2, heater off 22:32:04 Auto tune phase 1, heater on 22:31:58 M303 H1 S200 Auto tuning heater 1 using target temperature 200.0°C and PWM 1.00 - do not leave printer unattended
-
@doctrucker ah, i will tighten that "always been" to its always been like this with the new tuning algorithm that came in as part of 3.2
-
@jay_s_uk fair enough! It looks like an oversight rather than intentional.
-
@doctrucker, I think I have already fixed this in the 3.3beta source code.
-
@dc42 this was 3.3beta2, I guess you mean since that release?
-
@doctrucker said in Minor Bug: Autotune missing Phase 2 report:
@dc42 this was 3.3beta2, I guess you mean since that release?
Yes.