(*): for a given application, the periodicity cannot be shorter than that for the
calculation of the indicators by MVX.
Example:
When an indicator goes into alarm mode, one can know whether this indicator
increased suddenly or progressively before reaching the alarm threshold.
2.5.3 OPC parameters via XCOM
When MVX is connected to XCOM (communication engine of ONEPROD NEST
ANALYST (XPR)), it can now:
Monitor original OPC parameters (*)
Use original OPC parameters (*), such as condition parameters
(*): MVX does not have a local OPC connection. Parameters called “original OPC
parameters” are retrieved by the OPC client of the XCOM component, which is
physically located on the same PC as ONEPROD NEST ANALYST (XPR)
2.5.4 Priority management
MVX can now take into account three possible priority levels for each task.
This function allows for a better monitoring of machines with complex or random
operating conditions.
2.5.5 Alarm triggering delay
The purpose of this function is to avoid untimely alarms due to interference or
transient phenomena (e.g., related to the start of a neighbouring machine). It consists
in, on request, acknowledging an alarm status ONLY if it is confirmed during a given
period.
This function is accessible only from ONEPROD NEST ANALYST (XPR). A
triggering delay is defined in seconds. If it is shorter than the cycling time, MVX
performs at least one confirmation measurement.
To Next Page
Loading...