Nico Tonnhofer
Nico Tonnhofer
One idea. I test this code on a 32bit-board. So maybe this line in heater.c needs a change: `uint16_t Ku = (heaters_runtime[h].d
@Traumflug I will make a patch. To get the PID-values you need one extra value. The tick-time of your heater. On the current master it is 10ms. We are working...
Maybe I'm again wrong with the units. I need to sleep now and will verify my formulas later. Edit: Don't try unit conversion after 11pm, tired and with dimmed light.
for 250ms-heater-tick: P = DEFAULT_P = 0.6 \* Ku \* PID_SCALE / 128 I = DEFAULT_I = 64 \* P / Tu ~~for D I have a mental block with...
Did you set PID_MAX to 255? Else it could be not reach the target temperature. This is a feature I want to add later for high power hotends (using 12V...
[TH_COUNTS](https://github.com/Traumflug/Teacup_Firmware/blob/master/config/printer.mendel.h#L294) But on the current master and experimental, the heater tick is 10ms. So the calculations above don't count. You could also try the latests commits in heaters_intervals.
> I think this can go away Yes, when we take the new 250ms-interval-code.
I found some time to test this code. Issues currently, the temperature values are too rough. For Ku we calculate the temperature difference of min and max. This value could...
Yes, it's wrong for 9.7 fixpoint. But correct is: `Ku = (d
L # 3 I'm using often for fast smoothing excel tables. with `smooth = (new_val + (x - 1) * old_smooth) / x`