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 minutes ago
All Commits Reviews
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Friday 30 Sep 2022
1:38 pm

Michael Garthwaite

Merge branch 'staging' into DEN-13903-sprint-80_mg_air_trap_optimization

Options
    • -5
    • +10
    /firmware/App/Modes/Prime.c
1:36 pm

Michael Garthwaite

DEN-13801: Fixed decay state failing with valid conditions. Loosened tolerances for Arterial and Venous pressure values during dry self pressurized state.

Options
    • -4
    • +5
    /firmware/App/Modes/SelfTests.c
1:35 pm

Michael Garthwaite

Merge branch 'staging' into DEN-13801-sw_dev-sprint-79_mg

Options
    • -127
    • +53
    /firmware/App/Controllers/PresOccl.c
    • -9
    • +21
    /firmware/App/Drivers/Battery.c
    • -19
    • +17
    /firmware/App/Modes/SelfTests.c
11:01 am

Steve Jarpe <sjarpe@diality.com>

DEN-14001-hd-battery-driver-update. Made recommended changes in label naming. Split logging data into two groups--battery status data which is published more frequently, and battery manager data which is published less frequently.

Options
    • -218
    • +218
    /firmware/App/Drivers/Battery.c
    • -32
    • +37
    /firmware/App/Drivers/Battery.h
9:00 am

Michael Garthwaite

Do we want this checked into staging?

Do we want this checked into staging?

Thursday 29 Sep 2022
5:17 pm

Sean Nash

These are defined in the Code Composer project for DG and HD firmware respectively. You can only have one defined and you must have one defined.

These are defined in the Code Composer project for DG and HD firmware respectively. You can only have one defined and you must have one defined.

5:06 pm

Sean Nash

What is the purpose of this "no event" event?

What is the purpose of this "no event" event?

5:06 pm

Sean Nash

What is the purpose of this "no event" event?

What is the purpose of this "no event" event?

5:04 pm

Sean Nash

No stop property for a high priority alarm? PRS 754 says dialysate temperature alarms are low priority. Temp too low = rank 902. Temp too high = rank 901.

No stop property for a high priority alarm?
PRS 754 says dialysate temperature alarms are low priority. Temp too low = rank 902. Temp too high = rank 901.

4:54 pm

Sean Nash

Why no stop?

Why no stop?

4:53 pm

Sean Nash

Why no stop?

Why no stop?

4:52 pm

Sean Nash

For DG faults, let's be consistent. DG fault = TRUE Clear Immediate = TRUE (alarm condition moot because DG going to fault mode) Stops = TRUE (HD pauses treatment for alarm) No Clear = FALSE (so HD...

For DG faults, let's be consistent.
DG fault = TRUE
Clear Immediate = TRUE (alarm condition moot because DG going to fault mode)
Stops = TRUE (HD pauses treatment for alarm)
No Clear = FALSE (so HD can clear alarm when user selects option)
No Resume = TRUE (cannot resume treatment w/o functioning DG)
No Rinseback = FALSE (no reason to prevent patient getting their blood back just because DG failed)
No End Treatment = FALSE (should try to end treatment as normally as possible w/o DG - won't be able to drain reservoirs though)
No Blood Recirc = FALSE (why not recirc blood?)
No Dialysate Recirc = TRUE (may not be possible depending on what's wrong w/ DG)
Clear Only = FALSE

4:45 pm

Sean Nash

Faults (HD and DG) should probably be consistent on clear immediate concept. I think faults should be TRUE on clear immediate (going to fault mode anyway, so alarm condition isn't relevant after th...

Faults (HD and DG) should probably be consistent on clear immediate concept. I think faults should be TRUE on clear immediate (going to fault mode anyway, so alarm condition isn't relevant after that).

4:44 pm

Sean Nash

No stop property for a high priority alarm?

No stop property for a high priority alarm?

1:52 pm

Dong Nguyen <dnguyen@diality.com>

DEN-14001: Update Battery.c

Options
    • -1
    • +1
    /firmware/App/Controllers/DialInFlow.c
    • -2
    • +6
    /firmware/App/Drivers/Battery.c
9:42 am

Dara Navaei

It seems correct to me.

It seems correct to me.

9:40 am

Dara Navaei

No this line is a temporary line until the pump control is fixed so the 100 mL/min can be achieved.

No this line is a temporary line until the pump control is fixed so the 100 mL/min can be achieved.

9:39 am

Dara Navaei

It is a const because we want it to be calculated upon compilation and be kept in memory. #define does the calculations every time it is called.

It is a const because we want it to be calculated upon compilation and be kept in memory. #define does the calculations every time it is called.

9:37 am

Dara Navaei

Both cannot be and are not defined at the same time.

Both cannot be and are not defined at the same time.

9:36 am

Dara Navaei

It is up to date.

It is up to date.

9:35 am

Dara Navaei

It is up to date.

It is up to date.

9:33 am

Dara Navaei

Done.

Done.

9:32 am

Dara Navaei

Done.

Done.

9:30 am

Dara Navaei

Done.

Done.

9:28 am

Dara Navaei

Done.

Done.

9:27 am

Dara Navaei

Done.

Done.

9:26 am

Dara Navaei

Done.

Done.

9:25 am

Dara Navaei

Done.

Done.

9:21 am

Dara Navaei

The comment says the alarms are implemented per Product Requirement Specifications.

The comment says the alarms are implemented per Product Requirement Specifications.

9:21 am

Dara Navaei

Done.

Done.