I think we may want to be a little more forgiving on this. Maybe allow for n errors within some window of time before triggering a fault. I added some functions to support this kind of thing in Utilities module. Also - should this be a conductivity sensor fault? Need to somehow differentiate from the other fault above so when we see it in a log file we know which occurred.
To MessagePayloads.h. I think I'll eventually redistribute these back to the appropriate individual module headers and remove MessagePayloads.h - still working out what makes most sense.
The mL to L is only used in ultrafiltration and only for volume and only for display on screen. it wasn't worth including utility class here which costs more code and build time only for a division/multiplication. comment will suffice.
1. I would call them consistently, cdi, cdo, inlet outlet is too confusing because there is also pressure and temperature;2 2. I would also focus only on cdi cdo and remove cd1/cd2, which have their own Stories.
Yes, I agree. For now, I've updated it so the flag will only disable the HD communication timeout error, instead of all the alarms. This will reduce the scope of the flag and also prevent it from affecting the other squishqt tests before we move things to Dialin.