Advanced Search

Do not use Dfuse 3.0.5, you can damage transmitter bootloader, it's demo version Dfuse, not Walkera Dfuse.

Try write to transmitter USB drive "devo.fs" file from firmware archive.

To use 4in1 module you will need to edit "hardware.ini" file inside ""devo.fs" file. It's not trivial task, search the forum for help.

After I tried again it turned out that it was really just a problem with the driver.
devo I succeeded in Dfuse. then I flash with firmware v.5.0.0-ac7f63e using the Dfuse 2.31 upgrade tool & found a problem. the monitor screen is just written "Deviation USB".
I was curious to try to flash again with the dfuse 3.0.5 upgrade tool. "Upgrade Program" without having to restore the button.

what should I do to move to a normal position.
Please help

Most likely it's problem with driver. Windows version? Do you use Dfuse USB Upgrade Tools v2.31? Do you try different USB cable?

Probably will be better for Devo F12E use Deviation Uploader.

www.deviationtx.com/manuals/html-devo10-en/ch_install.html

Also, match more reliable and convenient to use will be Devo F12E with flash memory mod:
www.deviationtx.com/forum/builds/6861-ul...-devof12e-xms-builds

I tried flashing the firmware with nightly build. but I have trouble connecting my devo F12E with the compiler. usb like not detected.
is there a way from the beginning to try to reinstall the firmware to be able to use the 4in1 module.

thank you very much for the answer.

You can use any Deviation nightly build. Devo F12E supported with nightly builds only.

Hello, what version of firmware is suitable for this 4in1 module. I have followed these instructions but I tried to bind eachine E011.
My devo F12E hardware is V 1.0 & Firmware V 1.3A

The f12e is supported now I have a black and white on deviation with memory upgrade. Just read the forum
www.deviationtx.com/forum/builds/6861-ul...-devof12e-xms-builds

And I use this
www.deviationtx.com/forum/builds/6407-de...-protocols?start=480

So far no problems for what I use it for. It is going to take some reading!!

For me it was fun or is fun.

So I bought a Devention F12E about half a year ago and I really like it.
It is the transmitter I always wanted (well almost, but its as close as commercial transmitters go).
However Walkera receivers are quite hard to get here in germany (they all ship from china) and getting one thats not just SBUS/PPM seems pretty much impossible.
Because of this I checked out Deviation (I already have a lot of DSM2 receivers as I used Spektrum before).
However I get quite a mixed feeling. All the official documentation says the F12E is not really supported.

So what is not supported on the F12E ?
What could happen worst case ?
I assume Deviation does not touch the bootloader, so I could flash back a stock firmware at any time right ?
If there is still important stuff missing for F12E (or generic), I would happily help implementing it (I work as a software engineer in C/C++).
Also is there a reason releases stopped with version 5 almost 4 years ago, despite development going on ?

Sincerely,
Thalhammer

Thank you for your answer i am glad that that you are here for so a long time. But i am not a DAU I know about the ACCES and ACCST

I have tried yesterday again.

R-XSR and XM+ i have used the 2.01 version downloaded on frsky page. I have controlled wether if have take a wrong version - but there was no mistake to find

I have flashed R-XSR 1.9 firmware and with this i was able to bind - similar to the XM+ there is a 1.7 firmware to find on the frsky page - also bindig possible

But with the 2.0X ACCST firmware i am not able to bind - testet twice i have tried FCC and LBT version.

Some weeks ago i want to bind my DEVO10 with an frsky R-XSR reciever on an QUAD it was not possible also - but i don't know with firmware there was flashed.

I have ordered 2 new XM reciever by banggood - they need in the moment a long time to deliver - but i think they come with the new firmware and i am not able to bind

Ok i have checked the frsky page again - there is an older version for the XM also

And i have read again the text on the frsky page. You have to update the Transmitter and the reciever .. and there is a small comment to read "some of the X9D may have compatibity issus - we do not recommend users to update"

Maybe there is a hint for all "open-source" users in future to use frsky recievers. Cause they are not glad that we not buying the frsky Transmitter.

