leahi-fwcommon

Clone Tools

Stats

Commits this week: 6
Total Committers: 12
Last Commit: 15:19
Commits this week: 6

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
Today
3 hrs ago

Raghu Kallala

LDT-473 updated acid types to F32 in message payload

Options
    • -2
    • +2
    /MessagePayloads.h
3 hrs ago

Vendor - TEL - Jashwant Gantyada

removed.

removed.

3 hrs ago

Raghu Kallala

Updated

Updated

3 hrs ago

Vendor - TEL - Jashwant Gantyada

changed.

changed.

3 hrs ago

Vendor - TEL - Jashwant Gantyada

removed.

removed.

4 hrs ago

Raghu Kallala

Updated

Updated

4 hrs ago

Sean Nash

I think this function should be in ModeTreatment or Messaging.

I think this function should be in ModeTreatment or Messaging.

4 hrs ago

Sean Nash

update params in header.

update params in header.

4 hrs ago

Raghu Kallala

you are right, I missed it here. Fixed.

you are right, I missed it here.
Fixed.

4 hrs ago

Sean Nash

Move pop to be right after last structure to be packed.

Move pop to be right after last structure to be packed.

4 hrs ago

Sean Nash

I thought acid fields were F32?

I thought acid fields were F32?

4 hrs ago

Sean Nash

Update inputs/outputs after updating function.

Update inputs/outputs after updating function.

4 hrs ago

Sean Nash

We need to look for user request to resume from pause where we would restart BP (at last rate we were at before pause) and re-open art/ven pinch valves and transition back to either ramp or run sta...

We need to look for user request to resume from pause where we would restart BP (at last rate we were at before pause) and re-open art/ven pinch valves and transition back to either ramp or run state (whichever state we were in when we paused).

4 hrs ago

Sean Nash

In this state, we still need to signal transition to dialysis when target volume is reached (same as in ramp state). We also need to look for user request to pause (same as in ramp state).

In this state, we still need to signal transition to dialysis when target volume is reached (same as in ramp state).
We also need to look for user request to pause (same as in ramp state).

4 hrs ago

Sean Nash

We do need an else if here for when user does change the blood flow rate. In that case, we would want to go to run state where we would run continuously at the requested rate without ramping anymor...

We do need an else if here for when user does change the blood flow rate. In that case, we would want to go to run state where we would run continuously at the requested rate without ramping anymore. Ask Nico which message UI sends when user changes blood flow rate.

And we need another else if for when user asks to pause blood prime and we would stop BP (and maybe close art/ven pinch valves) and go to pause state.

4 hrs ago

Sean Nash

Input and Output is cumulativeBloodPrimevolume_mL.

Input and Output is cumulativeBloodPrimevolume_mL.

4 hrs ago

Sean Nash

signal function will take us out of blood prime, so no reason to change state here. We would not want to go to run state even if we weren't leaving - run state is for when user changes blood flow r...

signal function will take us out of blood prime, so no reason to change state here. We would not want to go to run state even if we weren't leaving - run state is for when user changes blood flow rate which they have not done here.

4 hrs ago

Sean Nash

Raghu is fixing this in his Tx Params branch, but you should fix it too. TUBING_BLOOD_PRIME_VOLUME_ML is not a treatment parameter. See Raghu's fix and duplicate it here.

Raghu is fixing this in his Tx Params branch, but you should fix it too. TUBING_BLOOD_PRIME_VOLUME_ML is not a treatment parameter. See Raghu's fix and duplicate it here.

4 hrs ago

Raghu Kallala

the 2nd if statement for beta 1.0 is an ask from systems team to raise fault alarm if user by mistake enable Beta 2.0 config when Beta1.0 is active

the 2nd if statement for beta 1.0 is an ask from systems team to raise fault alarm if user by mistake enable Beta 2.0 config when Beta1.0 is active

4 hrs ago

Sean Nash

4 hrs ago

Vendor - TEL - Varshini Nagabooshanam

LEAHI-TD-FIRMWARE-LDT-3126_Blood Prime - TD
LEAHI-TD-FIRMWARE-LDT-3126_Blood Prime - TD
4 hrs ago

Raghu Kallala

removed both enums

removed both enums

6 hrs ago

Raghu Kallala

LDT-473 updated dialysate delivery request msg payload

Options
    • -2
    • +4
    /MessagePayloads.h
6 hrs ago

Raghu Kallala

Updated

Updated

6 hrs ago

Raghu Kallala

Updated

Updated

6 hrs ago

Sean Nash

Noe says we can distinguish between beta 1.9 and 2.0 w/ ID (4 and 6). We still need test configs for beta 1.0 stuff and non-fpga differences. We can use DD fpga ID # here in this macro instead of t...

Noe says we can distinguish between beta 1.9 and 2.0 w/ ID (4 and 6).
We still need test configs for beta 1.0 stuff and non-fpga differences.
We can use DD fpga ID # here in this macro instead of test config.
Since this is all temporary, I'm not that concerned about how we do this so long as it works.

7 hrs ago

Sean Nash

I think Sameer is saying that the monitor should just call one get level function in FPGA and that one function (in FpgaDD.c) would handle all of this beta 1/1.9/2.0 stuff. I agree, but didn't comm...

I think Sameer is saying that the monitor should just call one get level function in FPGA and that one function (in FpgaDD.c) would handle all of this beta 1/1.9/2.0 stuff.
I agree, but didn't comment on it because it's all temporary anyway.

7 hrs ago

Sean Nash

Why do we need a get function to call another get function? The caller of this function should just call getFPGAGPIOStatus() and then we wouldn't need this.

Why do we need a get function to call another get function? The caller of this function should just call getFPGAGPIOStatus() and then we wouldn't need this.

7 hrs ago

Sean Nash

Move this up to public definitions section.

Move this up to public definitions section.

7 hrs ago

Sean Nash

These don't need to be initialized.

These don't need to be initialized.