• Inhaltsverzeichnis

  1. ErrorCodes of the NaviControl
     1. 0 "No Error"
     2. 1 "FC not compatible "
     3. 2 "MK3Mag not compatible "
     4. 3 "no FC communication "
     5. 4 "no MK3Mag communication "
     6. 5 "no GPS communication "
     7. 6 "bad compass value"
     8. 7 "RC Signal lost "
     9. 8 "FC spi rx error "
     10. 9: "ERR: no NC communication"
     11. 10 "ERR: FC Nick Gyro"
     12. 11 "ERR: FC Roll Gyro"
     13. 12 "ERR: FC Yaw Gyro"
     14. 13 "ERR: FC Nick ACC"
     15. 14 "ERR: FC Roll ACC"
     16. 15 "ERR: FC Z-ACC"
     17. 16 "ERR: Pressure sensor"
     18. 17 "ERR: FC I2C"
     19. 18 "ERR: Bl Missing"
     20. 19 "Mixer Error"
     21. 20 "FC: Carefree Error"
     22. 21 "ERR: GPS lost"
     23. 22 "ERR: Magnet Error"
     24. 23 "Motor restart"
     25. 24 "BL Limitation"
     26. 25 "GPS range"
     27. 26 "ERR:No SD-Card"
     28. 27 "ERR:SD Logging aborted"
     29. 28 "ERR:Flying range!"
     30. 29 "ERR:Max Altitude"
  2. ErrorCodes of the FlightControl
     1. HardwareError 1:1
     2. HardwareError 1:2
     3. HardwareError 1:4
     4. HardwareError 1:8
     5. HardwareError 1:16
     6. HardwareError 1:32
     7. HardwareError 1:64
     8. HardwareError 1:128

ErrorCodes of the NaviControl

page under translation, please be patient

Representation in the virtual display:

Representation on the Jeti Box:

0 "No Error"

No Error

1 "FC not compatible "

Cause: The Flight Control software is not compatible to the software version of the NaviControl.

Solution:

• Software-Update

2 "MK3Mag not compatible "

Cause: The software of the MK3MAG is not compatible with the software version of the NaviControl.

Solution:

• Software-Update

3 "no FC communication "

Cause: The NaviControl has no communication with the Flight Control

Solution:

• Check the resistance (tr. note: with a multimeter) of connections (6-pins AND 10-pins flat cables) and the solder points on the pads

4 "no MK3Mag communication "

Cause: The NaviControl has no communication with the MK3Mag

Solution:

• Test the connection
• The green LED on the MK3MAG must be lit or flashing

5 "no GPS communication "

Cause: The NC has no communication to the GPS

Solution:

• Check connection
• The green LED on the MKGPS must be on or flashing

• If you use a new MK-GPS-Module (LEA-6S-0-001), the NC-firmware mus be at least V0.26g NC 0.26

6 "bad compass value"

Cause: The compass-value is invalide

Solution:

• Calibrate the MK3Mag

7 "RC Signal lost "

Cause: No RC-Signal

Solution:

• turn on transmitter
• check channel or binding

• check receiver setting in the KopterTool

8 "FC spi rx error "

Cause: the NC has noch communication via SPI to the FC

Solution:

• Check the SPI connection (6-pole and 10-pole ribbon cable) and the pins on FC and NC

9: "ERR: no NC communication"

Cause: The communication between FC and NC was suddenly interrupted

Solution:

• Check the flat cabled between FC and NC

10 "ERR: FC Nick Gyro"

Cause: the analoque sgyro ensor signal is not in the expected range during calibration (between 150 and 850)

The value is shown in the virtual display in brackets (xx)

Solution:

• calibrate sensors again
• check the soldered connections on the Gyro

11 "ERR: FC Roll Gyro"

Cause: the analoque gyro sensor signal is not in the expected range during calibration (between 150 and 850)

The value is shown in the virtual display in brackets (xx)

Solution:

• calibrate sensors again
• check the soldered connections on the Gyro

12 "ERR: FC Yaw Gyro"

Cause: the analoque gyro sensor signal is not in the expected range during calibration (between 150 and 850)

The value is shown in the virtual display in brackets (xx)

Solution:

• calibrate sensors again
• check the soldered connections on the Gyro

