system_modes
system_modes copied to clipboard
micro-ROS
System modes for ROS 2 and micro-ROS
- Seems natural to use the same concept (i.e. runtime lifecycle) for these to nodes themselves. - Yet, in many applications, the mode manager node will be used continuously from...
from (#47 ) > This is in the context of our exemplary case of the `laser_driver` error. We want to elaborate on the **layered** approach we discussed in the last...
This PR introduces the necessary changes to build the system modes packages on Windows, e.g., visibility control. Part of https://github.com/micro-ROS/system_modes/issues/35 and the quality level
When calling the services provided by the mode manager (e.g., `/{system}/change_state`), the service call never returns and never executes. This blocks #35.
Mode manager raises a segfault when working with nodes that live in namespaces. The error happened when trying to prepend a namespace (e.g., in the example for one of the...
If we know through mode inference, that a certain state or mode of a (sub-)system can't be transitioned to, should `get_available_states` and `get_available_modes` of (sub-)systems report accordingly? Example: * Subsystem...
See https://github.com/micro-ROS/system_modes/pull/33: Builds on windows and macos are failing for different reasons: windows fails due to failing osrf_testing_tools_cpp, macos fails due to missing boost.
The mode manager usually knows the **target** state/mode and the **current** state/mode (via mode_inference) of a system or node. Currently we assume, that there is a trivial transition to the...
For launching the nodes specified in a system-mode models file (SHM file) for control by the mode-manager, all these nodes have to be specified additionally in a launch file. This...