SystemComm.c

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
What is the status of these commented out lines of code? Are we removing or keeping?

What is the status of these commented out lines of code? Are we removing or keeping?

What is the status of this line of code? Are we removing it or keeping it?

What is the status of this line of code? Are we removing it or keeping it?

Align comment.

Align comment.

Need to restore this code.

Need to restore this code.

Need to restore this code.

Need to restore this code.

Why do I not see a call to this function in SystemComm.c?

Why do I not see a call to this function in SystemComm.c?

Either testSetStopRTC() should return a BOOL and set result to that BOOL or you need to just set result to TRUE in this if scope - otherwise the Ack sent below will always be a Nak.

Either testSetStopRTC() should return a BOOL and set result to that BOOL or you need to just set result to TRUE in this if scope - otherwise the Ack sent below will always be a Nak.

HD-DEN-9480_DG_DEV Dialysate Temperature Control
HD-DEN-9480_DG_DEV Dialysate Temperature Control
I couldn't find TBD anywhere in the code!!! What is TBD?

I couldn't find TBD anywhere in the code!!!
What is TBD?

There is nothing to be done in else, so why add it?

There is nothing to be done in else, so why add it?

There is nothing to be done in else, so why add it?

There is nothing to be done in else, so why add it?

Added file header.

Added file header.

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 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.

Fixed.

Fixed.

Fixed.

Fixed.

If using a "==" comparison operator, I like to put the literal first so that the compiler will error if I accidentally use "=" instead. Otherwise, I like to put the literal last because it reads be...

If using a "==" comparison operator, I like to put the literal first so that the compiler will error if I accidentally use "=" instead.
Otherwise, I like to put the literal last because it reads better.

I was thinking 150 was perhaps too fast for UI. But you're right - that only seems to be true at startup. I'll put back to 150.

I was thinking 150 was perhaps too fast for UI. But you're right - that only seems to be true at startup. I'll put back to 150.

This toggle macro is designed to be generic - so does not assume you are toggling between 0 and 1. Could be toggling between ON and OFF or OPEN and CLOSED, etc... So you have to give the macro the ...

This toggle macro is designed to be generic - so does not assume you are toggling between 0 and 1. Could be toggling between ON and OFF or OPEN and CLOSED, etc... So you have to give the macro the two values that you are toggling between.

FALSE is simply zero and TRUE is one. In case a boolean is somehow corrupted to something other than 1 or 0, I like to err on the side of safety. So the way I have it now, if isBloodPumpRunning() g...

FALSE is simply zero and TRUE is one. In case a boolean is somehow corrupted to something other than 1 or 0, I like to err on the side of safety.
So the way I have it now, if isBloodPumpRunning() gets corrupted to > 1, it will consider that the pump is not running which is the safer thing to do.

currentSubMode is already a U32 - no cast needed.

currentSubMode is already a U32 - no cast needed.

Shouldn't be? ( FALSE == isBloodPumpRunning() )

Shouldn't be?

( FALSE == isBloodPumpRunning() )