FPInterface.h

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
LDT-2198 was merged into this branch after being merged into staging_alpha. Branch will be killed and relevant code changes were reviewed appropriately.

LDT-2198 was merged into this branch after being merged into staging_alpha. Branch will be killed and relevant code changes were reviewed appropriately.

Done.

Done.

RESOLVED IN CODE WALKTHROUGH.

RESOLVED IN CODE WALKTHROUGH.

Done

Done

Done

Done

Done

Done

Done

Done

Done

Done

Appears to be dialysate to dialyzer flow rate.

Appears to be dialysate to dialyzer flow rate.

Looking at the implementation of this function, it appears that this function is setting dialysateFlowRate to target rate only when delivering dialysate to the dialyzer and to zero in all other cas...

Looking at the implementation of this function, it appears that this function is setting dialysateFlowRate to target rate only when delivering dialysate to the dialyzer and to zero in all other cases. Consider changing variable name to something like dialysateToDialyzerFlowRate and updating function description in header to make this more clear.

0.0F.

0.0F.

Check the current Gen dialysate sub state.

Check the current Gen dialysate sub state.

Please use 0.0F (since its float variable).

Please use 0.0F (since its float variable).

LEAHI-DD-FIRMWARE-LDT-1196_DD: Request for a variable for target Qd rate
LEAHI-DD-FIRMWARE-LDT-1196_DD: Request for a variable for target Qd rate
Why the extra leading zeroes? If you want to ensure the literal is treated like a U32, you can do 0x00000001 or simply 1U, but I suspect the compiler will default to 32 bits anyway.

Why the extra leading zeroes? If you want to ensure the literal is treated like a U32, you can do 0x00000001 or simply 1U, but I suspect the compiler will default to 32 bits anyway.

I believe baro is being moved to the TD firmware. DD will have to get baro readings from TD broadcasts.

I believe baro is being moved to the TD firmware. DD will have to get baro readings from TD broadcasts.

Do you want to add a space for the baro pressure sensor from which we receive from the TD?

Do you want to add a space for the baro pressure sensor from which we receive from the TD?

I have removed multiple M4 valve control across in DD. IO/FP will govern the M4 valve control.

I have removed multiple M4 valve control across in DD. IO/FP will govern the M4 valve control.

fixed. thanks

fixed. thanks

fixed. thanks

fixed. thanks

fixed. thanks

fixed. thanks

fixed. removed m4 from dd side

fixed. removed m4 from dd side

Align comments.

Align comments.

Is it FP software fault, instead of TD fault?

Is it FP software fault, instead of TD fault?

Michael Garthwaite: Can we remove the M4 valve controls (across) in DD and keep it only as part of the IO/FP? So that the M4 valve actuation is done by one entity.

Michael Garthwaite: Can we remove the M4 valve controls (across) in DD and keep it only as part of the IO/FP? So that the M4 valve actuation is done by one entity.

Removed FMI support for Beta. will maintain FMI support only in Alpha

Removed FMI support for Beta. will maintain FMI support only in Alpha