You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am having the same issue as closed issue 17286. I got the obstacle_distance data from zed camera to fcu using mavros. I can see on mavlink inspector. All good but promity display shows is skewed exactly as issue 17286. The issue was closed as apparently it was fixed in 4.1. I am using ardurover 4.2.2 so something is not right. I can move the skew around by changing min_angle which changes the angle_offset on mavlink inspector but what is the correct value and why? Also, no ability to change the frame. It is set to 0. Apparently I should be using 12 but how?
Lastly, was resize ever implemented to scale larger laser scans to 72 elements ? I saw a blog that it was implemented by .resize(72) does not exist.
The text was updated successfully, but these errors were encountered:
It is possible that the issue is actually in mavros. There have been at least two PRs trying to fix an issue on the mavros side (mavlink/mavros#1700, mavlink/mavros#1434).
I am having the same issue as closed issue 17286. I got the obstacle_distance data from zed camera to fcu using mavros. I can see on mavlink inspector. All good but promity display shows is skewed exactly as issue 17286. The issue was closed as apparently it was fixed in 4.1. I am using ardurover 4.2.2 so something is not right. I can move the skew around by changing min_angle which changes the angle_offset on mavlink inspector but what is the correct value and why? Also, no ability to change the frame. It is set to 0. Apparently I should be using 12 but how?
Lastly, was resize ever implemented to scale larger laser scans to 72 elements ? I saw a blog that it was implemented by .resize(72) does not exist.
The text was updated successfully, but these errors were encountered: