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

error: ‘BODY_FRD’ is not a member of ‘mavlink::common::MAV_FRAME’ #1424

Closed
cesarecaputi opened this issue May 7, 2020 · 13 comments
Closed

Comments

@cesarecaputi
Copy link

Hi,
when building the ~/catkin_ws I get this error message

/catkin_ws/src/mavros/mavros_extras/src/plugins/odom.cpp:228:53: error: ‘BODY_FRD’ is not a member of ‘mavlink::common::MAV_FRAME’
msg.child_frame_id = utils::enum_value(MAV_FRAME::BODY_FRD);

Does anybody know how to fix it?

@vooon
Copy link
Member

vooon commented May 7, 2020

Update mavlink package.

@vooon
Copy link
Member

vooon commented May 7, 2020

Well, seems that is opposite case. Too mavlink release 2020.5.5 breaks beacause of mavlink/mavlink#1112.

I think temporary solution to replace enum_value with hardcoded value until it would be fixed in upstream.

@vooon
Copy link
Member

vooon commented May 7, 2020

I added quick fix to master, please update.
1a898de

@Cristian-wp
Copy link

Thanks vooon, yesterday I was getting crazy about this error!

@vooon vooon added this to the Version 1.2 milestone May 8, 2020
@vooon
Copy link
Member

vooon commented May 8, 2020

Closing this as resolved. But feel free to reopen if needed.

@vooon vooon closed this as completed May 8, 2020
@Cristian-wp
Copy link

Hi, I start a new project few minutes ago and the problem is still there...(I have fix it like you do).
I have follow the instruction from here
https://github.com/mavlink/mavros/tree/master/mavros#installation
maybe there is a problem with the master version(not updated with your changes)?

@vooon
Copy link
Member

vooon commented May 8, 2020

@Cristian-wp commit was to master. Try to git pull.

@hamishwillee
Copy link

hamishwillee commented May 10, 2020

@vooon YOu can perhaps help me. The above appears to be caused by a mavlink removal of a frame, which I think may have been incorrect.
Can you help me understand whether that removal was appropriate? See mavlink/mavlink#1112 (comment)

EDITED. And now I see you're hard coding to fix this. Which tells me that we need MAV_FRAME_BODY_FRD - right? My assumption is we don't need FLU variant?

@vooon
Copy link
Member

vooon commented May 12, 2020

@hamishwillee unfortunately i'm not quire sure, my commit just a quick fix to solve compilation problem.
As i remember BODY_NED was actually FRD, so it's introducing reduce confusion a bit.

After 1789e81#diff-750c83d1bf274515183c544f142bac77 odom only uses FRD, not FLU.

@hamishwillee
Copy link

Hi @vooon FYI, MAV_FRAME_BODY_FRD just got added back into common.xml :-)

@vooon
Copy link
Member

vooon commented May 21, 2020

@hamishwillee thanks! I'll release packages soon.

@canberkgurel
Copy link

I solved this problem as follows:

  1. Uninstall the mavlink:

sudo apt-get remove ros-kinetic-mavlink

  1. Clone the mavlink-gbp-release:

cd catkin_ws/src/
git clone https://github.com/mavlink/mavlink-gbp-release.git
cd mavlink-gbp-release
git checkout release/kinetic/mavlink

  1. Build the catkin workspace:

cd ~/catkin_ws
catkin clean -y
catkin build

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants