Advanced Search

In general, there is no cooperation between any of the dsm development teams. lemon offered to send a TX to pbr for testing, but I never saw any indication of it actually happening.

magic_marty wrote: Crap ! I have a micro brushless Swirlie build soon and it has the micro XM rx but no OSD And the swerlie is so small adding a OSD will be very difficult without killing the flight time/performance...Unless i can find one that weighs less then 2 grams and is very tiny..

Do you need the OSD for RSSI? I'd be shocked if range was an issue on that build ...
The MinimOSD is tiny - but it's a bit of chore to setup and requires you to flash firmware onto it. It's 1.3g but with wires you'll push into the 2g territory.

But also if you're ok with just having this info on your TX you can get voltage and RSSI (warning that this is likely a clone of midelic's work and includes code that will cause this to malfunction if it's within about 1-2 feet of you) . You can update it to remove that issue .... but that would involve soldering directly to the chip on the board.

ORRR ... slightly bigger, perhaps doesn't have the close range issue , but it still likely a clone. Bot rx's have GIANT antenna that can be shortened ... easier to update the firmware ... (requires or USBASP or similar)

Note: none of these are FrSkyX.

We don't archive the nightly builds beyond the three in downloads. You need to either build them yourself or have someone build them and upload them. For what this sounds like - tracking down when a bug appeared - your are liable to need several builds, so building them yourself will be a lot quicker. The official method is to use the docker images.

How can we get back into some older nightlies, I want to experiment test with old Frsky X version, some builds starting from around end of November, but I do not know were to find or download them.

dustin_84 wrote: Hi, has any one a picture how to install the 4in1 Module into a Devo F12E?

thanks
markus

Seems Nightly is "fairly stable" as of 1-23-17... Been Following 5 threads in Deviation for a year, Tons of Struggle/Teamwork/Conquering for this Tx! Anyway, here is my attempt at F12E Deviation & 4-in-1 install...I'm stuck at step G below...please reprimand me where necessary...

A) Deviating the F12E seems to have worked flawlessly. The Walkera F-series transmitters have a VERY small Flash space(46KB). Too small for the traditional FAT file system used by Deviation for other Walkera transmitters. Instead a custom "Nightly" file system was designed for these cases called 'DevoFS' The file system installation is different because of this. No need/Unable to install multiple files like normal Deviation...just 1 tidy innovative file...Wiki recommended using Walkera DfuSe Tool & all seemed well except Win7 would not recognize Tx as an external drive and Tx was stuck in USB Mode even after reboot?... Deviation Uploader & Driver worked instantly!... Maybe too soon to tell but it Seems the Bugs: 'FPV stops working after Deviation' & 'Models erase after power off' have been resolved!?!? Just Sayin'...Now to install the 4-in-1 Module! *(Champion vlad_vy posted today in Development & Builds: Ultimate F12E Memory Mod!!! )

B ) Pre-Soldered wires before install...

C) Remove antenna, 2 top screws, and rock board side to side while lifting to remove stock module from pin sockets...

D) Mount & Secure 4-in-1 & re-secure antenna...

E) Soldered 2500 wire to TCK (A14)... 7105 wire to TMS (A13)

F) Holy...Son of a...Mother... There are NO accommodating pads to solder the 2401 wire to... It will need to be soldered to a pin leg of the MCU Apparently We have a choice of 2 pins: PB3/Pin 89(B3 ) OR PB10/Pin 47(B10)...neither of which end at a nice little copper hole... *Notice: If Pin 89 is used it must be enabled/assigned as "B3 " A space MUST be entered after the B3 or a glitch will occur causing your models NOT to be saved at power off !!!

G) ANY secret workaround soldering locations would be greatly appreciated lol...or ANY advice on HOW Artus was able to solder such a small connection super CLEAN like this in photo 'G'

H) The MCU installed in your F12E is actually upside-down compared to figure H below... pin 47 is on top 4th from the left & pin 89 is on bottom 12th from the right... just saying

Dumbtrucker wrote: ... AI have a new MacBook pro and a stock Devo 10 ...

I'm a Mac user & I've helped several people get started with Deviation. Try these instructions for installation. It might be helpful to print this info so you can have it at hand. Post here in the forum if you need help.

The Deviation manuals suggest 2 methods for installing Deviation:
1. Use the Deviation Java Uploader.
2. Use the Walkera Dfuse installation software.

