NVMessagingDD.c

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
LEAHI-DD-FIRMWARE-LDT-5357_Dialysate Composition (Dry Bicarbonate) - FW Implementation - 9/1:
LEAHI-DD-FIRMWARE-LDT-5357_Dialysate Composition (Dry Bicarbonate) - FW Implementation - 9/1:
LDT-5157: Added index logic for get calibration request

LDT-5157: Update set cal write function of the conductivity sensor

  1. … 1 more file in changeset.
LDT-5157: Added FPGA implementation for set cal of conductivity sensor

  1. … 6 more files in changeset.
LEAHI-DD-FIRMWARE-LDT-4873_(Request) Add config to disable conductive level sensor fault
LEAHI-DD-FIRMWARE-LDT-4873_(Request) Add config to disable conductive level sensor fault
LDT-5157: Added Conductivity Sensor Changes

  1. … 5 more files in changeset.
Added but crucible is not showing this change. Please check bitbucket.

Added but crucible is not showing this change. Please check bitbucket.

These variables are correctly initialized to the first enum in the list.

These variables are correctly initialized to the first enum in the list.

Not needed because the retry mechanism is going to be deleted in the next ticket.

Not needed because the retry mechanism is going to be deleted in the next ticket.

I would rather keep it. Anyways, we need an else block after else if, as per MISRA guidelines.

I would rather keep it. Anyways, we need an else block after else if, as per MISRA guidelines.

I would rather keep it. Anyways, we need an else block after else if, as per MISRA guidelines.

I would rather keep it. Anyways, we need an else block after else if, as per MISRA guidelines.

Not needed because the retry mechanism is going to be deleted in the next ticket.

Not needed because the retry mechanism is going to be deleted in the next ticket.

LDT-5157: Resolved all build errors

  1. … 4 more files in changeset.
LDT-5157: Updated set handlers

  1. … 2 more files in changeset.
LDT-5157: Added Conductivity Sensor Record

  1. … 5 more files in changeset.
Same question as above: should we alarm if the retries failed?

Same question as above: should we alarm if the retries failed?

This else is not needed because isFlashAddressValid is set to False at the top of the function (Optional to change).

This else is not needed because isFlashAddressValid is set to False at the top of the function (Optional to change).

This else is not needed because isFlashAddressValid is set to False at the top of the function (Optional to change).

This else is not needed because isFlashAddressValid is set to False at the top of the function (Optional to change).

If a retry goes wrong will you trigger an alarm?

If a retry goes wrong will you trigger an alarm?

Any fault alarm here?

Any fault alarm here?

Have these variables been initialized correctly?

Have these variables been initialized correctly?

Remove extra blank line.

Remove extra blank line.

We generally don't add { } to switch cases unless they require local variable declarations.

We generally don't add { } to switch cases unless they require local variable declarations.

If we're not including a timestamp, can we just remove this line of code?

If we're not including a timestamp, can we just remove this line of code?

Why commented out?

Why commented out?

LEAHI-DD-FIRMWARE-LDT-5157_System Data and Logs (DD) - Conductivity Sensor Calibration (1/3)
LEAHI-DD-FIRMWARE-LDT-5157_System Data and Logs (DD) - Conductivity Sensor Calibration (1/3)
LDT-3735: Addressed review comments

  1. … 4 more files in changeset.