Foxtech NAGA PRO, User Manual

Page: 70 / 75

NAGA PRO User Manual
66
Solution:
Correctly calibrate the acceleration, power off the flight controller after calibration,
reconnect, and calibrate the level,this step is very important. Assemble the GPS correctly,
make sure the GPS is fixed, and the arrow of the GPS and the arrow of the flight controller
should be the same. If the flight controller and GPS are integrated, that is to say, when moving,
GPS and flight controller are together, and you cannot move one of them. Correctly calibrate
the compass. If GPS is added, pay attention to calibrate the dual compass correctly.
2. Compass variance
The cause of the problem:
If the firmware is updated to version 3.3.3 or above and GPS is
added, the above problems will be encountered during debugging. Compass variance means:
compass movement deviation. It means that the direction of the built-in compass of the flight
controller and the GPS external compass are deviated and inconsistent.
Solution: The GPS arrow is the same as the flight controller arrow. Fix it. Do not move the
GPS or flight controller alone. The flight controller and GPS must be regarded as one. Do not
move one of them alone. Re-calibrate the magnetic compass.
3. Bad Accel Health solution
The cause of the problem:
the design of the IMU2 power supply of the flight controller is
defective, and the low temperature failure occurs in the environment below 5℃. Too low
temperature will cause IMU2 to report an error and cause unhealthy acceleration.
Solution: The solution is to disable IMU2, which is to set "INS_USE2"to 0 in "Configuration
debugging/All parameter list". If you open the "Configuration debugging/all parameter list",
there is no such parameter, please find the "INS_SPIC" parameter, and change it to 5. If the
acceleration error is still reported after this method is operated, please re-calibrate the
magnetic compass.
4. Check board voltage solution
The cause of the problem:
If you update the firmware of multirotor or fixed-wing version 3.5
or higher, and plug USB into the computer for debugging, you may encounter this error. It is
caused by insufficient USB power supply.
Solution: power by battery (Of course, the battery can not directly supply power to the flight
controller, use an ESC or BEC or ammeter to stabilize it to 5V to supply power to the flight
controller). In the debugging stage, if you must use USB, you can first ignore the function of
voltage detection (found ARM_CHECK in