DD-LDT-880

Done.

Done.

Done.

Done.

Done.

Done.

Redefined delta temperature to 0.5F to go over the target temperature (i.e., Target Temp + 0.5) to compensate with reduced Feedforward control. We will adjust this as needed based on the testing.

Redefined delta temperature to 0.5F to go over the target temperature (i.e., Target Temp + 0.5) to compensate with reduced Feedforward control. We will adjust this as needed based on the testing.

Recommend 0.0F if control interval is short (like 3 sec) so we don't introduce an initial error to PI controller.

Recommend 0.0F if control interval is short (like 3 sec) so we don't introduce an initial error to PI controller.

If timer set is initialized to FALSE, shouldn't the timer be initialized to zero?

If timer set is initialized to FALSE, shouldn't the timer be initialized to zero?

If you use timer functions to manage sample interval, it is possible to have 10ms jitter. Priority task is initiated every 10ms very accurately, but when code is executed within any given priority ...

If you use timer functions to manage sample interval, it is possible to have 10ms jitter.
Priority task is initiated every 10ms very accurately, but when code is executed within any given priority task interval can vary with position of the code in the task sequence and varying amount of time taken to complete each part of the task sequence from one interval to the next. So it is possible that sometimes you could have the ms timer saying something like 59ms when you would expect 60ms (because it's been 6 times through the 10ms task). In cases like this, you would wait for the next task (so 10ms later).
I think it's safer to use a task interval counter and multiplying the counter by the task interval (10ms).

I took alarm 98 and 99 in my TD branch.

I took alarm 98 and 99 in my TD branch.

DD-LDT-880_Dialysate Temperature DD 1
DD-LDT-880_Dialysate Temperature DD 1
DD-LDT-880_Dialysate Temperature DD 1
DD-LDT-880_Dialysate Temperature DD 1