dd-firmware

Clone Tools

Stats

Commits this week: 39
Total Committers: 16
Last Commit: 11:49
Commits this week: 39

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
Wednesday 08 Apr
1:32 pm

Vendor - TEL - Jashwant Gantyada

LDT-3103 addressed code review comments and merged latest staging

Options
    • -2
    • +2
    /firmware/App/Controllers/BalancingChamber.c
1:30 pm

Vendor - TEL - Jashwant Gantyada

Merge branch 'staging' into LDT-3103-closed-loop-control-pressure-threshold-fix

Options
    • -2
    • +24
    /firmware/App/Controllers/BalancingChamber.c
    • -4
    • +18
    /firmware/App/Modes/ModeGenDialysate.c
12:25 pm

Sean Nash

Why do some functions take sensor as a U32 and some as a CONDUCTIVITY_SENSORS_T? The latter seems appropriate.

Why do some functions take sensor as a U32 and some as a CONDUCTIVITY_SENSORS_T? The latter seems appropriate.

12:24 pm

Sean Nash

Remove blank line.

Remove blank line.

12:24 pm

Sean Nash

Remove blank line.

Remove blank line.

12:23 pm

Sean Nash

Add blank line before return.

Add blank line before return.

12:22 pm

Sean Nash

Add blank line before return.

Add blank line before return.

12:19 pm

Sean Nash

Remove blank line.

Remove blank line.

12:11 pm

Sean Nash

Why are we switching sensors around?

Why are we switching sensors around?

12:11 pm

Sean Nash

Why D43?

Why D43?

12:10 pm

Sean Nash

Remove blank line.

Remove blank line.

12:09 pm

Sean Nash

Should we be filtering a new sample every 700ms or should we do it when a new sample is received? FPGA is giving us a read count right? So we will know when we have a new data set from sensor. It m...

Should we be filtering a new sample every 700ms or should we do it when a new sample is received?
FPGA is giving us a read count right? So we will know when we have a new data set from sensor. It makes more sense to me to take them when they come. Otherwise, we will get out of phase with true sample frequency and occasionally process the previous sample again (if true sample freq is a little slower than 700ms) or miss a sample (if true sample freq is a little faster than 700ms).

12:04 pm

Sean Nash

Why do we need these static interval variables when we have the constants?

Why do we need these static interval variables when we have the constants?

12:03 pm

Sean Nash

Remove blank line.

Remove blank line.

11:14 am

Vinayakam Mani

Delete the macro if not being used.

Delete the macro if not being used.

10:03 am

Vendor - TEL - Arpita Srivastava

LDT-1195: Fixed indentation

Options
    • -3
    • +1
    /firmware/App/Controllers/BalancingChamber.c
    • -1
    • +1
    /firmware/App/Tasks/TaskGeneral.c
8:44 am

Michael Garthwaite

Merge branch 'staging' into LDT-3777-sprint-25-fixes

Options
8:24 am

Dara Navaei

Tuesday 07 Apr
2:54 pm

Vinayakam Mani

Probably, we need to signal FP as well when there is a mode change happens. say, DD changes standby to pre-gen/Gen Dialysate mode, FP needs to transition to pre-gen / generate permeate (as we imple...

Probably, we need to signal FP as well when there is a mode change happens. say, DD changes standby to pre-gen/Gen Dialysate mode, FP needs to transition to pre-gen / generate permeate (as we implemented in TD interface).

2:52 pm

Michael Garthwaite

LDT-2008: version request handler. fixes for D74 between test configs. reworked init state to handle sensors providing bad cal data if test config is enabled.

Options
    • -79
    • +114
    /firmware/App/Drivers/ConductivitySensors.c
    • -0
    • +1
    /firmware/App/Drivers/ConductivitySensors.h
    • -1
    • +9
    /firmware/App/Monitors/Conductivity.c
    • -1
    • +1
    /firmware/App/Monitors/Temperature.c
    • -0
    • +1
    /firmware/App/Services/AlarmMgmtSWFaults.h
    • -2
    • +2
    /firmware/App/Services/Messaging.c
2:06 pm

Vendor - TEL - Jashwant Gantyada

LDT-3103 addressed code review comments

Options
    • -5
    • +1
    /firmware/App/Controllers/BalancingChamber.c
8:49 am

Michael Garthwaite

Merge branch 'staging' into LDT-2008-v2-conductivity-sensors-CLEAN

Options
    • -1
    • +1
    /firmware/App/DDCommon.h
    • -38
    • +25
    /firmware/App/Services/FpgaDD.c
    • -8
    • +8
    /firmware/App/Services/FpgaDD.h
    • -3
    • +5
    /firmware/App/Services/Messaging.c
Monday 06 Apr
7:31 pm

Dara Navaei

LEAHI-DD-FIRMWARE-LDT-3735_System Data and Logs - DD - Non-Volatile Memory - 04: DEV - Feature Implementation
LEAHI-DD-FIRMWARE-LDT-3735_System Data and Logs - DD - Non-Volatile Memory - 04: DEV - Feature Implementation
4:44 pm

Vendor - TEL - Arpita Srivastava

LDT-3735: NVM module builds

Options
    • -4
    • +0
    /firmware/App/Drivers/NVDriver.c
    • -0
    • +34
    /firmware/App/Drivers/NVDriver.h
    • -290
    • +21
    /firmware/App/Services/NVMgmtDD.c
    • -8
    • +1
    /firmware/App/Services/NVMgmtDD.h
    • -56
    • +47
    /firmware/App/Services/NVMsgQ.c
    • -54
    • +9
    /firmware/App/Services/NVMsgQ.h
    • -77
    • +430
    /firmware/App/Services/NVRecordsDD.c
    • -21
    • +61
    /firmware/App/Services/NVRecordsDD.h
2:13 pm

Vendor - TEL - Jashwant Gantyada

removed

removed

2:13 pm

Vendor - TEL - Jashwant Gantyada

updated comment.

updated comment.

2:12 pm

Vendor - TEL - Jashwant Gantyada

removed.

removed.

2:12 pm

Vendor - TEL - Jashwant Gantyada

removed and added comments.

removed and added comments.

2:12 pm

Vinayakam Mani

2:12 pm

Vendor - TEL - Jashwant Gantyada

changed.

changed.