Technology / Engineering guide
Wind Turbine Yaw Faults: Event Records & Support Reporting
A useful yaw-fault report describes what the installation observed before it assigns a cause. Assemble the equipment identity, event sequence and available information so the responsible support team can review the actual configuration.
Report the event with a clear timeline.
Keep observations, controller records and equipment versions together, and distinguish unavailable information from a confirmed device state.
01 / Equipment identity
Begin with the exact installation being reported.
Record the turbine model, serial identity where available, controller identity and relevant configuration versions.
Record the turbine model, serial identity where available, controller identity and relevant configuration versions. Include the applicable supplied package and any documented changes since commissioning. An event from one control arrangement should not be assigned the expected behaviour of another.
The current FD14-50KW uses electric-motor yaw, while earlier Daqing material concerns a hydraulic-yaw configuration. Keep this distinction in a support request. A historical drawing or photograph can otherwise direct the review toward components that are absent from the current installation.
02 / Observed behaviour
Describe the symptom without naming an unverified cause.
Useful observations include when the event appeared, the displayed message, the reported operating state and the behaviour visible through existing permitted monitoring.
Useful observations include when the event appeared, the displayed message, the reported operating state and the behaviour visible through existing permitted monitoring. Terms such as no yaw response, repeated orientation changes or inconsistent heading readings describe observations; they do not diagnose a motor, bearing or sensor failure.
Keep exact alarm text or identifiers if available. Distinguish an operator’s description from a value recorded by a controller. Normal yaw behaviour and its permitted conditions depend on the supplied configuration, so one still image of a nacelle does not establish a control fault.
03 / Event timing
Build the sequence before and after the first indication.
Use one time reference and state the time zone.
Use one time reference and state the time zone. Record the first known indication and retain available information around it: operating mode, generation status, weather records and relevant messages. If systems use different clocks, note the known difference rather than silently align them.
Identify the order of observations and any authorised actions already performed. A later alarm may be a consequence of an earlier condition. Preserve the original records and mark gaps; a missing entry is not evidence that the installation was operating normally during that period.
04 / Signals & states
Separate a requested action from reported feedback.
Where the installed equipment already exposes them, retain yaw requests, permitted-operation states and available feedback.
Where the installed equipment already exposes them, retain yaw requests, permitted-operation states and available feedback. Include units and references for heading or direction values. A nacelle heading and a wind-direction reading need a common reference before their difference can be interpreted.
A command, acknowledgement, movement indication and final state are different records. Collect only the information supported by the supplied system. This guide does not assert that every MARSTON package includes those signals, remote access or a particular sensor.
05 / Context
Provide conditions that help the support team compare events.
Note whether the reported event recurs in a particular operating mode or coincides with other recorded changes.
Note whether the reported event recurs in a particular operating mode or coincides with other recorded changes. Include recent maintenance records, documented equipment replacements or approved configuration changes. Existing photographs may help identify equipment and its version when they were obtained within the permitted site access.
This reporting guide does not provide reset, energisation, cabinet-opening, brake-release or repair steps. Follow the applicable manufacturer and site instructions for operational decisions. The page’s purpose is to improve an evidence pack, not to reproduce a fault or prove a suspected component failure.
06 / Support handover
Send evidence with a specific review question.
Prepare a concise event summary, device list, timeline and the available logs or images.
Prepare a concise event summary, device list, timeline and the available logs or images. State what is known, what is missing and what question requires review, such as interpreting an alarm or identifying the applicable document. Keep confidential configuration material within the agreed support channel.
Request the responsible team’s configuration-specific assessment and any authorised next steps. Maintain the case reference and conclusions with the service record. A successful remote conversation is not evidence that a generic internet procedure is suitable for another turbine or control version.
Continue the review with Wind Turbine Monitoring Data & SCADA Requirements.
Continue the review with Wind Turbine Yaw Bearing & Flange Interface Review.
Continue the review with Wind Turbine Electrical & Mechanical Braking: Function Review.
For additional control-response terminology, review states, triggers and completion, fail-safe and fail-operational concepts, and sensor voting and common causes; keep each concept separate from verified equipment behaviour.
General background: DOE wind-turbine overview: direction, yaw and controller roles. These references explain industry concepts; they are separate from the applicable MARSTON product and project documents.
Prepare the information for this review.
Use the checklist to organise the project information. Mark unavailable items and retain document references.
| Review item | Information to provide | Purpose |
|---|---|---|
| Equipment | Model, controller, configuration and installed changes | Identify the case correctly. |
| Symptom | Exact messages and observed behaviour | Separate observations from suspected causes. |
| Timeline | Time zone, first indication and surrounding records | Establish event order. |
| Available signals | Definitions, units, references and missing values | Make records interpretable. |
| Support pack | Summary, logs, images and review question | Prepare a traceable case. |
Engineering questions.
Does a stationary nacelle prove a yaw fault?
No. Review the operating state, permitted yaw conditions and available records for the actual configuration.
Can I diagnose a failed yaw motor from an alarm alone?
An alarm identifies information for review; it does not by itself prove a component cause. Retain the event context and exact message.
Why do heading and wind-direction references matter?
Values need consistent units and directional references before their difference can be interpreted.
Should a missing signal be entered as zero?
No. Mark information unavailable or invalid as such. Zero may have a specific meaning within the actual data definition.
Does this page provide a reset or repair procedure?
No. Operational and service actions require the applicable manufacturer and site instructions and authorised personnel.
What should I send first?
The exact equipment identity, event summary, timeline, displayed messages and existing available records, with missing information clearly identified.
Technical enquiry
Bring your project information to the discussion.
A useful yaw-fault report describes what the installation observed before it assigns a cause. Share the available information and the equipment scope you want reviewed in a technical quotation.