UCO run-time status

The UCO has Status attributes to indicate the current state of the object's primitives (grouping of functionality).

The status initially starts as Ready. The ready state indicates that the object is performing normally and is waiting for a command.

When the UCO is processing a command, the Status goes to Busy while it waits for a response from the MES middleware. While in the Busy state, no other commands will be processed.

If the command processes successfully, the status will go back to Ready. If the command fails, the status will go to Error.

If the UCO is in Without Response mode, then the object does not wait for a response from the MES middleware and immediately transitions back to a ready state. The production attribute commands are executed in With Response mode and will reject commands while in the Busy or Error state. The logging of utilization events is done in Without Response mode and will remain in the Ready state.