hdfirmware

Clone Tools

Stats

Commits this week: 0
Total Committers: 17
Last Commit: 19 Nov 25
Commits this week: 0

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
Monday 26 Jul 2021
10:52 pm

Dara Navaei

DEN-9054 changed the build history file form text to log

Options
    • -0
    • +18
    /firmware/hd_build_history.log
    • -9
    • +0
    /firmware/hd_build_history.txt
5:49 pm

Dara Navaei

DEN-9054 aligned the build history file

Options
    • -8
    • +7
    /firmware/hd_build_history.txt
5:12 pm

Sean Nash

DEN-8886: Added UI compatibility POST test. Updated alarm audio per latest HDD. Added handling of UI and DG version messages. Fixed watchdog POST. Added recovery check to watchdog POST.

Options
    • -0
    • +25
    /firmware/App/HDCommon.h
    • -4
    • +0
    /firmware/App/Modes/BloodPrime.h
    • -12
    • +43
    /firmware/App/Modes/ModeInitPOST.c
    • -0
    • +2
    /firmware/App/Modes/ModeInitPOST.h
    • -4
    • +29
    /firmware/App/Services/AlarmMgmt.c
    • -3
    • +10
    /firmware/App/Services/FPGA.c
    • -1
    • +1
    /firmware/App/Services/FPGA.h
    • -0
    • +4
    /firmware/App/Services/SystemComm.c
    • -6
    • +34
    /firmware/App/Services/SystemCommMessages.c
    • -3
    • +7
    /firmware/App/Services/SystemCommMessages.h
    • -8
    • +28
    /firmware/App/Services/WatchdogMgmt.c
    • -1
    • +1
    /firmware/HD.dil
4:38 pm

Dara Navaei

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

Options
    • -1
    • +1
    /firmware/App/HDCommon.h
4:34 pm

Dara Navaei

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

Options
    • -1
    • +1
    /firmware/App/HDCommon.h
3:36 pm

Quang Nguyen <qnguyen@diality.com>

Merge branch 'DEN-8886-hd_dg_dev-self-tests-2-of-2' into develop

Options
    • -21
    • +21
    /firmware/App/Controllers/BloodFlow.c
    • -0
    • +2
    /firmware/App/Controllers/Bubble.c
    • -25
    • +37
    /firmware/App/Controllers/DialInFlow.c
    • -39
    • +44
    /firmware/App/Controllers/DialOutFlow.c
    • -7
    • +10
    /firmware/App/HDCommon.h
    • -33
    • +169
    /firmware/App/Modes/BloodPrime.c
    • -1
    • +1
    /firmware/App/Modes/Dialysis.c
    • -13
    • +63
    /firmware/App/Modes/ModeInitPOST.c
    • -0
    • +2
    /firmware/App/Modes/ModePreTreat.c
    • -1
    • +1
    /firmware/App/Modes/ModeTreatmentParams.c
    • -28
    • +68
    /firmware/App/Services/AlarmMgmt.c
    • -3
    • +22
    /firmware/App/Services/FPGA.c
    • -0
    • +2
    /firmware/App/Services/FPGA.h
    • -26
    • +7
    /firmware/App/Services/Interrupts.c
    • -26
    • +12
    /firmware/App/Services/SystemComm.c
  16. … 4 more files in changeset.
3:33 pm

Quang Nguyen <qnguyen@diality.com>

Merge branch 'DEN-7802-dg_dev-dialysate-generation' into develop

Options
    • -5
    • +57
    /firmware/App/Controllers/DGInterface.c
    • -24
    • +26
    /firmware/App/Controllers/DGInterface.h
    • -0
    • +1
    /firmware/App/HDCommon.h
    • -0
    • +4
    /firmware/App/Modes/ModeInitPOST.c
    • -0
    • +4
    /firmware/App/Modes/ModePreTreat.c
    • -0
    • +2
    /firmware/App/Modes/ModeTreatment.c
    • -16
    • +22
    /firmware/App/Modes/Prime.c
    • -0
    • +10
    /firmware/App/Modes/SelfTests.c
3:31 pm

Quang Nguyen <qnguyen@diality.com>

DEN-7802: Add build flag to disable dialysate temperature

Options
    • -6
    • +4
    /firmware/App/Controllers/DGInterface.c
    • -0
    • +1
    /firmware/App/HDCommon.h
3:15 pm

Quang Nguyen <qnguyen@diality.com>

Remove pack for blood prime data

Options
    • -4
    • +0
    /firmware/App/Modes/BloodPrime.h
    • -4
    • +0
    /firmware/App/Modes/ModeInitPOST.c
    • -1
    • +1
    /firmware/App/Services/SystemCommMessages.c
3:02 pm

Quang Nguyen <qnguyen@diality.com>

Merge branch 'DEN-8679-hd_dev-treatment-log' into develop

