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

Stop sending sensor offsets mavlink message #18368

Merged
merged 7 commits into from
Aug 18, 2021

Conversation

peterbarker
Copy link
Contributor

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.
Only works for first compass instance.

We have all of these in parameters anyway.
Copy link
Contributor

@amilcarlucas amilcarlucas left a 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.

@amilcarlucas
Copy link
Contributor

Forget about my comment. I now read mavlink/mavlink#1453 and understand why you want to fully remove this message.

Copy link
Contributor

@WickedShell WickedShell left a 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) {
Copy link
Contributor

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,
Copy link
Contributor

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.

@rmackay9
Copy link
Contributor

I certainly like the idea of reducing our telemetry bandwidth usage..

@tridge tridge merged commit f1e2e34 into ArduPilot:master Aug 18, 2021
@peterbarker peterbarker deleted the pr/stop-sending-sensor-offsets branch August 18, 2021 08:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants