You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: