OMNI 4000/7000 Operations and Maintenance Guide – Rev F
Buffer to allow prover to ready itself for next run
The prove sequence includes each run as configured in the prover Operational Setup tab to meet
the required run repeatability criteria ending with a Prove Complete and acceptable Meter Factor.
At this point you can choose to automatically or manually implement the Meter Factor. See
Section 0 for directions on how to configure prove operations criteria.
If there is a problem with an element of the prove configuration or any of the physical components
involved, you may receive a prove fail or prove abort message. Table 3-2 displays a list of
possible reasons why a prove may fail.
Table 3-2: Prove Sequence Fail Messages
A prove was requested but it exceeded the configured
Inactivity Timer before the sphere hit the first
detector switch.
The allowable temperature deviation between meter and
prover was exceeded.
Bad Repeatability/Bad
Uncertainty
The run results exceeded the Run Repeatability or
Random Uncertainty run acceptability criteria.
The prover seal status has failed.
During the Stability Check, the parameters were outside
the acceptable criteria.
The Prove Permissive status bit was in the wrong state.
A meter active status flag was set low.
Most ‘Prove Complete’ or ‘Prove Abort’ status flags indicating the result of a prove
sequence are updated at the end of a prove sequence or at the time of a prove
abort. These flags remain set until the next prove sequence is requested, at which
time all status flags are cleared.
To Next Page
Loading...
Need help?
General
