No version for distro humble showing jazzy. Known supported distros are highlighted in the buttons above.
Package symbol

sm_mode_state_behavior_1 package from SMACC2 repo

smacc2 cl_foundation_pose cl_gcalcli cl_generic_sensor cl_http cl_keyboard cl_lifecycle_node cl_mission_tracker cl_modbus_tcp_relay cl_moveit2z cl_nav2z backward_global_planner backward_local_planner forward_global_planner forward_local_planner nav2z_planners_common pure_spinning_local_planner undo_path_global_planner cl_px4_mr cl_ros2_timer eg_conditional_generator eg_random_generator smacc2_msgs sm_atomic_performance_trace_1 sm_atomic_subscribers_performance_test sm_coretest_action_client_1 sm_coretest_callback_rate_1 sm_coretest_exceptions_1 sm_coretest_features_1 sm_coretest_forced_finish_1 sm_coretest_poll_shutdown_1 sm_coretest_post_during_exit_1 sm_coretest_reactor_order_1 sm_coretest_signal_key_1 sm_coretest_timer_handoff_1 sm_coretest_transition_speed_1 sm_advanced_recovery_1 sm_atomic sm_atomic_http sm_atomic_lifecycle sm_atomic_mode_states sm_branching sm_cl_gcalcli_test_1 sm_cl_keyboard_unit_test_1 sm_cl_px4_mr_test_1 sm_cl_px4_mr_test_2 sm_cl_px4_mr_test_3 sm_cl_px4_mr_test_4 sm_cl_px4_mr_test_5 sm_cl_ros2_timer_unit_test_1 sm_data_sharing_1 sm_data_sharing_2 sm_modbus_tcp_relay_test_1 sm_mode_state_behavior_1 sm_multi_stage_1 sm_multithread_test_1 sm_nav2_gazebo_test_1 sm_nav2_gazebo_test_2 sm_nav2_gazebo_test_3 sm_pack_ml sm_panda_cl_moveit2z_cb_inventory sm_panda_cl_moveit2z_cb_inventory_isaacsim sm_retry_logic_1 sm_simple_action_client sm_three_some sr_all_events_go sr_conditional sr_event_countdown

ROS Distro
jazzy

Package Summary

Version 3.1.0
License Apache-2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/robosoft-ai/SMACC2.git
VCS Type git
VCS Version jazzy
Last Updated 2026-11-14
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Demonstrates a client behavior (CbDefaultKeyboardBehavior) defined at the mode state level, persisting across all inner superstate and leaf state transitions. Leaf states have only timer behaviors, avoiding double-event issues.

Maintainers

  • Brett Aldrich

Authors

No additional authors.

sm_mode_state_behavior_1

Demonstrates a client behavior defined at the mode state level, persisting across all inner superstate and leaf state transitions. The key insight: a behavior (here, CbDefaultKeyboardBehavior) owned by a parent state is created once when that parent enters and destroyed only when that parent exits — it survives every inner transition.

This machine also illustrates the correct solution to the double-event problem: if leaf states each had their own CbDefaultKeyboardBehavior, every keypress would generate two identical events (one per active behavior instance). By placing keyboard behavior exclusively in MsRunning, every keypress generates exactly one event regardless of which inner state is active.

What it demonstrates

  • CbDefaultKeyboardBehavior in OrKeyboard is declared in MsRunning::staticConfigure().
  • Leaf states (StPhaseA/B/C, StPhaseX/Y) have only CbTimerCountdownOnce — no keyboard behavior.
  • EvKeyPressN reactions in leaf states fire in response to events generated by MsRunning’s behavior — the event source and the reacting state are at different hierarchy levels.
  • EvKeyPressF reactions in SsPhase1/SsPhase2 switch between superstates; MsRunning’s keyboard behavior remains active throughout.

State hierarchy

SmModeStateBehavior1
├── OrTimer    (ClRos2Timer)
└── OrKeyboard (ClKeyboard)

MsRunning  ←  mode state; owns CbDefaultKeyboardBehavior in OrKeyboard
│              (keyboard behavior persists for the entire machine lifetime)
│
├── SsPhase1  (initial superstate)
│   │  Reacts: EvKeyPressF → SsPhase2
│   │
│   ├── StPhaseA  (initial)  3s timer
│   ├── StPhaseB             3s timer
│   └── StPhaseC             3s timer
│       (A → B → C → A cycle via timer or 'n')
│
└── SsPhase2
    │  Reacts: EvKeyPressF → SsPhase1
    │
    ├── StPhaseX  (initial)  5s timer
    └── StPhaseY             5s timer
        (X → Y → X cycle via timer or 'n')

Build

cd /home/brettpac/workspaces/isaac_ros-dev
colcon build --packages-select sm_mode_state_behavior_1
source install/setup.bash

Launch

ros2 launch sm_mode_state_behavior_1 sm_mode_state_behavior_1.launch.py

This opens two konsole terminals: the state machine node and the keyboard server.

Keyboard controls

Key Effect Handled by
n Advance to the next leaf state within the current superstate Leaf state reaction (event from MsRunning’s behavior)
f Switch between SsPhase1 and SsPhase2 SsPhase1 or SsPhase2 reaction (event from MsRunning’s behavior)
(timer) Auto-advance to next leaf state (3s in Phase1, 5s in Phase2) Leaf state reaction

Send keystrokes via ROS 2 topic (if not using the konsole keyboard server):

ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 110" --once  # n  — next leaf state
ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 102" --once  # f  — switch superstate

Example walkthroughs

Manual leaf state cycling in SsPhase1

Start → MsRunning/SsPhase1/StPhaseA
  → press n → StPhaseB
  → press n → StPhaseC
  → press n → StPhaseA   (back to start of cycle)

Switch to SsPhase2 and cycle there

(in SsPhase1/StPhaseB)
  → press f → SsPhase2/StPhaseX   (SsPhase2 always re-enters at StPhaseX)
  → press n → StPhaseY
  → press n → StPhaseX

Switch back to SsPhase1

```

File truncated at 100 lines see the full file

CHANGELOG
No CHANGELOG found.

Package Dependencies

System Dependencies

Name
xterm

Dependant Packages

No known dependants.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged sm_mode_state_behavior_1 at Robotics Stack Exchange

Package symbol

sm_mode_state_behavior_1 package from SMACC2 repo

smacc2 cl_foundation_pose cl_gcalcli cl_generic_sensor cl_http cl_keyboard cl_lifecycle_node cl_mission_tracker cl_modbus_tcp_relay cl_moveit2z cl_nav2z backward_global_planner backward_local_planner forward_global_planner forward_local_planner nav2z_planners_common pure_spinning_local_planner undo_path_global_planner cl_px4_mr cl_ros2_timer eg_conditional_generator eg_random_generator smacc2_msgs sm_atomic_performance_trace_1 sm_atomic_subscribers_performance_test sm_coretest_action_client_1 sm_coretest_callback_rate_1 sm_coretest_exceptions_1 sm_coretest_features_1 sm_coretest_forced_finish_1 sm_coretest_poll_shutdown_1 sm_coretest_post_during_exit_1 sm_coretest_reactor_order_1 sm_coretest_signal_key_1 sm_coretest_timer_handoff_1 sm_coretest_transition_speed_1 sm_advanced_recovery_1 sm_atomic sm_atomic_http sm_atomic_lifecycle sm_atomic_mode_states sm_branching sm_cl_gcalcli_test_1 sm_cl_keyboard_unit_test_1 sm_cl_px4_mr_test_1 sm_cl_px4_mr_test_2 sm_cl_px4_mr_test_3 sm_cl_px4_mr_test_4 sm_cl_px4_mr_test_5 sm_cl_ros2_timer_unit_test_1 sm_data_sharing_1 sm_data_sharing_2 sm_modbus_tcp_relay_test_1 sm_mode_state_behavior_1 sm_multi_stage_1 sm_multithread_test_1 sm_nav2_gazebo_test_1 sm_nav2_gazebo_test_2 sm_nav2_gazebo_test_3 sm_pack_ml sm_panda_cl_moveit2z_cb_inventory sm_panda_cl_moveit2z_cb_inventory_isaacsim sm_retry_logic_1 sm_simple_action_client sm_three_some sr_all_events_go sr_conditional sr_event_countdown

ROS Distro
jazzy

Package Summary

Version 3.1.0
License Apache-2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/robosoft-ai/SMACC2.git
VCS Type git
VCS Version jazzy
Last Updated 2026-11-14
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Demonstrates a client behavior (CbDefaultKeyboardBehavior) defined at the mode state level, persisting across all inner superstate and leaf state transitions. Leaf states have only timer behaviors, avoiding double-event issues.

Maintainers

  • Brett Aldrich

Authors

No additional authors.

sm_mode_state_behavior_1

Demonstrates a client behavior defined at the mode state level, persisting across all inner superstate and leaf state transitions. The key insight: a behavior (here, CbDefaultKeyboardBehavior) owned by a parent state is created once when that parent enters and destroyed only when that parent exits — it survives every inner transition.

This machine also illustrates the correct solution to the double-event problem: if leaf states each had their own CbDefaultKeyboardBehavior, every keypress would generate two identical events (one per active behavior instance). By placing keyboard behavior exclusively in MsRunning, every keypress generates exactly one event regardless of which inner state is active.

What it demonstrates

  • CbDefaultKeyboardBehavior in OrKeyboard is declared in MsRunning::staticConfigure().
  • Leaf states (StPhaseA/B/C, StPhaseX/Y) have only CbTimerCountdownOnce — no keyboard behavior.
  • EvKeyPressN reactions in leaf states fire in response to events generated by MsRunning’s behavior — the event source and the reacting state are at different hierarchy levels.
  • EvKeyPressF reactions in SsPhase1/SsPhase2 switch between superstates; MsRunning’s keyboard behavior remains active throughout.

State hierarchy

SmModeStateBehavior1
├── OrTimer    (ClRos2Timer)
└── OrKeyboard (ClKeyboard)

MsRunning  ←  mode state; owns CbDefaultKeyboardBehavior in OrKeyboard
│              (keyboard behavior persists for the entire machine lifetime)
│
├── SsPhase1  (initial superstate)
│   │  Reacts: EvKeyPressF → SsPhase2
│   │
│   ├── StPhaseA  (initial)  3s timer
│   ├── StPhaseB             3s timer
│   └── StPhaseC             3s timer
│       (A → B → C → A cycle via timer or 'n')
│
└── SsPhase2
    │  Reacts: EvKeyPressF → SsPhase1
    │
    ├── StPhaseX  (initial)  5s timer
    └── StPhaseY             5s timer
        (X → Y → X cycle via timer or 'n')

Build

cd /home/brettpac/workspaces/isaac_ros-dev
colcon build --packages-select sm_mode_state_behavior_1
source install/setup.bash

Launch

ros2 launch sm_mode_state_behavior_1 sm_mode_state_behavior_1.launch.py

This opens two konsole terminals: the state machine node and the keyboard server.

Keyboard controls

Key Effect Handled by
n Advance to the next leaf state within the current superstate Leaf state reaction (event from MsRunning’s behavior)
f Switch between SsPhase1 and SsPhase2 SsPhase1 or SsPhase2 reaction (event from MsRunning’s behavior)
(timer) Auto-advance to next leaf state (3s in Phase1, 5s in Phase2) Leaf state reaction

Send keystrokes via ROS 2 topic (if not using the konsole keyboard server):

ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 110" --once  # n  — next leaf state
ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 102" --once  # f  — switch superstate

Example walkthroughs

Manual leaf state cycling in SsPhase1

Start → MsRunning/SsPhase1/StPhaseA
  → press n → StPhaseB
  → press n → StPhaseC
  → press n → StPhaseA   (back to start of cycle)

Switch to SsPhase2 and cycle there

(in SsPhase1/StPhaseB)
  → press f → SsPhase2/StPhaseX   (SsPhase2 always re-enters at StPhaseX)
  → press n → StPhaseY
  → press n → StPhaseX

Switch back to SsPhase1

```

File truncated at 100 lines see the full file

CHANGELOG
No CHANGELOG found.

Package Dependencies

System Dependencies

Name
xterm

Dependant Packages

No known dependants.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged sm_mode_state_behavior_1 at Robotics Stack Exchange

No version for distro kilted showing jazzy. Known supported distros are highlighted in the buttons above.
Package symbol

sm_mode_state_behavior_1 package from SMACC2 repo

smacc2 cl_foundation_pose cl_gcalcli cl_generic_sensor cl_http cl_keyboard cl_lifecycle_node cl_mission_tracker cl_modbus_tcp_relay cl_moveit2z cl_nav2z backward_global_planner backward_local_planner forward_global_planner forward_local_planner nav2z_planners_common pure_spinning_local_planner undo_path_global_planner cl_px4_mr cl_ros2_timer eg_conditional_generator eg_random_generator smacc2_msgs sm_atomic_performance_trace_1 sm_atomic_subscribers_performance_test sm_coretest_action_client_1 sm_coretest_callback_rate_1 sm_coretest_exceptions_1 sm_coretest_features_1 sm_coretest_forced_finish_1 sm_coretest_poll_shutdown_1 sm_coretest_post_during_exit_1 sm_coretest_reactor_order_1 sm_coretest_signal_key_1 sm_coretest_timer_handoff_1 sm_coretest_transition_speed_1 sm_advanced_recovery_1 sm_atomic sm_atomic_http sm_atomic_lifecycle sm_atomic_mode_states sm_branching sm_cl_gcalcli_test_1 sm_cl_keyboard_unit_test_1 sm_cl_px4_mr_test_1 sm_cl_px4_mr_test_2 sm_cl_px4_mr_test_3 sm_cl_px4_mr_test_4 sm_cl_px4_mr_test_5 sm_cl_ros2_timer_unit_test_1 sm_data_sharing_1 sm_data_sharing_2 sm_modbus_tcp_relay_test_1 sm_mode_state_behavior_1 sm_multi_stage_1 sm_multithread_test_1 sm_nav2_gazebo_test_1 sm_nav2_gazebo_test_2 sm_nav2_gazebo_test_3 sm_pack_ml sm_panda_cl_moveit2z_cb_inventory sm_panda_cl_moveit2z_cb_inventory_isaacsim sm_retry_logic_1 sm_simple_action_client sm_three_some sr_all_events_go sr_conditional sr_event_countdown

ROS Distro
jazzy

Package Summary

Version 3.1.0
License Apache-2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/robosoft-ai/SMACC2.git
VCS Type git
VCS Version jazzy
Last Updated 2026-11-14
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Demonstrates a client behavior (CbDefaultKeyboardBehavior) defined at the mode state level, persisting across all inner superstate and leaf state transitions. Leaf states have only timer behaviors, avoiding double-event issues.

Maintainers

  • Brett Aldrich

Authors

No additional authors.

sm_mode_state_behavior_1

Demonstrates a client behavior defined at the mode state level, persisting across all inner superstate and leaf state transitions. The key insight: a behavior (here, CbDefaultKeyboardBehavior) owned by a parent state is created once when that parent enters and destroyed only when that parent exits — it survives every inner transition.

This machine also illustrates the correct solution to the double-event problem: if leaf states each had their own CbDefaultKeyboardBehavior, every keypress would generate two identical events (one per active behavior instance). By placing keyboard behavior exclusively in MsRunning, every keypress generates exactly one event regardless of which inner state is active.

