-
Notifications
You must be signed in to change notification settings - Fork 13.7k
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
DISTANCE_SENSOR adopting #2200
DISTANCE_SENSOR adopting #2200
Conversation
publication to range_finder topic added
*/ | ||
struct distance_sensor_s { | ||
|
||
uint32_t time_boot_ms; /**< Time since system boot */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please put this into the msg folder and let it auto-generate.
@LorenzMeier can you please do a mavlink release so I can add |
@TSC21 Can you please remove the auto-generated uorb topic file. :) |
Remove? Lorenz asked me in a comment to add it :D |
OK I understood now. I was comparing the |
I updated the mavlink lib on master. |
@LorenzMeier thanks! |
…ions in vtable' bug
…r data members, had to disable it
…eads from the driver, as well as various other small changes
…WM and I2C driver
I'm closing this PR, as #2224 is the current one! |
[work in progress] This PR pretends to add
DISTANCE_SENSOR
msg as the main message for pub range sensor data, being altimeters or side sensors for obsavoid.