Advanced Search

This was my fault - I had a bad merge that picked up some experimental FrSky telemetry changes. I have backed those out and pushed the results to the default branch.

Unfortunately, I had also merged in some protocol changes from goebish earlier this evening. Those also added enough bytes to break the 7E build, so they got backed out as well , just adding to the mess in the repository.

But what I just pushed to the team repository now builds on the 7e with gcc-arm-embedded-4_9-2015q2-20150609.

Looks like now that the devo.fs is available you do not need to use this method I put together using the Java loader.

Do the following 8 steps only:
1. Install the DFUSE upload utility and run it
2. Download the latest firmware build for F12E.
3. Put the device in DFU mode.
4. Select the firmware version of deviation-devof12e-v....and then Click upgrade.
5. Power off the device, then turn it back on.
6. It should come up with devo.fs on a windows drive.
7. Copy over the devo.fs onto the USB drive over the existing devo.fs file (I had to delete and then copy over).
8. Then power cycle again and it boots!

This is much easier now that they have the devo.fs filesystem built into it.

IGNORE the old method below... kept around for posterity.

DISCLAIMER:
First let me say, I am new here (first drone arrived last week) and it took me a while (39 minutes to be exact) to figure out how to load the F12E with Deviation. This guide will not have every variable or option for upgrading your F12E. This is how I got my F12E to load. I am using Windows 7 (32-bit) with the latest patches and updates. I have not tried any other OSes so please do not ask me about it. Although, that is a great opportunity for you to try and figure it out and contribute to the community by responding with a post saying "Hey, the version of Windows <insert version here> works when you <insert your changes here>." Also you do any of this at your own risk!

DOWNLOAD PHASE:
First Download the following files from www.deviationtx.com to an easy to find folder. I use C:\temp (Yes I created this folder)
1. DFU USBDrv Installer-1.1.zip
2. DeviationUpload-0.8.0.jar
3. deviation-devof12e-v4.0.1-667678f.zip (I am using this one, but you are free to try others)
4. Download and install Java from www.java.com (Please dont install all their free spyware/nagware crap, like McAfee or Chrome, or have them change your homepage.)
5. Locate your Java.exe file (Mine was in "C:\Program Files\Java\jre1.8.0_73\bin\java.exe" but yours might be different) you may need this later if prompted for running DeviationUpload-0.8.0.jar

