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
Rework LQ/RSSI (dBm) OSD elements for non-CRSF Rxs #9280
Comments
I initially get the blame on this and I welcome these changes, specifically the legacy 300% LQ thing that nobody uses. I could take a shot at it but it's going to take me a long time. Too busy at work. |
I agree that making it less CRSF specific is a good idea, but it is still at the mercy of the rf protocol reporting those values. |
There is nothing we can do about that, but at least having a generic framework within iNav will encourage radio manufacturers to support it. Certainly on the Ghost side I am 100% committed to get these values reported correctly. |
Does Ghost currently implement a LQ telemetry element? Or is it something that would need to be added on both sides? |
Ghost implements it, infact it is already processed in the iNav driver and passed to lqTrackerSet (although I am not quite sure what this is doing...) |
I believe lqTracker is not related to the LQ% statistic if I remember correctly. It's part of the rx protocol and more of an INAVs "are we live and connected to an rx link" thing. |
Current Behavior
Critical LQ/RSSI (dBm) values available only to users of the CRSF protocol.
Desired Behavior
Unlike Betaflight, critical iNav OSD elements for long-range flight such as LQ, and RSSI (dBm) are only available for CRSF receivers.
I propose a bit of a rework, to simplify this, and enable it for all receivers, Ghost included.
Suggested Solution
I am happy to help out with the changes required for this feature, ideally with contributors who are familiar in this area of code.
Who does this impact? Who is this for?
Everyone doing long-range flight with non-CRSF receivers
The text was updated successfully, but these errors were encountered: