Jumper T15 - 2.11.1 - used on two models (F3K) / DLG and had on both models RC outage short after launch.
Is there an existing issue for this problem?
- [x] I have searched the existing issues
What part of EdgeTX is the focus of this bug?
Transmitter firmware
Current Behavior
I flew two models yesterday and today and had similar loss of RC shortly after DLG launch, I was suspecting a bad power connection of first model, but today the same happened on other model. Bench tests have been ok and reliable, but after letting the start button go (TPL) the model became unresponsive and did crash.
I reverted to 2.10.6 as I never had problems this on this version and it was always reliable.
Radio : Jumper T15 RX userd: Diversity RX with matek crsf-pwm-10
I attached the model config. I can't explain otherwise than transmitter problem.
Expected Behavior
Reliable operation , no freezes of RC controls.
Steps To Reproduce
I couldnt't as it randomly happened. I'll not try to reproduce as I don't want to crash another model.
Version
2.11.1
Transmitter
Jumper T15
Operating System (OS)
No response
OS Version
No response
Anything else?
Why exactly are you posting this, if by your own admission, you will not work on that ? Why should unpaid volunteers work on your issue when you don't ?
Without involvement from your part, your issue cannot be worked on anyway. You say it doesn't happen on bench, only at distance, which rules out EdgeTX (ETX does NOT deal with RF), yet you said downgrade stop it from happening, which would mean Etx. Non conclusive.
Unless you work and manage to reproduce it on a bench so we have a chance to understand what is happening, there is nothing we can do to help. And if it really cannot be reproduced on the bench, then it is not Etx
In other words, if you are unwilling to grab a second (micro)SD card, and run that with 2.11.1 (i.e. have 2.10.x config and firmware on one SD card, and have 2.11.x firmware and config on the second, and use the bootloader to switch firmware after swapping the SD cards) and do more tests to find out how to reproduce this, this is unlikely this is going to get resolved with a report like this. Unless, of course, someone else has a similar issue or we are (un)lucky to experience this ourselves. Until then, we need your help to work out how to reproduce, diagnose and ultimately, resolve this.
I honestly do understand that you don't want to crash another model, and aren't suggesting you fly with that setup until you know exactly what the fault is / until it is resolved, but there are other tests that you could still do I'm sure ;)
@3djc - EdgeTX requests any issues being found to be reported - so I did this. Please don't blame me for that and stay objective. I know that it's hard to be fixed if it can't be replicated.
Having looked at the configuration changes between the versions while converting back to 2.10.6 I saw that global variables settings are stored differently. Likely this is an area that could cause the problem.
If I remember correctly, I also had issues using global variables in the mixer after upgrading. I'll try to reproduce and create a different report, likely I'll try to replicate on a different, not the main radio.
Also INAV widget screen is not showing up on 2.11.1 - I 'll create a different report for this. Replication is easy - do upgrade and screen does not show up.
@pfeerick - Unfortunately, the T15 does not have a swappable SD card but just built in memory that is not the quickest which makes going back and forth a time consuming and not straight forward activity.
I'll try to find time to reproduce or provide more information.
The iNav widget is part of iNav and not this project. That's probably the place to report bugs.
I never considered backing up models and settings, writing firmware and restoring models and settings time consuming or not straight forward. Beyond that you have one or two folders to copy, probably just SCRIPTS.
If you're going to create additional reports then closing this one would be helpful.
Unfortunately, the T15 does not have a swappable SD card ...
I'll try to find time to reproduce or provide more information.
Yeah, with radios that have onboard XTSD storage, you can instead copy old MODELS and RADIO folders to another name (I.e. maybe append version number to the name) and manually rename those before swapping the firmware - is a bit of a shortcut as it's not as clean as having two entirely separate/self-contained copies of everything, and will require a computer in order to rename the folders over when swapping firmware versions.
And thanks, that's all we want, some more investigation to see if you can narrow it down / determine how to reproduce it.
And more topical reports/issues are good... better chance of getting them closed in a single PR. ;)
You are using a Matek CRSF-PWM adapter, these are unstable if they do not have the latest FW, and can lock up during flight and result in a crash, this is common knowledge, and has also happened to me, but with the latest version FW they are completely stable!