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

Add Tx Snd RadioStat suggestion to SiK page #50

Closed
jlpoltrack opened this issue Jul 9, 2023 · 4 comments
Closed

Add Tx Snd RadioStat suggestion to SiK page #50

jlpoltrack opened this issue Jul 9, 2023 · 4 comments
Assignees

Comments

@jlpoltrack
Copy link
Collaborator

To have the RSSI of both radios, this parameter should be set (SiK does this).

@jlpoltrack jlpoltrack self-assigned this Jul 9, 2023
@olliw42
Copy link
Owner

olliw42 commented Jul 9, 2023

that's a most interesting comment, indeed

with regards to SiK specifically (and SBus), I think that's a good suggestion. It raises the question however if or why not it should be added to the other pages.

The RSSI topic is non trival. First as regards its sources and also as regards its value range. I would hope that there could be some canonicalization, by e.g. new MAVLink messages as suggested here mavlink/mavlink#1921 but the resistance to move is high, ArduPilot is largely driven by money today (partners, devs, companies) as it seems. So, we have to live with how it is.

AFAIK there can be/are 3 MAVLink sources of rssi from the flight controller, i.e., the receiver. As regards the rssi from the tx module, there is only one MAVLink source, the RadioStat message. But - except for SiK/SBus - there is also the CRSF data.

Maybe a RSSI page giving an overview of all options and approaches would be the best. But for the moment, adding it to Sik is probably a good idea, given that most people will be just confused otherwise.

@jlpoltrack
Copy link
Collaborator Author

PR: #51

@olliw42
Copy link
Owner

olliw42 commented Jul 9, 2023

great!! Thx!

I guess we can close this, but I think we want to keep the RSSI topic in mind to eventually, in some future, work it out.

@jlpoltrack
Copy link
Collaborator Author

jlpoltrack commented Jul 9, 2023

I guess we can close this, but I think we want to keep the RSSI topic in mind to eventually, in some future, work it out.

Agreed, I will create a new issue for a 'Link Statistics Page' and assign myself. #53

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

No branches or pull requests

2 participants