MsgDefs.h

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
arrange this code and new sensor code in a group- line 131 - 142

arrange this code and new sensor code in a group- line 131 - 142

I think we need a #ifdef TEENSY macro ?

I think we need a #ifdef TEENSY macro ?

Need two spaces before the test function

Need two spaces before the test function

It is there in line 131

It is there in line 131

This is already initialized (properly) near top of function. It is not proper (zero) here.

This is already initialized (properly) near top of function. It is not proper (zero) here.

Is there going to be an #else for new sensor?

Is there going to be an #else for new sensor?

Are we supporting multiple models? Is this for Teensy or new sensor or both?

Are we supporting multiple models? Is this for Teensy or new sensor or both?

Will new conductivity sensor driver have this override too? It looks Teensy specific.

Will new conductivity sensor driver have this override too? It looks Teensy specific.

Fixed it

Fixed it

Ya , I forgot the coding guide line . Fixed it

Ya , I forgot the coding guide line .
Fixed it

fixed it

fixed it

Fixed it

Fixed it

fixed it

fixed it

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

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

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.

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

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.

This doesn't look like a valid substate. We should have an enum for valid substates. In default case, we should trigger a s/w fault and also set the state to a valid state (idle or something like t...

This doesn't look like a valid substate. We should have an enum for valid substates. In default case, we should trigger a s/w fault and also set the state to a valid state (idle or something like that).

I think /// was correct. // will not be seen by doxygen.

I think /// was correct. // will not be seen by doxygen.