(03-Apr-2017, 04:32 PM)unseen Wrote: Good luck, I hope you can work it out!

Thanks for the help with the firmware flashing, I was having a hard time finding consistent information, every guide had a somewhat different process

(03-Apr-2017, 12:44 AM)Helibus Wrote: No on the Devo 12e. Any idea on what you did wrong? Mine's not expected to arrive until tomorrow, and it may be a while before I get around to doing anything with it. Unseen, thanks for all the reference info.

I'm pretty sure I broke it after clicking "exit dfu mode" in the walkera utility, my recommendation is to definitely use the deviation tool over the walkera utility.

Trying to fill in some details in reading the instructions here. DeviationUploader wants the full zip file with everything in it, but vlad_vy only provides the DFU file. I take it you need to build a new zip file that is say the Devo 10 Deviation 5.0.0 release except it contains vlad_vy'ss DFU for the 12e. Is this correct?

(03-Apr-2017, 09:33 PM)Helibus Wrote: Trying to fill in some details in reading the instructions here.  DeviationUploader wants the full zip file with everything in it, but vlad_vy only provides the DFU file.  I take it you need to build a new zip file that is say the Devo 10 Deviation 5.0.0 release except it contains vlad_vy'ss DFU for the 12e. Is this correct?

Good news, I flashed the devo 10 bootloader and my remote is back to life! I'm gonna flash deviation tonight and then I'll let you know the process Helibus

I had a bit of time so I went ahead and worked through it. Gave up on Deviation Uploader and my hacked zip file though and just used the dfuse utility to upgrade to the latest vlad_vy dfu. Then formatted & copied over the files from Devo10 5.0.0 except for the dfu and debug.

(running Win7 Pro 64-bit)

(04-Apr-2017, 01:41 AM)Helibus Wrote: I had a bit of time so I went ahead and worked through it. Gave up on Deviation Uploader and my hacked zip file though and just used the dfuse utility to upgrade the dfu. Then formatted & copied over the files from Devo10 5.0.0 except for the dfu and debug.

(running Win7 Pro 64-bit)

Ahhhh ok, yeah I basically have a Devo 10 now because I can't find the Devo 12e bootloader. I tried giving the 12e dfu a chance and it bricked it once again so I had to flash the bootloader again and then load the Devo 10 dfu. It kinda sucks but it's better than nothing

(03-Apr-2017, 09:33 PM)Helibus Wrote: Trying to fill in some details in reading the instructions here.  DeviationUploader wants the full zip file with everything in it, but vlad_vy only provides the DFU file.  I take it you need to build a new zip file that is say the Devo 10 Deviation 5.0.0 release except it contains vlad_vy'ss DFU for the 12e. Is this correct?

I just flash the DFU (the firmware) and then copy the file system from the full 5.0.0. release onto the radio's disk drive after flashing.

(02-Apr-2017, 10:42 PM)unseen Wrote: I hope you can bring the bricked one back to life.

The instructions for installing DeviationTX are in the user manual here: https://www.deviationtx.com/user-manual/...nual-7e-10

They are comprehensive instructions. The Devo 12e is essentially a Devo 10 with two extra pots, so just follow the instructions for the Devo 10 and it should work fine.

Note that you won't find a build for the 12e under the main downloads section as the 12e wasn't around when the last 5.0 release came out. You need to download one of the nightly builds from here: https://www.deviationtx.com/downloads-ne...tly-builds
or, you can download one of vlad_vy's builds which only add the latest protocols to the official 5.0 release. This is probably the best option and is what I run on my Devos. You can find vlad's thread here: https://www.deviationtx.com/forum/builds...-protocols
Just go to the last post to find the download links.

It's also really important to check you are downloading the correct firmware. A Devo 12 and a Devo 12e are two completely different radios!

I can't get my motors to stop spinning when armed, I have motors stop turned on and I also have throttle at a minimum, I can move the quad around and the motors will adjust speeds but still won't stop spinning at zero throttle

(07-Apr-2017, 01:33 AM)Nathaniel52441 Wrote: I can't get my motors to stop spinning when armed, I have motors stop turned on and I also have throttle at a minimum, I can move the quad around and the motors will adjust speeds but still won't stop spinning at zero throttle

Have you already set motor_pwm_rate to something fairly high (16000 or 32000) so the FC is put into brushed mode instead of brushless?

Another reason your motors are spinning could be if you have airmode activated?

(07-Apr-2017, 03:10 AM)Helibus Wrote: Have you already set motor_pwm_rate to something fairly high (16000 or 32000) so the FC is put into brushed mode instead of brushless?

Beta flight has a drop down in the config tab to select motor type as brushed, setting the pwm rate high as well, won't cause any issues will it?
Clutching at straws here trying to find a solution to my problems!

(07-Apr-2017, 03:10 AM)Helibus Wrote: Have you already set motor_pwm_rate to something fairly high (16000 or 32000) so the FC is put into brushed mode instead of brushless?

It's set to 32000 right now, btw in using a micro f3 evo brushed fc

So let me see if I understand your problem correctly.

When the quad isn't armed, the motors don't spin.
When you arm it, the motors start to spin, even though you have turned off air mode and enabled motor stop.

Is that correct?

(07-Apr-2017, 04:07 PM)unseen Wrote: So let me see if I understand your problem correctly.

When the quad isn't armed, the motors don't spin.
When you arm it, the motors start to spin, even though you have turned off air mode and enabled motor stop.

Is that correct?

Correct and it will respond to tilting, I can raise the throttle and the motors will spin faster but when I push the throttle back to zero the motors with start fluctuating speeds and never stopping.

Min throttle 1000 max 2000. The tx throttle only decreases to about 1100.I tried raising the minimum throttle above the lowest the tx will go and it still didn't work

OK. I'm beginning to understand.

If the lowest your radio's throttle channel goes is 1100, but you've set min_throttle to 1000, then as soon as you arm, you are asking the motors to spin!

The first thing you should do is use the mixer setup on the radio to increase the scale of your channels so that you can get from 1000 to 2000 on all of your sticks. The pitch, roll and yaw channels should be at 1500 when they are centred. Use the subtrim settings if they aren't.

Once you have done that, you should set min_throttle to lowest value needed to make the motors start spinning reliably.

Then, the throttle signal from the radio when the throttle is down will be less than the min_throttle value and the motors should not spin when you arm. Personally, I don't like the motor stop feature and think that you should always have the props spinning when the craft is armed as nobody can mistake that the craft may take off at any moment. Sure, a brushed motor won't cut your fingers off, but it's good to get used to having the motors spin when armed for when you move to larger craft.