td-firmware

Clone Tools

Stats

Commits this week: 77
Total Committers: 17
Last Commit: 05 Aug
Commits this week: 77

Lines of code count not available

Commit Activity

Commits By Day In Week
52 week commits volume
Commits By Day In Week
Commits by day
Commits By Day In Week
Commits by hour
Commits By Hour In Day
Commit calendar
 

Most active committers (90 days)

loading
loading
  • last updated a few seconds ago
All Commits Reviews
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Tuesday 04 Aug
2:13 pm

Vendor - TEL - Praneeth Bunne

LDT-4040: Resolve CR comments, merge latest staging & resolve merge conflicts

Options
    • -17
    • +14
    /firmware/App/Modes/ModeTreatment.c
    • -3
    • +3
    /firmware/App/Modes/StateTxBloodPrime.c
    • -17
    • +30
    /firmware/App/Modes/StateTxPaused.c
    • -5
    • +17
    /firmware/App/Modes/StateTxRecirc.c
    • -39
    • +65
    /firmware/App/Modes/StateTxRinseback.c
    • -11
    • +11
    /firmware/App/Monitors/Pressures.c
    • -3
    • +6
    /firmware/App/Services/AlarmMgmtSWFaults.h
    • -3
    • +58
    /firmware/App/Services/AlarmMgmtTD.c
    • -2
    • +3
    /firmware/App/Services/AlarmMgmtTD.h
    • -3
    • +8
    /firmware/App/Services/Messaging.c
    • -179
    • +71
    /firmware/App/Services/StateServices/FluidBolus.c
    • -13
    • +22
    /firmware/App/Services/TxParams.c
1:52 pm

Vendor - TEL - Jashwant Gantyada

LDT-4009 addressed code review comments

Options
    • -1
    • +0
    /firmware/App/Modes/ModeTreatment.c
    • -1
    • +1
    /firmware/App/Modes/StateTxIsolatedUF.c
    • -1
    • +5
    /firmware/App/Services/TxParams.c
1:31 pm

suresh

Addressed review comments

Options
    • -3
    • +3
    /firmware/App/Drivers/BatteryDriver.c
    • -1
    • +1
    /firmware/App/Drivers/BatteryDriver.h
    • -7
    • +7
    /firmware/App/Monitors/Battery.c
1:14 pm

Vendor - TEL - Praneeth Bunne

initialized using resetRinsebackFlags()

initialized using resetRinsebackFlags()

1:03 pm

Vendor - TEL - Praneeth Bunne

those are initialized in resetTreatmentRecircFlags() and that is called in init

those are initialized in resetTreatmentRecircFlags() and that is called in init

11:34 am

Dara Navaei

LEAHI-TD-FIRMWARE-LDT-5358_Pre-Treatment - FW Implementation - 10/6:
LEAHI-TD-FIRMWARE-LDT-5358_Pre-Treatment - FW Implementation - 10/6:
11:16 am

Vendor - TEL - Arpita Srivastava

align comment

align comment

11:11 am

Vendor - TEL - Vijay Pamula

Merge branch 'staging' into LDT-4029-pre-treatment---fw-implementation

Options
11:11 am

suresh

LDT-4063: Addressed review comments

Options
    • -1
    • +3
    /firmware/App/Modes/OperationModes.c
    • -2
    • +4
    /firmware/App/Services/Messaging.c
11:10 am

Vendor - TEL - Arpita Srivastava

Can we please break this line as to match our standard of 100 columns? SET_ALARM_WITH_2_U32_DATA( ALARM_ID_TD_AIR_PUMP_STALL, currentAirPumpPowerLevel, getU32OverrideValue( &currentAirPumpRPM ) );

Can we please break this line as to match our standard of 100 columns?

SET_ALARM_WITH_2_U32_DATA( ALARM_ID_TD_AIR_PUMP_STALL,
currentAirPumpPowerLevel,
getU32OverrideValue( &currentAirPumpRPM ) );

11:08 am

Vendor - TEL - Vijay Pamula

Merge branch 'staging' into LDT-4031-pre-treatment---fw-implementation

Options
11:02 am

Vendor - TEL - Varshini Nagabooshanam

Merge conflicts

Options
    • -4
    • +4
    /firmware/App/Modes/ModeTreatment.c
    • -5
    • +7
    /firmware/App/Services/AlarmMgmtSWFaults.h
    • -11
    • +22
    /firmware/App/Services/FpgaTD.c
    • -1
    • +3
    /firmware/App/Services/Messaging.c
