td-firmware / firmware / App / Services

SystemCommTD.c

Clone Tools

Stats

Commits this week: 1
Total Committers: 5
Last Commit: 18 Jun
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 minutes ago
All Commits Reviews
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Monday 22 Jun
5:39 pm

Sean Nash

Can we restore this code?

Can we restore this code?

5:36 pm

Sean Nash

Remove FANS test.

Remove FANS test.

5:34 pm

Sean Nash

Remove.

Remove.

5:33 pm

Sean Nash

Move this to Messaging.c

Move this to Messaging.c

5:32 pm

Sean Nash

Remove. Replaced by generic confirmation functions and messages.

Remove. Replaced by generic confirmation functions and messages.

5:30 pm

Sean Nash

Remove this function - replaced by generic confirmation functions.

Remove this function - replaced by generic confirmation functions.

5:28 pm

Sean Nash

Remove this timer code and replace with getConfirmationRequestStatus() and, if status is Accepted, do confirmation code above. If status is Rejected or TimedOut, clear offRequestAwaitingUserConfirm...

Remove this timer code and replace with getConfirmationRequestStatus() and, if status is Accepted, do confirmation code above. If status is Rejected or TimedOut, clear offRequestAwaitingUserConfirmation flag.

5:24 pm

Sean Nash

Replace with request code above.

Replace with request code above.

5:23 pm

Sean Nash

Remove this function after you've moved what we need.

Remove this function after you've moved what we need.

5:23 pm

Sean Nash

No need for these elses.

No need for these elses.

5:22 pm

Sean Nash

Remove send function call.

Remove send function call.

5:22 pm

Sean Nash

Move this code inside if statement to handleOffButtonProcessing() where same if statement exists.

Move this code inside if statement to handleOffButtonProcessing() where same if statement exists.

5:21 pm

Sean Nash

No need to move else - not needed.

No need to move else - not needed.

5:20 pm

Sean Nash

Replace this send function call with addConfirmationRequest()

Replace this send function call with addConfirmationRequest()

5:19 pm

Sean Nash

Move this if down to handleOffButtonProcessing()

Move this if down to handleOffButtonProcessing()

4:58 pm

Sean Nash

Add a confirmation for power off.

Add a confirmation for power off.

4:57 pm

Sean Nash

Remove B7 msg ID. Not needed.

Remove B7 msg ID. Not needed.

4:37 pm

Sean Nash

Use new generic confirmation approach.

Use new generic confirmation approach.

3:03 pm

Vendor - TEL - Arpita Srivastava

uiVersion is an input

uiVersion is an input

3:00 pm

Vendor - TEL - Arpita Srivastava

Should we update the comment as well to remove occlusion?

Should we update the comment as well to remove occlusion?

2:59 pm

Vendor - TEL - Arpita Srivastava

add a blank else block

add a blank else block

2:52 pm

Vendor - TEL - Arpita Srivastava

add comment

add comment

2:52 pm

Vendor - TEL - Arpita Srivastava

add a blank line above this comment.

add a blank line above this comment.

Monday 15 Jun
2:47 pm

Vendor - TEL - Jashwant Gantyada , Vendor - TEL - Arpita Srivastava and Sean Nash

11:36 am

Vendor - TEL - Arpita Srivastava

Thank you for the clarification!

Thank you for the clarification!

11:33 am

Vendor - TEL - Arpita Srivastava

break into two lines

break into two lines

11:32 am

Vendor - TEL - Arpita Srivastava

Add alarm ALARM_ID_TD_EMPTY_SALINE_BAG

Add alarm ALARM_ID_TD_EMPTY_SALINE_BAG

11:27 am

Vendor - TEL - Arpita Srivastava

Add newAlarmIndicateStop to output

Add newAlarmIndicateStop to output

11:21 am

Vendor - TEL - Arpita Srivastava

Add newAlarmIndicateStop to input and output.

Add newAlarmIndicateStop to input and output.

Friday 12 Jun
11:04 pm

Sean Nash

Arpita, we don't want to use doxygen style comments for function prototypes since we cover functions with the function headers. so this is the proper type of comments.

Arpita, we don't want to use doxygen style comments for function prototypes since we cover functions with the function headers. so this is the proper type of comments.