hdfirmware / firmware / App

Controllers

Clone Tools

Stats

Commits this week: 0
Total Committers: 16
Last Commit: 19 Nov 25
Commits this week: 0

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
Tuesday 22 Mar 2022
4:27 pm

Sean Nash

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

4:27 pm

Sean Nash

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

4:27 pm

Sean Nash

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

3:33 pm

Dara Navaei

3:32 pm

Sean Nash , Michael Garthwaite and Dara Navaei

2:46 pm

Sean Nash

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

2:22 pm

Sean Nash

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

2:21 pm

Sean Nash

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

2:19 pm

Sean Nash

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

2:18 pm

Sean Nash

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

2:15 pm

Sean Nash

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

2:13 pm

Sean Nash

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

2:12 pm

Sean Nash

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

2:10 pm

Sean Nash

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

2:07 pm

Sean Nash

RESOLVED in CODE WALKTHROUGH.

RESOLVED in CODE WALKTHROUGH.

2:04 pm

Michael Garthwaite

RESOLVED IN CODE WALKTHROUGH.

RESOLVED IN CODE WALKTHROUGH.

2:04 pm

Michael Garthwaite

RESOLVED IN CODE WALKTHROUGH.

RESOLVED IN CODE WALKTHROUGH.

2:00 pm

Dara Navaei

Done.

Done.

1:29 pm

hnguyen  (deleted user)

Removed // if ( TRUE == getNoNewTreatmentStatus() ) //{ // rejReason = REQUEST_REJECT_REASON_NO_NEW_TREATMENT_ALARM_TRIGGERED; // }

Removed
// if ( TRUE == getNoNewTreatmentStatus() )
//

Unknown macro: { // rejReason = REQUEST_REJECT_REASON_NO_NEW_TREATMENT_ALARM_TRIGGERED; // }
1:28 pm

hnguyen  (deleted user)

Removed line // payload.alarmsFlags |= ( almStatus.noNewTreatment ? BIT_BY_POS(ALARM_STATE_FLAG_BIT_POS_NO_NEW_TREATMENT) : 0 );

Removed line // payload.alarmsFlags |= ( almStatus.noNewTreatment ? BIT_BY_POS(ALARM_STATE_FLAG_BIT_POS_NO_NEW_TREATMENT) : 0 );

1:27 pm

hnguyen  (deleted user)

Removed line //noNewTreatment = ( TRUE == ALARM_TABLE[ a ].alarmNoNewTreatment ? TRUE : noNewTreatment );

Removed line //noNewTreatment = ( TRUE == ALARM_TABLE[ a ].alarmNoNewTreatment ? TRUE : noNewTreatment );

1:18 pm

Sean Nash

Just delete this line of code.

Just delete this line of code.

1:17 pm

Sean Nash

Just delete this line of code.

Just delete this line of code.

1:17 pm

Sean Nash

Just delete this code.

Just delete this code.

1:14 pm

Sean Nash

It looks like staging branch has things the way it was too.

It looks like staging branch has things the way it was too.

1:04 pm

Sean Nash

Should be since last service (not last treatment).

Should be since last service (not last treatment).

10:43 am

dcox  (deleted user)

This was part of the merge from staging branch.

This was part of the merge from staging branch.

Thursday 17 Mar 2022
1:28 pm

Sean Nash

What is the reason for these changes? Just reading the code, it makes more sense to me that way it was.

What is the reason for these changes? Just reading the code, it makes more sense to me that way it was.

Friday 11 Mar 2022
11:11 am

Michael Garthwaite

0xA04E was originally MSG_ID_DG_HD_COMMUNICATION_STATUS_OVERRIDE. It was moved to 0xA008 due to an out of sync error in our lovely excel sheet. MSG_ID_DG_SET_FANS_RPM_ALARM_START_TIME_OFFSET should...

0xA04E was originally MSG_ID_DG_HD_COMMUNICATION_STATUS_OVERRIDE. It was moved to 0xA008 due to an out of sync error in our lovely excel sheet. MSG_ID_DG_SET_FANS_RPM_ALARM_START_TIME_OFFSET should now be 0xA04E.

Note: These values are what is currently reflected on staging.

10:36 am

Sean Nash

Where is 0xA04E?

Where is 0xA04E?