Advanced Search

Trainer mode is now possible in the nightly builds, although it would be helpful to setup a template qand provide documentation for it. It is available in both standard and advanced guis, though I've only tested it in advanced mode.

Personally, I only ever use the Advanced GUI, and so most of my effort goes there. I know Suvsuv spends more time working on the basic GUI, so maybe his fork would be better for many folks. Since he doesn't post here anymore, and I'm unwilling to support it, it is largely limited to te Chinese speaking crowd though.

It should be evident that I spend much more time working on the Devo8 and Devo12 since I prefer the big colorful screens, and thus the7e and 10 tend to get less attention as well.

If we had a larger programming team, we could certainly do more, but it is currently just me and whoever feels like contributing patches (which I'm extremely grateful for), so I need to choose which parts to work on, and it means some areas get more focus than others.

Just want to say thanks to the Devation Development Team for a great piece of software and for all the time effort put into it. Very much appreciated. Just bought a Devo 8s and the software works great. Runs all my dsm2 planes and helis just fine.

The biggest challenge I see with articles is that there is no version control. i can't visualize or undo changes. That means we basically need a small trusted team to maintain it, rather than leaving it open for all members of the forum.

Bitbucket offers a way to add a Wiki to a repository. It is also a mercurial repository which can be handled similar, but there is also a web interface for creating and changing pages (similar to the issue editor).
I have setup a fast example here: rbe's testwiki . I have set it to public open - everybody can read, but writing seems to be restricted. I have allowed PhracturedBlue and myxiplx to write.

The main problems I see with a Wiki:

• structuring is hard (not impossible, but needs some care)
• we would have to conclude if anyone should be able to write text or if we have an editors team who decide which changes will be included (similar to a merge of code...) (for the bitbucket wiki the first might not work at all)

Hi,

sorry for asking, but I am not sure if I am missing something here. Could someone be so nice and tell me what the current state of the FrSky protol development is? I am not asking in the protocol development thread to not clutter it with random noise.

PB wrote that he has both FrSky versions running, but here and in another forums it was written that the module still seems to behave erratic. I have seen to document on doc to how to install a cc2500, but on my Nightly I could not find the FrSky protocol in the GUI.

So is FrSky currently dev-only or do I just need to install the cc2500 and it's then available in the GUI? Is there anything a normal user could do to help support the development team (besides not asking for it too much;)?

Thanks for your help and patience. And of course, the fantastic Deviation - muchos Kudos grande!

Olli

Just want you guys (no gurlz on the dev team?) to know that I absolutely love your work!

My fleet mainly consists of Walkera receivers, but the other day a colleague showed me his Nine Eagles 318 (?), and he was stumped when I took out my Devo 10, bound and flew (spun up anyway) his bird!
He's going for a Devo Tx now, and that dinky J6Whatever is never to be switched on again.

Walkera's engineering team seems to be consistently ahead of the support team. That isn't surprising. My guess is that they had a supply-chain issue, couldn't get any more of the devo8 lcd modules, and switched manufacturers. The software guys were able to do a patch and get everything working without a hiccup....They just never got around to making the firmware available on the website. As with the Devo7e before hand, I'm sure they'll get enough complaints of people installing a 'bad' firmware that it will necessitate them providing the firmware sooner rather than later.

Finally I can go and buy my devo 12. You guys are absolutely amazing. Beeing from sweden I say. Give the Noble price to the deviation team!!!
thanks for all the hard work! forever in debt...

Tomas
Sweden

The use of the ini-file is indisputable - I use them the same way, but all my configs were created from the gui; just to be sure of their correctness.

Now let's make a real job of it. Where should we start?
I see these steps (all comments in brackets are my opinion):

• search a place to save intermediate and final results (the forum is not because it makes teamwork difficult; I would prefer a new bitbucket repo or something similar)
• define format (should be similar to the regular manual)
• define a structure (easiest: the main blocks "global", radio, mixer, gui-qvga...)
• for every structure element: describe the use of this block, describe the possible parameters, their possible values, the page / place in the gui where it will be set in the real tx / emulator (separate for standard and advanced) and give some (one) example
• write a general description where everything what was announced to be a problem for some users is mentioned: filesystem, editor, line endings, 4k-size, comments in the file, the way the config is read, stored and written, ...
• search for volunteers who will write one section

Dear all,

For all users setting up the RX2702V the fist time I recommend to use the new version V3. Thumbs up to the team !!!

Please start with setting: Mixer GUI: STANDARD !!!
Then start with the swash setting 3x120
Then you can easily set all parameters as per your needs.
I tested yesterday almost all settings and I'm very happy with the new layout and usability.

Later on you can switch to andvanced if you have the feeling something is missing.


Regarding my settings - as you can see I fly only scale heli - so my settings are tailored to my models. Even my settings of the models differ a lot as I really "fly" my settings.

But if some of you would like to send me your settings and your problem I can check and give you some advice.

SICKNESS!

well done bro! Pic added to heliporn library

Slightly related... I Was thinking team Deviation should make a sticker that's says Deviation to go right above where you've mounted your led... It would fit the theme too if only the "IA" and "DEVO 10" was transparent to let the LED through

A kit, with the LED and the sticker would be a great fund raiser for a well deserved development team (but that's a whole separate topic!).

Next time you take off her pants off (DEVO 10), please take a pic or 4 of the mod, I'd love to add this too!

Thanks for sharing!
-=S=-

How about something akin to a kickstarter. If a bunch of us all pre-pay for modules, at a predefined and slightly inflated price, we can essentially fund the outsourcing of the module creation, and let the talented team of coders here work on the software side of things.

I know I would be willing, as I love the work done so far (I have been a long time lurker, and have owned a 8s, and now a 12s only because of the existence of this firmware).

PB, I know your anti dontation, but this is more like spending others money to achieve the desired goal.

Then you wouldnt have to bother learning any layout software, just defining the standards/requirements, and finding a offshore design house to create. I know there are a few native chinese speaking folks who could likely assist in finding a manufacturer/designer offshore.

Hello Team Deviation!

Many thanks as usual for your continued hard work!!! I've refrained from updating my firmware regularly because the longer I wait the more cool stuff you guys seem to add!!!!

Currently I'm running 3926ed5aa468 (night build) and I love the new switch icons! Its pretty cool how you can configure them also! LOVE the new pause/reset switches for timers now! Great idea on the permanent timer too!

Just a few general ideas:

1) It'd be cool if we could set up 0 transmit power for sims, hopefully get more (crash)hours per charge! Maybe it would be easier to just call it "PPMx" configure it as a "new" protocol and then you don't have to add 0 to the available transmit options for the other protos? (I'm not a programmer please don't be offended if I make big tasks seem small!)

2) It be really cool if in the "model menu" ->"model setup"-> "file"
-> "reset" set the name back to "NONE" instead of "model #".

