Devo F12E

Hi Folks,

I'm new here, yesterday I've received a set of Devo F12E and 4F

Sofwarechange to deviation 4.0.1 onto F12E was sucessfull and I've tried with one DSM2 and it's working fine.

Have someone tips to help me for addon some modules for e.g. Hubsan and WLToys? Can it workes with the multimodule?

Regards,

Micha

The code for the multimodule is in the build, so it should work.

You can check the "supported models" link on the left, and that opens a spreadsheet showing you which models use which protocols and which RF module they need.

The short summary is that the A7105 module is used for older models/protocols, the NRF24L01 for newer models/protocols, and the CC2500 for SkyArtec and FrSky.

E.g. WLToys uses both, with random changes between models (thus living down to the Toys part of their name). The Hubsan protocol used by all their craft and the Estes Proto X all use the A7105.

many thanks for these, so I'll order these and buildupt the module.

I've looked before if my models are supported from deviation. I found all exept the eachine models from banggod or sth.

in the moment i have some setup issues for may DSM2 models. I can't setup some switches on AUX 2, 3 and 4

Some of the eachines use the CG023 protocol. You'll have to add an NRF24L01 to get it, and you may need to upgrade to the nightly build.

a few days gone and I tried to add a A7105-SY module as mentioned on https://bitbucket.org/PhracturedBlue/deviation/wiki/Devo8ModuleInstall
and https://bitbucket.org/PhracturedBlue/deviation/wiki/ModuleList

I looked for the specific pin's but it wouldn't work, some idea how to find my mistake?

In moment i've using deviation-devof12e-v4.0.1-9cce188

thanks

micha

Have you got any photos of exactly what you did? Close up views of the connectors would be helpful. Also, what, if any, error messages did you get?

this are my wiring.

I've got not error messages, it wouldn't bind
added as link wiring

I know what the wiring should be, but what we need to see is what your actual as-built wiring looks like. Sometimes we can see something you may have missed, and at the very least we may be able to rule out a cabling issue.

Assuming then that your cabling is not an issue, then did you enable the module in hardware.ini? If the module is not enabled or it is not recognized by Deviation, you will see an asterisk in front of the protocol name in the Model setup (e.g. *Flysky).

Deal57 wrote: ...
Assuming then that your cabling is not an issue, then did you enable the module in hardware.ini? If the module is not enabled or it is not recognized by Deviation, you will see an asterisk in front of the protocol name in the Model setup (e.g. *Flysky).

i think this is the point, i have the java updater 0.8.0 on windows 10 64bit

just when put the devo in the softwareupdate i can flash the zipfile -> how can i do this to flash the zipfile unpacked to the unit?

The Java uploader allows you to click on the file manager tab and double click the Hardware.ini file. This should let you see exactly how the hardware is configured. To enable the A7105, you need to remove the semicolon (";") from the first position of the lines that look like:
If the semicolons are still there, you need to remove them. This should allow you to see the A7105 protocols (Hubsan, Flysky, etc.).

I'm not an expert on the uploader... this is just the second time I have used it, so maybe someone with more experience editing the files on an F12E could help out.
Let us know how it goes.

hey,

after few tries it worked fine. Many thanks for these hint to solve my problems, the bees from hubsan and estes now are fliing with my devo

one little thing is the uploader on windows 10 64bit. I can't access any files so i have to make a complete flash an loosing all data on it

now i can use dsm2 and hubsan protocols

thanks for all in these case

micha