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

display named value float in Quick status #2346

Closed
tridge opened this issue Mar 5, 2020 · 5 comments · Fixed by #2780
Closed

display named value float in Quick status #2346

tridge opened this issue Mar 5, 2020 · 5 comments · Fixed by #2780

Comments

@tridge
Copy link
Contributor

tridge commented Mar 5, 2020

It would be really useful to be able to display NAMED_VALUE_FLOAT values in the MissionPlanner "Quick" display. The NAMED_VALUE_FLOAT is a single float value in mavlink with a string name. If a user could add a "Quick" field and choose the name they want to display then that would allow us to send NAMED_VALUE_FLOAT from on-board lua scripts to display custom values. It would be a massively useful way of extending the ability of lua scripts.
There is one current NAMED_VALUE_FLOAT we send in ArduPilot, the "AS2" value which is the 2nd airspeed sensor. So in SITL you can enable a 2nd airspeed sensor and start getting AS2 NAMED_VALUE_FLOAT for testing.

@EosBandi
Copy link
Collaborator

EosBandi commented Mar 21, 2020

OK, should it be automatic, or something that we can define in the config ? I mean just wait for a mavlink message and add the named value to currentstate or we can predefine names in config and look for them when updating currentstate ? The latter have less impact on current code.

@meee1
Copy link
Contributor

meee1 commented Mar 22, 2020

im thinking about using a dictionary in currentstate. but need to work though how complicated it will get

@EosBandi
Copy link
Collaborator

#2360 implements support fort NAMED_VALUE_FLOAT display.

@IamPete1
Copy link
Member

I have just tested this with, ArduPilot/ardupilot#13753 Works great, thanks @EosBandi

I think this issue can now be closed.

@IamPete1
Copy link
Member

IamPete1 commented Jul 18, 2020

Having finished messing with named floats I have discovered that it is impossible to remove it from the tuning graph. I had ticked it, now I just get 'customfield0' on the graph but no way to un-tick as its not in the list.

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

Successfully merging a pull request may close this issue.

4 participants