-
Notifications
You must be signed in to change notification settings - Fork 36
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
LQ in MWPTools #184
Comments
Currently, mwp displays |
Do you know if it would be feasible to extend |
It has been considered acceptable to extend messages by appending fields (not inserting other than at the end). Then consumers can check the length to see of the extended data is available. Otherwise the options would be:
My preference would be to add the required fields to |
Actually: I have an idea for that I will discuss with Darren for a future version. We actually have the message for that. We have the MSP2_LINK_STATS message that came with 8.0. Right now its just to feed the FC with RC link information. But there would speak nothing against to request the same data back from the FC. Its all in there, technically even from other RC Link inputs like CRSF as they feed the same internal variables. Probably both variants would be good. Extend |
As a regular user, I appreciate the ideas you have for expanding the download of information from INAV to MWP. I look forward to your progress, I am very happy with MWP and I think it would be very useful to have it under MSP modality. |
as the Limitation is INAV here I opened a Request there. Guess we can close here for now unless stronnag want to keep it open for reference. |
Ok. For my part, I will be attentive to that INAV Request. |
Hello: I am using INAV 8.0.0 RC1 with MSP for RX and Telemetry. TX and RX are from Matek under mLRS mode.
My need is to see the LQ on screen along with the RSSI. I can only see RSS and it would be very useful to see the LQ and even the SNR (Signal to Noise Ratio) together.
Is this possible?
The text was updated successfully, but these errors were encountered: