The status for tracking conditions is handled in the same way as the CND block.
The T_PRE_OUT_Dn and T_OUT_Dn statuses are normally GoodNonCascade.
If any part of a condition's expression is not resolved at run time, the condition sets the T_PRE_OUT_Dn and T_OUT_Dn statuses to BadConfigErr. The entire expression is not evaluated as True if part of the expression is not resolved.
If the expression is resolved but a read error is encountered (for example, when a parameter references a non-communicating controller), the status of T_PRE_OUT_Dn and T_OUT_Dn depend on ALGO_OPTS. If the Abort on Read Errors option is selected, the status of T_PRE_OUT_Dn and T_OUT_Dn remain GoodNonCascade. Otherwise, the status of T_PRE_OUT_Dn and T_OUT_Dn is BadNoComm.
When T_RESET_REQDn is False the T_L_OUT_Dn status is the same as T_OUT_Dn status. The T_L_OUT_Dn status is the same as the T_OUT_Dn status when T_RESET_REQDn is True, T_OUT_Dn is False, and T_L_OUT_Dn is False. When T_L_OUT_Dn transitions to True and T_RESET_REQDn is True, the T_L_OUT_Dn status is copied from the T_OUT_Dn status and held at this status until T_L_OUT_Dn transitions to False.
The OUT_D status is set to the worst status among the T_OUT_Dn and T_L_OUT_Dn parameters. However, when at least one T_L_OUT_Dn is True and its status is not Bad, the output status is set to GoodNonCascade.
The OUT_INT status is set to the worst status among the T_OUT_Dn and T_L_OUT_Dn parameters.
The FIRST_OUT status is set to the worst status among the T_OUT_Dn and T_L_OUT_Dn parameters when the FIRST_OUT value is written. The FIRST_OUT status is reset when the FIRST_OUT value clears.