SEO Description: Design operational comparison checks for two pressure channels using matched references, verified scaling and documented discrepancy handling.
SEO Keywords: dual pressure sensor plausibility check, OEM skid diagnostics, pressure channel comparison, industrial pressure monitoring, Nexisense
Language versions: 中文 | Español | Русский | Português | Français | Deutsch | Bahasa Indonesia | ไทย | Tiếng Việt | العربية
Two pressure readings can help an OEM investigate inconsistent measurements, but agreement between them does not prove that either value is correct. System integrators should define the purpose of a comparison, the conditions under which it is valid and the action taken when the channels disagree. The result is an operational diagnostic, not an automatic safety qualification.
This guide addresses pressure-channel plausibility for industrial skids and monitoring packages. It does not claim SIL certification, independent protection, fault tolerance or a validated voting architecture for Nexisense products or for a system assembled from two ordinary measurement channels.

Application Requirements for System Integrators
A machine builder may compare two pressure channels during steady operation to identify a configuration or instrumentation issue. First establish whether both instruments are expected to measure the same pressure at the same time. A comparison between different process locations can reflect a real pressure difference rather than a failed sensor.
An engineering contractor may also compare a permanent transmitter with an approved reference during maintenance. Keep that temporary verification distinct from a continuous diagnostic implemented in the PLC. Each use needs its own conditions, acceptance criteria and traceable record.
Nexisense Product Reference
Nexisense YF-P150 and YF-P1101 provide pressure transmitter references with different published accuracy options and response entries. Either proposed channel still needs its ordered range, pressure reference, output and installation reviewed. Combining the best figures from the two families does not create a verified redundant measurement system.
Product specification (English): YF-P150
Product Parameters and Procurement Checks
| Parameter | Published Reference | Engineering Check |
|---|---|---|
| YF-P150 accuracy options | +/-1% FS; +/-0.5% FS; +/-0.25% FS | Use the actual ordered grade and range in the comparison review. |
| YF-P1101 accuracy options | +/-1% FS; +/-0.5% FS | Do not assume both channels have equal uncertainty. |
| YF-P150 response reference | <=2 ms | Review dynamic mismatch separately from a steady-state comparison. |
| YF-P1101 response reference | <=5 ms | Confirm response definition and receiving-system processing. |
| Comparison function | Project-defined operational diagnostic | No SIL, voting or protective-function qualification is asserted. |
Selection Guide
Define what must match before comparison is enabled: pressure reference, engineering unit, range interpretation, measurement location and time alignment. Use the uncertainty and operating conditions of both complete channels when agreeing a discrepancy limit. A convenient fixed difference should not be accepted without a documented application basis.
Review shared dependencies. A common supply, shared input configuration or repeated scaling error can affect both readings. The channels may agree because they share an incorrect assumption. Record the limitations of the diagnostic instead of equating a matching pair with two independent proofs of correct pressure.

Integration, Installation and Commissioning
Specify the comparison state in the PLC or receiving application, including how startup, unavailable data, maintenance and changing pressure are handled. Identify which measurements and timestamps are used. Different filtering or response behaviour can create a discrepancy during a transition even if the steady-state readings are consistent.
Test normal agreement, a simulated discrepancy and loss of each receiving channel using the approved procedure. Verify operator indication and the documented investigation route. Do not automatically suppress an alarm or substitute one reading for another unless that behaviour has been separately engineered and approved for the application.
Illustrative Project Application
Illustrative engineering example: a skid integrator compares two monitoring channels only after confirming matching units, pressure reference and steady-state conditions. A simulated scaling difference is used to test the operator indication and investigation record. This is a software diagnostic example, not a certified safety system or a measured customer outcome.

Why Consider Nexisense
Nexisense publishes model-specific output, accuracy and response references that support a disciplined comparison enquiry. Provide both channel configurations, installation conditions and the diagnostic objective. Request clarification where a product definition is incomplete and keep any safety-related requirement under a separate qualified engineering assessment.
Frequently Asked Questions
Q1. Do two matching readings prove correct pressure?
No. Shared configuration errors or dependencies can affect both channels. Use a documented diagnostic basis and an appropriate independent verification method when required.
Q2. Is a dual-sensor comparison a safety system?
Not by itself. This guide makes no SIL or protective-function claim. Safety-related design and qualification require a separate assessment of the complete application.
Q3. Must both channels use the same engineering unit?
Their values must have an explicitly compatible meaning before comparison. Verify unit, pressure reference, scaling and measurement location rather than comparing display numbers alone.
Q4. Can readings at different locations be compared directly?
Only within an engineered application basis. A real pressure difference between locations may be expected and should not automatically be classified as an instrument fault.
Q5. Why consider response and filtering?
Different dynamic behaviour can affect comparisons during pressure changes. Define when the diagnostic is valid and test it using the actual receiving-system settings.
Q6. What threshold should be used for disagreement?
Use the project requirement and both complete channel uncertainties and conditions. This article does not supply a universal discrepancy threshold or acceptance limit.
Q7. Should one channel automatically replace the other?
Do not assume that behaviour is appropriate. Any substitution, alarm suppression or control action needs its own documented engineering review and approved test scope.
Q8. What evidence belongs in handover?
Retain channel configurations, shared-dependency review, diagnostic conditions, discrepancy handling and test results. State the limitations so operators do not mistake a monitoring check for certified protection.
Summary
Use dual-channel plausibility as a clearly scoped operational diagnostic. Align measurement meaning and timing, review shared dependencies and test discrepancy handling without claiming that agreement establishes accuracy or a qualified protective function.
Further reading: Related Nexisense product specification (English); Existing pressure transmitter engineering guide (English)
