Status propagation from a secure parameter to a secure parameter reference works in the following ways:
All Good and Uncertain incoming statuses are seen in the secure parameter reference as GoodNonCascade NonSpecific NotLimited (128)
All Bad incoming statuses (except Bad NotConnected NotLimited) are seen in the secure parameter reference as Bad NonSpecific NotLimited (0)
Bad NotConnected NotLimited status is seen in the secure parameter reference as Bad NotConnected NotLimited (8)
If the receiving logic solver isn't receiving valid messages the secure parameter reference status is set to Bad NoCommLUV NotLimited (20) and the last value is retained.
If the receiving logic solver receives a valid message but the revision information doesn't match the secure parameter references revision information the parameter reference status is set to Bad ConfigErr NotLimited (4) and the last value is retained.
All Good and Uncertain statuses are seen in the secure parameter reference as GoodNonCascade NonSpecific NotLimited (128)
All Bad incoming statuses (except Bad NotConnected NotLimited) are seen in the secure parameter reference as Bad NonSpecific NotLimited (0)
Bad NotConnected NotLimited status is seen in the reference as Bad NotConnected NotLimited (8)
In CSLS systems if the receiving logic solver is not receiving valid messages the secure parameter reference status is set to Bad NoCommLUV NotLimited (20) and the last value is retained. This occurs if the secure parameter or reference is modified (the secure parameter name is changed, for example) and both source and destination are not redownloaded. This behavior is different compared to SLS 1508 systems.