firmware

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Bamboo Commit: Updated HDCommon.h with build versions from Bamboo

DEN-14860 Merge

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

Bamboo Commit: Updated the Copyright section and replaced tabs with 4 spaces

Merge DEN-14860 to staging

HD-DEN-15016_System Faults During Treatment Then Returns TO The Standby Screen

Closing code review comments.

I saw the corresponding alarm 44, on the initial power-up. However, going back to the UI log file shows UI communication within 1 second of triggering the error. So either the received message was ...

I saw the corresponding alarm 44, on the initial power-up. However, going back to the UI log file shows UI communication within 1 second of triggering the error. So either the received message was that much delayed, or the check is otherwise broken.

Done.

Done.

Done.

Done.

DEN-14999: Small fix to HD WD POST.

DEN-14999: Removed BP and DPi flow range checks.

DEN-14999: Removed redundant trigger for DG restarted alarm.

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

Merge branch 'DEN-14999-alarm-table-updates' into develop

    • -1
    • +11
    ./App/Services/SystemCommMessages.c
DEN-14999, DEN-15030 fixed the start DG command to only get the acid and bicarb parameters if the HD is sending a start command

My branch (and your DG branch) changed this to 10.

My branch (and your DG branch) changed this to 10.

Do you have data showing UI disappeared for > 5 seconds? Is this necessary?

Do you have data showing UI disappeared for > 5 seconds? Is this necessary?

Change back to 200.

Change back to 200.

Merge branch 'DEN-14999-alarm-table-updates' of ssh://dvm-linux02:7999/hd/hdfirmware into DEN-14999-alarm-table-updates

DEN-14999: Fixed sending of DG valve settings command.

DEN-14999, DEN-15030 updated the DG start command payload

DEN-14999: updates to pressure POST test and 24V range alarms.

RESOLVED IN CODE WALKTHROUGH.

RESOLVED IN CODE WALKTHROUGH.

I don't know. I believe check in msg should have no payload, but it usually does have a u32 of unknown purpose. I have found that the very first check-in after power up has no payload according to ...

I don't know. I believe check in msg should have no payload, but it usually does have a u32 of unknown purpose. I have found that the very first check-in after power up has no payload according to candump and this was causing alarm 46. Until UI sorts this out, I am not going to check payload.

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

Merge DEN-14860 branch

What is the other flavor of UI check in message. If it is a different size, shouldn't it be its own separate message?

What is the other flavor of UI check in message. If it is a different size, shouldn't it be its own separate message?