dd-firmware

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
LDT-4414 added fix to update the pwm value in broadcast and changed setpwm from count to percentage

    • -10
    • +15
    /firmware/App/Controllers/RinsePump.c
It is weird that we're responding so far from request. It is not clear to me that Dialin has requested anything at this point.

It is weird that we're responding so far from request. It is not clear to me that Dialin has requested anything at this point.

Details looks weird. Where is inputs and outputs like other function headers?

Details looks weird. Where is inputs and outputs like other function headers?

Now it's backward. You have to change the ENABLE to DISABLE too.

Now it's backward. You have to change the ENABLE to DISABLE too.

Add a blank line after banner.

Add a blank line after banner.

Please restore before you merge to staging.

Please restore before you merge to staging.

If I'm reading this right, we're saying that if bad CRC alarm is NOT enabled, initialize the alarm? That seems backward.

If I'm reading this right, we're saying that if bad CRC alarm is NOT enabled, initialize the alarm? That seems backward.

Same comments as ENABLE_ALARM_1 above.

Same comments as ENABLE_ALARM_1 above.

Same comments as ENABLE_ALARM_1 above.

Same comments as ENABLE_ALARM_1 above.

This definitions has a terrible name (I have no idea what it does) and I think it should be reversed (i.e. alarms are disabled when defined so that a release build will have alarms enabled).

This definitions has a terrible name (I have no idea what it does) and I think it should be reversed (i.e. alarms are disabled when defined so that a release build will have alarms enabled).

There is a #define for BAL_CHAMBER_FILL_VOLUME_ML in BalancingChamber.h. Why can't we just use that instead of redefining it here?

There is a #define for BAL_CHAMBER_FILL_VOLUME_ML in BalancingChamber.h. Why can't we just use that instead of redefining it here?

Should we set this flag to FALSE at top of loop?

Should we set this flag to FALSE at top of loop?

Should we just set this flag to FALSE at top of loop?

Should we just set this flag to FALSE at top of loop?

These P being so much bigger than I are going to be very volatile (lots of big ups and downs). I think these should all be primarily I with much smaller P coefficients.

These P being so much bigger than I are going to be very volatile (lots of big ups and downs). I think these should all be primarily I with much smaller P coefficients.

Update comment.

Update comment.

Is this eventually going to be d1Temp?

Is this eventually going to be d1Temp?

LDT-3273 renamed the CAN mailboxes of DD, disabled RAM ECC check

LDT-3272 updated the size of the comm buffers

align the indent.

align the indent.

Update the naming for 'balChamberSwPeriod' and 'isBalChamberFillinProgress' as per the assignment.

Update the naming for 'balChamberSwPeriod' and 'isBalChamberFillinProgress' as per the assignment.

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

merged LDT-3963 and resolved merge conflicts

LDT-3963 added potential fix for RO loop study issue for drybicarb

LDT-3223-dialysate-flow-rate---dd---mode-tel-dev-test-3-30-2026 : Added test cases for Temperature.c file

i see some of the code is for building the code , could you please remove all such code ? or create a new branch and push it , it will confuse. while pushing the code , all supporting code for buil...

i see some of the code is for building the code , could you please remove all such code ? or create a new branch and push it , it will confuse. while pushing the code , all supporting code for build / functionality should be removed.

LDT-3958 heater control update

    • -20
    • +80
    /firmware/App/Controllers/Heaters.c
I had this commented again to push to the develop branch. It is uncommented for my testing.

I had this commented again to push to the develop branch. It is uncommented for my testing.

Merge branch 'staging' into feature/LDT-3963-dialysate-flow-rate---fw-implem