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

iNav - HD Zero - Stick Command Issues #116

Closed
MartinHugh opened this issue Apr 4, 2023 · 2 comments · Fixed by #161
Closed

iNav - HD Zero - Stick Command Issues #116

MartinHugh opened this issue Apr 4, 2023 · 2 comments · Fixed by #161

Comments

@MartinHugh
Copy link

MartinHugh commented Apr 4, 2023

A common stick command/gesture in iNav is to save settings after tuning things like auto level, auto tune, auto trim.
This is normally done after landing and disarming.
It is useful to see confirmation that this has happened on the iNav OSD after saving.
If the video is being recorded (which it usually is) this can be checked later if necessary too.

However. The same stick command/gesture used in INav to Save Settings, is now used by HDZero to set 0mW power.
This command works even if LP MODE and PIT MODE are OFF.

The result is that Save Settings in iNav simply records the video going to HDZero Rainbow display, rather than showing confirmation of iNav save. It probably does Save Settings too, but who knows.

A secondary issue (though not the point of the one being raised) is that trying to bring the vtx out of 0mW mode (sticks in and down) does not work under these circumstances. One has to cycle the power on the aircraft to get the video to come back).

This is all a bit of a mess.

Can we please allow 0mW to be put on a different stick gesture so that it does not conflict with iNav, or, allow it to be disabled.

@ligenxxxx
Copy link
Member

allow it to be disabled. is a good idea.

@ligenxxxx
Copy link
Member

At present, the stick command of FC and VTX cannot be truly avoided. I'm still thinking of other options.

@ligenxxxx ligenxxxx linked a pull request Sep 22, 2023 that will close this issue
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

Successfully merging a pull request may close this issue.

2 participants