td-firmware / firmware / App

Modes

Clone Tools

Stats

Commits this week: 10
Total Committers: 11
Last Commit: 14 Mar
Commits this week: 10

Lines of code count not available

Commit Activity

Commits By Day In Week
52 week commits volume
Commits By Day In Week
Commits by day
Commits By Day In Week
Commits by hour
Commits By Hour In Day
Commit calendar
 

Most active committers (90 days)

loading
loading
  • last updated a few seconds ago
All Commits Reviews
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Tuesday 28 Apr
6:13 pm

Sean Nash and Vinayakam Mani

2:31 pm

Sean Nash

???

???

2:30 pm

Sean Nash

Do we need a parameter for confirmation?

Do we need a parameter for confirmation?

Sunday 26 Apr
3:41 pm

Sean Nash

It looks like you deleted it instead of fixing it.

It looks like you deleted it instead of fixing it.

3:40 pm

Sean Nash

Need to request syringe pump to start a seek before we go to seek state. It's not implemented yet, so just put a TODO comment for now.

Need to request syringe pump to start a seek before we go to seek state. It's not implemented yet, so just put a TODO comment for now.

3:39 pm

Sean Nash

Need to check heparin bolus volume > 0 too.

Need to check heparin bolus volume > 0 too.

3:38 pm

Sean Nash

Don't we need to check this too still?

Don't we need to check this too still?

3:37 pm

Sean Nash

Do we need to reset authStartTime here before we go to next state?

Do we need to reset authStartTime here before we go to next state?

3:35 pm

Sean Nash

Put positive case first ( TRUE == ...), then alarm and reject cases.

Put positive case first ( TRUE == ...), then alarm and reject cases.

3:33 pm

Sean Nash

No occlusion sensor in Leahi. Delete variable and references to it.

No occlusion sensor in Leahi. Delete variable and references to it.

3:32 pm

Sean Nash

We should now send the scanned text to the UI s/w for authentication before we go to next state where we wait for UI response.

We should now send the scanned text to the UI s/w for authentication before we go to next state where we wait for UI response.

3:31 pm

Sean Nash

Remove extra l at end of flag name (mis-spelled). And why are we sending this flag with scan event? Seems like the Received flag is what you want here.

Remove extra l at end of flag name (mis-spelled). And why are we sending this flag with scan event? Seems like the Received flag is what you want here.

3:26 pm

Sean Nash

The barcode reader is under TD f/w control via the FPGA (not implemented yet). So asking UI s/w to do a scan doesn't make sense.

The barcode reader is under TD f/w control via the FPGA (not implemented yet). So asking UI s/w to do a scan doesn't make sense.

3:25 pm

Sean Nash

What is this flag for? And why is it only set here and not above where test passed. Also, we are going to the loaded check state, but we are not requesting a scan first.

What is this flag for? And why is it only set here and not above where test passed.
Also, we are going to the loaded check state, but we are not requesting a scan first.

3:21 pm

Sean Nash

Local declarations should come first - move up above reset function above.

Local declarations should come first - move up above reset function above.

3:16 pm

Sean Nash

Leahi doesn't have occlusion sensor, so don't need this if statement. Not sure we need this start state. Maybe we can start in the wait for door close state.

Leahi doesn't have occlusion sensor, so don't need this if statement. Not sure we need this start state. Maybe we can start in the wait for door close state.

3:07 pm

Sean Nash

start state function has same description as wait for door close state function. We shouldn't need 2 states to ensure door is closed.

start state function has same description as wait for door close state function. We shouldn't need 2 states to ensure door is closed.

3:03 pm

Sean Nash

I meant that you should move this function up, not init function down.

I meant that you should move this function up, not init function down.

3:02 pm

Sean Nash

Change to initDrySelfTests() and move to top (should be first function).

Change to initDrySelfTests() and move to top (should be first function).

3:00 pm

Sean Nash

prime state not yet implemented. comment this out w/ TODO comment and add an assignemtn to Rx state here for now.

prime state not yet implemented. comment this out w/ TODO comment and add an assignemtn to Rx state here for now.

2:57 pm

Sean Nash

Why is this commented out?

Why is this commented out?

1:32 pm

Sean Nash

Remove blank line.

Remove blank line.

1:31 pm

Sean Nash

Move this transition function call to the transitionToPostTreatmentMode function below.

Move this transition function call to the transitionToPostTreatmentMode function below.

1:29 pm

Sean Nash

Invalid payload length shouldn't be a reject reason, it should cause a s/w fault (because it suggests the UI and TD software are not compatible versions).

Invalid payload length shouldn't be a reject reason, it should cause a s/w fault (because it suggests the UI and TD software are not compatible versions).

1:08 pm

Sean Nash

We can set bolus volume here now. These functions should be moved to TxParams where all of these settings exist and can be updated.

We can set bolus volume here now. These functions should be moved to TxParams where all of these settings exist and can be updated.

1:06 pm

Sean Nash

Why does confirm msg have duration again? If UI resends duration, we have to validate it again. If UI just sends confirmation of previously sent duration, we don't have to validate it again.

Why does confirm msg have duration again? If UI resends duration, we have to validate it again. If UI just sends confirmation of previously sent duration, we don't have to validate it again.

1:02 pm

Sean Nash

These are already in TxParams I believe.

These are already in TxParams I believe.

1:01 pm

Sean Nash

Should these be moved to Services\TxParams?

Should these be moved to Services\TxParams?

12:59 pm

Sean Nash

Change 1 to TRUE

Change 1 to TRUE

12:58 pm

Sean Nash

Agree with name change, but I think BOOL was the correct type. And BOOL is equivalent to U32 anyway so compiler won't care.

Agree with name change, but I think BOOL was the correct type. And BOOL is equivalent to U32 anyway so compiler won't care.