Protocol mismatch after upgrading to deviation 5.0

05 May 2017 05:24 #62014 by Human

Protocol mismatch after upgrading to deviation 5.0 was created by Human

I upgraded devo 7E to deviation 5.0.0 by Walkera DfuSe and after turn it on, it says
Protocol Mismatch
0801ef44
0801fc6c

05 May 2017 05:41 #62015 by vlad_vy

Replied by vlad_vy on topic Protocol mismatch after upgrading to deviation 5.0

Do you renew filesystem?

05 May 2017 06:06 #62017 by Human

Replied by Human on topic Protocol mismatch after upgrading to deviation 5.0

I formatted in fat and uploaded files

05 May 2017 18:58 - 05 May 2017 18:59 #62043 by mwm

Replied by mwm on topic Protocol mismatch after upgrading to deviation 5.0

That error means the protocol files don't match the dfu. Did you copy the old ones back, or use the ones that came with the dfu?

Do not ask me questions via PM. Ask in the forums, where I'll answer if I can.

My remotely piloted vehicle ("drone") is a yacht.

Last edit: 05 May 2017 18:59 by mwm.

05 May 2017 19:00 #62044 by Human

Replied by Human on topic Protocol mismatch after upgrading to deviation 5.0

mwm wrote: That error means the protocol files don't match the dfu. Did you copy the old ones back, or use the ones that came with the dfu?

I used that came with zip file

17 May 2017 04:38 #62378 by ticfifty

Replied by ticfifty on topic Protocol mismatch after upgrading to deviation 5.0

I am having the same issue. how do I renew file system? also when I turn the tx back on it still says version 4.0.1

17 May 2017 05:05 #62381 by ticfifty

Replied by ticfifty on topic Protocol mismatch after upgrading to deviation 5.0

never mind, I fixed it. guess I was working too late at night and not thinking right.

Time to create page: 0.087 seconds

Force desktop display