fmocke

Event Frame SetEndTime() Behaviour

Discussion created by fmocke on May 9, 2019
Latest reply on May 10, 2019 by sraposo

I'm experiencing strange behaviour using the SetEndTime() function (AF SDK) on an automatically generated event that has not yet closed.

 

I need to forcefully close the event in case the operators are trying to start the equipment but cannot for some reason. PI sees one event (looks at equipment amps), but in reality it is actually two events.

The idea is to let the operator close the event using the downtime interface, and let PI automatically open a new event as the condition for being down is still valid. However this is not happening. After closing the event with SetEndTime(), a new event is not opened by PI although the StartTrigger logic is valid.

 

Any idea what is going on here and how I can fix this?

Outcomes