13 "ERR: FC Nick ACC"

Cause: the analoque ACC sensor signal is not in the expected range during calibration (between 150 and 850)

The value is shown in the virtual display in brackets (xx)

Solution:

• calibrate sensors again
• check the soldered connections on the sensor

14 "ERR: FC Roll ACC"

Cause: the analoque ACC sensor signal is not in the expected range during calibration (between 150 and 850)

The value is shown in the virtual display in brackets (xx)

Solution:

• calibrate sensors again
• check the soldered connections on the sensor

15 "ERR: FC Z-ACC"

Cause: the analoque ACC sensor signal is not in the expected range during calibration (between 150 and 850)

The value is shown in the virtual display in brackets (xx)

Solution:

• calibrate sensors again
• check the soldered connections on the sensor

16 "ERR: Pressure sensor"

Cause: the analoque pressure sensor signal is not in the expected range during calibration

The MikroKopter might be in too high altitude above sea level. (more than 1000-1500m)

Solution:

• check connection to the sensor
• was the sensor soldered the wrong way?

• See here: testing the sensor

17 "ERR: FC I2C"

Cause: the I2C communication to the BL-Ctrls is disturbed

Solution:

• check supply of the BL-Ctrls
• check I2C-cables (mixed C and D?)
• check addresses of the BL-Ctrls
• disconnect single BL-Ctrls to find one defective

18 "ERR: Bl Missing"

Cause: one BL-Ctrl was not found, but it is used in the mixer table

Solution:

• check supply of the BL-Ctrls
• check addresses of the BL-Ctrls

• Check the MixerTable

19 "Mixer Error"

Cause: there are more BL-Ctrls connected than expected

Solution:

• Check the MixerTable. Maybe a Hexa is selected in a Okto

20 "FC: Carefree Error"

Cause: The function CareFree is used, but the value of the Mk3Mag is invalid

Solution:

• Check MK3Mag and NC
• Calibrate compass

21 "ERR: GPS lost"

Cause: The GPS-Signal was lost during flight (below 4 Satelites)

22 "ERR: Magnet Error"

Cause: The magnetic field of the compass-sensor is 15% different to the magentic field during calibration.

Solution:

• remove magnetic disturbing source (Cables, Buszzer,...)

• general points to the magnetic disturbtions: here

• Calibrate compass - use the new method!

See also: MagnetError

23 "Motor restart"

• One BL-Controller tries to restart the motor
• motor blocked od defect motor cable

24 "BL Limitation"

• A BL-Controller is in limitation - either overtemperature or overcurrent

25 "GPS range"

• The aimed waypoint is out of range and will not be reached
• the distance between Home-Position and the waypoint is larger than 250m (or the max-range of the NC-license)
• set the waypoint closer or start from a closer position

26 "ERR:No SD-Card"

• The option "No flight without SD-Card" is activated but there is no SD-card in the NC

27 "ERR:SD Logging aborted"

• The option "No flight without SD-Card" is activated and there were problems with the Log-file
• maybe contact problems od the SD-card

28 "ERR:Flying range!"

• in the "SETTINGS.INI" (SD-card in the NC) the parameter "MAX_FLYING_RANGE = xxx" is set and the range is exceeded.
• set this parameter to zero if it is not needed

29 "ERR:Max Altitude"

• in the "SETTINGS.INI" (SD-card in the NC) the parameter "MAX_FLYING_ALT" is set and the altitude is exceeded.
• NC with a commerciial license will uses "emergency gas" when the altitude goes 10m above this value to bring it back into the allowed range.
• set this parameter to zero if it is not needed

ErrorCodes of the FlightControl

(if no NC is connected)

HardwareError 1:1

Problems with the sensor: Gyro Nick

HardwareError 1:2

Problems with the sensor: Gyro Roll

HardwareError 1:4

Problems with the sensor: Gyro Gier

HardwareError 1:8

Problems with the sensor: ACC Nick

HardwareError 1:16

Problems with the sensor: ACC Roll

HardwareError 1:32

Problems with the sensor: ACC Z

HardwareError 1:64

Problems with the sensor: air pressure

HardwareError 1:128

Problems with the sensor: compass (not calibrated?)

---

KategorieAnleitung