Advanced Search

It's rainy all week so I'm not sure when I go out flying again.

I agree that's the most concerning, but I can't attribute it directly to a problem I've fixed. The code is definitely better now and it does not use the change that was in 7d14d15.

I can replicate the issue with the parameters not changing if there was a long delay before clearing the throttle warning. Won't have time to look at it until later today.

I'm worried most about the fail-saves I had on the 7d14d15. Is that issue under control now?

I know this thread is super old but hoping someone can help me! I recently purchased a spare DEVO10 White and it has the Deviation Firmware on it. I really would like to restore it to the factory firmware. Many of the links I come across are old and or broken. Can anyone direct me to the what exactly I need to get this radio back to Devention Firmware? I am fairly certain I have the Dfuse software on an old laptop but the library file eludes me. Any and all help would be appreciated! Absolutely love these radios for my planes and really don't want to go through the learning curve to program a model with Deviation.

Big Thank yous in advance!!!!

Super! Things seem to work better now. I installed a master build of today on TX too and 88d5ea7 on T8 and switched to the ELRS protocol.

The throttle high issue now only persists when keeping it high for a longer time, let's say 20 seconds. The menu now does show but values are incorrect and can change nothing. RX led blinking slow. BAD/GOOD shows 0/500 while packet rate is set lower, 250/150/50.

I don't mind but that happened today. Didn't take long to see the same issues you have described. Test build available - 88d5ea7 .

Trying to detect an ELRS module and then switching baudrates causes issues, especially when startup is delayed by the throttle warning. Also found a mistake in the previous test where I tried to fix the baudrate to 1.87Mbps. I decided to remove the baudrate switching. I created an ELRS protocol which is the same as CRSF except it runs at 1.87Mbps. After installing the test build, go into the model and change the protocol from CRSF to ELRS. Then power off and on the T8. This fixes the issue of turning on power with throttle not zero.

I turned on Dynamic Power and set the max to 250mW (highest it would go). But the telemetry said the power was 10mW the whole time. Don't know if that's a related issue or something else.

On the TX I'm running a build from master, and 2.2.0 on the RX. I only saw the issue of the Packet Rate setting jumping from 500 to 250 one time, immediately after installing the module.

Thanks! I will get this added to the repo.

I haven't worked with the fonts so don't have answers to your questions. This thread has some discussion about using a smaller font in the UI.

Do you mind when I wait with testing for you to receive your HM TX and see what's going on yourself?

What is the link telemetry showing when the power goes to 1W? That might give some clues. The bad/good numbers refer to the packets going from the T8 to the TX. If serial errors occur they will be on the data from TX to T8 so won't affect the bad/good number.

I bought the HappyModel TX with an EP1 receiver.

If the RX is connected and close by I would expect the power to be low. So as it seems the connection is at 50Hz is poor but not poor enough to make ELRS decide the connection is lost. Why good/bad is still 0/50 seems strange to me.

May I ask which 2.4GHz module you bought?

I'm a little surprised 82c3a77 doesn't behave the same as 6659b95 at 50Hz because the code is nearly identical. Nearly but not exactly. The f848942 change should be the one that fixes receiving multiple messages at once.

Is the increase to 1W not expected? If the RX is connected and close by I would expect the power to be low.

The 2.4G module I ordered should arrive today. I want to try a few things before putting out another test build.

Hi there!
Maybe someone will be interested in Polish translation for Devo 10.
Most things was checked, translated and works fine. For sure there will be something to fix to make it better but at all works great
Q1: Is there option to add polish characters to standard font? or add another font with that addional letters so all could be 100% local? I didn't use polish characters (ąęćżółźśżń) so all works but if it possible I want to add them later.
Q2: Can I change menu text to some smaller font to make longer texts apear at avaliable space? - some texts are too long so I have to short them somehow I tried to change stock font to smmaller one (works) but first letters disappear somehow so i leave all stock for now.

We will help you promote your site, backlinks for the site are here inexpensive www.links-for.site

We will help you promote your site, backlinks for the site are here inexpensive <a href=http://links-for.site> www.links-for.site </a>

On 6659b95 booting at 50Hz shows 0/50 when the menu builds up but often the menu doesn't build up. A connection with RX is not established. After going to 150Hz the connection with RX comes up and 50Hz can be selected and works. When leaving RX on and booting TX at 50Hz the connection stays. Good/bad is 0/50 when the menu builds up but often the menu doesn't build up. In Betaflight configurator the RX values jump of and on continuously while the RX led is solid green.
The 82c3a77 and f848942 do not have this issue but here the power is increased to 1W. I have dynamic power turned on.

Have a good weekend!

All three of the builds listed start at 400K and switch to 1.8M when the module is detected to be ELRS. Same code in all of them in that area.

From the bad/good it looks like the serial data transfer is working well.

On the safety warning issue I'll have to think about something to try. Build 82c3a77 has the same serial errors as 6659b95, so that can't be it. If my 2.4 module order goes through it will help. I'm out for the weekend so maybe inspiration will strike. We can resume next week.

These builds are 400Kbaud or 1.8Mbaud?

Simple test report. I tried to add borders to the table for clarity but didn't succeed.

---

Build#|	Throttle high on boot|	BAD/GOOD|	Remarks
6659b95	OK	0/501	Flies nice
82c3a77	FAIL	0/501	-
f848942	FAIL	0/501	-

---

Build f848942 is also available in the test build page. This has some additional complexity to eliminate the retries.