Method number 2 is for use with computers running the Windows operating system.
Method number 1, the Java Uploader, is cross-platform (Windows, MacOS, Unix, whatever can use Java), and is the simpler, more trouble-free method. The Updater was designed and built by the Deviation development team to ease installation of Deviation on a variety of Devo tramitters.. Using the Java Uploader, you can easily install any version of Deviation from version 4.01 or later, or return to the original Walkera firmware and file system if you wish. Installation uses the Firmware Zip file that you download without needing to unpack it. The Java Uploader takes care of unpacking and putting everything it the appropriate location on the radio. The application also includes other useful features you can explore.

Step-by-step downloads:
- Click on "Downloads" in the sidebar on the left side of this page.
- Download to your computer (in a location where you can find it) Deviation 5.0.0 firmware from the "Deviation Releases" section. You could also use the newest "Nightly Build", since it will have the most up-to-date information and the latest protocols.
- Click on "DFU USB Tool" from the "Downloads" page.
- Click on "DeviationUpload-0.8.0.jar." to download the Java version of the installer tool for installing Deviation.
- Go to www.java.com to download the current Java software for your computer if you don't already have it installed.
- If, for any reason, you decide to revert to Walkera's Devention firmware, go to the "Links" page in the sidebar, where you can find sources for the original Walkera installation files for your Devo.

Step-by-step Installing Deviation on the Devo:
- Ensure that your Devo is fully charged before beginning. Interrupting this process will lead to tears.
- Run the DeviationUpload-0.8.0.jar application on your computer.
- Connect your Devo to your computer using the appropriate USB cable.
- On the radio, turn on the power switch while pressing the "EXT" button. (On the Devo 12S radio, use the "Trainer" switch instead.)
The "Program Update" screen will be displayed on the radio and it is ready to receive an update.
- If your computer prompts you to format the device, accept the default recommendation and proceed. Formatting clears out the file system, but does not affect any firmware on the Devo. If you had Devention models, they are saved, but are not available to you under Deviaton firmware.
- On your computer, look at the "Transmitter" field at the top of the Uploader program that's running. The name of your Devo should appear there shortly after turning on the transmitter.
- Look for the series of tabs marked "Install/Upgrade | DFU | File Manager | Bin-Send" and see that "Install/Upgrade" is highlighted.
- Next to the "Firmware" field, click on the "..."button to browse for the Zip file for the Deviation firmware you are going to install and select it. The path and filename will appear in the "Firmware" field. You will also see that the fields for Firmware and Library Version and Size now contain information. Also, a number of item boxes have been checked in the program window to set up the installation. You're good to go!
- Click on the "Install/Upgrade" button at the bottom of the program window and wait while the installation takes place. You'll see the progress bar at the bottom of the window and then a dialog box will notify you when the installation is complete. Be patient.
- Job done. Unplug the USB cable and turn off the transmitter. When you turn it on again, you'll be greeted with the Deviation splash screen and your adventure can begin.

On Windows,to make the mp3 files I use natural reader free - www.naturalreaders.com/ - in which you can write anything and have it read by different voices. To record the speach I use Audacity - www.audacityteam.org/ - a very good free sound editor . Once all the commands have been typed on natural reader I record all in a row and afterwards it is very easy to split the global file to export all the mp3.

Hello and thanks to the team developing this marvel!

I just stumbled on this thread, and wanted to add my two cents. After damaging my Devo 7e trying to change the MPU, I moved to 9XR Pro with erSky9X for 4-in-1 compatibility. I was a bit deceived, as the little Devo7e had a much faster (did not measure) bind on power on. The reason? The AVR (arduino) in the multimodule needs to boot before talking to both the transmitter and the modules. While this may not seem interesting for some, I feel it is preferable to have the transmitter MPU talk to the radio modules directly via SPI by the "cut the middle man" philosophy.

As per the program storage size, perhaps if the code could allow for ease of selection of protocols (i.e. I only have CC2500 and nrf24l01 needs), we could use a small platform like the new Turnigy transmitter. I do agree it will be best to have all the protocols on one device, but on the absence of any capable candidate, perhaps modularity could be an option to reduce the binary size.

I do agree, the new platform should be technically comparable to Devo 10, or similar, or better. This would allow room to grow. As size also is an important factor, something like the Devo 7e would be great.

On the sourcing ourselves vs getting a readily available platform, companies would have already spend resources on the R&D on a device, which we may not have. Being less than other geniuses here, I can certainly design a PCB board that would work with the code already existing to be dropped into an inexpensive but good transmitter (like me designing for a board to replace in my Devo 7e with the stm32f103c8t6 already installed): but it is almost impossible to compete price wise with corporations that have capacity for volume production.to guarantee longevity... Even if the board is designed by us, electronic components discontinue as well, bringing us back to this conundrum.

