It looks like you have this as a T/F response from UI. UI should not be determining whether the modality matches - that's our job. UI should be telling us which type of tubing set was installed (HD or HDF type). Then when we get this response msg from UI, we will compare the type to the user selected modality (from TxParams) to see if it matches.

Add doxygen comments to the right of each structure field.

Why is this commented out? We will get stuck in this state if we don't move on to the pressure leak test states.

For now, we need to set authResponseReceived and authResponseValidTubingSet and authResponseModalityAccepted to TRUE until UI is properly responding to authentication request (TODO).

For now, we need to set barcodeScanResponseReceived to TRUE here until barcode scan command is implemented.

Add blank line before return statement.

Keep this blank line above group header.

Something is wrong here. We already had reg 33 at line 192 above. Reconcile with HDD.

Make sure UI s/w is looking for this message on the broadcast channel or change this channel to the TD=>UI channel if UI is looking for this message on that channel.

use ternary to make TRUE or FALSE.

Fixed

Yes

REmoved

Moved

Fixed

Removed

Which alarm?

bpPublishTimerCtr is the output?

Input is none.
Add @Alarms

Should we list the alarm ids? @Alarms?

requestAbortBPReading is the output?

requestPedsBPReading is the output?

requestAdultBPReading is the output?

pendingVitalsRequest is the output?

We should initialize in the init function?

bpMeasurementReady is an output?

nextState is the return value.
Should we add requestAdultBPMeasurement, bpMeasurementReady and bpDriverError to outputs?

Where are we updating the bpResults?

We should initialize this in init functions.