DeepE
lvl.1
Flight distance : 4544 ft
South Africa
Offline
|
Dear DJI
My avata displays the error "No M Mode UAV to Far High" when trying to start the motors of the drone by double pressing the stop start button on my fpv remote controller 2.
The avata at this time is on the ground, at zero metres of altitude right infront of me and definately not too far away. Its also not too high either.
I have researched this issue and tried resolving it myself. In order to assist you with the information you require to assist me, let me provide the following additional info.
1. The Avata firmware has been been updated to the latest version as of this posting 21 Jan 2024.
2. I am using the googles V2.
3. I am using the fpv remote coontroler 2
4. All the above has been bound to my account.
5. I am not flying in GEO locked zone - I checked the DJI webiste for South Africa - The longitude and latitude for the test - 33°52'53.4"S 18°39'54.5"E
6. The Avata flies normal in Sport and Normal mode, it takes offf and can be controlled with no issues or any warnings appearing at any stage
7. The issue only comes in when switching from N mode (or S Mode) to M mode, while the avata is stationary on the ground and the rotors are not spinning. If one tried to start the motors by double pressing the stop start button in quick succession the avata rotors give a short rotation but then stops turning and jumps back to N mode by itself in low power state.
-- When trying to swtich from N mode (or S mode ) to M Mode while in the air the avata reverts to N Mode and does not switch into M mode. No error messages are then displayed
8. I have restarted the avata and goggles as well as the coontroler several times, with no success.
9. Important to note that i do press the start/stop button in very quick sucession and has also tried pressing it 3 times very quickly in a row as suggested by some members on the forum - all with exactly the same result as described above.
PS:
But here is the snag. I have 2 avata's. Both bound to my account.
The other one arms and flies when switched to M mode as described above, with no error messages or problems. They both being tested at the same location with exactly the same Goggles and remote controler. The one fails to start and take off (as described above) while the other starts and takes off with no problems when swtiched to M mode.
Please help, i am out of solutions for this weird problem
|
|