11:02 am

Vendor - TEL - Arpita Srivastava

10:52 am

Vendor - TEL - Arpita Srivastava

use FALSE

use FALSE

10:52 am

Vendor - TEL - Arpita Srivastava

use FALSE

use FALSE

10:39 am

Vendor - TEL - Arpita Srivastava

It looks like the rows may be misaligned with the alarm ID declarations. For example, ALARM_ID_TD_BATTERY_CHARGER_ERROR_DETECTED is declared as 204.

It looks like the rows may be misaligned with the alarm ID declarations.
For example, ALARM_ID_TD_BATTERY_CHARGER_ERROR_DETECTED is declared as 204.

10:37 am

Michael Garthwaite

Merge branch 'staging' into LDT-4611-hdf-fw-implementation-5-4

Options
10:22 am

Vendor - TEL - Varshini Nagabooshanam

Changes

Options
    • -9
    • +6
    /firmware/App/Controllers/Valves.c
    • -48
    • +42
    /firmware/App/Drivers/PinchValve.c
    • -1
    • +1
    /firmware/App/Drivers/PinchValve.h
    • -1
    • +0
    /firmware/App/Modes/ModeStandby.c
10:13 am

Vendor - TEL - Arpita Srivastava

When we send any message to UI, usually add the message id in the doxygen header like this. @details \b Message \b Sent: MSG_ID_TD_RESP_TREATMENT_PARAMS_TO_VALIDATE Please refer to the function s...

When we send any message to UI, usually add the message id in the doxygen header like this.

@details \b Message \b Sent: MSG_ID_TD_RESP_TREATMENT_PARAMS_TO_VALIDATE

Please refer to the function sendTreatmentParamsResponse()

10:05 am

Vendor - TEL - Arpita Srivastava

When we send any message to UI, usually add the message id in the doxygen header like this. *@details \b Message \b Sent: MSG_ID_TD_RESP_TREATMENT_PARAMS_TO_VALIDATE Please refer to the functi...

When we send any message to UI, usually add the message id in the doxygen header like this.

  • @details \b Message \b Sent: MSG_ID_TD_RESP_TREATMENT_PARAMS_TO_VALIDATE


Please refer to the function sendTreatmentParamsResponse()

10:05 am

Vendor - TEL - Arpita Srivastava

When we send any message to UI, usually add the message id in the doxygen header like this. *@details \b Message \b Sent: MSG_ID_TD_RESP_TREATMENT_PARAMS_TO_VALIDATE Please refer to the functi...

When we send any message to UI, usually add the message id in the doxygen header like this.

  • @details \b Message \b Sent: MSG_ID_TD_RESP_TREATMENT_PARAMS_TO_VALIDATE


Please refer to the function sendTreatmentParamsResponse()

9:55 am

Vendor - TEL - Arpita Srivastava

It looks like the rows may be misaligned with the alarm ID declarations. For example, ALARM_ID_TD_SAFETY_SHUTDOWN_POST_TEST_FAILED is declared as 207.

It looks like the rows may be misaligned with the alarm ID declarations.
For example, ALARM_ID_TD_SAFETY_SHUTDOWN_POST_TEST_FAILED is declared as 207.

9:53 am

Vendor - TEL - Arpita Srivastava

Should Instructions part be this? A problem was detected with the hemodialysis device.

Should Instructions part be this?

A problem was detected with the hemodialysis device.

9:50 am

Vendor - TEL - Arpita Srivastava

Please confirm if the source is DD?

Please confirm if the source is DD?

Monday 03 Aug
3:45 pm

suresh

Merge branch 'staging' into LDT-4072-power-loss---fw-implementation-

Options
3:35 pm

Vendor - TEL - Varshini Nagabooshanam

Merge branch 'staging' of bitbucket.org:diality-cloud/td-firmware into LDT-4149-pinch-valves-fw-implementation

Options
    • -1
    • +1
    /firmware/App/TDCommon.h
3:33 pm

suresh

Merge branch 'staging' into LDT-4063-power-control-and-post---fw-imp

Options
3:32 pm

Dara Navaei

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

Options
    • -1
    • +1
    /firmware/App/TDCommon.h
3:32 pm

Dara Navaei

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

Options
    • -2
    • +2
    /firmware/App/Monitors/Pressures.c
3:30 pm

Vendor - TEL - Varshini Nagabooshanam