Bollar wrote:As far as testing goes, it did begin and pause/dock based on triggers I had previously setup.
It would be great if you could push the error / not ready in the same Plugin trigger, so I don't have to create a separate trigger for each error / not ready I want to track. I currently have one trigger for errors and one for not readys and each stores the latest numerical value and associated text.
The logic for the triggers (as of now) is:
If NotReady == 16, do the binFull trigger actions
If NotReady == 7, do the binMissing trigger actions
Are you saying that you would prefer:
if NotReady != 0, do NotReady trigger
And then you could just save or log the value?
And the same for ErrorCode != 0?