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

roslaunch mavros_apriltag_tracking tracker.launch #11

Open
Sunyuzxy opened this issue Mar 17, 2022 · 5 comments
Open

roslaunch mavros_apriltag_tracking tracker.launch #11

Sunyuzxy opened this issue Mar 17, 2022 · 5 comments

Comments

@Sunyuzxy
Copy link

My environment is as below:
Ubuntu18.04
Ros melodic
PX4 v1.10.1
I set up my environment as the instructions in PX4 website and your README.md, however there is some error as below:

Resource not found: The following package was not found in : mavlink_sitl_gazebo
ROS path [0]=/opt/ros/melodic/share/ros
ROS path [1]=/home/sy/catkin_ws/src/mavros_apriltag_tracking
ROS path [2]=/home/sy/can_module/src
ROS path [3]=/opt/ros/melodic/share
The traceback for the exception was written to the log file

Can you give me a hand please?

@Soapen
Copy link

Soapen commented Sep 8, 2022

How did you fixed it?

@Ethan-02
Copy link

Ethan-02 commented Nov 9, 2022

I have the issue too.
Did you fixed it?

@AlexWUrobot
Copy link

AlexWUrobot commented Nov 11, 2022

Ubuntu 18.04
ROS melodic
I already source devel/setup.zsh, but I have a similar issue.
image

@AlexWUrobot
Copy link

I solve it by put the whole package installing with PX4-Autopilot.
Then, catkin build again
Then, source
Then, check the package "mavlink_sitl_gazebo" exists by using "rospack list-names"
image

@bytesByHarsh
Copy link

Hi
You can solve this by running the following commands:

source ~/catkin_ws/devel/setup.bash 
source Tools/setup_gazebo.bash $(pwd) $(pwd)/build/px4_sitl_default
export ROS_PACKAGE_PATH=$ROS_PACKAGE_PATH:$(pwd)
export ROS_PACKAGE_PATH=$ROS_PACKAGE_PATH:$(pwd)/Tools/sitl_gazebo

Assuming, that you are running the command from the PX4 SITL folder. You can change the relative path if you want.

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

5 participants