A small voltage difference between two sensor leads does not prove that either lead is within an acquisition device's permitted operating conditions. For a UG35 payload-interface inquiry, ask the integrator to review differential range, common-mode conditions, reference connections and any required isolation together. Use the exact equipment documentation and a qualified reviewer. A subtraction on a proposal worksheet is not an electrical compatibility assessment, and this article supplies no wiring instructions or unverified UG35 electrical limits.

The missing reference in a two-number answer

A sensor proposal may describe a useful signal as the difference between two terminals. That description is incomplete when the receiving device also constrains those terminals relative to another reference. A buyer who asks only about the difference can receive an apparently satisfactory answer while the integrator's most important interface question remains unresolved.

The problem is not that differential measurement is inherently unsuitable. The problem is treating its name as a complete specification. Ask what the proposed equipment actually permits and under which configuration. The answer should identify the sensor, acquisition device and relevant documentation, rather than relying on a generic explanation of how differential inputs work.

For procurement, this is a document-review task before it becomes an integration task. Do not connect equipment experimentally to resolve a missing specification. Assign the technical review to qualified personnel who can consider the full system, including conditions not described in a short sales response. An unresolved interface should remain unresolved in the quotation.

What NI's guidance says, and what it does not

NI's grounding and measurement guidance explains that real differential systems have common-mode range and rejection limitations. It distinguishes the desired difference signal from conditions common to both inputs and warns that exceeding permitted input conditions can cause error or damage. That guidance supports asking two different questions; it does not provide a specification for UG35 or an unnamed payload.

Our editorial recommendation is to require an interface worksheet that identifies the reference behind every voltage statement. Where a supplier reports only a differential value, ask the integrator to complete the remaining assessment. Do not calculate an approval from incomplete figures or borrow a limit from a similar-looking acquisition module.

Separate three review questions

First, what is the desired signal and how is it represented? The supplier should identify its units, the relevant output configuration and the range applicable to the proposed use. This describes the measurement channel the project wants to receive. It is not yet an answer about whether the proposed connection is acceptable.

Second, what conditions can appear at each input relative to the acquisition system's reference? Ask the integrator to document the expected conditions and the manufacturer's applicable boundaries. The buyer's role is to require the assessment, not to improvise its electrical analysis from a marketing diagram.

Third, what protection or isolation claims are being made? Require documentation that applies to the exact device and use. Common-mode rejection and electrical isolation should not be treated as interchangeable assurances. If a proposal uses either term, ask what evidence supports it and which part of the integration responsibility it actually addresses.

Review item	Requested record
Signal identity	Sensor model, output mode, units and intended measurement
Receiving interface	Acquisition model, configuration and applicable manufacturer documentation
Reference conditions	Integrator's assessment of both inputs and their reference
Protection claims	Exact scope and limitations of any proposed isolation or protection
Decision ownership	Named qualified reviewer, open questions and release conditions

An illustrative paper review

Consider a hypothetical supplier worksheet that lists two input potentials as nine units and eight units relative to a stated reference. Their difference is one unit. That arithmetic alone tells the buyer nothing about whether the receiving device permits either input condition. No real hardware limit is being supplied by this example, and the values are not a suggested test.

A second proposal lists the same desired difference but includes a manufacturer-backed assessment of the reference conditions. That additional evidence makes the proposal more reviewable, not automatically safe or complete. The integrator still needs to consider the actual configuration and any other relevant constraints before making an engineering decision.

The commercial consequence is straightforward. If one bidder has included this review and another has not, their integration scopes are not yet comparable. Ask both to state what engineering work is included, who resolves open interface questions and how a required component change affects the quotation. Do not force an unsupported yes-or-no answer to keep a purchasing timetable unchanged.

Give every assumption an owner

Interface reviews often involve more than one organization. The sensor supplier knows its output, the acquisition supplier knows its inputs and the system integrator owns the combined design. The buyer should ask who collects the evidence and who signs off the resulting configuration. Responsibility should not disappear between separate purchase orders.

Record assumptions in plain language. A worksheet might depend on a particular output mode, an identified cable assembly or a defined reference arrangement. Those details should be confirmed by the responsible specialist and tied to the proposed equipment. An assumption that cannot be verified should remain a question, not quietly migrate into the final equipment list.

Also distinguish a proposed solution from an included solution. A supplier may suggest an additional interface device without including its cost, integration work or verification in the current offer. Ask for an explicit scope response. This article does not recommend any particular component or imply that an accessory is available with UG35.

Plan verification without prescribing a connection

Ask the qualified integrator to define a safe verification plan based on the actual manufacturers' instructions. The plan should state what question each step answers, which configuration it covers and what evidence will be retained. A purchasing article cannot replace equipment-specific electrical safety or integration procedures.

Require a review of the proposed plan before execution, including the authority to stop when an assumption is wrong. Avoid a demonstration whose only acceptance condition is that a plausible number appears on a screen. A displayed number may answer one narrow observation while leaving the documented operating conditions and system-level approval unresolved.

Preserve failed or inconclusive results in the engineering record. Replacing a component or changing a configuration may be reasonable, but the final report should explain what changed. The buyer needs to know which arrangement was evaluated, not merely that someone eventually produced a satisfactory-looking output.

Keep adjacent evidence questions separate

A camera's acquisition timing and an electrical input's operating conditions are different review subjects. The UVH2 RGB shutter-timing guide helps frame the former without specifying any installed camera. Do not use a favorable timing demonstration as proof that a proposed sensor interface has been electrically qualified.

Likewise, a laboratory document needs its own scope review. The UG82 calibration-provider guide explains why a general accreditation certificate does not answer every service question. Neither a calibration badge nor a successful bench reading replaces the integrator's assessment of the actual connection and operating conditions.

A handover package that survives a personnel change

The final purchasing record should identify the approved equipment combination, the documentation reviewed, the responsible decision-maker and any limitations. Keep a clear list of items that were not assessed. A new engineer should be able to distinguish the accepted configuration from an earlier proposal without searching through unrelated email attachments.

Use configuration identifiers on the worksheet and on the associated review evidence. If a supplier substitutes a module, cable or sensor revision, ask the integrator what must be reassessed. Do not assume that an unchanged connector appearance or product family name preserves the previous decision.

The field-oriented lesson is administrative but important: keep the reference conditions beside the signal range. A handover that retains only the desired measurement value loses the question this review was meant to answer. This is editorial buyer guidance, not a claim based on an invented installation or a reported customer incident.

Common purchasing questions

Does a high rejection figure mean unlimited tolerance?

No. Ask the manufacturer and integrator to distinguish the stated rejection behavior from the permitted operating range and other limits. Do not translate a performance figure into permission to exceed a boundary that the actual device documentation imposes.

Can we decide from a sensor data sheet alone?

Not when the decision concerns the combined interface. Request documentation for both sides and a review of the proposed configuration. The buyer should not fill gaps by assuming the receiving equipment behaves like another instrument used on a previous project.

Does UG35 include the reviewed interface?

No such inclusion is asserted here. Confirm the current offer, equipment responsibilities and verification scope directly. This article does not add electrical ratings, payload compatibility, warranty terms or integration services to the approved product information.

Turn the issue into a precise inquiry

Begin with the UG35 product page and the VTOL and fixed-wing drone collection. Describe the intended measurement and identify the proposed sensor if it is already known. Leave unspecified equipment and unverified limits clearly marked as open.

Ask for configuration details and a scoped integrator response covering the receiving interface, reference conditions and qualified review. Include who will accept the engineering evidence and what remains outside the aircraft purchase. The aim is a defensible configuration discussion, not a wiring experiment based on an incomplete subtraction.