2b) same concept but "copy as" instead of "copy to"-> this brings you right to the naming screen and after you modify the name it then asks you for the target slot. It could make the process a tad more intuitive.

3) "easy flip?" I Saw a cheapo-heli while browsing some heli-porn late in the evening (at least I'm honest!), basically it came with a crappy remote that had a switch to reverse the orientation to make upside down flight the same as regular. I'm not dying for this, but thought it might be cool...not sure how worthwhile it would be development wise though :/

DEVO 10 specifically:

1) Is there any way users could add their own switch icons? I'm thinking you add an icon inside the "toggle menu" which represents "add" then it works like the "icon" option inside the "model setup" menu? (Probably need a new folder "DEVO ROOT":\Toggle Icons). Then users can use their icons when setting up the toggles!

2) Can you add a function where I can use the 5th trim switches (left of antenna) to insta-switch main screens? Similar to how the "sexyscreen" Devos work with the icon, but because of our wimpy displays we don't get to see the on-screen icon? EX: push up x1 = "Transmitter menu -> channel monitor"... push down x1 (re-centered) = main screen.... push down again = whatever you think is useful to your style?

3) Please consider getting rid of the inside trim option completely for DEVO10! IF you have your trims on the outside you loose 0 functionality and you gain valuable screen real estate between the icon boxes 5-8 and boxes 1-4 as well as a nice 5 or 6 characters between the toggle icons and the transmit power level (potentially new boxes 9-12 for the next request...)

4)I would need to change my underpants at an increased frequency due to accidentally & uncontrollable bodily-fluid spillage if I could use the dials at the top to adjust EXPO and rates on the fly!!

I'm thinking/wishing you can adjust the current "A-down" icon from the toggles to be "A-X" to show the ail expo or "A-R" to show the rate, same for other functions... by using the 6th trim button (right of antenna) users could choose what they are adjusting! So lets say AUX4 controls rate and AUX 5 controls EXPO... on my screen I'd see ER 60 EX 25 and the dials would adjust accordingly.. IF I pressed 6th trim down then I'd see
AR 60 EX 10... and the joy continues!


I'm sure none of this is as easy as I'm making it sound, and I know devo 10 is a limited demographic in the deviation pool, but what ever you could make happen would be greatly appreciated!

Cheers!
-=S=-

Hi All,

I use windows system with mingw, yagarto toolchain and eclipse with Mercurial, and I can do all (compile, Hg-command, defuse tool calling) within Eclipse per mouse click.

I hope this quick eclipse instruction can help.

What you need:

---

1. Running toolchain on Mingw Shell (you can compile without toolchain error)
2. Phyton
3. Java Runtime
4. Eclipse with CDT
5. Mercurial v2.0 above ( mercurial.selenic.com/wiki/Download )
6. MercurialEclipse ( mercurialeclipse.eclipselabs.org.codespo...i/update_site/stable )
7. Project and environtment setting

If you did all PB instruction how to install the build environtment, you have done step 1 and 2.
Then just install 3, 4 and 5.