What it demonstrates

  • CbDefaultKeyboardBehavior in OrKeyboard is declared in MsRunning::staticConfigure().
  • Leaf states (StPhaseA/B/C, StPhaseX/Y) have only CbTimerCountdownOnce — no keyboard behavior.
  • EvKeyPressN reactions in leaf states fire in response to events generated by MsRunning’s behavior — the event source and the reacting state are at different hierarchy levels.
  • EvKeyPressF reactions in SsPhase1/SsPhase2 switch between superstates; MsRunning’s keyboard behavior remains active throughout.

State hierarchy

SmModeStateBehavior1
├── OrTimer    (ClRos2Timer)
└── OrKeyboard (ClKeyboard)

MsRunning  ←  mode state; owns CbDefaultKeyboardBehavior in OrKeyboard
│              (keyboard behavior persists for the entire machine lifetime)
│
├── SsPhase1  (initial superstate)
│   │  Reacts: EvKeyPressF → SsPhase2
│   │
│   ├── StPhaseA  (initial)  3s timer
│   ├── StPhaseB             3s timer
│   └── StPhaseC             3s timer
│       (A → B → C → A cycle via timer or 'n')
│
└── SsPhase2
    │  Reacts: EvKeyPressF → SsPhase1
    │
    ├── StPhaseX  (initial)  5s timer
    └── StPhaseY             5s timer
        (X → Y → X cycle via timer or 'n')

Build

cd /home/brettpac/workspaces/isaac_ros-dev
colcon build --packages-select sm_mode_state_behavior_1
source install/setup.bash

Launch

ros2 launch sm_mode_state_behavior_1 sm_mode_state_behavior_1.launch.py

This opens two konsole terminals: the state machine node and the keyboard server.

Keyboard controls

Key Effect Handled by
n Advance to the next leaf state within the current superstate Leaf state reaction (event from MsRunning’s behavior)
f Switch between SsPhase1 and SsPhase2 SsPhase1 or SsPhase2 reaction (event from MsRunning’s behavior)
(timer) Auto-advance to next leaf state (3s in Phase1, 5s in Phase2) Leaf state reaction

Send keystrokes via ROS 2 topic (if not using the konsole keyboard server):

ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 110" --once  # n  — next leaf state
ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 102" --once  # f  — switch superstate

Example walkthroughs

Manual leaf state cycling in SsPhase1

Start → MsRunning/SsPhase1/StPhaseA
  → press n → StPhaseB
  → press n → StPhaseC
  → press n → StPhaseA   (back to start of cycle)

Switch to SsPhase2 and cycle there

(in SsPhase1/StPhaseB)
  → press f → SsPhase2/StPhaseX   (SsPhase2 always re-enters at StPhaseX)
  → press n → StPhaseY
  → press n → StPhaseX

Switch back to SsPhase1

```

File truncated at 100 lines see the full file

CHANGELOG
No CHANGELOG found.

Package Dependencies

System Dependencies

Name
xterm

Dependant Packages

No known dependants.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged sm_mode_state_behavior_1 at Robotics Stack Exchange

No version for distro lyrical showing jazzy. Known supported distros are highlighted in the buttons above.
Package symbol

sm_mode_state_behavior_1 package from SMACC2 repo

smacc2 cl_foundation_pose cl_gcalcli cl_generic_sensor cl_http cl_keyboard cl_lifecycle_node cl_mission_tracker cl_modbus_tcp_relay cl_moveit2z cl_nav2z backward_global_planner backward_local_planner forward_global_planner forward_local_planner nav2z_planners_common pure_spinning_local_planner undo_path_global_planner cl_px4_mr cl_ros2_timer eg_conditional_generator eg_random_generator smacc2_msgs sm_atomic_performance_trace_1 sm_atomic_subscribers_performance_test sm_coretest_action_client_1 sm_coretest_callback_rate_1 sm_coretest_exceptions_1 sm_coretest_features_1 sm_coretest_forced_finish_1 sm_coretest_poll_shutdown_1 sm_coretest_post_during_exit_1 sm_coretest_reactor_order_1 sm_coretest_signal_key_1 sm_coretest_timer_handoff_1 sm_coretest_transition_speed_1 sm_advanced_recovery_1 sm_atomic sm_atomic_http sm_atomic_lifecycle sm_atomic_mode_states sm_branching sm_cl_gcalcli_test_1 sm_cl_keyboard_unit_test_1 sm_cl_px4_mr_test_1 sm_cl_px4_mr_test_2 sm_cl_px4_mr_test_3 sm_cl_px4_mr_test_4 sm_cl_px4_mr_test_5 sm_cl_ros2_timer_unit_test_1 sm_data_sharing_1 sm_data_sharing_2 sm_modbus_tcp_relay_test_1 sm_mode_state_behavior_1 sm_multi_stage_1 sm_multithread_test_1 sm_nav2_gazebo_test_1 sm_nav2_gazebo_test_2 sm_nav2_gazebo_test_3 sm_pack_ml sm_panda_cl_moveit2z_cb_inventory sm_panda_cl_moveit2z_cb_inventory_isaacsim sm_retry_logic_1 sm_simple_action_client sm_three_some sr_all_events_go sr_conditional sr_event_countdown

ROS Distro
jazzy

Package Summary

Version 3.1.0
License Apache-2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/robosoft-ai/SMACC2.git
VCS Type git
VCS Version jazzy
Last Updated 2026-11-14
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Demonstrates a client behavior (CbDefaultKeyboardBehavior) defined at the mode state level, persisting across all inner superstate and leaf state transitions. Leaf states have only timer behaviors, avoiding double-event issues.

Maintainers

  • Brett Aldrich

Authors

No additional authors.

sm_mode_state_behavior_1

Demonstrates a client behavior defined at the mode state level, persisting across all inner superstate and leaf state transitions. The key insight: a behavior (here, CbDefaultKeyboardBehavior) owned by a parent state is created once when that parent enters and destroyed only when that parent exits — it survives every inner transition.

This machine also illustrates the correct solution to the double-event problem: if leaf states each had their own CbDefaultKeyboardBehavior, every keypress would generate two identical events (one per active behavior instance). By placing keyboard behavior exclusively in MsRunning, every keypress generates exactly one event regardless of which inner state is active.

What it demonstrates

  • CbDefaultKeyboardBehavior in OrKeyboard is declared in MsRunning::staticConfigure().
  • Leaf states (StPhaseA/B/C, StPhaseX/Y) have only CbTimerCountdownOnce — no keyboard behavior.
  • EvKeyPressN reactions in leaf states fire in response to events generated by MsRunning’s behavior — the event source and the reacting state are at different hierarchy levels.
  • EvKeyPressF reactions in SsPhase1/SsPhase2 switch between superstates; MsRunning’s keyboard behavior remains active throughout.

State hierarchy

SmModeStateBehavior1
├── OrTimer    (ClRos2Timer)
└── OrKeyboard (ClKeyboard)

MsRunning  ←  mode state; owns CbDefaultKeyboardBehavior in OrKeyboard
│              (keyboard behavior persists for the entire machine lifetime)
│
├── SsPhase1  (initial superstate)
│   │  Reacts: EvKeyPressF → SsPhase2
│   │
│   ├── StPhaseA  (initial)  3s timer
│   ├── StPhaseB             3s timer
│   └── StPhaseC             3s timer
│       (A → B → C → A cycle via timer or 'n')
│
└── SsPhase2
    │  Reacts: EvKeyPressF → SsPhase1
    │
    ├── StPhaseX  (initial)  5s timer
    └── StPhaseY             5s timer
        (X → Y → X cycle via timer or 'n')

Build

cd /home/brettpac/workspaces/isaac_ros-dev
colcon build --packages-select sm_mode_state_behavior_1
source install/setup.bash

Launch

ros2 launch sm_mode_state_behavior_1 sm_mode_state_behavior_1.launch.py

This opens two konsole terminals: the state machine node and the keyboard server.

Keyboard controls

Key Effect Handled by
n Advance to the next leaf state within the current superstate Leaf state reaction (event from MsRunning’s behavior)
f Switch between SsPhase1 and SsPhase2 SsPhase1 or SsPhase2 reaction (event from MsRunning’s behavior)
(timer) Auto-advance to next leaf state (3s in Phase1, 5s in Phase2) Leaf state reaction

Send keystrokes via ROS 2 topic (if not using the konsole keyboard server):

ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 110" --once  # n  — next leaf state
ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 102" --once  # f  — switch superstate

Example walkthroughs

Manual leaf state cycling in SsPhase1

Start → MsRunning/SsPhase1/StPhaseA
  → press n → StPhaseB
  → press n → StPhaseC
  → press n → StPhaseA   (back to start of cycle)

Switch to SsPhase2 and cycle there

(in SsPhase1/StPhaseB)
  → press f → SsPhase2/StPhaseX   (SsPhase2 always re-enters at StPhaseX)
  → press n → StPhaseY
  → press n → StPhaseX

Switch back to SsPhase1

```

File truncated at 100 lines see the full file

CHANGELOG
No CHANGELOG found.

Package Dependencies

System Dependencies

Name
xterm

Dependant Packages

No known dependants.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged sm_mode_state_behavior_1 at Robotics Stack Exchange

No version for distro rolling showing jazzy. Known supported distros are highlighted in the buttons above.
Package symbol

sm_mode_state_behavior_1 package from SMACC2 repo

smacc2 cl_foundation_pose cl_gcalcli cl_generic_sensor cl_http cl_keyboard cl_lifecycle_node cl_mission_tracker cl_modbus_tcp_relay cl_moveit2z cl_nav2z backward_global_planner backward_local_planner forward_global_planner forward_local_planner nav2z_planners_common pure_spinning_local_planner undo_path_global_planner cl_px4_mr cl_ros2_timer eg_conditional_generator eg_random_generator smacc2_msgs sm_atomic_performance_trace_1 sm_atomic_subscribers_performance_test sm_coretest_action_client_1 sm_coretest_callback_rate_1 sm_coretest_exceptions_1 sm_coretest_features_1 sm_coretest_forced_finish_1 sm_coretest_poll_shutdown_1 sm_coretest_post_during_exit_1 sm_coretest_reactor_order_1 sm_coretest_signal_key_1 sm_coretest_timer_handoff_1 sm_coretest_transition_speed_1 sm_advanced_recovery_1 sm_atomic sm_atomic_http sm_atomic_lifecycle sm_atomic_mode_states sm_branching sm_cl_gcalcli_test_1 sm_cl_keyboard_unit_test_1 sm_cl_px4_mr_test_1 sm_cl_px4_mr_test_2 sm_cl_px4_mr_test_3 sm_cl_px4_mr_test_4 sm_cl_px4_mr_test_5 sm_cl_ros2_timer_unit_test_1 sm_data_sharing_1 sm_data_sharing_2 sm_modbus_tcp_relay_test_1 sm_mode_state_behavior_1 sm_multi_stage_1 sm_multithread_test_1 sm_nav2_gazebo_test_1 sm_nav2_gazebo_test_2 sm_nav2_gazebo_test_3 sm_pack_ml sm_panda_cl_moveit2z_cb_inventory sm_panda_cl_moveit2z_cb_inventory_isaacsim sm_retry_logic_1 sm_simple_action_client sm_three_some sr_all_events_go sr_conditional sr_event_countdown

ROS Distro
jazzy

Package Summary

Version 3.1.0
License Apache-2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/robosoft-ai/SMACC2.git
VCS Type git
VCS Version jazzy
Last Updated 2026-11-14
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Demonstrates a client behavior (CbDefaultKeyboardBehavior) defined at the mode state level, persisting across all inner superstate and leaf state transitions. Leaf states have only timer behaviors, avoiding double-event issues.

Maintainers

  • Brett Aldrich

Authors

No additional authors.

sm_mode_state_behavior_1

Demonstrates a client behavior defined at the mode state level, persisting across all inner superstate and leaf state transitions. The key insight: a behavior (here, CbDefaultKeyboardBehavior) owned by a parent state is created once when that parent enters and destroyed only when that parent exits — it survives every inner transition.

This machine also illustrates the correct solution to the double-event problem: if leaf states each had their own CbDefaultKeyboardBehavior, every keypress would generate two identical events (one per active behavior instance). By placing keyboard behavior exclusively in MsRunning, every keypress generates exactly one event regardless of which inner state is active.

What it demonstrates

  • CbDefaultKeyboardBehavior in OrKeyboard is declared in MsRunning::staticConfigure().
  • Leaf states (StPhaseA/B/C, StPhaseX/Y) have only CbTimerCountdownOnce — no keyboard behavior.
  • EvKeyPressN reactions in leaf states fire in response to events generated by MsRunning’s behavior — the event source and the reacting state are at different hierarchy levels.
  • EvKeyPressF reactions in SsPhase1/SsPhase2 switch between superstates; MsRunning’s keyboard behavior remains active throughout.

State hierarchy

SmModeStateBehavior1
├── OrTimer    (ClRos2Timer)
└── OrKeyboard (ClKeyboard)

MsRunning  ←  mode state; owns CbDefaultKeyboardBehavior in OrKeyboard
│              (keyboard behavior persists for the entire machine lifetime)
│
├── SsPhase1  (initial superstate)
│   │  Reacts: EvKeyPressF → SsPhase2
│   │
│   ├── StPhaseA  (initial)  3s timer
│   ├── StPhaseB             3s timer
│   └── StPhaseC             3s timer
│       (A → B → C → A cycle via timer or 'n')
│
└── SsPhase2
    │  Reacts: EvKeyPressF → SsPhase1
    │
    ├── StPhaseX  (initial)  5s timer
    └── StPhaseY             5s timer
        (X → Y → X cycle via timer or 'n')

Build

cd /home/brettpac/workspaces/isaac_ros-dev
colcon build --packages-select sm_mode_state_behavior_1
source install/setup.bash

Launch

ros2 launch sm_mode_state_behavior_1 sm_mode_state_behavior_1.launch.py

This opens two konsole terminals: the state machine node and the keyboard server.

Keyboard controls

Key Effect Handled by
n Advance to the next leaf state within the current superstate Leaf state reaction (event from MsRunning’s behavior)
f Switch between SsPhase1 and SsPhase2 SsPhase1 or SsPhase2 reaction (event from MsRunning’s behavior)
(timer) Auto-advance to next leaf state (3s in Phase1, 5s in Phase2) Leaf state reaction

Send keystrokes via ROS 2 topic (if not using the konsole keyboard server):

ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 110" --once  # n  — next leaf state
ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 102" --once  # f  — switch superstate

Example walkthroughs

Manual leaf state cycling in SsPhase1

Start → MsRunning/SsPhase1/StPhaseA
  → press n → StPhaseB
  → press n → StPhaseC
  → press n → StPhaseA   (back to start of cycle)

Switch to SsPhase2 and cycle there

(in SsPhase1/StPhaseB)
  → press f → SsPhase2/StPhaseX   (SsPhase2 always re-enters at StPhaseX)
  → press n → StPhaseY
  → press n → StPhaseX

Switch back to SsPhase1

