-
Notifications
You must be signed in to change notification settings - Fork 87
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
Frame conventions for global motion data and velocity data. #28
Comments
Update: Test flights revealed that motion along y-axis obeyed NED convention. I cannot confirm that the global motion data is indeed in NED space since the z value is zero most of the time. By inverting the motion along y-axis, I was able to perform flights using position from global motion data as a differential input. Another data point would help consolidated this issue. |
Hello, I'm trying to use guidance to have motion data but even if I put the select motion () function in the usb_example provided in the sdk I don't see the data displaying. The e_motion event doesn't occur, never... Thank you ! |
Hi, I've obtained the motion data successfully using select_motion(), and visualized the position and pose in Rviz. But the results show that the movement and orientation are incorrect. When moving along the z-axis and body frame y-axis, it goes in the opposite direction in Rviz. But when moving in the direction of the head of the drone(body frame x), the result is correct in Rviz. Do you have any idea how this happens? Thanks! |
I am using the guidance as a odometry source for UAVs. I am looking for some info on the frame conventions used. Is the odometry data reported in a NED or ENU frame ? The x axis seems to be consistent. But movements along y axis seemed to be inverted. Could someone shed some light on this ?
The text was updated successfully, but these errors were encountered: