td-firmware / firmware / App / Modes

ModeInitPOST.c

Clone Tools

Stats

Commits this week: 1
Total Committers: 4
Last Commit: 10:05
Commits this week: 1

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 18 Aug
4:41 pm

Vinayakam Mani , Sean Nash and Michael Garthwaite

3:48 pm

Sean Nash

This isn't right. Look at staging for correct code.

This isn't right. Look at staging for correct code.

Monday 17 Aug
4:56 pm

Sean Nash

Thursday 13 Aug
11:08 am

Sean Nash

Shouldn't this be in ModePostTreatment?

Shouldn't this be in ModePostTreatment?

11:06 am

Sean Nash

void cmdStartDDDisinfection( DD_COMMAND_T disCmdType )

void cmdStartDDDisinfection( DD_COMMAND_T disCmdType )

10:58 am

Sean Nash

Update this to work for all standby states w/ switch statement on given "new" state.

Update this to work for all standby states w/ switch statement on given "new" state.

10:32 am

Sean Nash

Why zeroes? Why not send TD version constants?

Why zeroes? Why not send TD version constants?

10:22 am

Sean Nash

Add parameter (disinfection cmd enum from DDDefs.h). Then only need one signal function for all disinfection types.

Add parameter (disinfection cmd enum from DDDefs.h). Then only need one signal function for all disinfection types.

10:16 am

Sean Nash

change enum name too. need 1 alarm for each disinfection type.

change enum name too. need 1 alarm for each disinfection type.

10:14 am

Sean Nash

Just do one dd disinfect request msg with a command ID payload (from enum in DDDefs.h).

Just do one dd disinfect request msg with a command ID payload (from enum in DDDefs.h).

10:06 am

Sean Nash

Missing some disinfects.

Missing some disinfects.

10:05 am

Sean Nash

Move up after HCOL

Move up after HCOL

Thursday 06 Aug
9:25 am

Vendor - TEL - Suresh Dharnala

Wednesday 05 Aug
4:54 pm

Vendor - TEL - Arpita Srivastava and Sean Nash

3:58 pm

Vendor - TEL - Arpita Srivastava

These new functions should be above the test functions. Please align with the Messaging.c file. It looks correct in the Messaging.c file.

These new functions should be above the test functions.

Please align with the Messaging.c file.
It looks correct in the Messaging.c file.

3:54 pm

Vendor - TEL - Arpita Srivastava

Move this above the test functions.

Move this above the test functions.

3:45 pm

Vendor - TEL - Arpita Srivastava

What is the use case of this header include?

What is the use case of this header include?

Tuesday 04 Aug
11:16 am

Vendor - TEL - Arpita Srivastava

align comment

align comment

10:13 am

Vendor - TEL - Arpita Srivastava

When we send any message to UI, usually add the message id in the doxygen header like this. @details \b Message \b Sent: MSG_ID_TD_RESP_TREATMENT_PARAMS_TO_VALIDATE Please refer to the function s...

When we send any message to UI, usually add the message id in the doxygen header like this.

@details \b Message \b Sent: MSG_ID_TD_RESP_TREATMENT_PARAMS_TO_VALIDATE

Please refer to the function sendTreatmentParamsResponse()

10:05 am

Vendor - TEL - Arpita Srivastava

When we send any message to UI, usually add the message id in the doxygen header like this. *@details \b Message \b Sent: MSG_ID_TD_RESP_TREATMENT_PARAMS_TO_VALIDATE Please refer to the functi...

When we send any message to UI, usually add the message id in the doxygen header like this.

  • @details \b Message \b Sent: MSG_ID_TD_RESP_TREATMENT_PARAMS_TO_VALIDATE


Please refer to the function sendTreatmentParamsResponse()

10:05 am

Vendor - TEL - Arpita Srivastava

When we send any message to UI, usually add the message id in the doxygen header like this. *@details \b Message \b Sent: MSG_ID_TD_RESP_TREATMENT_PARAMS_TO_VALIDATE Please refer to the functi...

When we send any message to UI, usually add the message id in the doxygen header like this.

  • @details \b Message \b Sent: MSG_ID_TD_RESP_TREATMENT_PARAMS_TO_VALIDATE


Please refer to the function sendTreatmentParamsResponse()

9:55 am

Vendor - TEL - Arpita Srivastava

It looks like the rows may be misaligned with the alarm ID declarations. For example, ALARM_ID_TD_SAFETY_SHUTDOWN_POST_TEST_FAILED is declared as 207.

It looks like the rows may be misaligned with the alarm ID declarations.
For example, ALARM_ID_TD_SAFETY_SHUTDOWN_POST_TEST_FAILED is declared as 207.

9:53 am

Vendor - TEL - Arpita Srivastava

Should Instructions part be this? A problem was detected with the hemodialysis device.

Should Instructions part be this?

A problem was detected with the hemodialysis device.

9:50 am

Vendor - TEL - Arpita Srivastava

Please confirm if the source is DD?

Please confirm if the source is DD?

Friday 31 Jul
9:33 am

Vendor - TEL - Arpita Srivastava

What is the use case of including this header?

What is the use case of including this header?

9:33 am

Vendor - TEL - Arpita Srivastava

What is the use case of including this header?

What is the use case of including this header?

9:32 am

Vendor - TEL - Arpita Srivastava

Should we move this up before the test functions?

Should we move this up before the test functions?

9:32 am

Vendor - TEL - Arpita Srivastava

Add @messages MSG_ID_TD_POST_FINAL_TEST_RESULT

Add @messages MSG_ID_TD_POST_FINAL_TEST_RESULT

9:32 am

Vendor - TEL - Arpita Srivastava

Add @messages MSG_ID_TD_POST_SINGLE_TEST_RESULT

Add @messages MSG_ID_TD_POST_SINGLE_TEST_RESULT

9:31 am

Vendor - TEL - Arpita Srivastava

is the function description correct? change DG -> DD

is the function description correct?
change DG -> DD