Company Events Academic Community Support Solutions Products & Services Contact NI MyNI

Statechart Development Objects

LabVIEW 2010 Statechart Module Help

Edition Date: June 2013

Part Number: 372103F-01

»View Product Info
Download Help (Windows Only)

Owning Palette: Statechart Functions and Objects

Requires: Statechart Module. This topic might not match its corresponding palette in LabVIEW depending on your operating system, licensed product(s), and target.

Use the Statechart Development objects, consisting of states, regions, pseudostates, and connectors, to construct statecharts. You can place these objects on a statechart diagram.

Palette ObjectDescription
Deep HistorySpecifies that, when the statechart leaves and then returns to a region, the statechart enters the lowest-level substates that were active when the statechart left the region.

To use the Deep History pseudostate, place this pseudostate in a region and then create a transition from a state to this pseudostate.

Note  You use this pseudostate in Part 5 of the Getting Started tutorial.
ForkSplits one incoming transition segment into multiple outgoing segments. You can place this connector within only a state.

Use the Fork connector to create one transition to multiple substates. Each substate must exist in a different orthogonal region.
InitialSpecifies the first state that the enclosing region enters when the statechart enters that region. To specify this state, create a transition from the Initial pseudostate to the state that you want to enter first.

You can place this pseudostate within only a region or at the top level of a statechart diagram. Each region must have one and only one Initial pseudostate.
JoinMerges multiple incoming transition segments into one outgoing segment. You can place this connector within only a state.

Use the Join connector to specify the substates that a statechart must be in before the statechart can leave the enclosing superstate. Each substate must exist in a different orthogonal region.
JunctionConnects common elements of multiple transitions together. For example, you can use a Junction connector to specify that multiple transitions use the same action, even though each transition might have a different trigger. You can place this connector only in a region.
PortIndicates where a transition leaves a state or connector. Ports also indicate where a transition passes through a region.

When you are editing a statechart, ports appear automatically as you create transitions. You can place ports manually only when you are viewing a state as a subdiagram.
RegionDefines the area in which you can place states and pseudostates. Each region must contain an Initial pseudostate and at least one substate.

The top-level statechart diagram represents a region. You can place regions within only a state.
Shallow HistorySpecifies that, when the statechart leaves and then returns to a region, the statechart enters the highest-level substates that were active when the statechart left the region.

To use the Shallow History pseudostate, place this pseudostate in a region and then create a transition from a state to this pseudostate.
StateDefines a state, which is a unique condition in which the statechart can be.

You must place all states within a region. All states must have at least one incoming transition.
TerminalSpecifies a state that can terminate the execution of the enclosing region. To specify this state, create a transition from a state to a Terminal pseudostate. You can place this pseudostate within only a region. You can place more than one Terminal pseudostate in a region.

 

Your Feedback! poor Poor  |  Excellent excellent   Yes No
 Document Quality? 
 Answered Your Question? 
Add Comments 1 2 3 4 5 submit