```

File truncated at 100 lines see the full file

CHANGELOG
No CHANGELOG found.

Package Dependencies

System Dependencies

Name
xterm

Dependant Packages

No known dependants.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged sm_mode_state_behavior_1 at Robotics Stack Exchange

No version for distro ardent showing jazzy. Known supported distros are highlighted in the buttons above.
Package symbol

sm_mode_state_behavior_1 package from SMACC2 repo

smacc2 cl_foundation_pose cl_gcalcli cl_generic_sensor cl_http cl_keyboard cl_lifecycle_node cl_mission_tracker cl_modbus_tcp_relay cl_moveit2z cl_nav2z backward_global_planner backward_local_planner forward_global_planner forward_local_planner nav2z_planners_common pure_spinning_local_planner undo_path_global_planner cl_px4_mr cl_ros2_timer eg_conditional_generator eg_random_generator smacc2_msgs sm_atomic_performance_trace_1 sm_atomic_subscribers_performance_test sm_coretest_action_client_1 sm_coretest_callback_rate_1 sm_coretest_exceptions_1 sm_coretest_features_1 sm_coretest_forced_finish_1 sm_coretest_poll_shutdown_1 sm_coretest_post_during_exit_1 sm_coretest_reactor_order_1 sm_coretest_signal_key_1 sm_coretest_timer_handoff_1 sm_coretest_transition_speed_1 sm_advanced_recovery_1 sm_atomic sm_atomic_http sm_atomic_lifecycle sm_atomic_mode_states sm_branching sm_cl_gcalcli_test_1 sm_cl_keyboard_unit_test_1 sm_cl_px4_mr_test_1 sm_cl_px4_mr_test_2 sm_cl_px4_mr_test_3 sm_cl_px4_mr_test_4 sm_cl_px4_mr_test_5 sm_cl_ros2_timer_unit_test_1 sm_data_sharing_1 sm_data_sharing_2 sm_modbus_tcp_relay_test_1 sm_mode_state_behavior_1 sm_multi_stage_1 sm_multithread_test_1 sm_nav2_gazebo_test_1 sm_nav2_gazebo_test_2 sm_nav2_gazebo_test_3 sm_pack_ml sm_panda_cl_moveit2z_cb_inventory sm_panda_cl_moveit2z_cb_inventory_isaacsim sm_retry_logic_1 sm_simple_action_client sm_three_some sr_all_events_go sr_conditional sr_event_countdown

ROS Distro
jazzy

Package Summary

Version 3.1.0
License Apache-2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/robosoft-ai/SMACC2.git
VCS Type git
VCS Version jazzy
Last Updated 2026-11-14
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Demonstrates a client behavior (CbDefaultKeyboardBehavior) defined at the mode state level, persisting across all inner superstate and leaf state transitions. Leaf states have only timer behaviors, avoiding double-event issues.

Maintainers

  • Brett Aldrich

Authors

No additional authors.

sm_mode_state_behavior_1

Demonstrates a client behavior defined at the mode state level, persisting across all inner superstate and leaf state transitions. The key insight: a behavior (here, CbDefaultKeyboardBehavior) owned by a parent state is created once when that parent enters and destroyed only when that parent exits — it survives every inner transition.

This machine also illustrates the correct solution to the double-event problem: if leaf states each had their own CbDefaultKeyboardBehavior, every keypress would generate two identical events (one per active behavior instance). By placing keyboard behavior exclusively in MsRunning, every keypress generates exactly one event regardless of which inner state is active.

What it demonstrates

  • CbDefaultKeyboardBehavior in OrKeyboard is declared in MsRunning::staticConfigure().
  • Leaf states (StPhaseA/B/C, StPhaseX/Y) have only CbTimerCountdownOnce — no keyboard behavior.
  • EvKeyPressN reactions in leaf states fire in response to events generated by MsRunning’s behavior — the event source and the reacting state are at different hierarchy levels.
  • EvKeyPressF reactions in SsPhase1/SsPhase2 switch between superstates; MsRunning’s keyboard behavior remains active throughout.

State hierarchy

SmModeStateBehavior1
├── OrTimer    (ClRos2Timer)
└── OrKeyboard (ClKeyboard)

MsRunning  ←  mode state; owns CbDefaultKeyboardBehavior in OrKeyboard
│              (keyboard behavior persists for the entire machine lifetime)
│
├── SsPhase1  (initial superstate)
│   │  Reacts: EvKeyPressF → SsPhase2
│   │
│   ├── StPhaseA  (initial)  3s timer
│   ├── StPhaseB             3s timer
│   └── StPhaseC             3s timer
│       (A → B → C → A cycle via timer or 'n')
│
└── SsPhase2
    │  Reacts: EvKeyPressF → SsPhase1
    │
    ├── StPhaseX  (initial)  5s timer
    └── StPhaseY             5s timer
        (X → Y → X cycle via timer or 'n')

Build

cd /home/brettpac/workspaces/isaac_ros-dev
colcon build --packages-select sm_mode_state_behavior_1
source install/setup.bash

Launch

ros2 launch sm_mode_state_behavior_1 sm_mode_state_behavior_1.launch.py

This opens two konsole terminals: the state machine node and the keyboard server.

Keyboard controls

Key Effect Handled by
n Advance to the next leaf state within the current superstate Leaf state reaction (event from MsRunning’s behavior)
f Switch between SsPhase1 and SsPhase2 SsPhase1 or SsPhase2 reaction (event from MsRunning’s behavior)
(timer) Auto-advance to next leaf state (3s in Phase1, 5s in Phase2) Leaf state reaction

Send keystrokes via ROS 2 topic (if not using the konsole keyboard server):

ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 110" --once  # n  — next leaf state
ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 102" --once  # f  — switch superstate

Example walkthroughs

Manual leaf state cycling in SsPhase1

Start → MsRunning/SsPhase1/StPhaseA
  → press n → StPhaseB
  → press n → StPhaseC
  → press n → StPhaseA   (back to start of cycle)

Switch to SsPhase2 and cycle there

(in SsPhase1/StPhaseB)
  → press f → SsPhase2/StPhaseX   (SsPhase2 always re-enters at StPhaseX)
  → press n → StPhaseY
  → press n → StPhaseX

Switch back to SsPhase1

```

File truncated at 100 lines see the full file

CHANGELOG
No CHANGELOG found.

Package Dependencies

System Dependencies

Name
xterm

Dependant Packages

No known dependants.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged sm_mode_state_behavior_1 at Robotics Stack Exchange

No version for distro bouncy showing jazzy. Known supported distros are highlighted in the buttons above.
Package symbol

sm_mode_state_behavior_1 package from SMACC2 repo

smacc2 cl_foundation_pose cl_gcalcli cl_generic_sensor cl_http cl_keyboard cl_lifecycle_node cl_mission_tracker cl_modbus_tcp_relay cl_moveit2z cl_nav2z backward_global_planner backward_local_planner forward_global_planner forward_local_planner nav2z_planners_common pure_spinning_local_planner undo_path_global_planner cl_px4_mr cl_ros2_timer eg_conditional_generator eg_random_generator smacc2_msgs sm_atomic_performance_trace_1 sm_atomic_subscribers_performance_test sm_coretest_action_client_1 sm_coretest_callback_rate_1 sm_coretest_exceptions_1 sm_coretest_features_1 sm_coretest_forced_finish_1 sm_coretest_poll_shutdown_1 sm_coretest_post_during_exit_1 sm_coretest_reactor_order_1 sm_coretest_signal_key_1 sm_coretest_timer_handoff_1 sm_coretest_transition_speed_1 sm_advanced_recovery_1 sm_atomic sm_atomic_http sm_atomic_lifecycle sm_atomic_mode_states sm_branching sm_cl_gcalcli_test_1 sm_cl_keyboard_unit_test_1 sm_cl_px4_mr_test_1 sm_cl_px4_mr_test_2 sm_cl_px4_mr_test_3 sm_cl_px4_mr_test_4 sm_cl_px4_mr_test_5 sm_cl_ros2_timer_unit_test_1 sm_data_sharing_1 sm_data_sharing_2 sm_modbus_tcp_relay_test_1 sm_mode_state_behavior_1 sm_multi_stage_1 sm_multithread_test_1 sm_nav2_gazebo_test_1 sm_nav2_gazebo_test_2 sm_nav2_gazebo_test_3 sm_pack_ml sm_panda_cl_moveit2z_cb_inventory sm_panda_cl_moveit2z_cb_inventory_isaacsim sm_retry_logic_1 sm_simple_action_client sm_three_some sr_all_events_go sr_conditional sr_event_countdown

ROS Distro
jazzy

Package Summary

Version 3.1.0
License Apache-2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/robosoft-ai/SMACC2.git
VCS Type git
VCS Version jazzy
Last Updated 2026-11-14
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Demonstrates a client behavior (CbDefaultKeyboardBehavior) defined at the mode state level, persisting across all inner superstate and leaf state transitions. Leaf states have only timer behaviors, avoiding double-event issues.

Maintainers

  • Brett Aldrich

Authors

No additional authors.

sm_mode_state_behavior_1

Demonstrates a client behavior defined at the mode state level, persisting across all inner superstate and leaf state transitions. The key insight: a behavior (here, CbDefaultKeyboardBehavior) owned by a parent state is created once when that parent enters and destroyed only when that parent exits — it survives every inner transition.

This machine also illustrates the correct solution to the double-event problem: if leaf states each had their own CbDefaultKeyboardBehavior, every keypress would generate two identical events (one per active behavior instance). By placing keyboard behavior exclusively in MsRunning, every keypress generates exactly one event regardless of which inner state is active.

What it demonstrates

  • CbDefaultKeyboardBehavior in OrKeyboard is declared in MsRunning::staticConfigure().
  • Leaf states (StPhaseA/B/C, StPhaseX/Y) have only CbTimerCountdownOnce — no keyboard behavior.
  • EvKeyPressN reactions in leaf states fire in response to events generated by MsRunning’s behavior — the event source and the reacting state are at different hierarchy levels.
  • EvKeyPressF reactions in SsPhase1/SsPhase2 switch between superstates; MsRunning’s keyboard behavior remains active throughout.

State hierarchy

SmModeStateBehavior1
├── OrTimer    (ClRos2Timer)
└── OrKeyboard (ClKeyboard)

MsRunning  ←  mode state; owns CbDefaultKeyboardBehavior in OrKeyboard
│              (keyboard behavior persists for the entire machine lifetime)
│
├── SsPhase1  (initial superstate)
│   │  Reacts: EvKeyPressF → SsPhase2
│   │
│   ├── StPhaseA  (initial)  3s timer
│   ├── StPhaseB             3s timer
│   └── StPhaseC             3s timer
│       (A → B → C → A cycle via timer or 'n')
│
└── SsPhase2
    │  Reacts: EvKeyPressF → SsPhase1
    │
    ├── StPhaseX  (initial)  5s timer
    └── StPhaseY             5s timer
        (X → Y → X cycle via timer or 'n')

Build

cd /home/brettpac/workspaces/isaac_ros-dev
colcon build --packages-select sm_mode_state_behavior_1
source install/setup.bash

Launch

ros2 launch sm_mode_state_behavior_1 sm_mode_state_behavior_1.launch.py

This opens two konsole terminals: the state machine node and the keyboard server.

Keyboard controls

Key Effect Handled by
n Advance to the next leaf state within the current superstate Leaf state reaction (event from MsRunning’s behavior)
f Switch between SsPhase1 and SsPhase2 SsPhase1 or SsPhase2 reaction (event from MsRunning’s behavior)
(timer) Auto-advance to next leaf state (3s in Phase1, 5s in Phase2) Leaf state reaction

Send keystrokes via ROS 2 topic (if not using the konsole keyboard server):

ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 110" --once  # n  — next leaf state
ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 102" --once  # f  — switch superstate

Example walkthroughs

Manual leaf state cycling in SsPhase1

Start → MsRunning/SsPhase1/StPhaseA
  → press n → StPhaseB
  → press n → StPhaseC
  → press n → StPhaseA   (back to start of cycle)

Switch to SsPhase2 and cycle there

(in SsPhase1/StPhaseB)
  → press f → SsPhase2/StPhaseX   (SsPhase2 always re-enters at StPhaseX)
  → press n → StPhaseY
  → press n → StPhaseX

Switch back to SsPhase1

```

File truncated at 100 lines see the full file

CHANGELOG
No CHANGELOG found.

Package Dependencies

System Dependencies

Name
xterm

Dependant Packages

No known dependants.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged sm_mode_state_behavior_1 at Robotics Stack Exchange

No version for distro crystal showing jazzy. Known supported distros are highlighted in the buttons above.
Package symbol

sm_mode_state_behavior_1 package from SMACC2 repo

smacc2 cl_foundation_pose cl_gcalcli cl_generic_sensor cl_http cl_keyboard cl_lifecycle_node cl_mission_tracker cl_modbus_tcp_relay cl_moveit2z cl_nav2z backward_global_planner backward_local_planner forward_global_planner forward_local_planner nav2z_planners_common pure_spinning_local_planner undo_path_global_planner cl_px4_mr cl_ros2_timer eg_conditional_generator eg_random_generator smacc2_msgs sm_atomic_performance_trace_1 sm_atomic_subscribers_performance_test sm_coretest_action_client_1 sm_coretest_callback_rate_1 sm_coretest_exceptions_1 sm_coretest_features_1 sm_coretest_forced_finish_1 sm_coretest_poll_shutdown_1 sm_coretest_post_during_exit_1 sm_coretest_reactor_order_1 sm_coretest_signal_key_1 sm_coretest_timer_handoff_1 sm_coretest_transition_speed_1 sm_advanced_recovery_1 sm_atomic sm_atomic_http sm_atomic_lifecycle sm_atomic_mode_states sm_branching sm_cl_gcalcli_test_1 sm_cl_keyboard_unit_test_1 sm_cl_px4_mr_test_1 sm_cl_px4_mr_test_2 sm_cl_px4_mr_test_3 sm_cl_px4_mr_test_4 sm_cl_px4_mr_test_5 sm_cl_ros2_timer_unit_test_1 sm_data_sharing_1 sm_data_sharing_2 sm_modbus_tcp_relay_test_1 sm_mode_state_behavior_1 sm_multi_stage_1 sm_multithread_test_1 sm_nav2_gazebo_test_1 sm_nav2_gazebo_test_2 sm_nav2_gazebo_test_3 sm_pack_ml sm_panda_cl_moveit2z_cb_inventory sm_panda_cl_moveit2z_cb_inventory_isaacsim sm_retry_logic_1 sm_simple_action_client sm_three_some sr_all_events_go sr_conditional sr_event_countdown

ROS Distro
jazzy

Package Summary

Version 3.1.0
License Apache-2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/robosoft-ai/SMACC2.git
VCS Type git
VCS Version jazzy
Last Updated 2026-11-14
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Demonstrates a client behavior (CbDefaultKeyboardBehavior) defined at the mode state level, persisting across all inner superstate and leaf state transitions. Leaf states have only timer behaviors, avoiding double-event issues.

Maintainers

  • Brett Aldrich

Authors

No additional authors.

sm_mode_state_behavior_1

Demonstrates a client behavior defined at the mode state level, persisting across all inner superstate and leaf state transitions. The key insight: a behavior (here, CbDefaultKeyboardBehavior) owned by a parent state is created once when that parent enters and destroyed only when that parent exits — it survives every inner transition.

This machine also illustrates the correct solution to the double-event problem: if leaf states each had their own CbDefaultKeyboardBehavior, every keypress would generate two identical events (one per active behavior instance). By placing keyboard behavior exclusively in MsRunning, every keypress generates exactly one event regardless of which inner state is active.

What it demonstrates

  • CbDefaultKeyboardBehavior in OrKeyboard is declared in MsRunning::staticConfigure().
  • Leaf states (StPhaseA/B/C, StPhaseX/Y) have only CbTimerCountdownOnce — no keyboard behavior.
  • EvKeyPressN reactions in leaf states fire in response to events generated by MsRunning’s behavior — the event source and the reacting state are at different hierarchy levels.
  • EvKeyPressF reactions in SsPhase1/SsPhase2 switch between superstates; MsRunning’s keyboard behavior remains active throughout.

State hierarchy

SmModeStateBehavior1
├── OrTimer    (ClRos2Timer)
└── OrKeyboard (ClKeyboard)

MsRunning  ←  mode state; owns CbDefaultKeyboardBehavior in OrKeyboard
│              (keyboard behavior persists for the entire machine lifetime)
│
├── SsPhase1  (initial superstate)
│   │  Reacts: EvKeyPressF → SsPhase2
│   │
│   ├── StPhaseA  (initial)  3s timer
│   ├── StPhaseB             3s timer
│   └── StPhaseC             3s timer
│       (A → B → C → A cycle via timer or 'n')
│
└── SsPhase2
    │  Reacts: EvKeyPressF → SsPhase1
    │
    ├── StPhaseX  (initial)  5s timer
    └── StPhaseY             5s timer
        (X → Y → X cycle via timer or 'n')

Build

cd /home/brettpac/workspaces/isaac_ros-dev
colcon build --packages-select sm_mode_state_behavior_1
source install/setup.bash

Launch

ros2 launch sm_mode_state_behavior_1 sm_mode_state_behavior_1.launch.py

This opens two konsole terminals: the state machine node and the keyboard server.

Keyboard controls

Key Effect Handled by
n Advance to the next leaf state within the current superstate Leaf state reaction (event from MsRunning’s behavior)
f Switch between SsPhase1 and SsPhase2 SsPhase1 or SsPhase2 reaction (event from MsRunning’s behavior)
(timer) Auto-advance to next leaf state (3s in Phase1, 5s in Phase2) Leaf state reaction

Send keystrokes via ROS 2 topic (if not using the konsole keyboard server):

ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 110" --once  # n  — next leaf state
ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 102" --once  # f  — switch superstate

Example walkthroughs

Manual leaf state cycling in SsPhase1

Start → MsRunning/SsPhase1/StPhaseA
  → press n → StPhaseB
  → press n → StPhaseC
  → press n → StPhaseA   (back to start of cycle)

Switch to SsPhase2 and cycle there

(in SsPhase1/StPhaseB)
  → press f → SsPhase2/StPhaseX   (SsPhase2 always re-enters at StPhaseX)
  → press n → StPhaseY
  → press n → StPhaseX

Switch back to SsPhase1

```

