firmware

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
DEN-11114 addressed the code review comments. DEN-11364 removed the 1 second fans monitor interval

Update message list with latest data details.

Update message list with latest data details.

Update message list with latest broadcast msg data details.

Update message list with latest broadcast msg data details.

We don't need to calculate digit count - just use strlen(tempCharBuffer) after sprintf creates your string.

We don't need to calculate digit count - just use strlen(tempCharBuffer) after sprintf creates your string.

I would set this to at least 11 because you are using sprintf to create an unsigned integer string (max is 10 digits + 1 zero terminator) and we want to make sure we give sprintf a large enough buf...

I would set this to at least 11 because you are using sprintf to create an unsigned integer string (max is 10 digits + 1 zero terminator) and we want to make sure we give sprintf a large enough buffer to populate - otherwise it will overwrite memory.

.crc?

.crc?

1 and 0 is not clear. Better to say FIFO send and reset.

1 and 0 is not clear. Better to say FIFO send and reset.

Create and trigger new alarm.

Create and trigger new alarm.

.crc?

.crc?

Recommend changing > to >= and then removing the - 1.

Recommend changing > to >= and then removing the - 1.

Please update message list details for this broadcast msg.

Please update message list details for this broadcast msg.

If h/w component is not required to have a calibration, we shouldn't alarm here - right?

If h/w component is not required to have a calibration, we shouldn't alarm here - right?

We should verify bufferLength is >= to cal section byte size before doing this memcpy - otherwise, we will be overwriting memory.

We should verify bufferLength is >= to cal section byte size before doing this memcpy - otherwise, we will be overwriting memory.

Is CRC check on individual cal section done elsewhere or should it be considered here as well?

Is CRC check on individual cal section done elsewhere or should it be considered here as well?

Done.

Done.

Recommend moving this rate to be with the others above.

Recommend moving this rate to be with the others above.

STEADY_VOLUME_COUNT_SEC is a number of seconds of stability indicating volume is steady. This only works because sampling time above is once per second. If somebody changes the sampling time, this ...

STEADY_VOLUME_COUNT_SEC is a number of seconds of stability indicating volume is steady. This only works because sampling time above is once per second. If somebody changes the sampling time, this condition will not be right.

Make 0.5 a #define.

Make 0.5 a #define.

Can we please use available alarm IDs above before adding a new one?

Can we please use available alarm IDs above before adding a new one?

DEN-11114, DEN-11364 worked on the blood leak calibration and removed the fans clear the alarm if the RPM was in range again

Bamboo Commit: Updated HDCommon.h with build versions from Bamboo

Merged DEN-11114

Merge branch 'DEN-11114-dg_dev-dg-dialysate-temperature-control-2-of-2' into develop

DEN-11114 added a publication to the fans

Bamboo Commit: Updated HDCommon.h with build versions from Bamboo

Merge branch 'DEN-11114-dg_dev-dg-dialysate-temperature-control-2-of-2' into develop

    • -26
    • +118
    ./App/Controllers/BloodLeak.c
    • -0
    • +33
    ./App/Services/SystemCommMessages.c
DEN-11114, DEN-11542 updated the fans RPM alarm

Bamboo Commit: Updated HDCommon.h with build versions from Bamboo

Merge branch 'develop' of ssh://dvm-linux02:7999/hd/hdfirmware into develop

Diabled prime swithces