Understand the interface decision

Driving against an engaged brake can stress the mechanism, while releasing it at an inappropriate time can permit unintended motion. The correct sequence depends on the brake, drive and mechanical design. No generic delay value can establish suitability across different yaw assemblies.

Electric-yaw arrangements differ between turbine designs. These questions describe control and interface reviews, not confirmed MARSTON hardware or operating logic. The relevant machine design, mechanical limits and risk assessment must establish the permitted movement and response.

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.

• Brake type, release method and behavior after supply loss. Identify the exact configuration and the supporting document.
• The approved motor-start and brake-release sequence. Keep the design assumptions visible in the project record.
• Any feedback confirming the relevant brake state. Name the responsible reviewer and resolve any missing information.
• Stop, fault and restoration behavior for the combined mechanism. State how this entry will be verified during acceptance.

Define the acceptance boundary

Accept the sequence when the required states and timing are documented and verified. A brake-release output command should not automatically be treated as proof of physical release. Any credited feedback must have a defined diagnostic role.

Use a test record showing command, brake state and movement together. Preserve abnormal-case evidence separately, particularly where a lost supply or failed release requires a response different from an ordinary commanded stop.