-
Notifications
You must be signed in to change notification settings - Fork 16.8k
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
Stop sending sensor offsets mavlink message #18368
Stop sending sensor offsets mavlink message #18368
Conversation
Only works for first compass instance. We have all of these in parameters anyway.
Only works for first compass instance. We have all of these in parameters anyway.
Only works for first compass instance. We have all of these in parameters anyway.
Only works for first compass instance. We have all of these in parameters anyway.
Only works for first compass instance. We have all of these in parameters anyway.
Only works for first compass instance. We have all of these in parameters anyway.
Only works for first compass instance. We have all of these in parameters anyway.
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.
How about having the message only as a response to MAV_CMD_REQUEST_MESSAGE
That one can use param1 to select the IMU to use.
Forget about my comment. I now read mavlink/mavlink#1453 and understand why you want to fully remove this message. |
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.
I'm good with the change, seems like it saves bandwidth, memory, and yeah... I didn't have this message in my black list, but I'm adding it now...
|
||
// run this message at a much lower rate - otherwise it | ||
// pointlessly wastes quite a lot of bandwidth | ||
if (send_sensor_offsets_counter++ < 10) { |
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.
Ha! This defeats a lot of the scheduling/buffering code as well because it's harder to land on the right order with stuff like this confusing the buffer backoffs :P
mag_offsets.z, | ||
compass.get_declination(), | ||
barometer.get_pressure(), | ||
barometer.get_temperature()*100, |
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.
This isn't actually available via the parameters, but it is in the scaled pressure, which is better anyways.
I certainly like the idea of reducing our telemetry bandwidth usage.. |
Only works for first compass instance.
We have all of these in parameters anyway.