Description
The EnumLastValidExt extension controls the output of a EnumPoint by setting it to the last known valid output if the current output is considered invalid. An annotation is then added to the output to indicate that the output has been modified.
Example: The point below has been set to have a "tuesday" and "wednesday" as invalid values and then "tuesday" has been sent to the object. The previous value for this change ("monday") has been retained and an annotation added, informing that an invalid value has been rejected.
Implementation
- Add the extension to an enum point
- Define the invalid ordinals of the monitored value or states considered as invalid.
Properties
- Status: The status of the component. It can produce a fault if there is a runtime error
- FaultCause: describes the origin of the fault in case of problem
- ActiveDerogation: Indicates that the input value is currently blocked (in this case, the property changes to true)
- LastValidTime: Displays the date and time at which the last valid value was observed
- InvalidStatus: Selects the states considered to be invalid
- InvalidValue: Selects theordinals considered to be invalid
The process of validating and saving the last valid output depends on the position of the extension in relation to other possible extensions.
Example: if a point has a proxyExt, a EnumLastValidExt and a history extension, the EnumLastValidExt will save the data from the driver (possibly limiting them) and then the history will save this modified value. If we wanted the history to keep the raw value, it would need to be placed before the EnumLastValidExt extension (via the Workbench's Reorder command). An alarm extension would encounter the same kind of problem (does it apply before or after the correction via EnumLastValidExt ?)
Actions
- refreshInvalidValues: Allows to refresh the invalid values after the range in the parent has been changed
Fault Causes
- "The extension parent was never valid since extension creation or modification"