DEVO10 button issue and repair !

Hi,

I've a problem on my DEVO10. the "DN" down button work not like the other, sometimes works well, sometimes not. It arrives that with 1 press, the selection jump one line.
can someone help me ?
If it's hardware issue, what sort of switch is it and where can i buy it ?



Thank you

What exact firmware version are you on so others might be able to replicate?

I'm running under nightly build : deviation-devo10-v5.0.0-dd199b1

Thank you

In some menus, this button does not work nearly

I have the same issues with mine,I believe there are a lot of bugs with 5.0 and devo 10 including range issues with some protocols.Before the update I had great range with the 2x2 protocol now it has diminished dramatically.The gurus are the best at ironing out the kinks as long as they are aware of the problem.5.0 is still relatively new and I believe all this will eventually run smooth.

I'm agree with you, i've bought an FRSKY XSR and have dropouts, i've bougth an D4R-II and i have range issue with it. It's maybe the RSSI signal that not efficient but at 300m i'm under 45db, My DEVO beep .. hope all these things will be resolved soon.

" I know many people do a great job and work hard to improve this, and I thank them. "

there was a huge gui rewrite (to enable the firmware to work with the at9 which has less input buttons) which caused most of these double bounce button press issues, and a lot of them were already fixed, but obviously there are a few more lurking about. but until the bugtracker is back up and the devs have some free time to look into them there isn't much can be done, unless that is you know C, and can fix the code and submit a pull request, which is beyond my skill levels for sure

So i'm an isolated case, but i can think that probably come from the firmware.
it is really very annoying
If i post a datalog, can you confirm that ?

Because if i need to replace the button, i can do it instead waiting and finally realize that is an hardware problem.

Thank you HappyHarry.

So, why do you run the 5.0-nightly-build dd199b1 if you are not a developer yourself?

If you go back to release 5.0 there won't be IMHO the AT9 GUI rewrites in, so not these bugs?!?

Thomas

Thomas.Heiss wrote: So, why do you run the 5.0-nightly-build dd199b1 if you are not a developer yourself?

You are right, but i for binding my XSR i have to install the nighlty !

Thomas.Heiss wrote: If you go back to release 5.0 there won't be IMHO the AT9 GUI rewrites in, so not these bugs?!?
Thomas

Before, with the standard "stable" V5.0 I already had this problem.

So it's maybe a hardware problem !

XSR = FrSkyX?
Oh, it is not included yet in 5.0 or any sub 5.0.x and still under on-going protocol development (aka trunk/default/master)?

Didn't the developers have plans to backport multi-protocols to one "stable release" builds, 5.0 in your case, too?
I remember I read that once...

It looks to me somehow weird that you have to switch to a true-developer non-100% testing nightly-build release including GUI rewrites just to use some of the later protocols.

Sorry I do not use 5.0 yet.

I can assure you that this release devo10-v4.0.1-fcd0669, I am using myself (well tested on DSMx + telemetry) works 100%.
Would be enough for your testing.

If your problem is gone with fcd0669, then the GUI bug is in release 5.0 + nightly-builds.
If not, it is your hardware button.

Thomas

Yup, XSR is FrSkyX. Some of the X series receivers will also do FrSky (aka FrSky D), but I don't think the XSR is one of them.

And yeah, we're supposed to have interim releases with bug fixes and new protocols. So far, only two protocols have been added to the nightly build, FrSkyX and MT99XX. Neither have been added to the manual yet, so they aren't ready for a release. Further, the FrSkyX changes include changes to the FrSky protocol telemetry (they use the same data format), and seem to be causing issues with it. Given the popularity of FrSky - even with the limited telemetry it has in 5.0.0 - breaking it in a release really isn't acceptable. So we don't have any new protocols ready for a point release yet.

FWIW, I haven't had any issues with the buttons on my 10 on 5.0.0. It wouldn't surprise me if the GUI rewrite broke things. I'd say test with 5.0.0 or the release Thomas suggested, and if you don't see the problem there open an issue on the bug tracker when it starts working again.

Ok, mwm, i've just done the clean downgrade to standard release. I erase all files after backup and put the files in the .zip

I have the multimodule with only CC2500, so i modify the hardware.ini
www.banggood.com/CC2500-PA-LNA-Romote-Wi...F24L01-p-922595.html

i'll try and tell if it's the same.

sfersystem wrote:

Thomas.Heiss wrote: If you go back to release 5.0 there won't be IMHO the AT9 GUI rewrites in, so not these bugs?!?
Thomas

Before, with the standard "stable" V5.0 I already had this problem.
So it's maybe a hardware problem !

Hmm, didn't you say you already tested normal V5.0 release?
But I suggest to redo testing and then jump to my nightly-build version if the problem persists.

What deletion are you talking about?
For Devo10 there is just the DFU - no protocol files.
The bug for sure is not in the model.ini, template.ini or hardware.ini.
How could it be in tx.ini? You do not have to calibrate buttons?!?

Thomas.Heiss wrote: Hmm, didn't you say you already tested normal V5.0 release?

Yes (see the video below)

Thomas.Heiss wrote: But I suggest to redo testing and then jump to my nightly-build version if the problem persists.

Where to find it ?

Thomas.Heiss wrote: What deletion are you talking about?
For Devo10 there is just the DFU - no protocol files.

All the file under my DEVO folder, and replace with the clean ones

Thomas.Heiss wrote: The bug for sure is not in the model.ini, template.ini or hardware.ini.
How could it be in tx.ini? You do not have to calibrate buttons?!?

Thank you for help

Here it is devo10-fcd0669: www.deviationtx.com/forum/builds/6306-ni...v4-0-1-fcd0669#53115

I had a similar issue with my devo 10. I solved it by opening up the button and cleaning it. You need to open the transmitter, unscrew that circuit board, then you can pop the sheet metal off the button and clean it. Reassemble and give it a try. It worked for me.

-Topher

Thanks guy,

Since I have already changed several times firmware without success program, I opened the DEVO and cleaned the button






It seems to work for now, i wait a while to confirm

Now I have the same thing with the left (EXT) side button "down" on the Devo10

A little bit of rain is hurting it, isn't it?

The board is labeled Walkera WK-2410-EXT 2009.06.23.

Maybe the rain could hurt the TX, but mine never saw a drop of water.
i think the contactor are in fault