Dialysis.c

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
This probably warrants a comment.

This probably warrants a comment.

Is this a TODO? Can we just do it?

Is this a TODO? Can we just do it?

Why are we checking non-zero here? Seems like we will get stuck here if years really is set to zero.

Why are we checking non-zero here? Seems like we will get stuck here if years really is set to zero.

This whole block of code ( lines 127 - 178 ) was removed in when staging was merged in and not reflected on crucible.

This whole block of code ( lines 127 - 178 ) was removed in when staging was merged in and not reflected on crucible.

This whole block of code ( lines 248 - 304 ) was removed in when staging was merged in and not reflected on crucible.

This whole block of code ( lines 248 - 304 ) was removed in when staging was merged in and not reflected on crucible.

Remove extra blank line.

Remove extra blank line.

Remove last param.

Remove last param.

Remove last param.

Remove last param.

Remove last param.

Remove last param.

Remove param.

Remove param.

Add space before last ")"

Add space before last ")"

Does this need to handle lowercase hex characters and invalid characters?

Does this need to handle lowercase hex characters and invalid characters?

Why not checking payload length?

Why not checking payload length?

Keep blank line.

Keep blank line.

These FPGA registers are obsolete - h/w is no longer in our design. Need to continue to maintain register space since registers after these have not moved. You can think of these obsolete registers...

These FPGA registers are obsolete - h/w is no longer in our design. Need to continue to maintain register space since registers after these have not moved. You can think of these obsolete registers as "reserved" for future purpose.
Dara, I do think we could rename these register fields to something like Reserved1, Reserved2, ...

Monitor execs should be before operation modes exec.

Monitor execs should be before operation modes exec.

Why was blank line removed?

Why was blank line removed?

Align "=".

Align "=".

Add another blank line here.

Add another blank line here.

Idea is to re-purpose these (instead of adding new alarms to bottom of enum). We prefer not to collapse the table when an alarm ID goes obsolete so other alarm IDs do not change.

Idea is to re-purpose these (instead of adding new alarms to bottom of enum). We prefer not to collapse the table when an alarm ID goes obsolete so other alarm IDs do not change.

What is the significance of (OBSOLETE)? Applies to several blocks.

What is the significance of (OBSOLETE)? Applies to several blocks.

fpgaPersistentAlarmGroup is an input.

fpgaPersistentAlarmGroup is an input.

Are all available ALARM_IDs being removed?

Are all available ALARM_IDs being removed?

Do we want this checked into staging?

Do we want this checked into staging?

These are defined in the Code Composer project for DG and HD firmware respectively. You can only have one defined and you must have one defined.

These are defined in the Code Composer project for DG and HD firmware respectively. You can only have one defined and you must have one defined.

What is the purpose of this "no event" event?

What is the purpose of this "no event" event?

What is the purpose of this "no event" event?

What is the purpose of this "no event" event?

No stop property for a high priority alarm? PRS 754 says dialysate temperature alarms are low priority. Temp too low = rank 902. Temp too high = rank 901.

No stop property for a high priority alarm?
PRS 754 says dialysate temperature alarms are low priority. Temp too low = rank 902. Temp too high = rank 901.

Why no stop?

Why no stop?

Why no stop?

Why no stop?