Options
    • -1
    • +14
    /firmware/App/Controllers/DGInterface.c
    • -13
    • +26
    /firmware/App/Controllers/DGInterface.h
    • -8
    • +8
    /firmware/App/HDCommon.h
    • -0
    • +6
    /firmware/App/Modes/ModeInitPOST.c
    • -7
    • +73
    /firmware/App/Services/SystemCommMessages.c
    • -0
    • +6
    /firmware/App/Services/SystemCommMessages.h
9:53 am

Sean Nash

Seems like the two states given as data are not very meaningful. Consider just setting before/after data to zero for this event.

Seems like the two states given as data are not very meaningful. Consider just setting before/after data to zero for this event.

9:50 am

Sean Nash

Not sure this variable (and related get function) are needed.

Not sure this variable (and related get function) are needed.

9:49 am

Sean Nash

User may not have changed all 4 settings. Should we only send events for those that actually changed?

User may not have changed all 4 settings. Should we only send events for those that actually changed?

9:41 am

Sean Nash

I think this will be the time we initiate a treatment. Is that what we want? Or should we move this to transition function to capture time of treatment start?

I think this will be the time we initiate a treatment. Is that what we want? Or should we move this to transition function to capture time of treatment start?

9:39 am

Sean Nash

Are there ever any reject reasons? Is this message requested by UI or sent unsolicited when ready?

Are there ever any reject reasons? Is this message requested by UI or sent unsolicited when ready?

9:34 am

Sean Nash

I think we set UF volume to zero in TreatmentParams mode, so this condition should not be necessary.

I think we set UF volume to zero in TreatmentParams mode, so this condition should not be necessary.

9:32 am

Sean Nash

Why not zero record here? I see it is zeroed just prior to creation at end of treatment, but that means this record may have prior treatment's data until current treatment is over.

Why not zero record here? I see it is zeroed just prior to creation at end of treatment, but that means this record may have prior treatment's data until current treatment is over.

9:18 am

Sean Nash

If typical h/w response is very quick (e.g. < 1ms) and worst case is still pretty quick (e.g. < 5ms), then I think this is ok with the t/o there to prevent getting stuck in loop forever. Also, batt...

If typical h/w response is very quick (e.g. < 1ms) and worst case is still pretty quick (e.g. < 5ms), then I think this is ok with the t/o there to prevent getting stuck in loop forever.
Also, battery monitor is called from background task so we can be a little more relaxed about this.

9:12 am

Sean Nash

Why would we zero it when no AC detected?

Why would we zero it when no AC detected?

9:08 am

Sean Nash

Why are DG definitions in HDDefs.h? If needed by both stacks, should we create a FWDefs.h common to both f/w stacks?

Why are DG definitions in HDDefs.h? If needed by both stacks, should we create a FWDefs.h common to both f/w stacks?

9:06 am

Dara Navaei

DEN-9054 updated the build history file

Options
    • -5
    • +5
    /firmware/hd_build_history.txt
Sunday 25 Jul 2021
4:15 pm

Dara Navaei

DEN-9054 initial commit of the switches

Options
    • -0
    • +244
    /firmware/App/Controllers/Switches.c
    • -0
    • +51
    /firmware/App/Controllers/Switches.h
    • -0
    • +12
    /firmware/App/Services/FPGA.c
    • -0
    • +2
    /firmware/App/Services/FPGA.h
    • -0
    • +8
    /firmware/App/Services/SystemComm.c
    • -0
    • +91
    /firmware/App/Services/SystemCommMessages.c
    • -4
    • +14
    /firmware/App/Services/SystemCommMessages.h
    • -1
    • +1
    /firmware/hd_build_history.txt
    • -0
    • +2
    /firmware/source/sys_main.c
4:10 pm

Dara Navaei

HD-DEN-9054_DG HD Switches
HD-DEN-9054_DG HD Switches
Saturday 24 Jul 2021
4:06 pm

Dara Navaei

Does the payload length does not match with the payload? In the payload, you have 1 U32 and 2 F32s so should not the length be U32 + 2 * F32?

Does the payload length does not match with the payload? In the payload, you have 1 U32 and 2 F32s so should not the length be U32 + 2 * F32?

3:54 pm

Dara Navaei

Do we not need a battery remaining percent override function for testing?

Do we not need a battery remaining percent override function for testing?

3:51 pm

Dara Navaei

The name of the function does not match with the actual name.

The name of the function does not match with the actual name.

3:49 pm

Dara Navaei

Is it safe to stay in while loop until the hardware responds? I understand that you have a timeout but I thought we still should not do that.

Is it safe to stay in while loop until the hardware responds? I understand that you have a timeout but I thought we still should not do that.

3:34 pm

Dara Navaei

How do you get the status of the battery charge in the self test before you check the whether it is in range?

How do you get the status of the battery charge in the self test before you check the whether it is in range?

3:28 pm

Dara Navaei

I recommend to explicitly name the input and output variables.

I recommend to explicitly name the input and output variables.

3:26 pm

Dara Navaei

Reverse the order of the condition.

Reverse the order of the condition.