1 of 1 people found this helpful
If you are using PI Server 2017 R2 (AF SDK 2.9.5) or later, an Analysis can output an expression to an attribute. It's not obvious with Event Frame Generation, so click on the down arrow next to Add...
The one obvious limitation of this is that you only write your custom Reason when the event frame closes.
You say this Reason attribute would be binary in nature, but I would suggest it is not. There is a 3rd possible value, and that would be None. One could argue that Waiting for Ore is the same as None, but Waiting for Ore indicates a process state where you are expecting to eventually engage in some process, whereas None indicates you are not simply waiting for ore, but rather not even expecting it and therefore not waiting for it. None could also be the catch-all of any SYSTEM state or badval.
Hi Rick. That is exactly what I need, cannot believe I missed that. Thanks a lot and thanks for your advice.
The Reason is not binary. The signal received from the crusher is.
I have more than one signal which triggers a down event. The official one which is based on the power signal for obvious downs, and then the additional two which are based off the operator status change for 'waiting for ore' and 'crusher bridged'.