You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When testing the YuMi gripper skill I started out by calling the actuate_yumi_gripper primitive with the left arm from the GUI.
When starting to test it on the right arm, it still received the world model element for the right arm inside the skill in the onStart function.
I haven't checked if this is a GUI issue or skill manager/world model issue. When debugging one can think about starting the skill directly from python.
@marcusklang: This should be possible to reproduce with that skill. I just set a breakpoint in onStart before it initializes the robot interface since that would not connect.
The text was updated successfully, but these errors were encountered:
When testing the YuMi gripper skill I started out by calling the
actuate_yumi_gripper
primitive with the left arm from the GUI.When starting to test it on the right arm, it still received the world model element for the right arm inside the skill in the
onStart
function.I haven't checked if this is a GUI issue or skill manager/world model issue. When debugging one can think about starting the skill directly from python.
@marcusklang: This should be possible to reproduce with that skill. I just set a breakpoint in
onStart
before it initializes the robot interface since that would not connect.The text was updated successfully, but these errors were encountered: