fix: concurency in skill nodes
This commit is contained in:
parent
adf84ebec7
commit
0798720a4c
8 changed files with 159 additions and 19 deletions
|
@ -1,19 +1,12 @@
|
|||
##Description: Moves robot arm to a specified pose relative to the frame in header.frame_id of target_pose
|
||||
#goal definition
|
||||
|
||||
#Used to indicate which hardcoded motion constraint to use
|
||||
#e.g 0 no constraint, 1 keep the same end effector orientation
|
||||
int32 constraint_mode
|
||||
#similar to geometry_msgs/PoseStamped but using euler instead of quaternion
|
||||
#at target_pose->header.frame_id define the tf frame
|
||||
# which the pose will be calculated relative from
|
||||
geometry_msgs/Pose target_pose
|
||||
string robot_name
|
||||
float32 end_effector_velocity
|
||||
float32 end_effector_acceleration
|
||||
float32 duration #if this action cannot be completed within this time period it should be considered failed.
|
||||
float32 duration
|
||||
string planner_id
|
||||
string pipeline_id
|
||||
float32 allowed_planning_time
|
||||
bool try_plan_untill_success
|
||||
---
|
||||
#result definition
|
||||
bool success
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue