Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to run input_device_teleop_example with PSM #163

Open
zhengdae opened this issue Apr 8, 2022 · 1 comment
Open

Unable to run input_device_teleop_example with PSM #163

zhengdae opened this issue Apr 8, 2022 · 1 comment

Comments

@zhengdae
Copy link

zhengdae commented Apr 8, 2022

Hi,

I was able to teleoperate the KUKA robot using the python GUI as demonstrated in the example.
However, then I tried to replace KUKA with PSM.

I tried two methods:

  1. $ /ambf_simulator -p60 -t1 --launch_file ~/ambf/ambf_models/descriptions/launch.yaml -l5 -i0. In this case, the PSM showed up with a small red gripper. The teleoperation was not working on the PSM but the gripper angle could be controlled.
  2. I added a line in the launch.yaml file in "input_device_teleop_example". It is like:

world config: ./world/world.yaml
color config: ./color/colors.yaml
input devices config: ./input_devices/input_devices.yaml
multibody configs:
- "./blender-kuka-tip-sphere.yaml" #0
- "/home/ambf/ambf_models/descriptions/multi-bodies/robots/blender-psm.yaml"

However, the KUKA showed up again, even though I have commented out the KUKA yaml."

Could you please help me with it?

Best,
Yi

adnanmunawar added a commit to adnanmunawar/ambf that referenced this issue Apr 11, 2022
@adnanmunawar
Copy link
Member

Hi Yi,
The above commit should fix the issue of applying forces to a body (end-effector) to move it for teleoperation purposes. You might want to take a look at this README to read more about what files and fields are required for setting up teleop control.
Lastly, please refer to this issue for reading up on the issues and recommendations on teleoperating robots with articulated links.

adnanmunawar added a commit that referenced this issue Jul 18, 2022
* Fix: python print command

* Fix: enable comm in worldComm plugin

* Fix: only update volumes from graphics loop

* Fix: reset didn't always work on all bodies.

* Adding capability to reset world and bodies from world comm obj

* Adding the ability to reset the world or the bodies

* FIX: Resetting the GLFW_VISIBLE flag to show subsequent visible windows

* Issue #163. Setting activeControllerType to Force.

* Fix: For rigid body's Position command, use the COM Transform.

* Reset sensors communication message

* Should address #178
adnanmunawar added a commit that referenced this issue Jan 10, 2024
* Fix: python print command

* Fix: enable comm in worldComm plugin

* Fix: only update volumes from graphics loop

* Fix: reset didn't always work on all bodies.

* Adding capability to reset world and bodies from world comm obj

* Adding the ability to reset the world or the bodies

* FIX: Resetting the GLFW_VISIBLE flag to show subsequent visible windows

* Issue #163. Setting activeControllerType to Force.

* Fix: For rigid body's Position command, use the COM Transform.

* Reset sensors communication message

* Should address #178

* Fixed inconsistency in rotation between 'get_rpy' and 'get_pose'

* Implement merging duplicate vertices

* Maintain a tree of duplicate vertices

* Assign the vertices Ptr to the triangleArray's copy of vertices

* Fixed algorithm

* Set only valid vertex data

* Default to false for resizing element array on every iteration

* Added method to set vtx pos of all duplicates by single index

* Minor cleanup

* Cleanup creating collision objects and softbody implementation

* Cleaned up fixing softbody nodes impl

* Allow for controlling whether to remove or not remove duplicates
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants