Advanced Search

Very strange.Hidden directory?
Did you do that as user or admin on your W7 systems?

that's strange no one from the team has a answer?

Honestly, I'm not even considering doing it myself. My hands just aren't steady enough, and therse parts are really small. Ideally I'll team up with someone to get the boards produced. Worst-case, eventually I'll pay to have a set of prototypes run through an APCB shop.

I got my F072 discovery board in the mail today. I'll need to hack up one of my nrf modules and see if the interrupt is fast enough soon. Probably not this weekend though. Other stuff going on.

Thank you SeByDocKy, and congratulations victzh and the team for this great work again.

Ok, all smiles.

Updated both tx's to latest nightly (4.0.1-3e3acc2).

Transfered old models folders and added txid= (same 8digit code for both), Notepad saved it with no problems.

Re-binded rx and telemetry unit to the 8s first, set fixed ID.

Changed the fixed ID in the 12s to match the 8s and it binds.

Out of curiosity, i tried turning on the 8s while the 12s was bound, expecting to have two controlers fighting for control of the model, but the 8s did not bind. Tried it in reverse, 8s bind first then turn on 12s and 12s did not bind, leaving the tx that was bound first in full control. Overjoyed

Great Job phracturedblue!

You, and the team of guys here are truly amazing.

Now to go about rebinding all my models that have devo rx's.....

The 2801pro rx's are not effected by this change, correct?

Thanks Greg! Yeah Walkera rules! I love my 8S a lot

I am going to get the DSMX receiver and stick it into a plane. I will swap all planes into my 8S as well. Miss u a lot! Wish I can come back to fly again at Croydon! Yeah team tornado !

Hey Rick, Don't sweat it I get full control at over 20m at the lowest power settings on both my 12s and 8s and I'm using them on my 700e and new gaui nx4 and thats on a dsmx ar7200bx, never a glitch on either of them. Stick them on your planes and I can fly them too when you come back long live the jets...and team tornado

henkerhaus wrote: Let's hope you have better luck with the new one!

Hello to all friends, I am back after waiting to get my new radio, I'm just here to thank the whole team and forum users for helping me when I needed. Now with my new radio all went well and I managed to put the firmware on it without diversion problem, really was a hardware problem, I just did and am very happy following the photo of my new radio firmware deviation! was first with no problem, thanks to all, I made a point to come thank and show who really had malfunctioned in the old radio! Thank you friends! Sorry for my english ... laughs ...

Thanks WheresWaldo, that explains it!

I could not understand why is the posted xxx.fodt.txt file a binary file and not a XML file. However I can open both with LibreOffice Writer with all formatting intact.

May I also suggest we add the Legal Status / Disclaimer to the Manuals, eg below is my suggested modified version of the Home page text. perhaps as a separate section or at the end of the Overview:

DISCLAIMER
Deviation is experimental software. There are no guarantees made or implied about the quality or reliability of this software. RC models can cause serious injury or even death if flown improperly. By deciding to use the Deviation software, you are taking sole responsibility for the control of your models. The authors of Deviation will not be held responsible for any injury or damage whatsoever caused by the use of the Deviation firmware. Be careful and cautious.

NOTICES
Deviation is an independent work. The Deviation project is not affiliated, supported or acknowledged by Walkera®. The Authors have never been in contact with Walkera nor have we knowledge of their stance on this project. The Deviation team provides no guarantee that the Deviation firmware will not harm your transmitter (although we do not believe that to be possible). We also cannot guarantee that Walkera® will not make changes to future versions of the hardware, firmware of Dfuse tool which would make it incompatible with Deviation.

LEGAL STATUS AND COPYRIGHT
This project is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

Deviation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with Deviation. If not, see < www.gnu.org/licenses/ >.

The Deviation Project is hosted at www.deviationtx.com and the Source are available at bitbucket.org/PhracturedBlue/deviation .

Also think this is an awesome project. Amazing quality and would be great to see it expand, both in terms of project team and scope (more radios - eg Taranis)... anyway, DeviationTX is something that PB and all the team can be very proud of.

By the way, Walkera is fully aware of this project and their support team even provides a link to this project if you ask for more features. So it seems they even support it. (Not officially of course....)

jazzjohn wrote: There are many users who very much appreciate the Deviation gift PB and the team have given to the RC community. I know that PB refuses to accept any compensation since he is doing this as a hobby and doesn't want to feel obligated. Very understandable.

However, may we contribute to a favorite non-profit cause in his and/or the team's name? The "no-obligation" clause will remain alive and well!

