Eachine E010 ini Devo 7E

Glad you got it working Luis

Many thanks.

Thanks for this. I've just installed the 4-in-1 mod in my 7e and was looking for how to bind it.
I had problems getting it to bind at first until I changed the output from 30mw to 10mw, now it binds and fly's fine.
I love the screen layout as well, I've only had the tx a few weeks and didn't know you could change the screen layout so much. Thanks again

I got a devo 10 with 4-in-1. I can bind the e010 at full power. I'm wondering if it's just the 7e which cannot bind at full power.
I just read another thread and noticed some devo 10 users also could not bind at high power. This is really weird.

do you need the 5.0.0 version to bind to the E010?
currently running 4.0.1 with A7105, NRF24, and the CYRF ( and missing my laptop that had all the files and programs on it )

I had to install the latest version 5.0 (nightly build on 3/12/16) before the E010 would work.

wrong answer!
well, let me rephrase, probably the correct answer but its not what I wanted to hear!
Im skeered to update it. Can I keep all the modules already soldered in or do I need to change that as well?

You don't need to re-solder anything, but you'll need to update firmware. 4.0.1 is ancient, there were many protocols added and improvements made. Including an addition of Eachine E010.

Assume it is the same to install as I did with 4.0.1?

Yes it is.
You just need to update the firmware to v5.0.0. Anything else.

Devo 7e - v5.00
But I just can't find the E010 format option in the model setup.
Where should it be? If I click Bayang, I dont get any deeper in the menu.
Any hint please?

I went with the nightly build route. used the "fixed" file done by goebish www.deviationtx.com/forum/protocol-devel...a-captures?start=100

first try worked like a charm.

wahnfried wrote: Devo 7e - v5.00
But I just can't find the E010 format option in the model setup.
Where should it be? If I click Bayang, I dont get any deeper in the menu.
Any hint please?

Download and flash a new nightly build. The E010 didn't exist 4 months ago when 5.0 stable came out.

Wish I would have known that 2 days ago when all the sentence enhances we're flowing like water because it would'nt work!!!
All good now, awaiting the family to wake up so I can test it out!

Nightly Build did the trick, thanks guys!

YAY! Thanks. This works great.

Hello, great work. Thank you. But unfortunately now have a problem

I have also made the conversion and could also use the 3 in 1 -Multiprotocol module to control my Eachine E010 - 2 weeks. Til today.
I wanted to fly the E010 as usual. When you turn on the spark is automatically tied. The first 2 times the binding worked, but the copter lost the binding after 2 seconds. After that, not even the more. For example, the model.ini copy again on the Devo copied, but no more binding possible.
DMX models can be tied and fly. I also screwed the Devo to control the soldering points of the module, but everything okay. The E010 can be controlled with the original remote control.
I have no idea. Should the module have broken? How can I tell if the module still works? Would a defective module display the option MJXq with the format option E010 in the model setup of the Devo?

For the help I would be very grateful ...

Greeting Mischa

Maxner, did you check that your antenna is still attached to your 3 in 1?
I the past, when I've messed up installation of a module, as soon as you turn on the Devo (as long as the config file is properly configured) it states, "missing module xxxx" or something. But that might not catch a bad antenna.
Just the first thing that comes to my mind.

it could also be a power supply issue, the vreg that you use as a power source for adding modules was only specced to run the mcu, and when using protocols that require more current than others (like the e010) it slowly degrades the vreg by running it over it's rated limit and it either gets to a point where it can't supply enough for the hungry protocols but still works ok for those less demanding protocols, or it just gives up altogether. to test this issue turn the transmitting power of the protocol to 3mw amd see if it keeps the bind ok, if that works i'd suggest adding a separate 3.3vreg to power the 3in1

Thanks for your quick reply. Great. In fact, the problem with the power supply of the 3 in 1 module is. At 3mW the binding works and remains stable.
How can I ensure a permanently stable power supply to the module? Use a LiFe battery, a separate voltage regulator, or Vcc + at another point of the Devo connect?
How much mA does the 3in1 module need for stable operation? Could I use a Pololu Stepdown 3.3v, 300mA ?

Greeting Mischa