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

Incorrect Mesh Path in husky_isaac_sim.py causing Launch Error #4

Open
mashikolort opened this issue Jun 12, 2024 · 0 comments
Open

Comments

@mashikolort
Copy link

Issue

After Isaac Sim is launched, the environment is loaded, and the terminal where Isaac Sim is running prints "Robot Loader Start," we run the following command, which should launch rviz and load Husky on Isaac Sim:
run ros2 launch husky_isaac_sim robot_display.launch.py

As a result, rviz launches and Husky robot is loaded in Isaac Sim, but it is not visible and doesn't contain meshes.

Cause

The husky_isaac_sim.py script, used in ./husky_demo.sh, which contains RobotLoader Class defines incorrect paths for the mesh locations on lines 160-161 of the callback_description function. The script assumes the meshes are located directly under share.

  1. isaac_ros/install/share/husky_description/meshes (incorrect)
  2. isaac_ros/install/share/husky_isaac_sim/meshes (incorrect)

These paths should have been:

  1. isaac_ros/install/husky_description/share/husky_description/meshes (correct)
  2. isaac_ros/install/husky_isaac_sim/share/husky_isaac_sim/meshes (correct)

Solution

The issue was resolved by updating the husky_isaac_sim.py script on lines 160-161 within the callback_description function. The updated code snippet is shown below:

else: print("Running from Workstation") # Get the current working directory path_meshes = os.path.join(os.getcwd(), "isaac_ros", "install", "husky_description", "share", "husky_description", "meshes") path_mesh_accessories = os.path.join(os.getcwd(), "isaac_ros", "install", "husky_isaac_sim", "share", "husky_isaac_sim", "meshes")
This ensures the script searches for meshes in the expected locations within the package structure. When running

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

1 participant