File truncated at 100 lines see the full file

CHANGELOG
No CHANGELOG found.

Package Dependencies

System Dependencies

Name
xterm

Dependant Packages

No known dependants.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged sm_mode_state_behavior_1 at Robotics Stack Exchange

No version for distro eloquent showing jazzy. Known supported distros are highlighted in the buttons above.
Package symbol

sm_mode_state_behavior_1 package from SMACC2 repo

smacc2 cl_foundation_pose cl_gcalcli cl_generic_sensor cl_http cl_keyboard cl_lifecycle_node cl_mission_tracker cl_modbus_tcp_relay cl_moveit2z cl_nav2z backward_global_planner backward_local_planner forward_global_planner forward_local_planner nav2z_planners_common pure_spinning_local_planner undo_path_global_planner cl_px4_mr cl_ros2_timer eg_conditional_generator eg_random_generator smacc2_msgs sm_atomic_performance_trace_1 sm_atomic_subscribers_performance_test sm_coretest_action_client_1 sm_coretest_callback_rate_1 sm_coretest_exceptions_1 sm_coretest_features_1 sm_coretest_forced_finish_1 sm_coretest_poll_shutdown_1 sm_coretest_post_during_exit_1 sm_coretest_reactor_order_1 sm_coretest_signal_key_1 sm_coretest_timer_handoff_1 sm_coretest_transition_speed_1 sm_advanced_recovery_1 sm_atomic sm_atomic_http sm_atomic_lifecycle sm_atomic_mode_states sm_branching sm_cl_gcalcli_test_1 sm_cl_keyboard_unit_test_1 sm_cl_px4_mr_test_1 sm_cl_px4_mr_test_2 sm_cl_px4_mr_test_3 sm_cl_px4_mr_test_4 sm_cl_px4_mr_test_5 sm_cl_ros2_timer_unit_test_1 sm_data_sharing_1 sm_data_sharing_2 sm_modbus_tcp_relay_test_1 sm_mode_state_behavior_1 sm_multi_stage_1 sm_multithread_test_1 sm_nav2_gazebo_test_1 sm_nav2_gazebo_test_2 sm_nav2_gazebo_test_3 sm_pack_ml sm_panda_cl_moveit2z_cb_inventory sm_panda_cl_moveit2z_cb_inventory_isaacsim sm_retry_logic_1 sm_simple_action_client sm_three_some sr_all_events_go sr_conditional sr_event_countdown

ROS Distro
jazzy

Package Summary

Version 3.1.0
License Apache-2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/robosoft-ai/SMACC2.git
VCS Type git
VCS Version jazzy
Last Updated 2026-11-14
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Demonstrates a client behavior (CbDefaultKeyboardBehavior) defined at the mode state level, persisting across all inner superstate and leaf state transitions. Leaf states have only timer behaviors, avoiding double-event issues.

Maintainers

  • Brett Aldrich

Authors

No additional authors.

sm_mode_state_behavior_1

Demonstrates a client behavior defined at the mode state level, persisting across all inner superstate and leaf state transitions. The key insight: a behavior (here, CbDefaultKeyboardBehavior) owned by a parent state is created once when that parent enters and destroyed only when that parent exits — it survives every inner transition.

This machine also illustrates the correct solution to the double-event problem: if leaf states each had their own CbDefaultKeyboardBehavior, every keypress would generate two identical events (one per active behavior instance). By placing keyboard behavior exclusively in MsRunning, every keypress generates exactly one event regardless of which inner state is active.

What it demonstrates

  • CbDefaultKeyboardBehavior in OrKeyboard is declared in MsRunning::staticConfigure().
  • Leaf states (StPhaseA/B/C, StPhaseX/Y) have only CbTimerCountdownOnce — no keyboard behavior.
  • EvKeyPressN reactions in leaf states fire in response to events generated by MsRunning’s behavior — the event source and the reacting state are at different hierarchy levels.
  • EvKeyPressF reactions in SsPhase1/SsPhase2 switch between superstates; MsRunning’s keyboard behavior remains active throughout.

State hierarchy

SmModeStateBehavior1
├── OrTimer    (ClRos2Timer)
└── OrKeyboard (ClKeyboard)

MsRunning  ←  mode state; owns CbDefaultKeyboardBehavior in OrKeyboard
│              (keyboard behavior persists for the entire machine lifetime)
│
├── SsPhase1  (initial superstate)
│   │  Reacts: EvKeyPressF → SsPhase2
│   │
│   ├── StPhaseA  (initial)  3s timer
│   ├── StPhaseB             3s timer
│   └── StPhaseC             3s timer
│       (A → B → C → A cycle via timer or 'n')
│
└── SsPhase2
    │  Reacts: EvKeyPressF → SsPhase1
    │
    ├── StPhaseX  (initial)  5s timer
    └── StPhaseY             5s timer
        (X → Y → X cycle via timer or 'n')

Build

cd /home/brettpac/workspaces/isaac_ros-dev
colcon build --packages-select sm_mode_state_behavior_1
source install/setup.bash

Launch

ros2 launch sm_mode_state_behavior_1 sm_mode_state_behavior_1.launch.py

This opens two konsole terminals: the state machine node and the keyboard server.

Keyboard controls

Key Effect Handled by
n Advance to the next leaf state within the current superstate Leaf state reaction (event from MsRunning’s behavior)
f Switch between SsPhase1 and SsPhase2 SsPhase1 or SsPhase2 reaction (event from MsRunning’s behavior)
(timer) Auto-advance to next leaf state (3s in Phase1, 5s in Phase2) Leaf state reaction

Send keystrokes via ROS 2 topic (if not using the konsole keyboard server):

ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 110" --once  # n  — next leaf state
ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 102" --once  # f  — switch superstate

Example walkthroughs

Manual leaf state cycling in SsPhase1

Start → MsRunning/SsPhase1/StPhaseA
  → press n → StPhaseB
  → press n → StPhaseC
  → press n → StPhaseA   (back to start of cycle)

Switch to SsPhase2 and cycle there

(in SsPhase1/StPhaseB)
  → press f → SsPhase2/StPhaseX   (SsPhase2 always re-enters at StPhaseX)
  → press n → StPhaseY
  → press n → StPhaseX

Switch back to SsPhase1

```

File truncated at 100 lines see the full file

CHANGELOG
No CHANGELOG found.

Package Dependencies

System Dependencies

Name
xterm

Dependant Packages

No known dependants.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged sm_mode_state_behavior_1 at Robotics Stack Exchange

No version for distro dashing showing jazzy. Known supported distros are highlighted in the buttons above.
Package symbol

sm_mode_state_behavior_1 package from SMACC2 repo

smacc2 cl_foundation_pose cl_gcalcli cl_generic_sensor cl_http cl_keyboard cl_lifecycle_node cl_mission_tracker cl_modbus_tcp_relay cl_moveit2z cl_nav2z backward_global_planner backward_local_planner forward_global_planner forward_local_planner nav2z_planners_common pure_spinning_local_planner undo_path_global_planner cl_px4_mr cl_ros2_timer eg_conditional_generator eg_random_generator smacc2_msgs sm_atomic_performance_trace_1 sm_atomic_subscribers_performance_test sm_coretest_action_client_1 sm_coretest_callback_rate_1 sm_coretest_exceptions_1 sm_coretest_features_1 sm_coretest_forced_finish_1 sm_coretest_poll_shutdown_1 sm_coretest_post_during_exit_1 sm_coretest_reactor_order_1 sm_coretest_signal_key_1 sm_coretest_timer_handoff_1 sm_coretest_transition_speed_1 sm_advanced_recovery_1 sm_atomic sm_atomic_http sm_atomic_lifecycle sm_atomic_mode_states sm_branching sm_cl_gcalcli_test_1 sm_cl_keyboard_unit_test_1 sm_cl_px4_mr_test_1 sm_cl_px4_mr_test_2 sm_cl_px4_mr_test_3 sm_cl_px4_mr_test_4 sm_cl_px4_mr_test_5 sm_cl_ros2_timer_unit_test_1 sm_data_sharing_1 sm_data_sharing_2 sm_modbus_tcp_relay_test_1 sm_mode_state_behavior_1 sm_multi_stage_1 sm_multithread_test_1 sm_nav2_gazebo_test_1 sm_nav2_gazebo_test_2 sm_nav2_gazebo_test_3 sm_pack_ml sm_panda_cl_moveit2z_cb_inventory sm_panda_cl_moveit2z_cb_inventory_isaacsim sm_retry_logic_1 sm_simple_action_client sm_three_some sr_all_events_go sr_conditional sr_event_countdown

ROS Distro
jazzy

Package Summary

Version 3.1.0
License Apache-2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/robosoft-ai/SMACC2.git
VCS Type git
VCS Version jazzy
Last Updated 2026-11-14
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Demonstrates a client behavior (CbDefaultKeyboardBehavior) defined at the mode state level, persisting across all inner superstate and leaf state transitions. Leaf states have only timer behaviors, avoiding double-event issues.

Maintainers

  • Brett Aldrich

Authors

No additional authors.

sm_mode_state_behavior_1

Demonstrates a client behavior defined at the mode state level, persisting across all inner superstate and leaf state transitions. The key insight: a behavior (here, CbDefaultKeyboardBehavior) owned by a parent state is created once when that parent enters and destroyed only when that parent exits — it survives every inner transition.

This machine also illustrates the correct solution to the double-event problem: if leaf states each had their own CbDefaultKeyboardBehavior, every keypress would generate two identical events (one per active behavior instance). By placing keyboard behavior exclusively in MsRunning, every keypress generates exactly one event regardless of which inner state is active.

What it demonstrates

  • CbDefaultKeyboardBehavior in OrKeyboard is declared in MsRunning::staticConfigure().
  • Leaf states (StPhaseA/B/C, StPhaseX/Y) have only CbTimerCountdownOnce — no keyboard behavior.
  • EvKeyPressN reactions in leaf states fire in response to events generated by MsRunning’s behavior — the event source and the reacting state are at different hierarchy levels.
  • EvKeyPressF reactions in SsPhase1/SsPhase2 switch between superstates; MsRunning’s keyboard behavior remains active throughout.

State hierarchy

SmModeStateBehavior1
├── OrTimer    (ClRos2Timer)
└── OrKeyboard (ClKeyboard)

MsRunning  ←  mode state; owns CbDefaultKeyboardBehavior in OrKeyboard
│              (keyboard behavior persists for the entire machine lifetime)
│
├── SsPhase1  (initial superstate)
│   │  Reacts: EvKeyPressF → SsPhase2
│   │
│   ├── StPhaseA  (initial)  3s timer
│   ├── StPhaseB             3s timer
│   └── StPhaseC             3s timer
│       (A → B → C → A cycle via timer or 'n')
│
└── SsPhase2
    │  Reacts: EvKeyPressF → SsPhase1
    │
    ├── StPhaseX  (initial)  5s timer
    └── StPhaseY             5s timer
        (X → Y → X cycle via timer or 'n')

Build

cd /home/brettpac/workspaces/isaac_ros-dev
colcon build --packages-select sm_mode_state_behavior_1
source install/setup.bash

Launch

ros2 launch sm_mode_state_behavior_1 sm_mode_state_behavior_1.launch.py

This opens two konsole terminals: the state machine node and the keyboard server.

Keyboard controls

Key Effect Handled by
n Advance to the next leaf state within the current superstate Leaf state reaction (event from MsRunning’s behavior)
f Switch between SsPhase1 and SsPhase2 SsPhase1 or SsPhase2 reaction (event from MsRunning’s behavior)
(timer) Auto-advance to next leaf state (3s in Phase1, 5s in Phase2) Leaf state reaction

Send keystrokes via ROS 2 topic (if not using the konsole keyboard server):

ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 110" --once  # n  — next leaf state
ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 102" --once  # f  — switch superstate

Example walkthroughs

Manual leaf state cycling in SsPhase1

Start → MsRunning/SsPhase1/StPhaseA
  → press n → StPhaseB
  → press n → StPhaseC
  → press n → StPhaseA   (back to start of cycle)

Switch to SsPhase2 and cycle there

(in SsPhase1/StPhaseB)
  → press f → SsPhase2/StPhaseX   (SsPhase2 always re-enters at StPhaseX)
  → press n → StPhaseY
  → press n → StPhaseX

Switch back to SsPhase1

```

File truncated at 100 lines see the full file

CHANGELOG
No CHANGELOG found.

Package Dependencies

System Dependencies

Name
xterm

Dependant Packages

No known dependants.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged sm_mode_state_behavior_1 at Robotics Stack Exchange

No version for distro galactic showing jazzy. Known supported distros are highlighted in the buttons above.
Package symbol

