dd-firmware

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
LDT-2004-3 implementing code review comments

    • -3
    • +21
    /firmware/App/Modes/ModeGenDialysate.c
This function sounds a duplicate of 'testValveStateOverride' and not specifically in use. we can delete it.

This function sounds a duplicate of 'testValveStateOverride' and not specifically in use. we can delete it.

Use explicit BOOL conditions (e.g. TRUE == isFreshDialysatePressureInRange).

Use explicit BOOL conditions (e.g. TRUE == isFreshDialysatePressureInRange).

So shouldn't we stop trimmer heater here then?

So shouldn't we stop trimmer heater here then?

The type of payload expected by the function u32ArrayOverride is TEST_OVERRIDE_ARRAY_PAYLOAD_T whereas the type of payload received by the function testBCValveStatesOverride is DD_BC_VALVE_OVERRIDE...

The type of payload expected by the function u32ArrayOverride is TEST_OVERRIDE_ARRAY_PAYLOAD_T whereas the type of payload received by the function testBCValveStatesOverride is DD_BC_VALVE_OVERRIDE_PAYLOAD_T. Because of the mismatch is payload type, we cannot use the function u32ArrayOverride in this case.

We can update this function as part of another Jira ticket.

We can update this function as part of another Jira ticket.

This one looks like maybe we could use the helper function. Have Vinay look at it.

This one looks like maybe we could use the helper function. Have Vinay look at it.

I don't think so. The state is bit encoded, so special handling is required.

I don't think so. The state is bit encoded, so special handling is required.

I prefer to be explicit on BOOL conditions like this (e.g. TRUE == isFreshDialysatePressureInRange).

I prefer to be explicit on BOOL conditions like this (e.g. TRUE == isFreshDialysatePressureInRange).

Remove extra blank line.

Remove extra blank line.

LDT-3344 added function to initialize FPGA registers with every setConfig call

I don't think we need to check test config for variable initialization.

I don't think we need to check test config for variable initialization.

fixed it

fixed it

Fixed it

Fixed it

fixed it

fixed it

fixed it

fixed it

fixed it

fixed it

fixed it

fixed it

fixed it

fixed it

LDT-2004-3 dry bicart review comment implementation

    • -103
    • +144
    /firmware/App/Controllers/DryBiCart.c
    • -21
    • +33
    /firmware/App/Modes/ModeGenDialysate.c
    • -10
    • +10
    /firmware/App/Modes/ModePreGenDialysate.c
LDT-3223-dialysate-flow-rate---dd---mode-tel-dev-test : peer review findings addressed for ConcentratePumps file

Since fill and drain is a single time request and it is not a frequent request similar to supply during dialysate generation. I removed and now run as idle

Since fill and drain is a single time request and it is not a frequent request similar to supply during dialysate generation. I removed and now run as idle

To make it exclusive operation. no previous request should be pending when a new operation is requested. So only one state machine is running at a time. otherwise, while chamber fill is in progress...

To make it exclusive operation. no previous request should be pending when a new operation is requested. So only one state machine is running at a time. otherwise, while chamber fill is in progress, anyone can request drain and both requests will be handled. even through new code run only one state machine at a time, this will ensure that only one request is submitted to drybicart

This was a concern reported by Sean and proposed for restructuring into a single state machine.

LDT-3344 reverted valve changes

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

Merged staging

LDT-3344 latest from staging

LDT-3344 changes made to registers

LDT-3344-changed registers according to beta 2 hdd