RESOLVED IN CODE WALKTHROUGH.
RESOLVED in CODE WALKTHROUGH.
Agree, though this comment belongs in NVDataMgmt.c where setServiceTime() is lives. That function should return TRUE if successful.
removed
Add endTreatmentAlarmResponseRequest and sendLastTreatmentPeriodicData.
Remove gap before "=" as alignment no longer relevant.
Will resolve in next branch.
RESOLVED
I'll assume this has been fixed but not pushed since it still shows up here.
Done
No HD in Leahi. Change to TD.
Does not appear to be referenced.
Should not be able to transition from fault to either new mode.
This message clearly has a payload - we should check payload length to be whatever it is.
These two variables are local.
Did you intentionally leave this commented out?
Need function header.
"situaltoins" -> "situations"
"availabel" => "available"
RESOLVED.
Need to change to match the function name
Applicaion - > Application
FOUNT -> FOUND ?
Do we need to do this? The previous text binding had the "pairedAddr" in it.
Correct. Removed the code.
this CR is to old and obsolete.
We are assuming blood pump was already stopped and VBA/VBV were closed by first blood leak alarm? Also, since dialysate pump is on, need to start trimmer heater.
Thank you, fixed.
HD -> TD.
No CPLD for RO?
There two new variables added.
Fixed.
= 0 on first enum.
Referring to RO alarms as RO here. In properties table, RO faults will be marked as DD faults (from TD perspective, they kind of are DD faults).
Got a suggestion or an issue? Discuss it on the Atlassian Community or visit Atlassian Support for other options.
