Understand the interface decision

Range checks detect some wiring faults but do not establish that a sensor measures the intended quantity correctly. A wind controller may need rate-of-change, cross-signal or state-dependent checks. Each diagnostic must account for legitimate operating conditions so that useful protection does not become a source of false trips.

Control performance depends on signal meaning, timing and the approved operating limits. Keep normal optimization separate from protective constraints, and identify which function owns each decision. The selected turbine and controller documentation must define the actual settings.

Put these inputs in the review record

Use a project-specific worksheet to capture the following information. For each entry, name the document, revision and person responsible for resolving any uncertainty.

• Signal range, update behavior and known diagnostic codes. Identify the exact configuration and the supporting document.
• Related measurements or state information available for comparison. Keep the design assumptions visible in the project record.
• Permitted rates of change and legitimate exceptional conditions. Name the responsible reviewer and resolve any missing information.
• The response to doubtful data and the criteria for restoring trust. State how this entry will be verified during acceptance.

Define the acceptance boundary

Define the diagnostic’s purpose and limitations before setting thresholds. Do not claim complete sensor validation from a single comparison. The turbine supplier should determine which control actions remain permitted when a critical signal becomes implausible.

The test plan should include a believable but incorrect signal, not only an obvious open-circuit value. Record both detected failures and diagnostic cases deliberately left outside coverage so the evidence remains specific.