-
-
Notifications
You must be signed in to change notification settings - Fork 347
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
Cannot change to a different model 2.7.0 T-Pro ELRS #1898
Comments
@pfeerick this bug does not seem to have any attention. Does the team need anything more? |
1 similar comment
@pfeerick this bug does not seem to have any attention. Does the team need anything more? |
Have you tried updating to 2.7.1, or a nightly build to see if it has been resolved? |
I tried the latest nightly build today and the problem is still present. |
Thx for trying. We will need your settings/models to be able to reproduce. |
In other words, can you zip up a copy of the |
@raphaelcoeffic @pfeerick I have attached the |
1 similar comment
@raphaelcoeffic @pfeerick I have attached the |
Thanks for the reminder 😮 🙏 Right, so I'm juggling a few things atm, and am still puzzled as to why the semver version field is zero instead of 2.7.0, 2.8.0 etc, but that should be a cosmetic issue. What is a problem is not that it won't change models... but after doing the first model switch (as I was able to switch models exactly one time with that file set on the radio) ... it would show the loading screen as you mention, freeze, and it would trigger an emergency mode reboot... as signified by a ! shown at the top right of the screen. What seems to be the cuplrit is that the trainer mode for all of the models is set to |
@pfeerick Thank you for checking into this. I use Master/SBUS trainer mode all the time because I only fly with my son who is still training. So, I will have to stick with the original firmware that came with my T-Pro ELRS. Please let me know when a fix is available so I can update to newer firmware. |
Hm... so how do you use SBUS with the T-Pro? 👀 |
I want to be clear, I have verified I was able to change my receiver (which is connected to the JR module connector) to PPM and switch the T-Pro trainer mode to I know the ELRS team will not support SBUS or PPM for receivers, which is why I created this enhancement request for trainer mode. ##1607 If enhancement request ##1607 CANNOT be supported, then it is important for the T-Pro and other radios to support Since the original firmware that came with the T-Pro ELRS worked with If enhancement request ##1607 CAN be supported and the EDGE team does not want to support SBUS on the T-Pro, then please replace I appreciate your help! |
I made a video to better explain my writing above. |
Yes, that video clearly explains what you are after, thanks! :) I was more interested in the how it was connected, as I wasn't aware of any documentation on SBUS being a supported function on that transmitter. I noticed it doesn't crash if you re-enable Master/SBUS afterwards, so does it actually work then? i.e. It only crashes when changing models, but otherwise functions? Just means we are getting closer to identifying exactly where it is going wrong. re: CRSF trainer input, did you give the PR that was linked to that issue a try to see if the works? #1462 It will need some re-work as it needs to fit in with the changes to the serial model, but I did have CRSF student input working on a TX16S via the module bay. |
I tried to use trainer mode When using the original T-Pro ELRS firmware,
With regard to testing a PR, I assume you mean to compile the PR for use? If so, I am not savvy enough to compile. |
AFAIK, nothing was changed in the SBUS code. Note likely it is some clash/incompatability with the lower level serial driver rewrite and the tpro configuration - which wouldn't have been picked as SBUS isn't exactly plug and play on that radio ;) I'm on phone atm, but will link the guide for self-compile... It's pretty easy now :) |
Fixes #1898 De-initialising the external module while SBUS trainer is used on external module RX leads to the following sequence: - `extmoduleStop()` is called, thus shutting down the timer DMA - on certain targets, the timer DMA stream is the same as the external module RX DMA stream - when this DMA stream is used by the SBUS trainer input, this leads to DMAFifo to return random bytes continuously - thus driving `processSbusInput()` into an endless loop, which is run in the mixer task - as the mixer task has the highest priority, it runs forever - after some time the watchdog timer expires, and causes a reboot
* fix: prevent generic module de-init if protocol is NONE Fixes #1898 De-initialising the external module while SBUS trainer is used on external module RX leads to the following sequence: - `extmoduleStop()` is called, thus shutting down the timer DMA - on certain targets, the timer DMA stream is the same as the external module RX DMA stream - when this DMA stream is used by the SBUS trainer input, this leads to DMAFifo to return random bytes continuously - thus driving `processSbusInput()` into an endless loop, which is run in the mixer task - as the mixer task has the highest priority, it runs forever - after some time the watchdog timer expires, and causes a reboot * DMAFifo: check if the stream is enabled This provides some hardening to avoid the conditions described in previous commit.
@sk8board Would you mind checking everything is working ok now? You can either use the next nightly, or 2.8.0-RC3 which is likely to come out later today. |
* fix: prevent generic module de-init if protocol is NONE Fixes #1898 De-initialising the external module while SBUS trainer is used on external module RX leads to the following sequence: - `extmoduleStop()` is called, thus shutting down the timer DMA - on certain targets, the timer DMA stream is the same as the external module RX DMA stream - when this DMA stream is used by the SBUS trainer input, this leads to DMAFifo to return random bytes continuously - thus driving `processSbusInput()` into an endless loop, which is run in the mixer task - as the mixer task has the highest priority, it runs forever - after some time the watchdog timer expires, and causes a reboot * DMAFifo: check if the stream is enabled This provides some hardening to avoid the conditions described in previous commit.
@pfeerick I have tested 2.8.0-rc3 and verified this problem is fixed. Thank you to all who solved this problem. |
Fantastic! Thanks for checking it so quickly :) |
Is there an existing issue for this problem?
What part of EdgeTX is the focus of this bug?
Transmitter firmware
Current Behavior
After updating the T-Pro ELRS to EdgeTX 2.7.0, I cannot change to a different model. When I select a different model, there is a pop-up screen that states, "Loading model...", then the screen returns to the original model.
When creating a new model, I get the same result.
If I down-grade to the firmware that came with the T-Pro, the problem is not present.
I also have a T-Pro 4in1, which does not have this problem when upgrading to EdgeTX 2.7.0.
The problem is only present on the ELRS version of the T-Pro.
Expected Behavior
When selecting a new or different model, I expect to change to the model I selected.
Steps To Reproduce
Version
2.7.0
Transmitter
Jumper T-Pro
Anything else?
No response
The text was updated successfully, but these errors were encountered: