fillWeightLoadCell initialized to A1 at top of function (assuming active reservoir is R2 and so we would want load cell associated with the inactive reservoir R1 which is A1. So we only need to see if that assumption is wrong here.
Consider having a property for persistent alarms for whether alarm is clearable. Then, do not do any of the clear alarm logic if not clearable. User clearing will be handled between UI and HD f/w, so will not be handled in this module.
The conductivity value coming from both FPGA and conductivity sensor is unsigned integer. The conversion to float type is to get the two decimal embedded in the unsigned integer.
This is the link which is used for our C++ coding standard and has been already mentioned as a reference in the doc. This codding standard and this implementation has been done by having those comments in mind,
There are so many debates on so many c++ features that might be the case people are prefer to use Java or python sometimes. For example threads are strongly suggested to not to be used until you really need them because they are very hard (or almost impossible) to debug and needs so much work to keep them safe. But we are using them because we need them.
I put those #define in code to guard the code and I'm willing to keep them at least for quite a while until we are going to refactor them and implement the actual slots when required. So until then we are not removing them and it remains as it is.
If it's still not clear to you how to use them after I explained, come to me and ask please.
This is the TI copyright that we got these API files originally. Yes, they are different from the other TI files that are generated by HALCoGen but they are still TI files and not ours. When I was working on the copyright script, I realized the script did not realize they are not our files and added our copyright. I enhanced the algorithm that checks whether a file belongs to Diality or not, so this issue will not happen. At the same time, I removed the Diality copyright. I am not sure why there is a "?" in their copyright that does not affect the script's parsing capabilities.
