Global Variables GV10 & GV11 problem
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- c
- Domain
- embedded-iot
Research direction
Start by tracing how global variables GV10 and above are read by mixer sources in both transmitter firmware and Companion, then compare that path with GV3. Reproduce the report with the described TX16S Mk3 setup on version 2.12.4 and inspect the mixer monitor while adjusting T2. Done means the displayed mixer percentage responds to GV10/GV11 changes under the stated logical switch conditions, or the restriction causing the behavior is identified.
Written by the indexing model from the issue text.
Description
Is there an existing issue for this problem?
- I have searched the existing issues
What part of EdgeTX is the focus of this bug?
Transmitter firmware
Current Behavior
Using RadioMaster Tx16S Mk3 updated to v2.12.4.
Application is F5J glider with motor power controlled by 3-posn switch SE. The desire is to allow in-flight adjustment of elevator for both of the motor power settings.
Problem occurs with Global variables - Mk3 now has 16 GVs and appears to related to GV10 and above.
Programming
- Logical switches are used to detect FM1 (power) AND SE position. Works ok
- Special functions used to Adjust GV10/11 via Throttle Trim T2 - Values in GV increases/decreases as expected.
- Mixers - Source GV10, Weight MAX, Offset 0, Switch LS (above), Curve Diff
- Mixer line turns green when conditions for LS are met - Works ok
Expected Behavior
Looking at mixers with mixer monitors on, I expected the % value to increase/decrease when T2 is indexed, Sometimes there is a % value but this does not change, even though I know the GV value is changing (via pop-up)
If I switch the GV from GV10 or 11 to, say GV3 it works ok.
My conclusion is that GV10 and above have different restrictions, or there is a bug.
I get the same behaviour on Companion.
Steps To Reproduce
See above
Version
2.12.4
Transmitter
RadioMaster TX16S MK3
Operating System (OS)
Windows
OS Version
No response
Anything else?
No response
- Dominant language
- C
- Stars
- 2.4k
- Forks
- 614
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 68
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from EdgeTX/edgetx
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug 🪲 triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
EdgeTX/edgetx#7412 · 2 comments ·
Maintainers usually reply within 1 day
-
bug 🪲 triage
Difficulty 2/5 Under an hour Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
bug 🪲 triage
Difficulty 3/5 1-2 days Newbie friendliness 52/100
Maintainers usually reply within 1 day
-
bug 🪲 triage
Difficulty 3/5 1-2 days Newbie friendliness 50/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
FujiNetWIFI/fujinet-firmware#2261 ·
Maintainers usually reply within 1 day
-
area/infrared type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
DarkFlippers/unleashed-firmware#1201 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
pocoproject/poco#5626 ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
VMAFx/vmafx#3260 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
FujiNetWIFI/fujinet-lib#272 ·
Maintainers usually reply within 1 day