sm_mode_state_behavior_1 package from SMACC2 repo

smacc2 cl_foundation_pose cl_gcalcli cl_generic_sensor cl_http cl_keyboard cl_lifecycle_node cl_mission_tracker cl_modbus_tcp_relay cl_moveit2z cl_nav2z backward_global_planner backward_local_planner forward_global_planner forward_local_planner nav2z_planners_common pure_spinning_local_planner undo_path_global_planner cl_px4_mr cl_ros2_timer eg_conditional_generator eg_random_generator smacc2_msgs sm_atomic_performance_trace_1 sm_atomic_subscribers_performance_test sm_coretest_action_client_1 sm_coretest_callback_rate_1 sm_coretest_exceptions_1 sm_coretest_features_1 sm_coretest_forced_finish_1 sm_coretest_poll_shutdown_1 sm_coretest_post_during_exit_1 sm_coretest_reactor_order_1 sm_coretest_signal_key_1 sm_coretest_timer_handoff_1 sm_coretest_transition_speed_1 sm_advanced_recovery_1 sm_atomic sm_atomic_http sm_atomic_lifecycle sm_atomic_mode_states sm_branching sm_cl_gcalcli_test_1 sm_cl_keyboard_unit_test_1 sm_cl_px4_mr_test_1 sm_cl_px4_mr_test_2 sm_cl_px4_mr_test_3 sm_cl_px4_mr_test_4 sm_cl_px4_mr_test_5 sm_cl_ros2_timer_unit_test_1 sm_data_sharing_1 sm_data_sharing_2 sm_modbus_tcp_relay_test_1 sm_mode_state_behavior_1 sm_multi_stage_1 sm_multithread_test_1 sm_nav2_gazebo_test_1 sm_nav2_gazebo_test_2 sm_nav2_gazebo_test_3 sm_pack_ml sm_panda_cl_moveit2z_cb_inventory sm_panda_cl_moveit2z_cb_inventory_isaacsim sm_retry_logic_1 sm_simple_action_client sm_three_some sr_all_events_go sr_conditional sr_event_countdown

ROS Distro
jazzy

Package Summary

Version 3.1.0
License Apache-2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/robosoft-ai/SMACC2.git
VCS Type git
VCS Version jazzy
Last Updated 2026-11-14
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Demonstrates a client behavior (CbDefaultKeyboardBehavior) defined at the mode state level, persisting across all inner superstate and leaf state transitions. Leaf states have only timer behaviors, avoiding double-event issues.

Maintainers

  • Brett Aldrich

Authors

No additional authors.

sm_mode_state_behavior_1

Demonstrates a client behavior defined at the mode state level, persisting across all inner superstate and leaf state transitions. The key insight: a behavior (here, CbDefaultKeyboardBehavior) owned by a parent state is created once when that parent enters and destroyed only when that parent exits — it survives every inner transition.

This machine also illustrates the correct solution to the double-event problem: if leaf states each had their own CbDefaultKeyboardBehavior, every keypress would generate two identical events (one per active behavior instance). By placing keyboard behavior exclusively in MsRunning, every keypress generates exactly one event regardless of which inner state is active.

What it demonstrates

  • CbDefaultKeyboardBehavior in OrKeyboard is declared in MsRunning::staticConfigure().
  • Leaf states (StPhaseA/B/C, StPhaseX/Y) have only CbTimerCountdownOnce — no keyboard behavior.
  • EvKeyPressN reactions in leaf states fire in response to events generated by MsRunning’s behavior — the event source and the reacting state are at different hierarchy levels.
  • EvKeyPressF reactions in SsPhase1/SsPhase2 switch between superstates; MsRunning’s keyboard behavior remains active throughout.

State hierarchy

SmModeStateBehavior1
├── OrTimer    (ClRos2Timer)
└── OrKeyboard (ClKeyboard)

MsRunning  ←  mode state; owns CbDefaultKeyboardBehavior in OrKeyboard
│              (keyboard behavior persists for the entire machine lifetime)
│
├── SsPhase1  (initial superstate)
│   │  Reacts: EvKeyPressF → SsPhase2
│   │
│   ├── StPhaseA  (initial)  3s timer
│   ├── StPhaseB             3s timer
│   └── StPhaseC             3s timer
│       (A → B → C → A cycle via timer or 'n')
│
└── SsPhase2
    │  Reacts: EvKeyPressF → SsPhase1
    │
    ├── StPhaseX  (initial)  5s timer
    └── StPhaseY             5s timer
        (X → Y → X cycle via timer or 'n')

Build

cd /home/brettpac/workspaces/isaac_ros-dev
colcon build --packages-select sm_mode_state_behavior_1
source install/setup.bash

Launch

ros2 launch sm_mode_state_behavior_1 sm_mode_state_behavior_1.launch.py

This opens two konsole terminals: the state machine node and the keyboard server.

Keyboard controls

Key Effect Handled by
n Advance to the next leaf state within the current superstate Leaf state reaction (event from MsRunning’s behavior)
f Switch between SsPhase1 and SsPhase2 SsPhase1 or SsPhase2 reaction (event from MsRunning’s behavior)
(timer) Auto-advance to next leaf state (3s in Phase1, 5s in Phase2) Leaf state reaction

Send keystrokes via ROS 2 topic (if not using the konsole keyboard server):

ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 110" --once  # n  — next leaf state
ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 102" --once  # f  — switch superstate

Example walkthroughs

Manual leaf state cycling in SsPhase1

Start → MsRunning/SsPhase1/StPhaseA
  → press n → StPhaseB
  → press n → StPhaseC
  → press n → StPhaseA   (back to start of cycle)

Switch to SsPhase2 and cycle there

(in SsPhase1/StPhaseB)
  → press f → SsPhase2/StPhaseX   (SsPhase2 always re-enters at StPhaseX)
  → press n → StPhaseY
  → press n → StPhaseX

Switch back to SsPhase1

```

File truncated at 100 lines see the full file

CHANGELOG
No CHANGELOG found.

Package Dependencies

System Dependencies

Name
xterm

Dependant Packages

No known dependants.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged sm_mode_state_behavior_1 at Robotics Stack Exchange

No version for distro foxy showing jazzy. Known supported distros are highlighted in the buttons above.
Package symbol

sm_mode_state_behavior_1 package from SMACC2 repo

smacc2 cl_foundation_pose cl_gcalcli cl_generic_sensor cl_http cl_keyboard cl_lifecycle_node cl_mission_tracker cl_modbus_tcp_relay cl_moveit2z cl_nav2z backward_global_planner backward_local_planner forward_global_planner forward_local_planner nav2z_planners_common pure_spinning_local_planner undo_path_global_planner cl_px4_mr cl_ros2_timer eg_conditional_generator eg_random_generator smacc2_msgs sm_atomic_performance_trace_1 sm_atomic_subscribers_performance_test sm_coretest_action_client_1 sm_coretest_callback_rate_1 sm_coretest_exceptions_1 sm_coretest_features_1 sm_coretest_forced_finish_1 sm_coretest_poll_shutdown_1 sm_coretest_post_during_exit_1 sm_coretest_reactor_order_1 sm_coretest_signal_key_1 sm_coretest_timer_handoff_1 sm_coretest_transition_speed_1 sm_advanced_recovery_1 sm_atomic sm_atomic_http sm_atomic_lifecycle sm_atomic_mode_states sm_branching sm_cl_gcalcli_test_1 sm_cl_keyboard_unit_test_1 sm_cl_px4_mr_test_1 sm_cl_px4_mr_test_2 sm_cl_px4_mr_test_3 sm_cl_px4_mr_test_4 sm_cl_px4_mr_test_5 sm_cl_ros2_timer_unit_test_1 sm_data_sharing_1 sm_data_sharing_2 sm_modbus_tcp_relay_test_1 sm_mode_state_behavior_1 sm_multi_stage_1 sm_multithread_test_1 sm_nav2_gazebo_test_1 sm_nav2_gazebo_test_2 sm_nav2_gazebo_test_3 sm_pack_ml sm_panda_cl_moveit2z_cb_inventory sm_panda_cl_moveit2z_cb_inventory_isaacsim sm_retry_logic_1 sm_simple_action_client sm_three_some sr_all_events_go sr_conditional sr_event_countdown

ROS Distro
jazzy

Package Summary

Version 3.1.0
License Apache-2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/robosoft-ai/SMACC2.git
VCS Type git
VCS Version jazzy
Last Updated 2026-11-14
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Demonstrates a client behavior (CbDefaultKeyboardBehavior) defined at the mode state level, persisting across all inner superstate and leaf state transitions. Leaf states have only timer behaviors, avoiding double-event issues.

Maintainers

  • Brett Aldrich

Authors

No additional authors.

sm_mode_state_behavior_1

Demonstrates a client behavior defined at the mode state level, persisting across all inner superstate and leaf state transitions. The key insight: a behavior (here, CbDefaultKeyboardBehavior) owned by a parent state is created once when that parent enters and destroyed only when that parent exits — it survives every inner transition.

This machine also illustrates the correct solution to the double-event problem: if leaf states each had their own CbDefaultKeyboardBehavior, every keypress would generate two identical events (one per active behavior instance). By placing keyboard behavior exclusively in MsRunning, every keypress generates exactly one event regardless of which inner state is active.

What it demonstrates

  • CbDefaultKeyboardBehavior in OrKeyboard is declared in MsRunning::staticConfigure().
  • Leaf states (StPhaseA/B/C, StPhaseX/Y) have only CbTimerCountdownOnce — no keyboard behavior.
  • EvKeyPressN reactions in leaf states fire in response to events generated by MsRunning’s behavior — the event source and the reacting state are at different hierarchy levels.
  • EvKeyPressF reactions in SsPhase1/SsPhase2 switch between superstates; MsRunning’s keyboard behavior remains active throughout.

State hierarchy

SmModeStateBehavior1
├── OrTimer    (ClRos2Timer)
└── OrKeyboard (ClKeyboard)

MsRunning  ←  mode state; owns CbDefaultKeyboardBehavior in OrKeyboard
│              (keyboard behavior persists for the entire machine lifetime)
│
├── SsPhase1  (initial superstate)
│   │  Reacts: EvKeyPressF → SsPhase2
│   │
│   ├── StPhaseA  (initial)  3s timer
│   ├── StPhaseB             3s timer
│   └── StPhaseC             3s timer
│       (A → B → C → A cycle via timer or 'n')
│
└── SsPhase2
    │  Reacts: EvKeyPressF → SsPhase1
    │
    ├── StPhaseX  (initial)  5s timer
    └── StPhaseY             5s timer
        (X → Y → X cycle via timer or 'n')

Build

cd /home/brettpac/workspaces/isaac_ros-dev
colcon build --packages-select sm_mode_state_behavior_1
source install/setup.bash

Launch

ros2 launch sm_mode_state_behavior_1 sm_mode_state_behavior_1.launch.py

This opens two konsole terminals: the state machine node and the keyboard server.

Keyboard controls

Key Effect Handled by
n Advance to the next leaf state within the current superstate Leaf state reaction (event from MsRunning’s behavior)
f Switch between SsPhase1 and SsPhase2 SsPhase1 or SsPhase2 reaction (event from MsRunning’s behavior)
(timer) Auto-advance to next leaf state (3s in Phase1, 5s in Phase2) Leaf state reaction

Send keystrokes via ROS 2 topic (if not using the konsole keyboard server):

ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 110" --once  # n  — next leaf state
ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 102" --once  # f  — switch superstate

Example walkthroughs

Manual leaf state cycling in SsPhase1

Start → MsRunning/SsPhase1/StPhaseA
  → press n → StPhaseB
  → press n → StPhaseC
  → press n → StPhaseA   (back to start of cycle)

Switch to SsPhase2 and cycle there

(in SsPhase1/StPhaseB)
  → press f → SsPhase2/StPhaseX   (SsPhase2 always re-enters at StPhaseX)
  → press n → StPhaseY
  → press n → StPhaseX

Switch back to SsPhase1

```

File truncated at 100 lines see the full file

CHANGELOG
No CHANGELOG found.

Package Dependencies

System Dependencies

Name
xterm

Dependant Packages

No known dependants.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged sm_mode_state_behavior_1 at Robotics Stack Exchange

No version for distro iron showing jazzy. Known supported distros are highlighted in the buttons above.
Package symbol

sm_mode_state_behavior_1 package from SMACC2 repo

smacc2 cl_foundation_pose cl_gcalcli cl_generic_sensor cl_http cl_keyboard cl_lifecycle_node cl_mission_tracker cl_modbus_tcp_relay cl_moveit2z cl_nav2z backward_global_planner backward_local_planner forward_global_planner forward_local_planner nav2z_planners_common pure_spinning_local_planner undo_path_global_planner cl_px4_mr cl_ros2_timer eg_conditional_generator eg_random_generator smacc2_msgs sm_atomic_performance_trace_1 sm_atomic_subscribers_performance_test sm_coretest_action_client_1 sm_coretest_callback_rate_1 sm_coretest_exceptions_1 sm_coretest_features_1 sm_coretest_forced_finish_1 sm_coretest_poll_shutdown_1 sm_coretest_post_during_exit_1 sm_coretest_reactor_order_1 sm_coretest_signal_key_1 sm_coretest_timer_handoff_1 sm_coretest_transition_speed_1 sm_advanced_recovery_1 sm_atomic sm_atomic_http sm_atomic_lifecycle sm_atomic_mode_states sm_branching sm_cl_gcalcli_test_1 sm_cl_keyboard_unit_test_1 sm_cl_px4_mr_test_1 sm_cl_px4_mr_test_2 sm_cl_px4_mr_test_3 sm_cl_px4_mr_test_4 sm_cl_px4_mr_test_5 sm_cl_ros2_timer_unit_test_1 sm_data_sharing_1 sm_data_sharing_2 sm_modbus_tcp_relay_test_1 sm_mode_state_behavior_1 sm_multi_stage_1 sm_multithread_test_1 sm_nav2_gazebo_test_1 sm_nav2_gazebo_test_2 sm_nav2_gazebo_test_3 sm_pack_ml sm_panda_cl_moveit2z_cb_inventory sm_panda_cl_moveit2z_cb_inventory_isaacsim sm_retry_logic_1 sm_simple_action_client sm_three_some sr_all_events_go sr_conditional sr_event_countdown

ROS Distro
jazzy

Package Summary

Version 3.1.0
License Apache-2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/robosoft-ai/SMACC2.git
VCS Type git
VCS Version jazzy
Last Updated 2026-11-14
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Demonstrates a client behavior (CbDefaultKeyboardBehavior) defined at the mode state level, persisting across all inner superstate and leaf state transitions. Leaf states have only timer behaviors, avoiding double-event issues.

Maintainers

  • Brett Aldrich

Authors

No additional authors.

sm_mode_state_behavior_1

Demonstrates a client behavior defined at the mode state level, persisting across all inner superstate and leaf state transitions. The key insight: a behavior (here, CbDefaultKeyboardBehavior) owned by a parent state is created once when that parent enters and destroyed only when that parent exits — it survives every inner transition.

This machine also illustrates the correct solution to the double-event problem: if leaf states each had their own CbDefaultKeyboardBehavior, every keypress would generate two identical events (one per active behavior instance). By placing keyboard behavior exclusively in MsRunning, every keypress generates exactly one event regardless of which inner state is active.

