wrong PID values are stored when using autotune

[Loki44]

PID autotune kept not working for me, so I monitored it via repetier host and noticed this:

15:17:41.353 : bias: 141 d: 113 min: 239.00 max: 250.31 15:17:41.353 : Ku: 25.44 Tu: 30.70 15:17:41.353 : Classic PID 15:17:41.353 : Kp: 15.26 15:17:41.353 : Ki: 0.99 15:17:41.356 : Kd: 58.58

15:18:12.559 : bias: 141 d: 113 min: 239.50 max: 250.63 15:18:12.563 : Ku: 25.87 Tu: 31.23 15:18:12.563 : Classic PID 15:18:12.563 : Kp: 15.52 15:18:12.563 : Ki: 0.99 15:18:12.563 : Kd: 60.58

15:18:42.559 : bias: 142 d: 112 min: 239.33 max: 250.31 15:18:42.563 : Ku: 25.98 Tu: 30.01 15:18:42.563 : Classic PID 15:18:42.563 : Kp: 15.59 15:18:42.563 : Ki: 1.04 15:18:42.563 : Kd: 58.48

15:19:12.362 : bias: 139 d: 115 min: 240.16 max: 250.16 15:19:12.362 : Ku: 29.28 Tu: 29.82 15:19:12.366 : Classic PID 15:19:12.366 : Kp: 17.57 15:19:12.366 : Ki: 1.18 15:19:12.366 : Kd: 65.49

The penultimate values it generates work well, but something seems to go wrong with the final values that are generated.

[EldRick]

I have also experienced this issue. After PID setting using 16.08 firmware, the extruder temp would soar 8C over setpoint initially. I used Printrun to run the PID tuning, and the result is much more satisfactory, with little swing during printing..