Dashboard

mis aligned ?

mis aligned ?

mis aligned ?

mis aligned ?

its a standard c library , for that no need to comment. using ceil() function

its a standard c library , for that no need to comment. using ceil() function

it is used for publish

it is used for publish

This is a default framework for all modules, even though there is nothing right now, left it as it is.

This is a default framework for all modules, even though there is nothing right now, left it as it is.

I don't see it being used in this state. Do we need this?

I don't see it being used in this state. Do we need this?

LDT-2821 Edit Treatment Parameters During Treatment - SW - 02 - Edit Treatment Parameters During Treatment - Q&R - 15: SIT - Software Integration Tests - Squish Qt

pushing functional way to handle testing received value to fw

    • -15
    • +13
    /suite_leahi/tst_edit_parameters/test.py
LDT-3103 special chnages

    • -4
    • +4
    /firmware/App/Modes/ModeGenDialysate.c
LDT-3126: Fixes to state machine.

    • -54
    • +58
    /firmware/App/Modes/StateTxBloodPrime.c
    • -2
    • +1
    /firmware/App/Modes/StateTxBloodPrime.h
LDT-2821 Edit Treatment Parameters During Treatment - SW - 02 - Edit Treatment Parameters During Treatment - Q&R - 15: SIT - Software Integration Tests - Squish Qt

    • -1
    • +36
    /suite_leahi/shared/scripts/names.py
    • -0
    • +512
    /suite_leahi/tst_edit_parameters/test.py
I don't think we need a start state as this state is doing nothing. It is just transitioning to the next state. We can just directly start from the next state.

I don't think we need a start state as this state is doing nothing. It is just transitioning to the next state. We can just directly start from the next state.

I think we have to define macros for magic number.

I think we have to define macros for magic number.

Why NUM_OF_?

Why NUM_OF_?

Variable name suggests it is an action/cmd from UI. Comment suggests it is the number of actions. Which is it? And we should initialize in the init function - not here.

Variable name suggests it is an action/cmd from UI. Comment suggests it is the number of actions. Which is it?
And we should initialize in the init function - not here.

I think we have to include a comment specifying what function is being used from this file.

I think we have to include a comment specifying what function is being used from this file.

Is this really a timer counter? Looks like a flow rate.

Is this really a timer counter? Looks like a flow rate.

Updated

Updated

Added back

Added back

Updated

Updated

LDT-3126-blood-prime-td

    • -48
    • +93
    /firmware/App/Modes/StateTxBloodPrime.c
LDT-3062 Service - SW - 02 - Feature Configurations - Q&R - 15: SIT - Software Integration Tests - Squish Qt

    • -6
    • +3
    /suite_leahi/tst_feature_options/test.py
LDT-3062 Service - SW - 02 - Feature Configurations - Q&R - 15: SIT - Software Integration Tests - Squish Qt

    • -4
    • +5
    /suite_leahi/tst_feature_options/test.py
changed as per comment mouseClick(utility.findChildByText(main_menu_container, "Treatment"))

changed as per comment mouseClick(utility.findChildByText(main_menu_container, "Treatment"))

LDT-2743 Service - SW - 02 - Service - Q&R - 15: SIT - Software Integration Tests - Squish Qt

    • -2
    • +10
    /suite_leahi/tst_feature_options/test.py
LDT-3219 removing D3 open in standby mode

Bamboo Commit: Updated Branch develop For Project TD

    • binary
    /TD/BETA/TD_Debug_Beta_v0.0.0-47.out
    • binary
    /TD/BETA/TD_Debug_Beta_v0.0.0-48.out
Bamboo Commit: Updated TDCommon.h with build versions from Bamboo.

Merge branch LDT-1903-air-trap-level-control---td---0 into develop