What it demonstrates

  • CbDefaultKeyboardBehavior in OrKeyboard is declared in MsRunning::staticConfigure().
  • Leaf states (StPhaseA/B/C, StPhaseX/Y) have only CbTimerCountdownOnce — no keyboard behavior.
  • EvKeyPressN reactions in leaf states fire in response to events generated by MsRunning’s behavior — the event source and the reacting state are at different hierarchy levels.
  • EvKeyPressF reactions in SsPhase1/SsPhase2 switch between superstates; MsRunning’s keyboard behavior remains active throughout.

State hierarchy

SmModeStateBehavior1
├── OrTimer    (ClRos2Timer)
└── OrKeyboard (ClKeyboard)

MsRunning  ←  mode state; owns CbDefaultKeyboardBehavior in OrKeyboard
│              (keyboard behavior persists for the entire machine lifetime)
│
├── SsPhase1  (initial superstate)
│   │  Reacts: EvKeyPressF → SsPhase2
│   │
│   ├── StPhaseA  (initial)  3s timer
│   ├── StPhaseB             3s timer
│   └── StPhaseC             3s timer
│       (A → B → C → A cycle via timer or 'n')
│
└── SsPhase2
    │  Reacts: EvKeyPressF → SsPhase1
    │
    ├── StPhaseX  (initial)  5s timer
    └── StPhaseY             5s timer
        (X → Y → X cycle via timer or 'n')

Build

cd /home/brettpac/workspaces/isaac_ros-dev
colcon build --packages-select sm_mode_state_behavior_1
source install/setup.bash

Launch

ros2 launch sm_mode_state_behavior_1 sm_mode_state_behavior_1.launch.py

This opens two konsole terminals: the state machine node and the keyboard server.

Keyboard controls

Key Effect Handled by
n Advance to the next leaf state within the current superstate Leaf state reaction (event from MsRunning’s behavior)
f Switch between SsPhase1 and SsPhase2 SsPhase1 or SsPhase2 reaction (event from MsRunning’s behavior)
(timer) Auto-advance to next leaf state (3s in Phase1, 5s in Phase2) Leaf state reaction

Send keystrokes via ROS 2 topic (if not using the konsole keyboard server):

ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 110" --once  # n  — next leaf state
ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 102" --once  # f  — switch superstate

Example walkthroughs

Manual leaf state cycling in SsPhase1

Start → MsRunning/SsPhase1/StPhaseA
  → press n → StPhaseB
  → press n → StPhaseC
  → press n → StPhaseA   (back to start of cycle)

Switch to SsPhase2 and cycle there

(in SsPhase1/StPhaseB)
  → press f → SsPhase2/StPhaseX   (SsPhase2 always re-enters at StPhaseX)
  → press n → StPhaseY
  → press n → StPhaseX

Switch back to SsPhase1

```

File truncated at 100 lines see the full file

CHANGELOG
No CHANGELOG found.

Package Dependencies

System Dependencies

Name
xterm

Dependant Packages

No known dependants.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged sm_mode_state_behavior_1 at Robotics Stack Exchange

No version for distro lunar showing jazzy. Known supported distros are highlighted in the buttons above.
Package symbol

sm_mode_state_behavior_1 package from SMACC2 repo

smacc2 cl_foundation_pose cl_gcalcli cl_generic_sensor cl_http cl_keyboard cl_lifecycle_node cl_mission_tracker cl_modbus_tcp_relay cl_moveit2z cl_nav2z backward_global_planner backward_local_planner forward_global_planner forward_local_planner nav2z_planners_common pure_spinning_local_planner undo_path_global_planner cl_px4_mr cl_ros2_timer eg_conditional_generator eg_random_generator smacc2_msgs sm_atomic_performance_trace_1 sm_atomic_subscribers_performance_test sm_coretest_action_client_1 sm_coretest_callback_rate_1 sm_coretest_exceptions_1 sm_coretest_features_1 sm_coretest_forced_finish_1 sm_coretest_poll_shutdown_1 sm_coretest_post_during_exit_1 sm_coretest_reactor_order_1 sm_coretest_signal_key_1 sm_coretest_timer_handoff_1 sm_coretest_transition_speed_1 sm_advanced_recovery_1 sm_atomic sm_atomic_http sm_atomic_lifecycle sm_atomic_mode_states sm_branching sm_cl_gcalcli_test_1 sm_cl_keyboard_unit_test_1 sm_cl_px4_mr_test_1 sm_cl_px4_mr_test_2 sm_cl_px4_mr_test_3 sm_cl_px4_mr_test_4 sm_cl_px4_mr_test_5 sm_cl_ros2_timer_unit_test_1 sm_data_sharing_1 sm_data_sharing_2 sm_modbus_tcp_relay_test_1 sm_mode_state_behavior_1 sm_multi_stage_1 sm_multithread_test_1 sm_nav2_gazebo_test_1 sm_nav2_gazebo_test_2 sm_nav2_gazebo_test_3 sm_pack_ml sm_panda_cl_moveit2z_cb_inventory sm_panda_cl_moveit2z_cb_inventory_isaacsim sm_retry_logic_1 sm_simple_action_client sm_three_some sr_all_events_go sr_conditional sr_event_countdown

ROS Distro
jazzy

Package Summary

Version 3.1.0
License Apache-2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/robosoft-ai/SMACC2.git
VCS Type git
VCS Version jazzy
Last Updated 2026-11-14
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Demonstrates a client behavior (CbDefaultKeyboardBehavior) defined at the mode state level, persisting across all inner superstate and leaf state transitions. Leaf states have only timer behaviors, avoiding double-event issues.

Maintainers

  • Brett Aldrich

Authors

No additional authors.

sm_mode_state_behavior_1

Demonstrates a client behavior defined at the mode state level, persisting across all inner superstate and leaf state transitions. The key insight: a behavior (here, CbDefaultKeyboardBehavior) owned by a parent state is created once when that parent enters and destroyed only when that parent exits — it survives every inner transition.

This machine also illustrates the correct solution to the double-event problem: if leaf states each had their own CbDefaultKeyboardBehavior, every keypress would generate two identical events (one per active behavior instance). By placing keyboard behavior exclusively in MsRunning, every keypress generates exactly one event regardless of which inner state is active.

What it demonstrates

  • CbDefaultKeyboardBehavior in OrKeyboard is declared in MsRunning::staticConfigure().
  • Leaf states (StPhaseA/B/C, StPhaseX/Y) have only CbTimerCountdownOnce — no keyboard behavior.
  • EvKeyPressN reactions in leaf states fire in response to events generated by MsRunning’s behavior — the event source and the reacting state are at different hierarchy levels.
  • EvKeyPressF reactions in SsPhase1/SsPhase2 switch between superstates; MsRunning’s keyboard behavior remains active throughout.

State hierarchy

SmModeStateBehavior1
├── OrTimer    (ClRos2Timer)
└── OrKeyboard (ClKeyboard)

MsRunning  ←  mode state; owns CbDefaultKeyboardBehavior in OrKeyboard
│              (keyboard behavior persists for the entire machine lifetime)
│
├── SsPhase1  (initial superstate)
│   │  Reacts: EvKeyPressF → SsPhase2
│   │
│   ├── StPhaseA  (initial)  3s timer
│   ├── StPhaseB             3s timer
│   └── StPhaseC             3s timer
│       (A → B → C → A cycle via timer or 'n')
│
└── SsPhase2
    │  Reacts: EvKeyPressF → SsPhase1
    │
    ├── StPhaseX  (initial)  5s timer
    └── StPhaseY             5s timer
        (X → Y → X cycle via timer or 'n')

Build

cd /home/brettpac/workspaces/isaac_ros-dev
colcon build --packages-select sm_mode_state_behavior_1
source install/setup.bash

Launch

ros2 launch sm_mode_state_behavior_1 sm_mode_state_behavior_1.launch.py

This opens two konsole terminals: the state machine node and the keyboard server.

Keyboard controls

Key Effect Handled by
n Advance to the next leaf state within the current superstate Leaf state reaction (event from MsRunning’s behavior)
f Switch between SsPhase1 and SsPhase2 SsPhase1 or SsPhase2 reaction (event from MsRunning’s behavior)
(timer) Auto-advance to next leaf state (3s in Phase1, 5s in Phase2) Leaf state reaction

Send keystrokes via ROS 2 topic (if not using the konsole keyboard server):

ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 110" --once  # n  — next leaf state
ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 102" --once  # f  — switch superstate

Example walkthroughs

Manual leaf state cycling in SsPhase1

Start → MsRunning/SsPhase1/StPhaseA
  → press n → StPhaseB
  → press n → StPhaseC
  → press n → StPhaseA   (back to start of cycle)

Switch to SsPhase2 and cycle there

(in SsPhase1/StPhaseB)
  → press f → SsPhase2/StPhaseX   (SsPhase2 always re-enters at StPhaseX)
  → press n → StPhaseY
  → press n → StPhaseX

Switch back to SsPhase1

```

File truncated at 100 lines see the full file

CHANGELOG
No CHANGELOG found.

Package Dependencies

System Dependencies

Name
xterm

Dependant Packages

No known dependants.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged sm_mode_state_behavior_1 at Robotics Stack Exchange

No version for distro jade showing jazzy. Known supported distros are highlighted in the buttons above.
Package symbol

sm_mode_state_behavior_1 package from SMACC2 repo

smacc2 cl_foundation_pose cl_gcalcli cl_generic_sensor cl_http cl_keyboard cl_lifecycle_node cl_mission_tracker cl_modbus_tcp_relay cl_moveit2z cl_nav2z backward_global_planner backward_local_planner forward_global_planner forward_local_planner nav2z_planners_common pure_spinning_local_planner undo_path_global_planner cl_px4_mr cl_ros2_timer eg_conditional_generator eg_random_generator smacc2_msgs sm_atomic_performance_trace_1 sm_atomic_subscribers_performance_test sm_coretest_action_client_1 sm_coretest_callback_rate_1 sm_coretest_exceptions_1 sm_coretest_features_1 sm_coretest_forced_finish_1 sm_coretest_poll_shutdown_1 sm_coretest_post_during_exit_1 sm_coretest_reactor_order_1 sm_coretest_signal_key_1 sm_coretest_timer_handoff_1 sm_coretest_transition_speed_1 sm_advanced_recovery_1 sm_atomic sm_atomic_http sm_atomic_lifecycle sm_atomic_mode_states sm_branching sm_cl_gcalcli_test_1 sm_cl_keyboard_unit_test_1 sm_cl_px4_mr_test_1 sm_cl_px4_mr_test_2 sm_cl_px4_mr_test_3 sm_cl_px4_mr_test_4 sm_cl_px4_mr_test_5 sm_cl_ros2_timer_unit_test_1 sm_data_sharing_1 sm_data_sharing_2 sm_modbus_tcp_relay_test_1 sm_mode_state_behavior_1 sm_multi_stage_1 sm_multithread_test_1 sm_nav2_gazebo_test_1 sm_nav2_gazebo_test_2 sm_nav2_gazebo_test_3 sm_pack_ml sm_panda_cl_moveit2z_cb_inventory sm_panda_cl_moveit2z_cb_inventory_isaacsim sm_retry_logic_1 sm_simple_action_client sm_three_some sr_all_events_go sr_conditional sr_event_countdown

ROS Distro
jazzy

Package Summary

Version 3.1.0
License Apache-2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/robosoft-ai/SMACC2.git
VCS Type git
VCS Version jazzy
Last Updated 2026-11-14
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Demonstrates a client behavior (CbDefaultKeyboardBehavior) defined at the mode state level, persisting across all inner superstate and leaf state transitions. Leaf states have only timer behaviors, avoiding double-event issues.

Maintainers

  • Brett Aldrich

Authors

No additional authors.

sm_mode_state_behavior_1

Demonstrates a client behavior defined at the mode state level, persisting across all inner superstate and leaf state transitions. The key insight: a behavior (here, CbDefaultKeyboardBehavior) owned by a parent state is created once when that parent enters and destroyed only when that parent exits — it survives every inner transition.

This machine also illustrates the correct solution to the double-event problem: if leaf states each had their own CbDefaultKeyboardBehavior, every keypress would generate two identical events (one per active behavior instance). By placing keyboard behavior exclusively in MsRunning, every keypress generates exactly one event regardless of which inner state is active.

What it demonstrates

  • CbDefaultKeyboardBehavior in OrKeyboard is declared in MsRunning::staticConfigure().
  • Leaf states (StPhaseA/B/C, StPhaseX/Y) have only CbTimerCountdownOnce — no keyboard behavior.
  • EvKeyPressN reactions in leaf states fire in response to events generated by MsRunning’s behavior — the event source and the reacting state are at different hierarchy levels.
  • EvKeyPressF reactions in SsPhase1/SsPhase2 switch between superstates; MsRunning’s keyboard behavior remains active throughout.

State hierarchy

SmModeStateBehavior1
├── OrTimer    (ClRos2Timer)
└── OrKeyboard (ClKeyboard)

MsRunning  ←  mode state; owns CbDefaultKeyboardBehavior in OrKeyboard
│              (keyboard behavior persists for the entire machine lifetime)
│
├── SsPhase1  (initial superstate)
│   │  Reacts: EvKeyPressF → SsPhase2
│   │
│   ├── StPhaseA  (initial)  3s timer
│   ├── StPhaseB             3s timer
│   └── StPhaseC             3s timer
│       (A → B → C → A cycle via timer or 'n')
│
└── SsPhase2
    │  Reacts: EvKeyPressF → SsPhase1
    │
    ├── StPhaseX  (initial)  5s timer
    └── StPhaseY             5s timer
        (X → Y → X cycle via timer or 'n')

Build

cd /home/brettpac/workspaces/isaac_ros-dev
colcon build --packages-select sm_mode_state_behavior_1
source install/setup.bash

Launch

ros2 launch sm_mode_state_behavior_1 sm_mode_state_behavior_1.launch.py

This opens two konsole terminals: the state machine node and the keyboard server.

Keyboard controls

Key Effect Handled by
n Advance to the next leaf state within the current superstate Leaf state reaction (event from MsRunning’s behavior)
f Switch between SsPhase1 and SsPhase2 SsPhase1 or SsPhase2 reaction (event from MsRunning’s behavior)
(timer) Auto-advance to next leaf state (3s in Phase1, 5s in Phase2) Leaf state reaction

Send keystrokes via ROS 2 topic (if not using the konsole keyboard server):

ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 110" --once  # n  — next leaf state
ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 102" --once  # f  — switch superstate

Example walkthroughs

Manual leaf state cycling in SsPhase1

Start → MsRunning/SsPhase1/StPhaseA
  → press n → StPhaseB
  → press n → StPhaseC
  → press n → StPhaseA   (back to start of cycle)

Switch to SsPhase2 and cycle there

(in SsPhase1/StPhaseB)
  → press f → SsPhase2/StPhaseX   (SsPhase2 always re-enters at StPhaseX)
  → press n → StPhaseY
  → press n → StPhaseX

Switch back to SsPhase1

