Unterschiede zwischen den Revisionen 5 und 48 (über 43 Versionen hinweg)
Revision 5 vom 30.08.2010 10:56
Größe: 5310
Autor: HolgerB
Kommentar: translation
Revision 48 vom 12.12.2016 13:21
Größe: 11051
Autor: HolgerB
Kommentar: 44 & 45
Gelöschter Text ist auf diese Art markiert. Hinzugefügter Text ist auf diese Art markiert.
Zeile 1: Zeile 1:
||<tablewidth="720px" tablestyle="text-align: center;"bgcolor="#ffffa0"> {{http://mikrokopter.de/images/deu.gif}} Seite auf [[ErrorCodes|deutsch]] ||<bgcolor="#ffffa0"> {{http://mikrokopter.de/images/fra.gif}} Page en [[fr/ErrorCodes|francais]] ||


see also (possibly insert links to other related sites ...)
{{{#!wiki MK_Nav
||<class="MK_Nav_Header">ErrorCodes||
}}}

{{{#!wiki MK_select1

 * {{http://mikrokopter.de/images/deu.gif}} [[ErrorCodes|deutsch]]
 * {{http://mikrokopter.de/images/fra.gif}} [[fr/ErrorCodes|francais]]
}}}

<<BR>><<BR>>
Zeile 12: Zeile 20:
[[http://gallery.mikrokopter.de/main.php/v/tech/KopterToolStatus2.gif.html|{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=63286}}]] [[http://gallery.mikrokopter.de/main.php/v/tech/KopterToolStatus2.gif.html|{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=63286|http://gallery.mikrokopter.de/main.php/v/tech/KopterToolStatus2.gif.html}}]]
Zeile 16: Zeile 24:
[[http://gallery.mikrokopter.de/main.php/v/tech/JetiError.jpg.html|{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=63251}}]]


== 0 "No Error" ==


No Error
[[http://gallery.mikrokopter.de/main.php/v/tech/JetiError.jpg.html|{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=63251|http://gallery.mikrokopter.de/main.php/v/tech/JetiError.jpg.html}}]]
Zeile 25: Zeile 27:
Cause: The Flight Control software is not compatible to the software version of the NaviControl. 

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

Solution:
Zeile 31: Zeile 34:

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

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

Solution:
Zeile 38: Zeile 41:
Zeile 41: Zeile 43:
Solution:  Solution:
Zeile 44: Zeile 47:
== 4 "no MK3Mag communication " ==

Cause: The NaviControl has no communication with the MK3Mag

Solution: 
== 4 "no compass communication " ==
Cause: The NaviControl has no communication with the compass

Solution:
Zeile 50: Zeile 53:
 * The green LED on the MK3MAG must be lit or flashing  * MK3Mag: The green LED on the MK3MAG must be lit or flashing
Zeile 53: Zeile 56:
Zeile 57: Zeile 59:
Zeile 59: Zeile 62:
 * If you use a new MK-GPS-Module (LEA-6S-0-00'''1'''), the NC-firmware mus be at least V0.26'''g''' [[en/Firmware-0.86#Bugfixes|NC 0.26]]
Zeile 61: Zeile 65:
Zeile 64: Zeile 67:
Solution:
 * Calibrate the MK3Mag
Solution:

 * [[en/MK3Mag#Calibration|Calibrate the MK3Mag]]
 * if the Error occures during flight or if the compass was already calibrated: Then the magnet-sensor might have a problem and you should contact HiSystems
Zeile 68: Zeile 73:
Zeile 71: Zeile 75:
Solution:  Solution:
Zeile 79: Zeile 84:
Solution:  Solution:
Zeile 82: Zeile 88:
== 9 not used == == 9: "ERR: no NC communication" ==
Cause: The communication between FC and NC was suddenly interrupted

Solution:

 * Check the flat cabled between FC and NC
Zeile 89: Zeile 100:
Solution:  Solution:
Zeile 98: Zeile 110:
Solution:  Solution:
Zeile 107: Zeile 120:
Solution:  Solution:
Zeile 116: Zeile 130:
Solution:  Solution:
Zeile 125: Zeile 140:
Solution:  Solution:
Zeile 134: Zeile 150:
Solution:  Solution:
Zeile 139: Zeile 156:
Cause: the analoque pressure sensor signal is not in the expected range during calibration  Cause: the analoque pressure sensor signal is not in the expected range during calibration
Zeile 143: Zeile 160:
Solution:  Solution:
Zeile 146: Zeile 164:
 * See here: [[en/heightsensor#Testing_the_height_sensor|testing the sensor]]  * See here: [[en/heightsensor#Measuring_the_output_voltage|testing the sensor]]
Zeile 152: Zeile 170:
Zeile 161: Zeile 180:
Zeile 163: Zeile 183:
 * Check the [[en/MixerTable|MixerTabelle]]  * Check the MixerTable
Zeile 169: Zeile 189:
 * Check the [[en/MixerTable|MixerTabelle]]. Maybe a Hexa is selected in a Okto
* Check the MixerTable. Maybe a Hexa is selected in a Okto
Zeile 175: Zeile 196:
Zeile 176: Zeile 198:
 * Calibrate MK3Mag  * 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: [[http://www.mikrokopter.de/ucwiki/en/MK3Mag#General_Points|here]]
 * Calibrate compass - use the [[http://www.mikrokopter.de/ucwiki/en/MK3Mag#Calibration|new method]]!

See also: [[en/MagnetError|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 "Waypoint 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 commercial 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

== 30 "No GPS Fix" ==
 * no GPS fix while Motors are starting
 * the option "No Start without GPS-Fix" in the KopterTool is activated

== 31 "compass not calibrated" ==
 * The magnet sensor on the NC s not calibrated
 * (Not for MK3Mag)

== 32 "BL Selftest error" ==
 * One BL-Ctrl reports a selftest error

== 33 "no ext. compass" ==
 * invalid answer of the external compass
 * check cable to the magnet sensor
 * the flat cable on "Debug" might be too long

== 34 "compass sensor" ==
 * the magnet sensor value is invalid
 * the sensor might be defective

== 35 "FAILSAFE pos.! " ==
 * The MK flies to a Failsafe-Position instead of !ComingHome
 * Undervoltage or RC-Lost and a Failsafe-Position is programmed

== 36 "ERR:Redundancy " ==
 * Only for Redundant setups: Redundancy is not working

== 37 "Redundancy test " ==
 * Only for Redundant setups: The Test-Switch is in "Test" position -> the slave controls the MK

== 38 "GPS Update rate" ==
 * The update rate of the GPS module went below a critical value

== 39 "ERR:Canbus" ==
 * Canbus error (only if canbus is used)
 * check Canbus connection between Master/Slave

== 40 "ERR: 5V RC-Supply" ==
 * The 5V supply to external components is missing

== 41 "ERR:Power-Supply" ==
 * The power supply is below 5V

== 42 "ACC not calibr." ==
 * ACC not yet calibrated

== 43 "ERR:Parachute!" ==
 * the input for the parachute function was closed -> the MK switches off

== 44 "ERR:Outside Area ==
 * The MK is outside the defined Flyzone

== 45 "ERR:No Flyzone ==
 * The flyzone is not downloaded into Kopter
 * The flyzone is defined by the Waypoint list
 * in the settings, the option "No flight without Flyzone" is activated

Zeile 179: Zeile 301:

= 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?)

= Beeptones =
 * [[http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=116140&g2_GALLERYSID=4a727a8c25ff2b4a7ca60ab985747261|RC-Signal lost]]
 * [[http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=116144&g2_GALLERYSID=4a727a8c25ff2b4a7ca60ab985747261|Undervoltage - empty Lipo]]
 * [[http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=116132&g2_GALLERYSID=4a727a8c25ff2b4a7ca60ab985747261|Communication between FC and NC during flight]]
 * [[http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=116118&g2_GALLERYSID=4a727a8c25ff2b4a7ca60ab985747261|Compass - communication during flight ore during CareFree]]
 * [[http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=116136&g2_GALLERYSID=4a727a8c25ff2b4a7ca60ab985747261|Flying range]]
 * [[http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=116128&g2_GALLERYSID=4a727a8c25ff2b4a7ca60ab985747261|I2C-Error]]



ErrorCodes of the NaviControl

page under translation, please be patient

Representation in the virtual display:

http://gallery.mikrokopter.de/main.php/v/tech/KopterToolStatus2.gif.html

Representation on the Jeti Box:

http://gallery.mikrokopter.de/main.php/v/tech/JetiError.jpg.html

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 compass communication "

Cause: The NaviControl has no communication with the compass

Solution:

  • Test the connection
  • MK3Mag: 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

  • if the Error occures during flight or if the compass was already calibrated: Then the magnet-sensor might have a problem and you should contact HiSystems

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 "Waypoint 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 commercial 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

30 "No GPS Fix"

  • no GPS fix while Motors are starting
  • the option "No Start without GPS-Fix" in the KopterTool is activated

31 "compass not calibrated"

  • The magnet sensor on the NC s not calibrated
  • (Not for MK3Mag)

32 "BL Selftest error"

  • One BL-Ctrl reports a selftest error

33 "no ext. compass"

  • invalid answer of the external compass
  • check cable to the magnet sensor
  • the flat cable on "Debug" might be too long

34 "compass sensor"

  • the magnet sensor value is invalid
  • the sensor might be defective

35 "FAILSAFE pos.! "

  • The MK flies to a Failsafe-Position instead of ComingHome

  • Undervoltage or RC-Lost and a Failsafe-Position is programmed

36 "ERR:Redundancy "

  • Only for Redundant setups: Redundancy is not working

37 "Redundancy test "

  • Only for Redundant setups: The Test-Switch is in "Test" position -> the slave controls the MK

38 "GPS Update rate"

  • The update rate of the GPS module went below a critical value

39 "ERR:Canbus"

  • Canbus error (only if canbus is used)
  • check Canbus connection between Master/Slave

40 "ERR: 5V RC-Supply"

  • The 5V supply to external components is missing

41 "ERR:Power-Supply"

  • The power supply is below 5V

42 "ACC not calibr."

  • ACC not yet calibrated

43 "ERR:Parachute!"

  • the input for the parachute function was closed -> the MK switches off

44 "ERR:Outside Area

  • The MK is outside the defined Flyzone

45 "ERR:No Flyzone

  • The flyzone is not downloaded into Kopter
  • The flyzone is defined by the Waypoint list
  • in the settings, the option "No flight without Flyzone" is activated


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?)

Beeptones


KategorieAnleitung