After you have installed Elipse then open it and install plugins MercurialEclipse over Help->Install New Software.

Project import and environtment setting

---

1. Click File->Import, select Clone Exixting Mercurial Repository, then click next and follow until finish (you can clone in other directory name, just change it to your desire name)
2. Select the project in Project Explorer by clicking it the open File->New->Convert to a C/C++ Projects
3. Choose makefile project and --Other Toolchain--, then click finish
4. Click File->Properties then click C/C++ Build
5. On Builder Settings Tab->Build location add /src before }, example: ${workspace_loc:/deviation/src}, this ist your working directory for this project.
6. On Behavious Tab -> Workbench Build Behavior, Build (Incremental build) put your desire make argument (ex: TARGET=devo10) and clean argument (ex: TARGET=devo10 clean)
7. Explode C/C++ Build then click Environtment add:

PATH -> Your compiler bin path, mingw bin path, msys bin path, python path, mercurial path, and JRE path
example:
PATH D:\compiler\arm\bin;C:\MinGW\bin;C:\MinGW\msys\1.0\bin;C:\Program Files\Python27;C:\Program Files\Mercurial;C:/Program Files/Java/jre6/bin/client;

TEMP -> your temporary directory
TMP -> your temporary directory
8. Now you can build project by right clicking your project->Build project

To do Mercurial command just right clicking your project and choose Team.

What you need next is to configure code style to accomodate nearest PB codestyle

Hi team!

I can't display the DevoDfuSe window.
Everything is installed correctly, the driver is recognized but I can't launch the application. It won't be displayed but rather be "hidden" in the background. When I launch the app I see Windows undocked taskbar "moving" like when a new icon goes there and...nothing.
- STM32DFU recognizes the driver
- I've tried to run the app in compatibility mode (WinXP) and with Admin rights.
- The program won't run regardless if the device (DEVO 6S) is connected or not.

On my wife's Vista laptop it works flawless.
Any help would be very appreciated!
Thanks

FYI, WIN7 Event viewer:
Faulting application name: DevoDfuSe.exe, version: 1.5.0.0, time stamp: 0x4fbc9168
Faulting module name: DevoDfuSe.exe, version: 1.5.0.0, time stamp: 0x4fbc9168
Exception code: 0xc0000005
Fault offset: 0x000065bf
Faulting process id: 0x1768
Faulting application start time: 0x01cdab8ac02b5276
Faulting application path: C:\Program Files (x86)\Devention Upgrade Tools\DevoDfuSe.exe
Faulting module path: C:\Program Files (x86)\Devention Upgrade Tools\DevoDfuSe.exe
Report Id: fdde72eb-177d-11e2-adfb-5404a62c5e85

I have a DEVO12 and now I'm testing deviation Fw on a DEVO8.
I would have the FW ported to DEVO12 also, and one problem is that PhracturedBlue has no DEVO12 in his hands.
As consequence I propose to start a fundrising so PB (and main devel teams members) can buy a DEVO12 to use for development.
Having a Deviation Fw on a fullfeatured radio like DEVO12, will be a big success in the worldwide RC community .
Maybe (as form of public thanks) names of donors can be showed in an "about page" in the radio itself! )
Collecting money can be done through PayPal, I think.
Not problem on amount, I think few dollars would be enough.
If the proposal will be accepted, then I would start with my US$ 50.

Bye

I would also like to say THANK YOU very much to the Deviation team for all the hard work that has gone into this AMAZING firmware! It's great to finally be able to use one TX to control all my helis! I actually went out and bought a DEVO 8s just because of this firmware and must say it works flawlessly! Huge thanks guys!!

Hi,i'm french and i just flashed "Devi" my Devo8s and it seems to be really what i expected ...There are 2 or 3 things that i need to clear but it looks really Great for me...
It's just to thank you and all of your team for your great job!!!
Congratulations!

great news! You mentioned DSMX, but does this include the DSM2 issues as well?

I have to say, on a side note, that Deviation is probably one of the biggest things to ever happen to Hobby RC IMO. You probably already know this, but you and your team have LITERALLY achieved the holy grail of RC flight. And the fact that you're doing all this work and giving it away for free is incredible.

THANK YOU!

at first I want to thank the complete team of this great project. It's extremly usefull for pilots of microhelis with the old Wk-Recievers, the new Devo Stuff and the products from Eflite with one extremly costeffective transmitter... . (Exspecially since it has been completed just in time, I had planed to buy a DX6 for my MCPX today ).

Playing with the emulator, I have found some minor points, that could be improved (perhaps)... .

- Timer: It would be great to have a Reset Button.
- DR-Expo: Sometimes you need values bigger than 100% (for example 125) for some channels. Currently it's possible to get this with a second mixer, with the same source, that adds to the first, but alowing values bigger than 100% for the scale factor would be great
- Binding for DSM2: Some kind of "autobinding" would improve the handling massivly
- do you plan support for telemetrie in the future ?