Shadetail
lvl.2
Flight distance : 785125 ft
Croatia
Offline
|
TL;DR: After experiencing unexpected behavior with my new DJI FPV drone controller, I discovered it has limited input range compared to the old one, either due to different firmware versions or manufacuring error. I'm considering downgrading the firmware to resolve this but seek advice on the process, potential issues, and whether this behavior is known or intentional.
I purchased the DJI FPV drone combo at launch. Two years later, the controller began exhibiting an occasional twitch on the yaw axis, causing unexpected rotations. Initially, I suspected the drone, but experiencing the same issue in PC simulators indicated a hardware defect in the controller. I bought a new controller, and noticed it behaved differently in the Velocidrone simulator, achieving less than half my rotation rates.
Upon further investigation using x360ce to read the raw inputs, I found that the old controller would appropriately send inputs ranging from -32768 to +32767 which is a full range of a 16 bit integer variable, while the new controller was only sending inputs between values of -21002 and +20990. The rest of the way until the maximum deflection behaves like a sort of deadzone, so the new controller keeps sending +20990 the rest of the way, rather than increasing all the way to +32767 as it reaches maximum deflection.
I confirmed this happens with the real life DJI FPV drone too by testing without props in manual mode, where the new controller exhibited the same outer deadzone effect. Motors would spin up to roughtly half of their max speed at 64% of the stick deflection, and then just stay at that speed even as the stick deflection increases to 100%.
I noticed controllers have different firmware versions:
New controller: 02.00.09.00
Old controller: 01.02.00.00
I'm considering a firmware downgrade for the new controller in hopes that could resolve the issue. As I understand, that would make the controller Avata-incompatible, but I don't own Avata so I'm ok with that.
Questions:
1. What causes this behavior?
2. Is it a known issue or intentional design?
3. Can I downgrade the firmware on the new controller?
4. How would I do so?
5. Are there any other potential downsides to downgrading firmware?
|
|