```

File truncated at 100 lines see the full file

CHANGELOG
No CHANGELOG found.

Package Dependencies

System Dependencies

Name
xterm

Dependant Packages

No known dependants.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged sm_mode_state_behavior_1 at Robotics Stack Exchange

No version for distro indigo showing jazzy. Known supported distros are highlighted in the buttons above.
Package symbol

sm_mode_state_behavior_1 package from SMACC2 repo

smacc2 cl_foundation_pose cl_gcalcli cl_generic_sensor cl_http cl_keyboard cl_lifecycle_node cl_mission_tracker cl_modbus_tcp_relay cl_moveit2z cl_nav2z backward_global_planner backward_local_planner forward_global_planner forward_local_planner nav2z_planners_common pure_spinning_local_planner undo_path_global_planner cl_px4_mr cl_ros2_timer eg_conditional_generator eg_random_generator smacc2_msgs sm_atomic_performance_trace_1 sm_atomic_subscribers_performance_test sm_coretest_action_client_1 sm_coretest_callback_rate_1 sm_coretest_exceptions_1 sm_coretest_features_1 sm_coretest_forced_finish_1 sm_coretest_poll_shutdown_1 sm_coretest_post_during_exit_1 sm_coretest_reactor_order_1 sm_coretest_signal_key_1 sm_coretest_timer_handoff_1 sm_coretest_transition_speed_1 sm_advanced_recovery_1 sm_atomic sm_atomic_http sm_atomic_lifecycle sm_atomic_mode_states sm_branching sm_cl_gcalcli_test_1 sm_cl_keyboard_unit_test_1 sm_cl_px4_mr_test_1 sm_cl_px4_mr_test_2 sm_cl_px4_mr_test_3 sm_cl_px4_mr_test_4 sm_cl_px4_mr_test_5 sm_cl_ros2_timer_unit_test_1 sm_data_sharing_1 sm_data_sharing_2 sm_modbus_tcp_relay_test_1 sm_mode_state_behavior_1 sm_multi_stage_1 sm_multithread_test_1 sm_nav2_gazebo_test_1 sm_nav2_gazebo_test_2 sm_nav2_gazebo_test_3 sm_pack_ml sm_panda_cl_moveit2z_cb_inventory sm_panda_cl_moveit2z_cb_inventory_isaacsim sm_retry_logic_1 sm_simple_action_client sm_three_some sr_all_events_go sr_conditional sr_event_countdown

ROS Distro
jazzy

Package Summary

Version 3.1.0
License Apache-2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/robosoft-ai/SMACC2.git
VCS Type git
VCS Version jazzy
Last Updated 2026-11-14
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Demonstrates a client behavior (CbDefaultKeyboardBehavior) defined at the mode state level, persisting across all inner superstate and leaf state transitions. Leaf states have only timer behaviors, avoiding double-event issues.

Maintainers

  • Brett Aldrich

Authors

No additional authors.

sm_mode_state_behavior_1

Demonstrates a client behavior defined at the mode state level, persisting across all inner superstate and leaf state transitions. The key insight: a behavior (here, CbDefaultKeyboardBehavior) owned by a parent state is created once when that parent enters and destroyed only when that parent exits — it survives every inner transition.

This machine also illustrates the correct solution to the double-event problem: if leaf states each had their own CbDefaultKeyboardBehavior, every keypress would generate two identical events (one per active behavior instance). By placing keyboard behavior exclusively in MsRunning, every keypress generates exactly one event regardless of which inner state is active.

What it demonstrates

  • CbDefaultKeyboardBehavior in OrKeyboard is declared in MsRunning::staticConfigure().
  • Leaf states (StPhaseA/B/C, StPhaseX/Y) have only CbTimerCountdownOnce — no keyboard behavior.
  • EvKeyPressN reactions in leaf states fire in response to events generated by MsRunning’s behavior — the event source and the reacting state are at different hierarchy levels.
  • EvKeyPressF reactions in SsPhase1/SsPhase2 switch between superstates; MsRunning’s keyboard behavior remains active throughout.

State hierarchy

SmModeStateBehavior1
├── OrTimer    (ClRos2Timer)
└── OrKeyboard (ClKeyboard)

MsRunning  ←  mode state; owns CbDefaultKeyboardBehavior in OrKeyboard
│              (keyboard behavior persists for the entire machine lifetime)
│
├── SsPhase1  (initial superstate)
│   │  Reacts: EvKeyPressF → SsPhase2
│   │
│   ├── StPhaseA  (initial)  3s timer
│   ├── StPhaseB             3s timer
│   └── StPhaseC             3s timer
│       (A → B → C → A cycle via timer or 'n')
│
└── SsPhase2
    │  Reacts: EvKeyPressF → SsPhase1
    │
    ├── StPhaseX  (initial)  5s timer
    └── StPhaseY             5s timer
        (X → Y → X cycle via timer or 'n')

Build

cd /home/brettpac/workspaces/isaac_ros-dev
colcon build --packages-select sm_mode_state_behavior_1
source install/setup.bash

Launch

ros2 launch sm_mode_state_behavior_1 sm_mode_state_behavior_1.launch.py

This opens two konsole terminals: the state machine node and the keyboard server.

Keyboard controls

Key Effect Handled by
n Advance to the next leaf state within the current superstate Leaf state reaction (event from MsRunning’s behavior)
f Switch between SsPhase1 and SsPhase2 SsPhase1 or SsPhase2 reaction (event from MsRunning’s behavior)
(timer) Auto-advance to next leaf state (3s in Phase1, 5s in Phase2) Leaf state reaction

Send keystrokes via ROS 2 topic (if not using the konsole keyboard server):

ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 110" --once  # n  — next leaf state
ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 102" --once  # f  — switch superstate

Example walkthroughs

Manual leaf state cycling in SsPhase1

Start → MsRunning/SsPhase1/StPhaseA
  → press n → StPhaseB
  → press n → StPhaseC
  → press n → StPhaseA   (back to start of cycle)

Switch to SsPhase2 and cycle there

(in SsPhase1/StPhaseB)
  → press f → SsPhase2/StPhaseX   (SsPhase2 always re-enters at StPhaseX)
  → press n → StPhaseY
  → press n → StPhaseX

Switch back to SsPhase1

```

File truncated at 100 lines see the full file

CHANGELOG
No CHANGELOG found.

Package Dependencies

System Dependencies

Name
xterm

Dependant Packages

No known dependants.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged sm_mode_state_behavior_1 at Robotics Stack Exchange

No version for distro hydro showing jazzy. Known supported distros are highlighted in the buttons above.
Package symbol

sm_mode_state_behavior_1 package from SMACC2 repo

smacc2 cl_foundation_pose cl_gcalcli cl_generic_sensor cl_http cl_keyboard cl_lifecycle_node cl_mission_tracker cl_modbus_tcp_relay cl_moveit2z cl_nav2z backward_global_planner backward_local_planner forward_global_planner forward_local_planner nav2z_planners_common pure_spinning_local_planner undo_path_global_planner cl_px4_mr cl_ros2_timer eg_conditional_generator eg_random_generator smacc2_msgs sm_atomic_performance_trace_1 sm_atomic_subscribers_performance_test sm_coretest_action_client_1 sm_coretest_callback_rate_1 sm_coretest_exceptions_1 sm_coretest_features_1 sm_coretest_forced_finish_1 sm_coretest_poll_shutdown_1 sm_coretest_post_during_exit_1 sm_coretest_reactor_order_1 sm_coretest_signal_key_1 sm_coretest_timer_handoff_1 sm_coretest_transition_speed_1 sm_advanced_recovery_1 sm_atomic sm_atomic_http sm_atomic_lifecycle sm_atomic_mode_states sm_branching sm_cl_gcalcli_test_1 sm_cl_keyboard_unit_test_1 sm_cl_px4_mr_test_1 sm_cl_px4_mr_test_2 sm_cl_px4_mr_test_3 sm_cl_px4_mr_test_4 sm_cl_px4_mr_test_5 sm_cl_ros2_timer_unit_test_1 sm_data_sharing_1 sm_data_sharing_2 sm_modbus_tcp_relay_test_1 sm_mode_state_behavior_1 sm_multi_stage_1 sm_multithread_test_1 sm_nav2_gazebo_test_1 sm_nav2_gazebo_test_2 sm_nav2_gazebo_test_3 sm_pack_ml sm_panda_cl_moveit2z_cb_inventory sm_panda_cl_moveit2z_cb_inventory_isaacsim sm_retry_logic_1 sm_simple_action_client sm_three_some sr_all_events_go sr_conditional sr_event_countdown

ROS Distro
jazzy

Package Summary

Version 3.1.0
License Apache-2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/robosoft-ai/SMACC2.git
VCS Type git
VCS Version jazzy
Last Updated 2026-11-14
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Demonstrates a client behavior (CbDefaultKeyboardBehavior) defined at the mode state level, persisting across all inner superstate and leaf state transitions. Leaf states have only timer behaviors, avoiding double-event issues.

Maintainers

  • Brett Aldrich

Authors

No additional authors.

sm_mode_state_behavior_1

Demonstrates a client behavior defined at the mode state level, persisting across all inner superstate and leaf state transitions. The key insight: a behavior (here, CbDefaultKeyboardBehavior) owned by a parent state is created once when that parent enters and destroyed only when that parent exits — it survives every inner transition.

This machine also illustrates the correct solution to the double-event problem: if leaf states each had their own CbDefaultKeyboardBehavior, every keypress would generate two identical events (one per active behavior instance). By placing keyboard behavior exclusively in MsRunning, every keypress generates exactly one event regardless of which inner state is active.

What it demonstrates

  • CbDefaultKeyboardBehavior in OrKeyboard is declared in MsRunning::staticConfigure().
  • Leaf states (StPhaseA/B/C, StPhaseX/Y) have only CbTimerCountdownOnce — no keyboard behavior.
  • EvKeyPressN reactions in leaf states fire in response to events generated by MsRunning’s behavior — the event source and the reacting state are at different hierarchy levels.
  • EvKeyPressF reactions in SsPhase1/SsPhase2 switch between superstates; MsRunning’s keyboard behavior remains active throughout.

State hierarchy

SmModeStateBehavior1
├── OrTimer    (ClRos2Timer)
└── OrKeyboard (ClKeyboard)

MsRunning  ←  mode state; owns CbDefaultKeyboardBehavior in OrKeyboard
│              (keyboard behavior persists for the entire machine lifetime)
│
├── SsPhase1  (initial superstate)
│   │  Reacts: EvKeyPressF → SsPhase2
│   │
│   ├── StPhaseA  (initial)  3s timer
│   ├── StPhaseB             3s timer
│   └── StPhaseC             3s timer
│       (A → B → C → A cycle via timer or 'n')
│
└── SsPhase2
    │  Reacts: EvKeyPressF → SsPhase1
    │
    ├── StPhaseX  (initial)  5s timer
    └── StPhaseY             5s timer
        (X → Y → X cycle via timer or 'n')

Build

cd /home/brettpac/workspaces/isaac_ros-dev
colcon build --packages-select sm_mode_state_behavior_1
source install/setup.bash

Launch

ros2 launch sm_mode_state_behavior_1 sm_mode_state_behavior_1.launch.py

This opens two konsole terminals: the state machine node and the keyboard server.

Keyboard controls

Key Effect Handled by
n Advance to the next leaf state within the current superstate Leaf state reaction (event from MsRunning’s behavior)
f Switch between SsPhase1 and SsPhase2 SsPhase1 or SsPhase2 reaction (event from MsRunning’s behavior)
(timer) Auto-advance to next leaf state (3s in Phase1, 5s in Phase2) Leaf state reaction

Send keystrokes via ROS 2 topic (if not using the konsole keyboard server):

ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 110" --once  # n  — next leaf state
ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 102" --once  # f  — switch superstate

Example walkthroughs

Manual leaf state cycling in SsPhase1

Start → MsRunning/SsPhase1/StPhaseA
  → press n → StPhaseB
  → press n → StPhaseC
  → press n → StPhaseA   (back to start of cycle)

Switch to SsPhase2 and cycle there

(in SsPhase1/StPhaseB)
  → press f → SsPhase2/StPhaseX   (SsPhase2 always re-enters at StPhaseX)
  → press n → StPhaseY
  → press n → StPhaseX

Switch back to SsPhase1

```

File truncated at 100 lines see the full file

CHANGELOG
No CHANGELOG found.

Package Dependencies

System Dependencies

Name
xterm

Dependant Packages

No known dependants.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged sm_mode_state_behavior_1 at Robotics Stack Exchange

No version for distro kinetic showing jazzy. Known supported distros are highlighted in the buttons above.
Package symbol

sm_mode_state_behavior_1 package from SMACC2 repo

smacc2 cl_foundation_pose cl_gcalcli cl_generic_sensor cl_http cl_keyboard cl_lifecycle_node cl_mission_tracker cl_modbus_tcp_relay cl_moveit2z cl_nav2z backward_global_planner backward_local_planner forward_global_planner forward_local_planner nav2z_planners_common pure_spinning_local_planner undo_path_global_planner cl_px4_mr cl_ros2_timer eg_conditional_generator eg_random_generator smacc2_msgs sm_atomic_performance_trace_1 sm_atomic_subscribers_performance_test sm_coretest_action_client_1 sm_coretest_callback_rate_1 sm_coretest_exceptions_1 sm_coretest_features_1 sm_coretest_forced_finish_1 sm_coretest_poll_shutdown_1 sm_coretest_post_during_exit_1 sm_coretest_reactor_order_1 sm_coretest_signal_key_1 sm_coretest_timer_handoff_1 sm_coretest_transition_speed_1 sm_advanced_recovery_1 sm_atomic sm_atomic_http sm_atomic_lifecycle sm_atomic_mode_states sm_branching sm_cl_gcalcli_test_1 sm_cl_keyboard_unit_test_1 sm_cl_px4_mr_test_1 sm_cl_px4_mr_test_2 sm_cl_px4_mr_test_3 sm_cl_px4_mr_test_4 sm_cl_px4_mr_test_5 sm_cl_ros2_timer_unit_test_1 sm_data_sharing_1 sm_data_sharing_2 sm_modbus_tcp_relay_test_1 sm_mode_state_behavior_1 sm_multi_stage_1 sm_multithread_test_1 sm_nav2_gazebo_test_1 sm_nav2_gazebo_test_2 sm_nav2_gazebo_test_3 sm_pack_ml sm_panda_cl_moveit2z_cb_inventory sm_panda_cl_moveit2z_cb_inventory_isaacsim sm_retry_logic_1 sm_simple_action_client sm_three_some sr_all_events_go sr_conditional sr_event_countdown

ROS Distro
jazzy

Package Summary

Version 3.1.0
License Apache-2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/robosoft-ai/SMACC2.git
VCS Type git
VCS Version jazzy
Last Updated 2026-11-14
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Demonstrates a client behavior (CbDefaultKeyboardBehavior) defined at the mode state level, persisting across all inner superstate and leaf state transitions. Leaf states have only timer behaviors, avoiding double-event issues.

Maintainers

  • Brett Aldrich

Authors

No additional authors.

sm_mode_state_behavior_1

Demonstrates a client behavior defined at the mode state level, persisting across all inner superstate and leaf state transitions. The key insight: a behavior (here, CbDefaultKeyboardBehavior) owned by a parent state is created once when that parent enters and destroyed only when that parent exits — it survives every inner transition.

This machine also illustrates the correct solution to the double-event problem: if leaf states each had their own CbDefaultKeyboardBehavior, every keypress would generate two identical events (one per active behavior instance). By placing keyboard behavior exclusively in MsRunning, every keypress generates exactly one event regardless of which inner state is active.

What it demonstrates

  • CbDefaultKeyboardBehavior in OrKeyboard is declared in MsRunning::staticConfigure().
  • Leaf states (StPhaseA/B/C, StPhaseX/Y) have only CbTimerCountdownOnce — no keyboard behavior.
  • EvKeyPressN reactions in leaf states fire in response to events generated by MsRunning’s behavior — the event source and the reacting state are at different hierarchy levels.
  • EvKeyPressF reactions in SsPhase1/SsPhase2 switch between superstates; MsRunning’s keyboard behavior remains active throughout.

State hierarchy

SmModeStateBehavior1
├── OrTimer    (ClRos2Timer)
└── OrKeyboard (ClKeyboard)

MsRunning  ←  mode state; owns CbDefaultKeyboardBehavior in OrKeyboard
│              (keyboard behavior persists for the entire machine lifetime)
│
├── SsPhase1  (initial superstate)
│   │  Reacts: EvKeyPressF → SsPhase2
│   │
│   ├── StPhaseA  (initial)  3s timer
│   ├── StPhaseB             3s timer
│   └── StPhaseC             3s timer
│       (A → B → C → A cycle via timer or 'n')
│
└── SsPhase2
    │  Reacts: EvKeyPressF → SsPhase1
    │
    ├── StPhaseX  (initial)  5s timer
    └── StPhaseY             5s timer
        (X → Y → X cycle via timer or 'n')

Build

cd /home/brettpac/workspaces/isaac_ros-dev
colcon build --packages-select sm_mode_state_behavior_1
source install/setup.bash

Launch

ros2 launch sm_mode_state_behavior_1 sm_mode_state_behavior_1.launch.py

This opens two konsole terminals: the state machine node and the keyboard server.

Keyboard controls

Key Effect Handled by
n Advance to the next leaf state within the current superstate Leaf state reaction (event from MsRunning’s behavior)
f Switch between SsPhase1 and SsPhase2 SsPhase1 or SsPhase2 reaction (event from MsRunning’s behavior)
(timer) Auto-advance to next leaf state (3s in Phase1, 5s in Phase2) Leaf state reaction

Send keystrokes via ROS 2 topic (if not using the konsole keyboard server):

ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 110" --once  # n  — next leaf state
ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 102" --once  # f  — switch superstate

Example walkthroughs

Manual leaf state cycling in SsPhase1

Start → MsRunning/SsPhase1/StPhaseA
  → press n → StPhaseB
  → press n → StPhaseC
  → press n → StPhaseA   (back to start of cycle)

Switch to SsPhase2 and cycle there

(in SsPhase1/StPhaseB)
  → press f → SsPhase2/StPhaseX   (SsPhase2 always re-enters at StPhaseX)
  → press n → StPhaseY
  → press n → StPhaseX

Switch back to SsPhase1

```

