Update of from 3.2 goes badly wrong

Hi I have several quads and hex and all running 3.2.  I updates my IRIS+ successfully but when I connected the hex it updated to 3.1.2 and thats backwards I know.  Its not a typo and it won't allow me to try anything else. even via beta.  Then i wondered if that would happen to my other amp 2.6 quad and that did exactly the same.  Cannot use sonar and am very frustrated as to how to get it back to 3.2.

When i finally do manage that how do we stop this happening again on future UPDATES?

Any help and suggestions gratefully received.  Currently having little to no confidence to fly this not knowing what it may toy may not do.

As i am able to interrogate it via Terminal i know its not a typo as 3.2 stopped terminal working.

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –

Replies

  • Here is a log for anyone able to understand them more fully than me.  thanks

    2015-02-11 15-40-03_155.log

    https://storage.ning.com/topology/rest/1.0/file/get/3701932542?profile=original
This reply was deleted.

Activity

Neville Rodrigues liked Neville Rodrigues's profile
Jun 30
Santiago Perez liked Santiago Perez's profile
Jun 21
More…