Thank you Vlad_vy for your great assist in supporting F12E.

Hello,

I have flashed 2 frsky recievers with the newest firmware and now i am not able to bind.
I have tried all what i know - i have installed the latested file on my F12E

With non updatet receivers i have no problem with binding.

Yes, I did that according to my setup:
enable-a7105 = A13
has_pa-a7105 = 1
enable-cc2500 = A14
has_pa-cc2500 = 1
enable-nrf24l01 = A2
has_pa-nrf24l01 = 1

In fact I was a little misled by the manual which reads:
2.3. Upgrading the file system via USB
On the Devo F7 and F12E, do not enable USB mode, as the file system cannot be accessed from the desktop, and you need to use the ‘File Manager’ tab on the ‘Deviation Uploader’ to manage files. If you enable it, all you can do is format the drive, which will destroy your installation.

For one, in fact the USB access can be used for F7 (non XMS), but only one file should be there: devo.fs (which contains files in special format)
and for F7-XMS we can actually use the USB access


If I understand well, by selecting a protocol in a model that automatically select the appropriate module of 4-in-1

1. F7-XMS firmware is for devo F7 with upgraded flash memory chip.

2. The system will work with the stock memory chip. But, XMS version has much more stable transmitter filesystem and you will have direct access to filesystem on USB drive.

Supported flash memory chips:
www.deviationtx.com/forum/builds/6861-ul...e-xms-builds?start=0

I did not try it with my deviated F12E.

However, you should be able to reproduce all of the outputs as the devention F12E does.

If you need switch assignments, channel orders and values I will try to help.

I`ll get a crashed Voyager these days.
Do you know if it is possible to use it with a deviated F12E-XMS

Reference nightly build Deviation v5.x.x with latest protocols. Based on "8 Nov 2018" nightly build, before any massive changes, with protocols mostly updated to current state.

* Change SPI speed from 2.25MHz to 4.5MHz
* Fix "HAS_4IN1_FLASH" SPI speed
* Fix A7105 hanging
* Fix Radiolink SPI speed
* Fix Radiolink A7105 hanging

29.10.2019
=========================================
Part 1 (first 10 files)

I can't attach more than 10 files, and so XMS builds attached with separate message

(29.10.2019)

I have a problem with the LED backlight.
can anyone help find a solution?
would be very appreciated for the advice given ... thanks.

Anyone know the type of LCD DEVO F12E.

My plan is to change my devo f12e if there is a match. because it's broken in the unregulated power regulator.
my plan will change with openTx using AVRC like RC Group posts.

Edit: Before reading the whole post: sorted it, a look into the Voyager 3 manual for connecting with an F12E showed the complete setup for a non-deviated TX (still have one lying around) It's alive! However the GCS problem persists.

---

Hi everyone!

Does anybody know how to set up a deviated F12E (CE Version?, if something like this does exist) for a Walkera Voyager 3? (the voyager receiver/flight control unit is a FCC Version).

Background story:
I got a voyager 3 for "an apple and an egg", the previous owner did not get it to work/connect to the transmitter (only a Walkera BT2401 GCS), no Transmitter (should usually have been a Devo F12E) was included.
The flight control unit (including receiver?) of the voyager 3 is an RC-701 (FCC) board.
The aircraft came with an GCS BT-2401 unit but when switched on, all but the Bluetooth LEDs light up and no bluetooth device is found on several android devices.
Connecting the GCS to a Win10 PC and installed "Dfuse SUB Upgrade Tools 3.0.5" does nothing, no "USB Device found" sound, no new device in device manager, but the charging light of the GCS lights up.
The voyager itself was not connected to a PC via USB for now by me.
When the battery is inserted into the voyager and switched on, the flight controller and a smaller device near to it (no clue what it is) show some lights.
Nothing else happens.

Is this whole voyger a case for the bin or is there any chance to revive it?
Any advice is welcome!

Best regards
Max

vlad_vy wrote: Can you desolder and check Schottky Rectifier SS14? Is it good? If so, solder it back.

Is there another solution to fix my F12E by making a separate power regulator without the existing power regulator on the board.
if there is, please info & help me