DG-DEN-4169

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

Done

Done

Done

Done

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTRHOUGH

RESOLVED in CODE WALKTRHOUGH

RESOLVED in CODE WALKTRHOUGH

RESOLVED in CODE WALKTRHOUGH

Align with "a" character

Align with "a" character

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

The structure allows grouping of temperature sensor properties in one place rather than spanning across multiple 2D arrays.

The structure allows grouping of temperature sensor properties in one place rather than spanning across multiple 2D arrays.

The structure allows grouping of temperature sensor properties in one place rather than spanning across multiple 2D arrays.

The structure allows grouping of temperature sensor properties in one place rather than spanning across multiple 2D arrays.

The windowed count should be used for FPGA error. For this one, the time is 40 ms (4 read and 10 ms per read) of unchanged read count.

The windowed count should be used for FPGA error. For this one, the time is 40 ms (4 read and 10 ms per read) of unchanged read count.

Done.

Done.

Done. Without the sense of time, it is easier to make mistakes. The intention here is 5 seconds rather than 50 seconds.

Done. Without the sense of time, it is easier to make mistakes. The intention here is 5 seconds rather than 50 seconds.

Fixed, the intention is 5 seconds for both rather than 50 seconds. The SYS team will define the threshold later on.

Fixed, the intention is 5 seconds for both rather than 50 seconds. The SYS team will define the threshold later on.

This is not squaring through, it is power of 2.

This is not squaring through, it is power of 2.

Update function header description to remove this functionality.

Update function header description to remove this functionality.

Do we want to have some kind of persistence for this?

Do we want to have some kind of persistence for this?

Recommend using time windowed count here to narrow the time. Currently, it is enforcing a maximum # of instances over entire time system is on.

Recommend using time windowed count here to narrow the time. Currently, it is enforcing a maximum # of instances over entire time system is on.

I generally prefer not using pow() for squaring. Simpler and more efficient to just multiply by itself instead.

I generally prefer not using pow() for squaring. Simpler and more efficient to just multiply by itself instead.

Clearing should probably be a longer persistence than triggering threshold. Currently both are 50 sec. I think that's too long for triggering. Maybe ok for clearing.

Clearing should probably be a longer persistence than triggering threshold. Currently both are 50 sec. I think that's too long for triggering. Maybe ok for clearing.

Try to give a sense of time for this. I think Modes are calling the check function so that's on the General Task so that's every 50ms x 1000 = 50 seconds. I usually define these types of things as ...

Try to give a sense of time for this. I think Modes are calling the check function so that's on the General Task so that's every 50ms x 1000 = 50 seconds. I usually define these types of things as a # of ms divided by the appropriate task interval (in ms).