5310
Kommentar: translation
|
7227
|
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 ...) <<TableOfContents>> |
||<tablewidth="720px" tablestyle="text-align: center;"#ffffa0> {{http://mikrokopter.de/images/deu.gif}} Seite auf [[ErrorCodes|deutsch]] ||<#ffffa0> {{http://mikrokopter.de/images/fra.gif}} Page en [[fr/ErrorCodes|francais]] || see also (possibly insert links to other related sites ...) <<TableOfContents>> |
Zeile 12: | Zeile 11: |
[[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 15: |
[[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|{{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 20: | Zeile 18: |
Zeile 25: | Zeile 21: |
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 28: |
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 35: |
Zeile 41: | Zeile 37: |
Solution: | Solution: |
Zeile 45: | Zeile 42: |
Cause: The NaviControl has no communication with the MK3Mag Solution: |
Cause: The NaviControl has no communication with the MK3Mag Solution: |
Zeile 53: | Zeile 50: |
Zeile 57: | Zeile 53: |
Zeile 61: | Zeile 58: |
Zeile 64: | Zeile 60: |
Solution: * Calibrate the MK3Mag |
Solution: * [[en/MK3Mag#Calibration|Calibrate the MK3Mag]] |
Zeile 68: | Zeile 65: |
Zeile 71: | Zeile 67: |
Solution: | Solution: |
Zeile 79: | Zeile 76: |
Solution: | Solution: |
Zeile 82: | Zeile 80: |
== 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 92: |
Solution: | Solution: |
Zeile 98: | Zeile 102: |
Solution: | Solution: |
Zeile 107: | Zeile 112: |
Solution: | Solution: |
Zeile 116: | Zeile 122: |
Solution: | Solution: |
Zeile 125: | Zeile 132: |
Solution: | Solution: |
Zeile 134: | Zeile 142: |
Solution: | Solution: |
Zeile 139: | Zeile 148: |
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 152: |
Solution: | Solution: |
Zeile 146: | Zeile 156: |
* 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 162: |
Zeile 161: | Zeile 172: |
Zeile 163: | Zeile 175: |
* Check the [[en/MixerTable|MixerTabelle]] | * Check the MixerTable |
Zeile 169: | Zeile 181: |
* 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 188: |
Zeile 176: | Zeile 190: |
* 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]]! == 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 See also: [[en/MagnetError|MagnetError]] |
Zeile 179: | Zeile 218: |
= 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?) |
see also (possibly insert links to other related sites ...)
Inhaltsverzeichnis
-
ErrorCodes of the NaviControl
- 0 "No Error"
- 1 "FC not compatible "
- 2 "MK3Mag not compatible "
- 3 "no FC communication "
- 4 "no MK3Mag communication "
- 5 "no GPS communication "
- 6 "bad compass value"
- 7 "RC Signal lost "
- 8 "FC spi rx error "
- 9: "ERR: no NC communication"
- 10 "ERR: FC Nick Gyro"
- 11 "ERR: FC Roll Gyro"
- 12 "ERR: FC Yaw Gyro"
- 13 "ERR: FC Nick ACC"
- 14 "ERR: FC Roll ACC"
- 15 "ERR: FC Z-ACC"
- 16 "ERR: Pressure sensor"
- 17 "ERR: FC I2C"
- 18 "ERR: Bl Missing"
- 19 "Mixer Error"
- 20 "FC: Carefree Error"
- 21 "ERR: GPS lost"
- 22 "ERR: Magnet Error"
- 23 "Motor restart"
- 24 "BL Limitation"
- 25 "Waypoint range"
- ErrorCodes of the FlightControl
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
6 "bad compass value"
Cause: The compass-value is invalide
Solution:
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!
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
See also: MagnetError
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?)