PresOccl.c

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
HD-DEN-15183_IN Treatment Rinseback Workflow Changes
HD-DEN-15183_IN Treatment Rinseback Workflow Changes
HD-DEN-15104_HD Fpga Communications
HD-DEN-15104_HD Fpga Communications
RESOLVED IN CODE WALKTHROUGH

RESOLVED IN CODE WALKTHROUGH

RESOLVED IN CODE WALKTHROUGH

RESOLVED IN CODE WALKTHROUGH

Has 0 persistence on trigger. I'll remove.

Has 0 persistence on trigger. I'll remove.

where?

where?

Isn't the ALARM_ID_HD_AC_POWE_LOST already cleared?

Isn't the ALARM_ID_HD_AC_POWE_LOST already cleared?

Interested in return value?

Interested in return value?

HD-DEN-14999_Alarm Table Updates Part 2
HD-DEN-14999_Alarm Table Updates Part 2
RESOLVED IN CODE WALKTHROUGH.

RESOLVED IN CODE WALKTHROUGH.

I don't know. I believe check in msg should have no payload, but it usually does have a u32 of unknown purpose. I have found that the very first check-in after power up has no payload according to ...

I don't know. I believe check in msg should have no payload, but it usually does have a u32 of unknown purpose. I have found that the very first check-in after power up has no payload according to candump and this was causing alarm 46. Until UI sorts this out, I am not going to check payload.

What is the other flavor of UI check in message. If it is a different size, shouldn't it be its own separate message?

What is the other flavor of UI check in message. If it is a different size, shouldn't it be its own separate message?

RESOLVED IN CODE WALKTHROUGH

RESOLVED IN CODE WALKTHROUGH

RESOLVED IN CODE WALKTHROUGH

RESOLVED IN CODE WALKTHROUGH

Warning (13 min) removed since no longer alarming at 15 min.

Warning (13 min) removed since no longer alarming at 15 min.

Fixed.

Fixed.

Add timeOfLastUICheckin and uiDidCommunicate.

Add timeOfLastUICheckin and uiDidCommunicate.

Does the new code result in one less TRUE comparison? Can rinsebackTimerCtr ever be greater than RINSEBACK_DONE_WARNING_TIME?

Does the new code result in one less TRUE comparison? Can rinsebackTimerCtr ever be greater than RINSEBACK_DONE_WARNING_TIME?

RESOLVED IN CODE WALKTHROUGH

RESOLVED IN CODE WALKTHROUGH

RESOLVED IN CODE WALKTHROUGH

RESOLVED IN CODE WALKTHROUGH

Fixed.

Fixed.

Changing from U32 to S32. It is a relative ms timer (so wouldn't be negative), but I needed to initialize this to something less than zero so that alarm ranking logic will be forced to rank a brand...

Changing from U32 to S32. It is a relative ms timer (so wouldn't be negative), but I needed to initialize this to something less than zero so that alarm ranking logic will be forced to rank a brand new alarm (triggered 0 ms ago).