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

Better handling of Multiple telemetry sources from one balloon flight. #5

Open
darksidelemm opened this issue Feb 12, 2019 · 0 comments
Labels
enhancement New feature or request

Comments

@darksidelemm
Copy link
Member

On many Horus flights we may have redundant telemetry payloads. Usually these are fed into OziMux, where an operator can observe which is providing the 'best' data (best = highest update rate, with valid position), and select that payload to feed into the map.

It would be better if this selection was handled automatically.

The idea would be you would configure a set of telemetry sources (be it either a Horus_UDP type source, or an ozimux type source... really need to unify this stuff), and define them to be from the same 'flight'. Some algorithm would then monitor the frequency of updates and pick the best source to use for mapping. If that source has a gap in data, it then drops back to the next source. and so on.

@darksidelemm darksidelemm added the enhancement New feature or request label Feb 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant