Devo 7E won't bind after update to Deviation 5.0.0

  • dpowellmeii@gmail.com
  • dpowellmeii@gmail.com's Avatar Topic Author
  • Offline
More
25 Oct 2017 04:48 #65245 by dpowellmeii@gmail.com
Devo 7E won't bind after update to Deviation 5.0.0 was created by dpowellmeii@gmail.com
Greetings,

I have a Devo 7e what I flashed with Deviation 4.0.1 a little while back and today I flashed it with v5.0.0 and can't get it to bind with anything. Prior to this it worked fine with my Super CP and a few DSM2 models but now, nothing. What did I do wrong? Any help would be greatly appreciated.

Thanks,
D

Please Log in or Create an account to join the conversation.

More
25 Oct 2017 05:01 #65246 by vlad_vy
Do you renew filesystem? Especially "protocol" folder.

Please Log in or Create an account to join the conversation.

  • dpowellmeii@gmail.com
  • dpowellmeii@gmail.com's Avatar Topic Author
  • Offline
More
25 Oct 2017 13:31 - 25 Oct 2017 13:57 #65259 by dpowellmeii@gmail.com
Replied by dpowellmeii@gmail.com on topic Devo 7E won't bind after update to Deviation 5.0.0

vlad_vy wrote: Do you renew filesystem? Especially "protocol" folder.


I did, I followed the instructions exactly like they are written in the manual.

When the issue started it would bind initially but would keep dropping the signal. Eventually, after trying a few other models, it wouldn't bind at all. My DX7 binds just fine with my eachine quad and other DSM2 aircraft I have but my Devo won't bind anymore. The other odd thing I found is that when you click bind, it only shows a 2 second countdown timer.

I re-installed the original firmware and no change, still won't bind.

What are the chances that something internally went bad? Any way to check the internal components?
Last edit: 25 Oct 2017 13:57 by dpowellmeii@gmail.com.

Please Log in or Create an account to join the conversation.

More
26 Oct 2017 00:15 - 26 Oct 2017 00:21 #65275 by aMax
Clear the ID on the SuperCP rx with the delivered plug. Check the manual which connector to use. As far as I remenber the
second one from top.
Then start a bind and keep the computed ID as new fixed ID, use it with every old or new model ini for the CP

Edit: This is only necessary once, from firmware version 4 to 5.

Devo7e, TaranisQ X7, R9M , 4in1 MM, Futaba FC18plusV3.2 & DFT/FLD-02
Last edit: 26 Oct 2017 00:21 by aMax.

Please Log in or Create an account to join the conversation.

Time to create page: 0.029 seconds
Powered by Kunena Forum