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 example.launch #103

Open
deepak-1530 opened this issue Feb 20, 2020 · 3 comments
Open

Unable to run example.launch #103

deepak-1530 opened this issue Feb 20, 2020 · 3 comments

Comments

@deepak-1530
Copy link

When I run the example.launch file and then press ENTER, I get the following error-:

[FATAL] [1582182912.640695319, 11.590000000]: Trying to publish message of type [mav_planning_msgs/PolynomialTrajectory/2daf5d705534e84f80980f4673a0e62b] on a publisher with type [mav_planning_msgs/PolynomialTrajectory4D/4d68d15524ede489eecd674bb6dc3ee8]
[FATAL] [1582182912.640714553, 11.590000000]:

@yvesdaoud
Copy link

Was this ever solved?

@Jadelogan65
Copy link

I'm receiving the same error message - any ideas?

@Jadelogan65
Copy link

I looked into this a bit today. There's a small change to get it working:

Small change to
/home/counterswarm/catkin_newrotors/src/mav_trajectory_generation/mav_trajectory_generation_example/src/example_planner.cc

Line 133-134 converts the planned trajectory (cleverly named trajectory) to a PolynomialTrajectory type called msg
mav_planning_msgs::PolynomialTrajectory msg;
mav_trajectory_generation::trajectoryToPolynomialTrajectoryMsg(trajectory, &msg);

At line 137 msg is published
pub_trajectory_.publish(msg);

msg is a mav_planning_msgs/PolynomialTrajectory message type
While pub_trajectory_ is defined as a mav_planning_msgs/PolynomialTrajectory4D message type

Change msg to
mav_planning_msgs::PolynomialTrajectory4D msg;

Run catkin build and the example ran successfully for me.

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

3 participants