In brief:
1- Chose a new platform already available to slow down obsolescence.
2- With SPI, to talk to the modules directly.
3- Size wise, like the Devo 7e, technical prowess like the Devo 10. TBS Tango looks great, so does the Taranis Q X7. Hopefully the MPU could run Deviation. Like the AT9 as well...

Regards,
CesKQuad

thank you a lot for your answer FDR I don't know that's not a real "Team" but i respected their great job for Deviation and thank all for their support and efforts.

I am pushing a litte the F12E threads - maybee the develeopers see thats some users are interessed in this part of deviation.

Only an idea ... what do you think about a sorting for what kind of Transmitter the user is looking for - threads for "DEVO 7 / DEVO 8 / DEVO 10 and 12" ...

I see some threads ending here with "give up" cause they dont know what to do - but the solution is hidden in any thread here.

And thank you FDR for your time you spend with this forum bringing DEVIATION step by step forward.

Yep, you can use the CYRF module at 100mW (or even at 150mW) with deviation, and of course the original limitation doesn't affect the additional modules at all.

Sometimes threads become burried too fast without an answer.
As you probably know, there is no dedicated development team, but only a few nice people, who doing this on their free time if and when they have some...

It seems nobody is intend to answer a question which is not "new". I also asked some questions - and after some hours (more than 10) of reading and searching in threads with 100 and more replies i found my answer

Deviation is a great work for me - and i am using this since one year. Only the forum is sometimes a little unsorted and many thread are starting with one question und then changed to 10 and more the question. It's hard to find out if you want to know anything special.

Maybee the programm team of Deviation has a lot to do with development - and less time for the forum.

I have read anywhere that the Difference of the F12E version A und B is the bootloader of Walkera - so the output is regulated by software - And Deviation opens the output power from 10 to 100 mW of the CRY6939 Transiever modul.

(My CC2500 modul shows me an output power of 300 mW with Deviation)


Sometimes a thread is ending "i have it" - but with no word about the solution.

The Deviation manuals suggest 2 methods for installing Deviation:
1. Use the Deviation Java Uploader.
2. Use the Walkera Dfuse installation software.

Method number 2 is for use with computers running the Windows operating system.
Method number 1, the Java Uploader, is cross-platform (Windows, MacOS, Unix, whatever can use Java), and is the simpler, more trouble-free method. The Updater was designed and built by the Deviation development team to ease installation of Deviation on a variety of Devo tramitters.. Using the Java Uploader, you can easily install any version of Deviation from version 4.01 or later, or return to the original Walkera firmware and file system if you wish. Installation uses the Firmware Zip file that you download without needing to unpack it. The Java Uploader takes care of unpacking and putting everything it the appropriate location on the radio. The application also includes other useful features you can explore.

Step-by-step downloads:
- Click on "Downloads" in the sidebar on the left side of the home page on the website.
- Download to your computer to a location where you can find it, a version of your choice from the "Deviation Releases" section. We recommend using the newest "Nightly Build", since it will have the most up-to-date information and the latest protocols.
- Click on "DFU USB Tool" from the "Downloads" page.
- Windows users can click on "DFU USBDrv Installer 1.1.zip" to download Windows driver software in order to recognize the USB port of the Devo radio (if needed).
- Click on "DeviationUpload-0.8.0.jar." to download the Java software used for installing Deviation.
- Go to www.java.com to download the current Java software for your computer if you don't already have it installed.
- From the sidebar on the deviationtx website, go to the "Links" page, where you can find sources for the original Walkera installation files for your Devo, if you decide to fall back or start over.

Step-by-step Installing Deviation on the Devo:
- Ensure that your Devo is fully charged before beginning. Interrupting this process will lead to tears.
- Run the DeviationUpload-0.8.0.jar application on your computer.
- Connect your Devo to your computer using the appropriate USB cable.
- On the radio, turn on the power switch while pressing the "EXT" button. (On the Devo 12S radio, use the "Trainer" switch instead.)
The "Program Update" screen will be displayed on the radio and it is ready to receive an update.
- If your computer prompts you for driver software, take the steps necessary to satisfy that request, Window users should start with the "DFU USBDrv Installer" that you downloaded earlier.
- If your computer prompts you to format the device, accept the default recommendation and proceed. Formatting clears out the file system, but does not affect the firmware. If you had Devention models, they are saved, but are not available to you under Deviaton firmware.
- On your computer, look at the "Transmitter" field at the top of the Uploader program that's running. The name of your Devo should appear there shortly after turning on the transmitter.
- Look for the series of tabs marked "Install/Upgrade | DFU | File Manager | Bin-Send" and see that "Install/Upgrade" is highlighted.
- Next to the "Firmware" field, click on the "..."button to browse for the Zip file for the Deviation firmware you are going to install and select it. The path and filename will appear in the "Firmware" field. You will also see that the fields for Firmware and Library Version and Size now contain information. Also, a number of item boxes have been checked in the program window to set up the installation. You're good to go!
- Click on the "Install/Upgrade" button at the bottom of the program window and wait while the installation takes place. You'll see the progress bar at the bottom of the window and then a dialog box will notify you when the installation is complete. Be patient.
- Job done. Unplug the USB cable and turn off the transmitter. When you turn it on again, you'll be greeted with the Deviation splash screen and your adventure can begin.

