1. at this point we need to verify after all parameters are populated then the names.o_PreTreatmentButton is now enabled. 2. User needs to first press the button for the FW to respond
I would prefer to keep it here, as the start state (DRY_BICART_START_STATE) is always executed when the fill bicart flag (dryBiCartFillRequested) is not set. There are other execs, say fill chamber (execBicarbChamberFillMode) mode controls D80 in its sub states. So, not two execs controlling same valve. Once we identified where all modes using these execs, will come up with signals to avoid such scenarios.
Its like we need to compile the safe library and include it. But if we are using only memcpy and memset, memcmp and static code analyzer check the destination buffer size , I am marking it as resolved
Should use existing override payload structure (the one with the index) located in TestSupport.h. Add an enum in this unit for the 5 DD treatment parameters so you can interpret the index field of the message payload to find the specific parameter that is being overridden.
The value will be updated based on the target value provided by the user. To adjust the minimum and maximum values, use the left and right arrows to update them accordingly.
Thanks for the clarification. This handler already follows the single-parameter MESSAGE_T *message pattern, and the message ID is already defined and registered in Messaging.c. I’ll keep using the existing ID, ensure payload length is validated, and parse the param/value from the payload as expected.
Dara Navaei, this is not a CAN message payload, but it does look like a sensor serial message payload. I'm assuming this code works, so sensor does not expect a packed structure?