File truncated at 100 lines see the full file

CHANGELOG
No CHANGELOG found.

Package Dependencies

System Dependencies

Name
xterm

Dependant Packages

No known dependants.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged sm_mode_state_behavior_1 at Robotics Stack Exchange

No version for distro melodic showing jazzy. Known supported distros are highlighted in the buttons above.
Package symbol

sm_mode_state_behavior_1 package from SMACC2 repo

smacc2 cl_foundation_pose cl_gcalcli cl_generic_sensor cl_http cl_keyboard cl_lifecycle_node cl_mission_tracker cl_modbus_tcp_relay cl_moveit2z cl_nav2z backward_global_planner backward_local_planner forward_global_planner forward_local_planner nav2z_planners_common pure_spinning_local_planner undo_path_global_planner cl_px4_mr cl_ros2_timer eg_conditional_generator eg_random_generator smacc2_msgs sm_atomic_performance_trace_1 sm_atomic_subscribers_performance_test sm_coretest_action_client_1 sm_coretest_callback_rate_1 sm_coretest_exceptions_1 sm_coretest_features_1 sm_coretest_forced_finish_1 sm_coretest_poll_shutdown_1 sm_coretest_post_during_exit_1 sm_coretest_reactor_order_1 sm_coretest_signal_key_1 sm_coretest_timer_handoff_1 sm_coretest_transition_speed_1 sm_advanced_recovery_1 sm_atomic sm_atomic_http sm_atomic_lifecycle sm_atomic_mode_states sm_branching sm_cl_gcalcli_test_1 sm_cl_keyboard_unit_test_1 sm_cl_px4_mr_test_1 sm_cl_px4_mr_test_2 sm_cl_px4_mr_test_3 sm_cl_px4_mr_test_4 sm_cl_px4_mr_test_5 sm_cl_ros2_timer_unit_test_1 sm_data_sharing_1 sm_data_sharing_2 sm_modbus_tcp_relay_test_1 sm_mode_state_behavior_1 sm_multi_stage_1 sm_multithread_test_1 sm_nav2_gazebo_test_1 sm_nav2_gazebo_test_2 sm_nav2_gazebo_test_3 sm_pack_ml sm_panda_cl_moveit2z_cb_inventory sm_panda_cl_moveit2z_cb_inventory_isaacsim sm_retry_logic_1 sm_simple_action_client sm_three_some sr_all_events_go sr_conditional sr_event_countdown

ROS Distro
jazzy

Package Summary

Version 3.1.0
License Apache-2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/robosoft-ai/SMACC2.git
VCS Type git
VCS Version jazzy
Last Updated 2026-11-14
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Demonstrates a client behavior (CbDefaultKeyboardBehavior) defined at the mode state level, persisting across all inner superstate and leaf state transitions. Leaf states have only timer behaviors, avoiding double-event issues.

Maintainers

  • Brett Aldrich

Authors

No additional authors.

sm_mode_state_behavior_1

Demonstrates a client behavior defined at the mode state level, persisting across all inner superstate and leaf state transitions. The key insight: a behavior (here, CbDefaultKeyboardBehavior) owned by a parent state is created once when that parent enters and destroyed only when that parent exits — it survives every inner transition.

This machine also illustrates the correct solution to the double-event problem: if leaf states each had their own CbDefaultKeyboardBehavior, every keypress would generate two identical events (one per active behavior instance). By placing keyboard behavior exclusively in MsRunning, every keypress generates exactly one event regardless of which inner state is active.

What it demonstrates

  • CbDefaultKeyboardBehavior in OrKeyboard is declared in MsRunning::staticConfigure().
  • Leaf states (StPhaseA/B/C, StPhaseX/Y) have only CbTimerCountdownOnce — no keyboard behavior.
  • EvKeyPressN reactions in leaf states fire in response to events generated by MsRunning’s behavior — the event source and the reacting state are at different hierarchy levels.
  • EvKeyPressF reactions in SsPhase1/SsPhase2 switch between superstates; MsRunning’s keyboard behavior remains active throughout.

State hierarchy

SmModeStateBehavior1
├── OrTimer    (ClRos2Timer)
└── OrKeyboard (ClKeyboard)

MsRunning  ←  mode state; owns CbDefaultKeyboardBehavior in OrKeyboard
│              (keyboard behavior persists for the entire machine lifetime)
│
├── SsPhase1  (initial superstate)
│   │  Reacts: EvKeyPressF → SsPhase2
│   │
│   ├── StPhaseA  (initial)  3s timer
│   ├── StPhaseB             3s timer
│   └── StPhaseC             3s timer
│       (A → B → C → A cycle via timer or 'n')
│
└── SsPhase2
    │  Reacts: EvKeyPressF → SsPhase1
    │
    ├── StPhaseX  (initial)  5s timer
    └── StPhaseY             5s timer
        (X → Y → X cycle via timer or 'n')

Build

cd /home/brettpac/workspaces/isaac_ros-dev
colcon build --packages-select sm_mode_state_behavior_1
source install/setup.bash

Launch

ros2 launch sm_mode_state_behavior_1 sm_mode_state_behavior_1.launch.py

This opens two konsole terminals: the state machine node and the keyboard server.

Keyboard controls

Key Effect Handled by
n Advance to the next leaf state within the current superstate Leaf state reaction (event from MsRunning’s behavior)
f Switch between SsPhase1 and SsPhase2 SsPhase1 or SsPhase2 reaction (event from MsRunning’s behavior)
(timer) Auto-advance to next leaf state (3s in Phase1, 5s in Phase2) Leaf state reaction

Send keystrokes via ROS 2 topic (if not using the konsole keyboard server):

ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 110" --once  # n  — next leaf state
ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 102" --once  # f  — switch superstate

Example walkthroughs

Manual leaf state cycling in SsPhase1

Start → MsRunning/SsPhase1/StPhaseA
  → press n → StPhaseB
  → press n → StPhaseC
  → press n → StPhaseA   (back to start of cycle)

Switch to SsPhase2 and cycle there

(in SsPhase1/StPhaseB)
  → press f → SsPhase2/StPhaseX   (SsPhase2 always re-enters at StPhaseX)
  → press n → StPhaseY
  → press n → StPhaseX

Switch back to SsPhase1

```

File truncated at 100 lines see the full file

CHANGELOG
No CHANGELOG found.

Package Dependencies

System Dependencies

Name
xterm

Dependant Packages

No known dependants.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged sm_mode_state_behavior_1 at Robotics Stack Exchange

No version for distro noetic showing jazzy. Known supported distros are highlighted in the buttons above.
Package symbol

sm_mode_state_behavior_1 package from SMACC2 repo

smacc2 cl_foundation_pose cl_gcalcli cl_generic_sensor cl_http cl_keyboard cl_lifecycle_node cl_mission_tracker cl_modbus_tcp_relay cl_moveit2z cl_nav2z backward_global_planner backward_local_planner forward_global_planner forward_local_planner nav2z_planners_common pure_spinning_local_planner undo_path_global_planner cl_px4_mr cl_ros2_timer eg_conditional_generator eg_random_generator smacc2_msgs sm_atomic_performance_trace_1 sm_atomic_subscribers_performance_test sm_coretest_action_client_1 sm_coretest_callback_rate_1 sm_coretest_exceptions_1 sm_coretest_features_1 sm_coretest_forced_finish_1 sm_coretest_poll_shutdown_1 sm_coretest_post_during_exit_1 sm_coretest_reactor_order_1 sm_coretest_signal_key_1 sm_coretest_timer_handoff_1 sm_coretest_transition_speed_1 sm_advanced_recovery_1 sm_atomic sm_atomic_http sm_atomic_lifecycle sm_atomic_mode_states sm_branching sm_cl_gcalcli_test_1 sm_cl_keyboard_unit_test_1 sm_cl_px4_mr_test_1 sm_cl_px4_mr_test_2 sm_cl_px4_mr_test_3 sm_cl_px4_mr_test_4 sm_cl_px4_mr_test_5 sm_cl_ros2_timer_unit_test_1 sm_data_sharing_1 sm_data_sharing_2 sm_modbus_tcp_relay_test_1 sm_mode_state_behavior_1 sm_multi_stage_1 sm_multithread_test_1 sm_nav2_gazebo_test_1 sm_nav2_gazebo_test_2 sm_nav2_gazebo_test_3 sm_pack_ml sm_panda_cl_moveit2z_cb_inventory sm_panda_cl_moveit2z_cb_inventory_isaacsim sm_retry_logic_1 sm_simple_action_client sm_three_some sr_all_events_go sr_conditional sr_event_countdown

ROS Distro
jazzy

Package Summary

Version 3.1.0
License Apache-2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/robosoft-ai/SMACC2.git
VCS Type git
VCS Version jazzy
Last Updated 2026-11-14
Dev Status DEVELOPED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

Demonstrates a client behavior (CbDefaultKeyboardBehavior) defined at the mode state level, persisting across all inner superstate and leaf state transitions. Leaf states have only timer behaviors, avoiding double-event issues.

Maintainers

  • Brett Aldrich

Authors

No additional authors.

sm_mode_state_behavior_1

Demonstrates a client behavior defined at the mode state level, persisting across all inner superstate and leaf state transitions. The key insight: a behavior (here, CbDefaultKeyboardBehavior) owned by a parent state is created once when that parent enters and destroyed only when that parent exits — it survives every inner transition.

This machine also illustrates the correct solution to the double-event problem: if leaf states each had their own CbDefaultKeyboardBehavior, every keypress would generate two identical events (one per active behavior instance). By placing keyboard behavior exclusively in MsRunning, every keypress generates exactly one event regardless of which inner state is active.

What it demonstrates

  • CbDefaultKeyboardBehavior in OrKeyboard is declared in MsRunning::staticConfigure().
  • Leaf states (StPhaseA/B/C, StPhaseX/Y) have only CbTimerCountdownOnce — no keyboard behavior.
  • EvKeyPressN reactions in leaf states fire in response to events generated by MsRunning’s behavior — the event source and the reacting state are at different hierarchy levels.
  • EvKeyPressF reactions in SsPhase1/SsPhase2 switch between superstates; MsRunning’s keyboard behavior remains active throughout.

State hierarchy

SmModeStateBehavior1
├── OrTimer    (ClRos2Timer)
└── OrKeyboard (ClKeyboard)

MsRunning  ←  mode state; owns CbDefaultKeyboardBehavior in OrKeyboard
│              (keyboard behavior persists for the entire machine lifetime)
│
├── SsPhase1  (initial superstate)
│   │  Reacts: EvKeyPressF → SsPhase2
│   │
│   ├── StPhaseA  (initial)  3s timer
│   ├── StPhaseB             3s timer
│   └── StPhaseC             3s timer
│       (A → B → C → A cycle via timer or 'n')
│
└── SsPhase2
    │  Reacts: EvKeyPressF → SsPhase1
    │
    ├── StPhaseX  (initial)  5s timer
    └── StPhaseY             5s timer
        (X → Y → X cycle via timer or 'n')

Build

cd /home/brettpac/workspaces/isaac_ros-dev
colcon build --packages-select sm_mode_state_behavior_1
source install/setup.bash

Launch

ros2 launch sm_mode_state_behavior_1 sm_mode_state_behavior_1.launch.py

This opens two konsole terminals: the state machine node and the keyboard server.

Keyboard controls

Key Effect Handled by
n Advance to the next leaf state within the current superstate Leaf state reaction (event from MsRunning’s behavior)
f Switch between SsPhase1 and SsPhase2 SsPhase1 or SsPhase2 reaction (event from MsRunning’s behavior)
(timer) Auto-advance to next leaf state (3s in Phase1, 5s in Phase2) Leaf state reaction

Send keystrokes via ROS 2 topic (if not using the konsole keyboard server):

ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 110" --once  # n  — next leaf state
ros2 topic pub /keyboard_unicode std_msgs/msg/UInt16 "data: 102" --once  # f  — switch superstate

Example walkthroughs

Manual leaf state cycling in SsPhase1

Start → MsRunning/SsPhase1/StPhaseA
  → press n → StPhaseB
  → press n → StPhaseC
  → press n → StPhaseA   (back to start of cycle)

Switch to SsPhase2 and cycle there

(in SsPhase1/StPhaseB)
  → press f → SsPhase2/StPhaseX   (SsPhase2 always re-enters at StPhaseX)
  → press n → StPhaseY
  → press n → StPhaseX

Switch back to SsPhase1

```

File truncated at 100 lines see the full file

CHANGELOG
No CHANGELOG found.

Package Dependencies

System Dependencies

Name
xterm

Dependant Packages

No known dependants.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged sm_mode_state_behavior_1 at Robotics Stack Exchange