So from the name it sounds like it is the protocol intended for their small models. Then we could name it ESky_mini. As if they publish another big model, it could be very likely that it isn't using this protocol, but again the original esky one.

I guess those who can approve the pull request should decide on this matter.

BTW: Easiest way to reverse a channel is just to calculate 3000-old_value. I would do it in the esky2_read_controls.

I'm really glad didn't need your advice on this one

I already apologize that I will not have much (any?) time these next 3 days. And today I'm on the road, so...I already wish you all a nice christmas.

So am I. You can find the promised builds in the post above, including the protocol option for fixed RF channels just in case somebody encounters problems - I guess it doesn't hurt.

Thanks for the excellent team work on this protocol!

Well.. I find myself constantly looking for a new tx... and i don't mean "a tx", but the "all in one tx".

as it seems there will not be good/cheap/chinese tx launching soon... I honestly don't want to buy another walkera or noname brand.
Main reason is parts availability. (board fried for some reason, gymbal broke, lcd dead... it happened to many of us)

IMHO the only way to standout and keep the project alive is turning it 100% DIY.
Drop the chinese tx "rubbish".
some ideas:

- the heart will be a main board to satisfy every deviated desire, as in this thread CUSTOM TRANSMITTER BOARD
- maybe two boards, the mainboard and the tx board. Different mainboards for different prices? So you could start with a cheaper mainboard/less channels/less features and upgrade later
- custom 3d printed chassis (a few form factors), files from deviation team and everyone can have it 3d printed OR the taranis case is available cheap (15$) OR user designed
- using gymbal from taranis or easily available ones
- BOM, user would source all the external components (buzzers/speakers/switches/gymbals/lcd etc)

Kinda like a "modular DIY taranis"

edit the 3d file to fit the gymbals / lcd you want and such, if supported in code.

One main "official" project/code. Plugins in HW/SW for modules to add custom parts when needed.

Don't sell the transmitter as a ready made product. (regulations etc)


- PROS:

• can do whatever you need hw/sw wise without constraints (except money )
• lifelong project
• when a spare is no more available, e.g. gymbals or lcd, design a new cad model and 3d print it
• big potential user base (programmers/engineers etc)
• all protocols

- CONS:

• the old farts will not understand how to build it etc. I bet they will have friends in their r/c circle that would! "build it and they will come"
• more resources needed to start the project
• not "legal"? so, do you think a deviated walkera is "legal"?

Hey Deviation team,

I'm trying to log in to the bug reporting system, but I'm getting an error each time. I know I have the right username and password because I log in just fine to the forums. But every time I try to log in I'm getting:

Your account may be disabled or blocked or the username/password you entered is incorrect.

Is there something I have to do to register for bug reporting as well?

Thanks for the help!

It’s amazing how the Deviation firmware has evolved throughout these years. Since I first tried it out last year, I fell in love with it. Today I fly all my sub 250 class heli’s (and sub 500mm fixed wings) exclusively with Deviated Devo7e. What a wonderful job the Deviation team has done! Thank you so much for your great effort – I really enjoyed it.

Now I’d like to share some experience gained when fiddling with the Devo7e, specifically in the power distribution area. I’ve learned a lot from previous posts including the one I participated. Have done some experiment and measurement and finally came up with my solution for the D7e.

If you are thinking about powering the unit with a 2s Lipo, and want to take advantage of the higher voltage (potentially translates into longer running hours) and don’t want to risk over driving the on-board ldo/modules and don’t want to lose the capability of monitoring the battery pack, try these simple steps below.