CONFIGURATION PHASE:
Now that you have the files downloaded begin the configuration phase.
1. Extract the DFU USBDrv Installer 1.1.zip file
2. Open the extracted folder
3. Run the file DFU USBDrv Installer-1.1.exe (Say yes to the run prompt if you have Windows 7 like I do)
4. Install the Deviation USB driver (currently the first option)
5. After the installation is complete, close out.
6. VERY IMPORTANT to reboot your computer here! (I did not reboot the first time and I had many problems with the Deviation Uploader File Manager once it was formatted.

LOADING PHASE
Now that you have downloaded everything and configured your system begin the Loading Phase.
1. Find the DeviationUpload-0.8.0.jar file and double-click it (or you can right-click and say open).
2. If you are prompted tell it you want to manually find the application
3. To select an application to open the file, click the Browse button and then select the location of your Java.exe file. (You should see the Java splash screen starting and then the Deviation Uploader should open)
4. Once you have the Uploader open, connect your device via USB
5. Now hold down the EXT button and power on your device. (You should see "Program Update...." with a loading bar)
6. Go back to the Deviation USB Uploader and you should see the Transmitter change from Unknown to "Devo F12E"
7. Now select the "..." at the end of the Firmware section and then browse to deviation-devof12e-v4.0.1-667678f.zip and select open. (The Firmware information should update in the screen)
8. On my second F12E I selected the "Format" check box and the Replace tx.ini, hardware.ini, and replace models. This was a fresh from package unit so there were no models on it. The Format switch is recommended by PhracturedBlue (The person making this all possible ) when you do the first time loading of an F12E.
9. Once you are ready to load it (Be 100% sure) click the Install/Upgrade button.
10. After it completes, power off your device.
11. Unplug the device and power it back on!
12. There are more steps to get the model.ini, hardware.ini, and tx.ini on the device but I am still working on this part. I noticed that if I select the "USB" mode after Deviation boots that it will ask me to format using windows. Once I formatted it wiped out the Deviation install. I believe we need to use the Deviation Uploader for the File Management using the "File Manager" tab in the uploader. More to come when I have more time. If you are having an issue with uploading files with the Deviation Uploader then you did not reboot after installing the drivers and you need to uninstall. Reboot, Re-install, then Reboot again. Then go back to the start of the LOADING PHASE step 1.

CONGRATULATIONS!!! (<- three exclamations means to go drink three beers and celebrate).

THANK YOU PHASE:
Thank you to the development team for Deviation and a special thanks to PhracturedBlue for all your work on this model. We appreciate all you do and for including this wonderful transmitter in the builds.

The bad thing about the Devo 10 compared to Spektrum DX8/DX9/DX18 is:

- it has no real hold switch on the back (I have to use rudder D/R as a Mode3 flyer)
- 2-way Gear is on left top instead of back side (counterpart of TH)
- top left (Gear) switch is only two-way, not 3-way like "Flap/Gyro switch" on Spektrum DX8++

@Walkera: How about a Devo 10 V2/V3 switch update?
The white Devo 10 (I like black or silver) has no more sticks than the black version, right?

@DeviationTX team: Are there any free places on the Devo 10 board to maybe support adding switches or changing the top left 2-way switch to 3-way (just like your Devo7E mods)?

Thomas

Not sure where (in what (sticky???) thread) the (new team) source Bitbucket repository was referenced...

It may be a good idea to link it above/below downloads section as "Source code repository".

Mwm thanks for your help, and for your answer.
it was my way of thinking that the issue was a conflict between Win and deviation or Tx.. I have understood that yesterday PM (in France) and decided immediately to study linux.
I hope to succeed in this challenge.
it's perfectly unbearable to see the desertion of the "support" of Walkera and the devention "team".
But keep in mind that they are always here to sell devices "ready to use".
For some weeks maybe.
regards

Did you select the proper format ('X600') under protocol options ?
Looking at the code (team repo), the default seems to be WLH08.

deviationtx.com/forum/7-development/5370...0d-usb-wont-turn-off
My initial fix is not a fix. it only worked because I reflashed the 4.0.1
this issue has been reported for many users across the range of transmitters

I had a similar issue with them also,
I used dfuse to reflash the DSU file from the nightly and then copied the filesystem over, then copied over my saved model / icon/whatever data and all worked fine

hi,

i don't know where to report this, but all recent nightlies fail on devo 12, after entering usb mode, there is no way to turn it off, just powering off the thx. also, the calibration panels are displayed as simple text on the top-left corner of the display instead of a popup panel.

Hi,
For my birthday I got a Syma X4 from my girlfriend, just to cruise around in the living room and kitchen when it is raining and windy outside. I was happy like a kid when I recieved it (although I became 34 ). Of course the stock transmitter is pretty crappy when you are used to the Devo 7E, so I was hoping to get my Devo 7E - Deviation binded with my new X4.

I installed the last nightly build, selected the SymaX protocol and the Tx binded like a charm (I already had the necessary module installed, www.banggood.com/DEVO-Transmitter-Tuner-...ys-V922-p-89812.html ). Not only does it work really good with my Devo7E, when I turn the transmitter it automatically binds with the quad, which wasn't the case with the previous version I used of the software.

With this superb control you can gently fly the quad through the house, I love the combo Syma X4/Deviation Tx.

Untitled by Hannu Coopman , on Flickr

So a big thank you to the Deviation team, your software is awesome!!!

Hardware.ini was introduced after the release of 4.0.1. That release used the rx.ini file to set up the additional modules. Post-release the team decided to use a new hardware.ini file to manage hardware modifications. If you run the nightly builds you'll find the hardware.ini in the root folder of the USB drive, alongside tx.ini.

"Without Tx mods" means you want a DSMx receiver. The other protocol options are either obsolete or have big, heavy overpriced receivers. DSM2 is older, less reliable and of questionable legality in some areas. Spektrum owns the protocol and charges for a license for protocol info. OrangeRx, LemonRx and deviation are unlicensed versions of it, and they have all gotten better in the last year or two. But some oddities in the protocol sometimes cause the unlicensed versions to work better when using DSM2 even if both ends support DSMx. Also, the only testing of the unlicensed products with each other is by the deviation team in the nightly builds.

OrangeRx telemetry works on deviation, but they don't have Rx battery telemetry. The older versions have been widely reported as having reliability and QC issues. QC had been much better after the first generation of them, and reliability has improved every generation. If you're going with FBL, you'll either need a flight controller or an Rx that does the FBL mixing. I'm not sure that OrangeRx makes the latter. If your getting a flight controller, check to see if it can do either SBUS or (C)PPM, and if so get an Rx that does that to simplify the build. If it does both, go with SBUS.

enineee wrote: So I finally joined the team after a long while of wanting in, and since icouldnt wait for a frsky port, I went ahead and bought the new 7e. I want add a NRF, CC2500, and probanly an A7150 later. Well I had got the first deviation uploaded, i feel remedial, but I cannot figure out how to change channelorder for the life of me, but I feel as if ive gone evertwhere on it, all i have not done is use the computer, perhaps it has a app simillar too Companion9x. So on my Taranis regardless of the radio setup, i can put my labels on any channel in the mix page. So how must I change the walkera AETR to DSMX TAER??

s

When you setup a new model by choosing a template, then choosing the DSMX protocol, you should see TAER in the mixer. If you've started with another protocol -- I think it will default to DEVO -- and then gone into the mixer and made changes, I think the channel order stays AETR.

Let us know if you see it differently.

So I finally joined the team after a long while of wanting in, and since icouldnt wait for a frsky port, I went ahead and bought the new 7e. I want add a NRF, CC2500, and probanly an A7150 later. Well I had got the first deviation uploaded, i feel remedial, but I cannot figure out how to change channelorder for the life of me, but I feel as if ive gone evertwhere on it, all i have not done is use the computer, perhaps it has a app simillar too Companion9x. So on my Taranis regardless of the radio setup, i can put my labels on any channel in the mix page. So how must I change the walkera AETR to DSMX TAER??

s

I have finally ordered a Walkera Devo 7E, so that I could make my self one of the most capable transmitters of all time. I already have all the additional modules I need to utilize the separate protocols. I love that this 7 channel TX has the capabilities from deviation, along with the abilities to utilize the modules. I cant wait!!!!!

Hi all, Have been using a Walkera 10 with Deviation for over a year now. It works so well and is absolutely great!
For my long range FPV project I am using the DCS trainer port on the transmitter to out put PPM control signal for my external long range radio transmitter (openpilot OPLM), so that port is already used.
Lots of people have this setup.
Now, most Goggles do have Head tracking functionality sending PPM - so how to get that signal in to the Deviation? The USB port is the only I/O left on the transmitter.

Any plans to support PPM Goggle Head tracking input using the USB port?
Any other solution to this situation?

Thanks a lot Deviation team
karla

I do it on my with an

hg pull ssh://hg@bitbucket.org/deviationTx/deviation

then push that back to your bitbucket repository. You can also edit the paths section of .hg/hgrc to add

team = ssh://hg@bitbucket.org/deviationTx/deviation

them do hg pull team

I could also use someone to review some of the existing requests. Like my dfu.py change...

That's what I do. You need a branch for your stuff and one for the team default in any case.

hexfet wrote: I merged lyndros' language fix, and almost mwm's display fix but thought mwm might want to I agree with merging fixes and minor updates. Less work for PB.

I think PB took away my commit bit to the team repo. I no longer have a "merge" button on it . Could you please merge this one?

I've been working on bringing the FrSky sensor hub telemetry working properly. As far as I know, the only one that has actually been tested was the voltage sensor, and it was pretty bogus.

I am handicapped by not having any FrSky sensors to work with, but building my own. So I could use a lot of help testing, especially from people with FrSky sensors, or DIY sensors known to work with FrSky transmitters. I've just listed the issues at the bottom here, and will expand on each in it's own post on this thread. I'll change the title to help people find/skip them, so please reply to them.

Test builds are at deviationtx.com/downloads-new/category/2...kysensorhubtelemetry

If you want source for some reason, it's at bitbucket.org/mwm/deviation , in the FrSky-temp-names branch.

Pull request for the team repository is at
bitbucket.org/deviationtx/deviation/pull...lemetry-display/diff

Issues:

1. The monitor page layout needs fixing. I need ideas for this!
2. Not sure if the values are right, as I'm writing both ends of the system
3. Connections appears to be flaky, even though non-hub data is rock solid.
4. Items that need more than 16 bits are flaky.