DJI WOOKONG-motor running while connected to a PC

[Zaidy]

Good day to you all.

I have a bit of a problem with my DJI Wookong and was wondering if anyone else had experienced the same issue

While connected to a PC and the Motor output indicator clearly stating motor output is OFF, I was calibrating my TX and the motors all 8 of them started (when both sticks are in the lower extreme corners out) and I can shut them down (if I position the sticks in the lower extreme corners in) , thankfully the props were off !! so no injury or damage there !
This only occurs on my Octo and NOT on the the S800evo which has a DJI Wookong as well!!! :dread:


Any help advice or suggestions are gratefully received.

Thank you

Zaidy

 

[Benjamin Kenobi]

You performed a CSC and the motors started. Sounds like that was the problem. Just calibrate slightly differently next time without accidentally doing the CSC movement. Just do one stick at a time.

 

[Zaidy]

Hi Benjamin, many thanks for your reply and advice. The issue I have is it only happens to one of the two wookongs I have ! The motors should not come on at all whitest connect to a PC, especially when the display clearly states that the MC output is OFF no matter what. It gives a false sense of security!!!

So I thought there might be a way of resetting the Wookong and somehow make it behave like the other DJI products whilst connected to a computer !!

Ah well, fingers crosses for the test flight !
thanks

 

[Benjamin Kenobi]

True, it shouldn't come on whilst connected. But a few people mention odd errors when using WKM for an OCTO setup. Does it happen everytime you do the same movement during the calibration? Sure it's connected properly?

 

[Zaidy]

Yes Ben it does happen every time but like I mentioned before I can stop it by going opposite sticks in !! I tried it on the other unit and it does not do it !! I even reverted back to default settings an still doing the same !! very confusing :-/ Might try and contact DJI !
I thought I better ask just in case somebody came across the same issue, if not then its a warning to all it could happen!!

 

[ZAxis]

We have had an odd problem with our Coaxial Octo that was only fixed by dropping back from firmware 5.26 to 5.16, losing bluetooth and motor test facilities. If you are on v5.26 then do try dropping back to v5.16 or possibly 5.20 and then perhaps upgrading(??) through to v5.24 to see if the problem disappears and reappears.

andy

 

[Zaidy]

We have had an odd problem with our Coaxial Octo that was only fixed by dropping back from firmware 5.26 to 5.16, losing bluetooth and motor test facilities. If you are on v5.26 then do try dropping back to v5.16 or possibly 5.20 and then perhaps upgrading(??) through to v5.24 to see if the problem disappears and reappears.

andy

Thanks Andy, Will have to do something !! will start looking into going back to 5.16/5.20 and see what is what !