1. Lift the positive side of the big diode which feeds into the built-in RF module
2. Add a Pololu 5V stepup/down module (Part number S7V7F5, item #2119, recommended by Fernandez – thank you.) to feed into the diode
3. Add a Pololu 3.3V stepup/down module (Part number S7V8F3, item #2122) to feed into the 3-in-1 module
4. Remove the tiny 3.3v LDO
5. Instead, wire in a 1117 based LDO module with a ~1ohm resistor at the output

Refer to the picture for these numbered areas.

If you are interested in the background of these changes, they can be found here.

Enjoy flying!

I've seen several people ask about upgrading via mac, and every time, the same answer seems to be given. "read the manual". This is not a suitable answer or helpful in anyway.

I really dissagree that the manuals are complete or easy to get information from, especially if one is using a mac. I'm an experienced computer user, and find the documentation to be lacking, and every forum thread regarding noob questions or mac/osx usually ends in "read the manual"

if the manual was clear and simple, and included how to upgrade the firmware via a mac, it would be great. but instead the documentation makes assumptions that the reader knows as much as the author, about related technical tools and topics, and doesn't really lay out the path as clearly as the author thinks.

I'll give you an example. on the first page of the manual for devo 6/8/12, it says

"If you do not have the Windows™ operating system, go with the first choice, the Deviation Uploader tool. It is a Java application that was designed by the Deviation developer team to be efficient and simple to use with any Devo radio and any version of deviation or even Devention, if you should wish to revert to the original Walkera firmware. "

but there is no link to this tool. and when I go to the downloads page, there is nothing specifically labelled "Deviation Uploader Tool", it is a buried download inside the DFU USB Tool folder, that was described in the same paragraph above, as for windows only. already confusing. so you find it, download it and then skip down the manual to use this tool on the mac...

"The ‘Deviation Uploader’ is a Java (jar) file. You can either pass the jar file to the Java executable on the command line, or open the file in the GUI, using the Java application to open it. You will need to install Java from www.java.com/ if you haven’t already installed it."

This set of instructions is gibberish to anyone who isn't a developer. This is not straight forward instructions for a new user. Having java installed is not even the issue. How is a new user supposed to know how to use the Java Application to open it or pass it on a command line? What Java Application? Where? At this point an average new user on a mac is stopped dead, and we're only on step one.

Also, there is no specific mention of upgrading a device once it has already had deviation installed on it. Maybe this is the same process as the initial installation. Maybe it is not. The only thing that is certain is that it is not described.

I'm not trying to start any arguments or anything... but I brought up similar issues a year ago in some circles and was met with a lot of "the manuals are complete and detailed"... back then I didn't really need to update, so I didn't. My Devo 6s already has deviation running and it was sufficient. But here I am a year later, and it feels like nothing has changed, except now I need to be able to handle frsky SBUS on my devo and I'm still on a mac, and the instructions still don't actually include steps that are critical to using the software. I've managed to learn how to do everything else I need to do in RC on a mac... but updating my devo is still a mystery.

I'm hoping someone can post some actual instructions and tips in this thread, or update the manuals with specific instructions and screenshots...

Cheerson's mini drones CX-10W, CX-10WD, and some other models can be controlled by WIFI as well as conventional 2.4GHz RC. Some of these models also use WIFI to receive steaming video from onboard cameras.

The conventional TX protocols are available as deviation modules. However, seems little is known about the protocol used to control via WIFI. What protocol is used to control via WIFI and receive video via WIFI? Has anyone cracked this yet? Sniffing WIFI communication may be necessary to do so; have never used a WIFI packet sniffer.

Would like to develop custom control software on iOS and/or Andoird for these Cheerson WIFI capable mini drones.

I didn't realize Sierra was still beta, didn't know apple did that. Does the apple beta dev team take bug reports from Random people?

I feel like not many people wouldnt have access to such a generic game pad HID such as deviation/ open-tx so it may not be reported yet, queuing them on your specific issues may help them out. There's nothing to do on the devo side of things...


If you have an Xbox or even ps2 controller that's wired (NOT wireless w/ a charging USB cable) plug it in and see what it happens (Xbox should show up as xbpx/Microsoft but work the same as devo and ps2 will show up same as devo: "generic USB Gamepad"). If nothing else you'll have more data to report.

Yes I believe that too - test-build(s) from one of the latest nightly-builds (depending on the latest developer repository clone).
But what is the point in creating "protocol test builds" being (only) from latest 5.0-nightly-build? Any benefit?

That may only make sense for new transmitter GUI support like AT9, F-series - but not for older Devo series.

Well, somehow there needs to be a start for a "core smaller test team" to try out new releases / protocol code which could is not 100% finished and such can not be released as 5.0.x/5.1.x.

I would vote for creating two test releases
- one based on latest 5.0-nightly-builds
- one based on core release 5.0 code + (protocol) additions

Tester can choose which he wants / what works better for him.