I am sure there is a deserving charity there somewhere, but another thing you can do to help show appreciation would be to donate a bit of your time to the 3.1 project just starting up. It could be anything, like testing a new build, reporting anomalous behavior or even writing a paragraph that might better explain what a setting does. I know I could use some help documenting the model configuration options.

There are many users who very much appreciate the Deviation gift PB and the team have given to the RC community. I know that PB refuses to accept any compensation since he is doing this as a hobby and doesn't want to feel obligated. Very understandable.

However, may we contribute to a favorite non-profit cause in his and/or the team's name? The "no-obligation" clause will remain alive and well!

Hello every buddy,

First of all many thanks to the Deviation Team for this great development. Keep going........ Got my Devo 10 (Mode 1)about 2 month ago and installed Deviation 3.00
Did flying my Lotus T380 with the Walkera Rx 1002 without any problems. Last week I got a orange 610 DSM@ Rx and I tried it on my T380.
Created a new model with Mode 1 and DSM2 output, connected the Rx and switched on to bind.
Binding no problem but I got a message saying Channel 1 is 0% save value is -100% meaning the throttle was connected to the left stick. I could not figure out how to change this. At the end I tried changing the Tx to Mode2 and Bingo!!!! it worked.
Do I miss anything here? why the TX have to be in Mode2 with DSM2??

any reply is appreciated.

please let me know if more informations or pics are needed

Thanks

sllewji wrote: I think the _team_ deserve a monument

You're right. I didn't mean to be disrespectful...

All of those guys who worked on it, yes.

I think the _team_ deserve a monument

I mean the basic idea is to fly the heli in a safe manner - away from yourself and other people-
Apart from throttle hold and failsafe going wrong, when you are near, there should be no danger to you if the remote goes berserk... if you fly the bird as described in the "read this first" safety chapters... apart from shelling out big bucks for the repairs.

Let's see: electronics are electronis - all made in China (or worse). If the board is not, then the chips for sure - so whatever. A Walkera board can go wrong with the same chance as a Futaba or Spektrum one. If you are picky, take it apart, put the board under a microscope and rework the critical solder joints with a digital heat gun... to make sure the board is "error free" There is not much else you can do, really.

On the software side... Others have factory written firmwares, tested and proven. Mostly by a single person - with a development/testing team of 2-3 persons max... most brands have a feedback forum... so not much different, really from the Deviation, apart it is not factory made (luckily...).


So - for me it looks like this: even the 450s are are expensive "not toys" for me. Therefore, flying in a safe manner, having the range checked properly, doing all possible settings right with the antennae and other rules of thumb (ESC and motor far from antennae, etc), there should be no difference in the cathegory--- 450 or bigger: fly it safely and all you can lose is money.

Buy the size of chopper you can afford to lose

Hexperience wrote:

Essen1 wrote:

If we could apply speed at the mixer level then when you flip the switch, it would take X number of seconds to ADD the +30 (or whatever amount). So in effect you would have full speed control on the ailerons, but they would both slowly tilt down... that would be neat.

That would be a great feature to have, Hex!

Something to slow down the servos at a certain setting or value on the switches, if desired. It would make the whole flaps, gear, spoilerons and flaperons much smoother and more scale-like instead of having them deployed so abruptly.

Maybe one of the software wizards on the development team & PhracturedBlue can look into it?

You can slow a channel but not a mix. So if you have gear on it's own channel you adjust the speed setting in the channel output page. But in the case of flaperons that would also slow your inputs to the ailerons which we dont want.

Hex,

Slowing everything down isn't going to work, you're right. It would require two different speed settings.

Essen1 wrote:

If we could apply speed at the mixer level then when you flip the switch, it would take X number of seconds to ADD the +30 (or whatever amount). So in effect you would have full speed control on the ailerons, but they would both slowly tilt down... that would be neat.

That would be a great feature to have, Hex!

Something to slow down the servos at a certain setting or value on the switches, if desired. It would make the whole flaps, gear, spoilerons and flaperons much smoother and more scale-like instead of having them deployed so abruptly.

Maybe one of the software wizards on the development team & PhracturedBlue can look into it?

You can slow a channel but not a mix. So if you have gear on it's own channel you adjust the speed setting in the channel output page. But in the case of flaperons that would also slow your inputs to the ailerons which we dont want.

If we could apply speed at the mixer level then when you flip the switch, it would take X number of seconds to ADD the +30 (or whatever amount). So in effect you would have full speed control on the ailerons, but they would both slowly tilt down... that would be neat.

That would be a great feature to have, Hex!

Something to slow down the servos at a certain setting or value on the switches, if desired. It would make the whole flaps, gear, spoilerons and flaperons much smoother and more scale-like instead of having them deployed so abruptly.

Maybe one of the software wizards on the development team & PhracturedBlue can look into it?