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

2 Hz OpenDroneID rate + unknown pressure altitude accuracy #21819

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

n-snyder
Copy link
Contributor

@n-snyder n-snyder commented Jul 7, 2023

Solved Problem

The remote ID broadcast latency and message rate must be <= 1 per sec. If there is any delay in relaying the message to the beacon, packing the message, and broadcasting the message, the system will not meet the requirement.

In addition, the pressure altitude accuracy is given an arbitrary large default value instead of just 'unknown'.

Solution

  • Increased location and system messages from 1 Hz to 2 Hz
  • Changed pressure altitude accuracy to 'unknown'

@DronecodeBot
Copy link

This pull request has been mentioned on Discussion Forum for PX4, Pixhawk, QGroundControl, MAVSDK, MAVLink. There might be relevant details there:

https://discuss.px4.io/t/remote-id-coordination-july-11th/33191/1

@github-actions github-actions bot added the stale label Aug 11, 2023
@julianoes
Copy link
Contributor

I agree with the baro uncertainty flag but I don't think we should send it at 1 Hz if the requirement is 1 <= per sec. I would think it's completely reasonable to send it at 1 Hz, even if there is a slight bit of jitter.

I'm already/also fixing the baro uncertainty in #23113.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants