I kept it for debugging. The usual behavior of the SquishQt is to continue even if an error happens to stop it if an error happens this value needs to be set. I'm still trying to figure out how exactly this works and later may move it in a better file.
I meant "retains" and "retain". A complete sentence would be : "if 90% retains ...." or "if 90% shall retain" I prefer to have a present verb, for input and if it was output, a past verb.
So in this dry test, I guess if any one of these is out of range we can say something is wrong with the way the cartridge was loaded. Should we try to distinguish between improperly loaded cartridge and no cartridge loaded (all 3 occlusions are < threshold)?
What if DG does not go to drain mode (e.g. DG rejected drain command)? We will get stuck in this state. Let's discuss DG command handling - we may need to add more to DG response so HD can handle these types of issues.
RTCs are sync'd by UI sending its date/time to HD and DG f/w. However, RTC time is not used for treatment time. Treatment time is accumulated using HD timer counter. HD then uses this and set treatment duration to calculate time remaining. All are then sent to UI regularly.
No one is using this flag. This flag gets set to TRUE previously when the HD starts to command DG to sample water. The DG sample water command consists of start, stop, end sample water. So this flag does not make sense anymore.
Twice the size of the main menu height (140) happened to leave a good sized margin between minimized alarm + main menu and the save button. I've updated it to be defined more clearly so the notification height (60) + the main menu height (70) + settingsNotificationMargin (10) decides the bottomMargin instead of just 2x the main menu height.
I'm not sure an enum is what we want for mfg location. We don't want to have to make a new build every time we a new location is added. I think location should probably be a 3 or 4 character alpha-numeric location code.
