dialin

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
DEN-14262: Added a/c power loss flag to alarm info broadcast.

DIALIN-DEN-15246_Active Reservoir Empty Post Concentrate Alarm Recovery
DIALIN-DEN-15246_Active Reservoir Empty Post Concentrate Alarm Recovery
Why 0xFFFFFFFF?

Why 0xFFFFFFFF?

Let's try not to use words like enable/disable unless we're literally doing just that (e.g. disable x alarm). I think the core of this test config is "use wet cartridge".

Let's try not to use words like enable/disable unless we're literally doing just that (e.g. disable x alarm). I think the core of this test config is "use wet cartridge".

Why commented out and why setting to a DG test config?

Why commented out and why setting to a DG test config?

DEN-15199 initial commit of the hd_test_configs. Updated the messages ID and the test configs enums

    • -0
    • +157
    /dialin/hd/hd_test_configs.py
DEN-14988 [Recirculation and patient connection instructions] - Ready
DEN-14988 [Recirculation and patient connection instructions] - Ready
DIALIN-DEN-14262_Vba Homing Fails When Cartridge IS Loaded ON Device
DIALIN-DEN-14262_Vba Homing Fails When Cartridge IS Loaded ON Device
DIALIN-DEN-15199_FW DN Sprint 95 Part 2
DIALIN-DEN-15199_FW DN Sprint 95 Part 2
Bamboo Commit: generated the code change report

Merge branch 'DEN-15235-UI-BN-S96' into develop

Bamboo Commit: generated the code change report

Merged staging

DEN-14988 : Add recirculation and patient connection instructions to normal rinseback workflow screens

Bamboo Commit: generated the code change report

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

DEN-15199 updated the alarms table

RESOLVED.

RESOLVED.

DEN-15199 addressed the code review comment

This is here is because when they request the configs I set the dictionary to reset mode until the new values have been received from the firmware and then the dictionary is updated with the firmwa...

This is here is because when they request the configs I set the dictionary to reset mode until the new values have been received from the firmware and then the dictionary is updated with the firmware values. Thanks I moved it to only execute it if the message was received successfully.

Shouldnt this reset be in cmd_reset_all_test_configs()? It should also be executed after a successful message.

Shouldnt this reset be in cmd_reset_all_test_configs()? It should also be executed after a successful message.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

The file header will be added upon the staging build.

The file header will be added upon the staging build.

The file heater will be added automatically in upon the staging build.

The file heater will be added automatically in upon the staging build.

This will be updated once we move to HD.

This will be updated once we move to HD.