The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
Based on the callback-and-loop-in-execute-with-mutex scheme Ugo mentioned in his answer I made a fully generic message receiver smach.State class that helps a lot for receiving messages in a SMACH machine, as I couldn't made use of the the MonitorState.
The current feature set includes waiting, timeout, userdata access and latching, of course optional.
Class WaitForMsgState in module util.py in unreleased package uashh_smach. The class CheckSmachEnabledState right underneath is a simple usage example
As the whole class has a lot of (docstring) lines I just post the commit-static link to its code line and the up-to-date link to the module's file in the repository.
| | 2 | No.2 Revision |
Based on the callback-and-loop-in-execute-with-mutex scheme Ugo mentioned in his answer I made a fully generic message receiver smach.State class that helps a lot for receiving messages in a SMACH machine, as I couldn't made use of the the MonitorState.
The current feature set includes waiting, timeout, userdata access and latching, of course optional.
Class WaitForMsgState in module util.py in unreleased package uashh_smach. The class CheckSmachEnabledState right underneath is a simple usage example
As the whole class has a lot of (docstring) lines I just post the commit-static link to its code line and the up-to-date link to the module's file in the repository. (and just for read only reference the commit-static link to its code line).
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
