How do we wish to handle the output of the automated script? It currently does not handle conditional statements to determine ack requiredness. If set to false, the output is: 0x4A MSG_ID_UI_PATI...
How do we wish to handle the output of the automated script? It currently does not handle conditional statements to determine ack requiredness.
If set to false, the output is:
0x4A MSG_ID_UI_PATIENT_DISCONNECTION_CONFIRM hdfirmware response COMM_BUFFER_OUT_CAN_HD_2_UI ACK_REQUIRED PAYLOAD
which is incorrect to what the code is doing. We have 2 different implementations of calling sendAckResponseMsg()
1. sendAckResponseMsg( (MSG_ID_T)message->hdr.msgID, COMM_BUFFER_OUT_CAN_HD_2_UI, FALSE );
- if we dont meet an expected condition. Later in the handler we will call a response message with the response message calling:
serializeMessage( msg, COMM_BUFFER_OUT_CAN_DG_2_HD, ACK_REQUIRED );
2. sendAckResponseMsg( (MSG_ID_T)message->hdr.msgID, COMM_BUFFER_OUT_CAN_HD_2_UI, result );
- a conditional based on?
Please review the FW_Message_list.csv within latest develop & staging builds to understand how the automated script is determining "ack requireness"
