Este guia está disponível atualmente em inglês.
Technology / Technical guide
Wind Control State Machines: State, Trigger & Completion
A state machine represents behaviour through named states and defined transitions. Its active state summarises a logic context; it is not automatically a direct measurement of every physical component. Understanding that distinction helps explain why a requested transition and its completed physical effect can occur at different times.
A logical transition does not prove a physical action completed.
Separate the state, event, condition and output request before interpreting an operating label.
01 / State meaning
A state selects a context for behaviour.
A finite-state model has a defined set of states.
A finite-state model has a defined set of states. The active state can determine which rules or outputs are relevant. It may summarise a mode such as waiting or active without containing every continuous quantity in the system.
MathWorks’ state-transition explanation distinguishes states and transitions. A continuous speed or temperature can influence the model while remaining different from its state label. Two moments with the same active state can therefore have different physical values.
02 / Events and guards
Occurrence and eligibility are different.
An event marks an occurrence relevant to evaluating the model.
An event marks an occurrence relevant to evaluating the model. A guard is a condition controlling whether a transition is eligible. An event can occur while the guard remains false, so the model need not change states merely because it received the event.
A time-related condition is also different from the arrival of a message labelled with an earlier time. The represented timing and the condition’s meaning affect whether the observed record can explain a transition. Event order alone is not the entire model.
03 / Action boundary
An output request is an effect of the logic.
A transition may produce an output or action request.
A transition may produce an output or action request. The receiving mechanism can require time to respond, encounter a limit or provide a separate indication. Request issued and physical action achieved are therefore distinct statements.
An abstract model could enter state B when issuing a request, or it could use another defined state while waiting for confirmation. Those choices have different semantics. This is a comparison of logical representations, not a turbine protection sequence.
04 / Observation gap
Logic knows the indications it is given.
If completion is represented through a feedback indication, that indication needs an actual physical meaning.
If completion is represented through a feedback indication, that indication needs an actual physical meaning. A command echo is not the same as independently observed completion. Missing, stale or ambiguous information cannot become achieved physical state merely because a state label remains visible.
The feedback guide explains requested and measured quantities. A state machine can organise decisions around those quantities; it does not by itself improve their accuracy or establish additional sensors.
05 / Concurrent behaviour
One label may not describe the whole system.
Several logical regions can represent different functions concurrently.
Several logical regions can represent different functions concurrently. An active state in one function need not establish the state of another. Similarly, a higher-level mode may contain more detailed substates whose distinction matters to interpreting an event.
State labels should therefore be read within their represented boundary. A summary labelled active may describe permission, a selected mode or actual ongoing work depending on the model. These meanings cannot be derived from the word alone.
06 / Product scope
Conceptual logic is separate from released control behaviour.
A useful interpretation distinguishes the modelled state, eligible transition, issued request and supported physical observation.
A useful interpretation distinguishes the modelled state, eligible transition, issued request and supported physical observation. The failure-response guide addresses a separate question about functions under defined failures.
No MARSTON state list, transition guard, completion signal or protection implementation is disclosed or assigned here. The explanation gives no operating sequence, reset command, fault injection or procedure for changing equipment state.
Continue the review with Yaw Feedback: Setpoint, Measurement & Closed-Loop Error.
Continue the review with Fail-Safe & Fail-Operational: Wind Control Concepts.
Continue the review with Control Saturation, Integral Windup & Anti-Windup.
General background: MathWorks: States, events, guards and transition actions. These references explain industry concepts; they are separate from the applicable MARSTON product and project documents.
Key concepts and conditions.
Read each quantity with its reference, units and stated conditions. A general relation does not establish a model-specific value.
| Concept / quantity | Meaning / relation | Conditions / limits |
|---|---|---|
| State | Active logic context | Its physical interpretation must be defined. |
| Event | Relevant occurrence | It need not make a transition eligible. |
| Guard | Condition on a transition | Eligibility differs from action completion. |
| Action request | Output produced by the logic | Requested and achieved effects can differ. |
| Completion indication | Observation with defined physical meaning | A command echo alone is insufficient. |
Engineering questions.
Is a state label always a direct measurement?
No. It can describe a logic mode, permission or summary.
Does every event cause a transition?
No. Defined guards and model context also matter.
Does entering a state prove motion finished?
Only if that completion is part of the state’s defined and supported meaning.
Can several functions have different active states?
Yes. Concurrent or nested behaviour can have different boundaries.
Is a command echo physical confirmation?
Not automatically. It may only show the requested action.
Does this page publish turbine protection logic?
No. It explains concepts without actual guards or operating sequences.
Technical enquiry
Discuss the technical question.
A state machine represents behaviour through named states and defined transitions. Share the model and applicable operating or design information for an engineering discussion.