Reason:

• The installed software versions in your FlightCtrl and NaviCtrl are different

Remedy:

• Install the same versions (numbers) in your FlightCtrl and NaviCtrl (Download)

INFO Applies only to older NaviCtrl V1.1 (red) with external "MK3Mag" Modul!

Reason:

• The software on your MK3Mag is not compatible with the Software-Version on your NaviCtrl.

Remedy:

• Software-Update Mk3Mag (Download)

Reason:

• The NaviCtrl has no communication / connection to FlightCtrl

• After a faulty update Software is deleted on the FlightCtrl

Remedy:

• Update the software on your FlightCtrl (connect the MKUSB directly with the FlightCtrl)

• Check power supply to FlightCtrl

• Check / exchange the 6- AND 10-pol ribbon cable between FlightCtrl/NaviCtrl

• Check the soldered pin headers for contact / damage

Reason:

• No communication between compass and NaviCtrl/FlightCtrl

Remedy:

• Check connection between NaviCtrl / compass (Molex cabel FC/Navi<->Kompass not connected / damaged)

• Eventually interference by other hardware (e.e. Gimbal, Video transmitter etc. - to close to your compass)

• MK3Mag: Pin headers too short or oxidized (the green LED on your !MK3Mag must be lit or blinking)

Reason:

• No communication from GPS to NaviCtrl/FlightCtrl

or

• You use the button "MKGPS" in the KopterTool -> The data is diverted from the copter to the PC

Remedy:

• Check/change molex cable between NaviCtrl/FlightCtrl

• The green LED on your MKGPS must be lit or blinking

• install the latest software on your NaviCtrl/FlightCtrl

• close the GPS-window in your KopterTool

Reason:

• The compass value is invalid

Remedy:

• Recalibrate the compass and check the values (Manual)

• If the message occurs in flight or if the compass has already been calibrated correctly,
  the compass sensor may have a defect.
  Then please contact the MikroKopter-support: support@hisystems.de

Reason:

• No reception / signal from the receiver to the FlightCtrl
  Info-Beepton: signal loss

Remedy:

• Switch on transmitter

• Check connection cable between receiver / FlightCtrl

• Bind receiver with remote control and check settings (sum signal)

• Set correct receiver in the KopterTool

INFO Applies only to older single module NaviCtrl and FlightCtrl (not FlightCtrl V3)

Reason:

• No "SPI"-communication between NaviCtrl and FlightCtrl

Remedy:

• Check / exchange the 6- AND 10-pol ribbon cable between FlightCtrl/NaviCtrl

• Check the soldered pin headers for contact / damage

Reason:

• Communication between FlightCtrl and NaviCtrl suddenly interrupted
  Info-Beepton: lost communication between FC and NC

Remedy:

• Check / exchange the 6- AND 10-pol ribbon cable between FlightCtrl/NaviCtrl

• Check the soldered pin headers for contact / damage

Reason:

• The analog sensor signal of the Nick gyro was out of tolerance during calibration
  The value must be between 1500 and 8500. This can be checked in the KopterTool
  (Button -> FlightCtrl / in the virtual display under "Gyro-Sensor" - the value in brackets)

Remedy:

• Recalibrate gyros - Important: the copter must stand still!
• Check solder joints to the gyro

• If the error is displayed permanently and repeatedly, there will be a defect on the gyro.
  Then please contact the MikroKopter-support: support@hisystems.de

Reason:

• The analog sensor signal of the Roll gyro was out of tolerance during calibration
  The value must be between 1500 and 8500. This can be checked in the KopterTool
  (Button -> FlightCtrl / in the virtual display under "Gyro-Sensor" - the value in brackets)

Remedy:

• Recalibrate gyros - Important: the copter must stand still!
• Check solder joints to the gyro

• If the error is displayed permanently and repeatedly, there will be a defect on the gyro.
  Then please contact the MikroKopter-support: support@hisystems.de

Reason:

• The analog sensor signal of the Yaw gyro was out of tolerance during calibration
  The value must be between 1500 and 8500. This can be checked in the KopterTool
  (Button -> FlightCtrl / in the virtual display under "Gyro-Sensor" - the value in brackets)

Remedy:

• Recalibrate gyros - Important: the copter must stand still!
• Check solder joints to the gyro

• If the error is displayed permanently and repeatedly, there will be a defect on the gyro.
  Then please contact the MikroKopter-support: support@hisystems.de

Reason:

• The analog sensor signal of the ACC acceleration sensor (for Nick) was out of tolerance during calibration
  The value must be between 300 and 750. This can be checked in the KopterTool
  (Button -> FlightCtrl / in the virtual display under "ACC-Sensor" - the value in brackets)

Remedy:

• Recalibrate gyros - Important: the copter must stand still!
• Check solder joints to the gyro

• If the error is displayed permanently and repeatedly, there will be a defect on the gyro.
  Then please contact the MikroKopter-support: support@hisystems.de

Reason:

• The analog sensor signal of the ACC acceleration sensor (for Roll) was out of tolerance during calibration
  The value must be between 300 and 750. This can be checked in the KopterTool
  (Button -> FlightCtrl / in the virtual display under "ACC-Sensor" - the value in brackets)

Remedy:

• Recalibrate gyros - Important: the copter must stand still!
• Check solder joints to the gyro

• If the error is displayed permanently and repeatedly, there will be a defect on the gyro.
  Then please contact the MikroKopter-support: support@hisystems.de

Reason:

• The analog sensor signal of the ACC acceleration sensor (for Z-axis) was out of tolerance during calibration
  The value must be between 300 and 750. This can be checked in the KopterTool
  (Button -> FlightCtrl / in the virtual display under "ACC-Sensor" - the value in brackets)

Remedy:

• Recalibrate gyros - Important: the copter must stand still!
• Check solder joints to the gyro

• If the error is displayed permanently and repeatedly, there will be a defect on the gyro.
  Then please contact the MikroKopter-support: support@hisystems.de

Reason:

• The analog sensor signal from the air pressure sensor was out of tolerance during calibration

Remedy:

• Kopter is located outside of the air pressure measuring range

  • FlightCtrl V2.1 -> Measuring range up to 1500m height

  • FlightCtrl V2.5 / V3.0 -> Measuring range up to 5000m height

• For manual flights above the measuring range => Deactivate the air pressure sensor in the settings

• Air pressure sensor is defective or a connection contact broken (only for FlightCtrl V1.x/V2.1)

Reason:

• The I2C communication to the BL-Ctrls is disturbed

Remedy:

• Check supply of the BL-Ctrls
• Check I2C-cables

  • Molexkabel FC<->BL-Ctrl = Loose connection / disconnection

  • For self-soldered cables = C to C / D to D check
• Check addresses of the BL-Ctrls (Double occupancy / missing address)

• Disconnect single BL-Ctrls to find one defective
  (only possible with single controllers - not possible with V3 BL distributors)

• Until FlightCtrl V2.5

  • Check 10pol. ribbon cable from FlightCtrl to NaviCtrl

  • If something else is connected on the 10pol pin stripe, remove it
    (on this 10pol. pin stripe we also have the I2C-Bus)

Reason:

• One (or more) BL-Ctrl was not found, but it is used in the mixer table

Remedy:

• Check supply of the BL-Ctrls
• Check addresses of the BL-Ctrls (Double occupancy / missing address)

• Wrong mixer set - check Mixer table

Reason:

• There are more BL-Ctrls connected than expected

Remedy:

• Check addresses of the BL-Ctrls (Double occupancy / missing address)

• Wrong mixer set - check Mixer table

Reason:

• The CareFree function is activated even though there is no valid compass value
  Info-Beep: Compass failure in flight

Remedy:

• Compass is not calibrated / recalibrated

• Up to FlightCtrl V2.5 -> no NaviCtrl and/or no Kompass connected

• FlightCtrl V3.0 -> no Kompass connected

Reason:

• The GPS-Signal was lost during flight

• Less than 4 satellites are received
  (at least 6 satellites are needed)

Remedy:

• Avoid shadowing of the GPS
  (Tall trees, houses etc.)

• Check if disturbing solar storms prevail during the flight (Link)
  if available -> fly at a later date

• If problem persists, replace GPS

Reason:

• The magnetic field of the compass-sensor is 15% different to the magnetic field during calibration

Remedy:

• Eliminate magnetic sources of interference

• Search for another starting place (Do not start from buildings or other metallic substrates)

• If necessary, shorten the incorrectly laid power cable, buzzer, etc. and twist it

• Recalibrate the compass and check the values (Link)

Reason:

• A BL-Ctrl tries to restart the connected motor
• Motor is blocked
• Cable break on the motor

Remedy:

• Regularly check engines for smooth running
• Avoid landing in tall grass
• Route motor cables without sharp creases

Reason:

• A BL regulator goes into the power limit
  • either overcurrent
  • or overtemperature

Remedy:

• Combination of motor / propeller does not fit together optimally
• Total weight of the copter is too high

• Heat accumulation at the BL-Ctrl -> ensure ventilation

Reason:

• The approached waypoint is out of reach and will not be reached

Remedy:

• Place waypoints within the possible range

• Purchase a license with a longer range for WP-flight (Link)

Reason:

• There is no SD-Karte in your FlightCtrl V3 / NaviCtrl

Remedy:

• Option "No flight without SD-Card"
  If this option is activated and there is no SD-card (max.2GB/FAT16) in your FlightCtrl V3.0 / NaviCtrl,
  or the SD-card is not inserted correctly you will see this error and you can not start the copter
  

  • Remedy: Insert SD card (max.2GB/FAT16)
    

  or
• Deactivate the Option "No flight without SD-Card"

Reason:

• The Option "No flight without SD-Card" is set in the settings active and the logging was stopped

Remedy:

• maybe Contact problems with the SD card => Remove the card and plug it in again

• SD-Karte is not ok => change the SD-card (max. 2GB / FAT16)

• Write speed of the SD card is maybe too slow => change the SD-card (max. 2GB / FAT16)

Reason:

• The copter has reached the maximum possible flight radius

Remedy:

• Normal Flight

  • A flight radius is set under "Navi-Ctrl2" -> "Max.Flying Range"
    Change the radius (1m-247m) or deactivate this function (0) to fly so far away as you want

• Waypoint flight

  • The max. possible flight range for a waypoint flight is reached

  • A flight radius is set under "Navi-Ctrl2" -> "Max.Flying Range" and reached

    • Disable the "Max.Flying Range" (0) to fly the max. possible range for a waypoint flight (see INFO)

• INFO: The range for a waypoint flight is limited !

  • Without license -> you can fly to waypoints in a flight range up to 250m around the place where you start

  • With license -> you can fly to waypoints in a flight range the license allows around the place where you start

    • Buy a bigger range: Link

Reason:

• In the settings under "Altitude" a limit is set under "Max.Altitude" and this limit is reached

Remedy:

• Change the value under "Max.Altitude" (1-247m) or deactivate it (0) to fly so high as you want

Reason:

• In the settings under "Misc" the function "no start without GPS fix" is activated

and

• there s no GPS fix when you will start the motors => so you can NOT start themotors

Remedy:

• Wait until the GPS receive enough satellites (min.6) and the GPS fix is there (It will not work indoor!)

• Deactivate the function "no start without GPS fix"
  INFO: If you deactivate this function you can start the copter also without GPS fix <<BR> BUT: The copter did not have a Homeposition and the functions ComingHome or the emergency functions FailSafe / AkkuSafe will NOT work !

Reason:

• The sensor (compass) on your copter is not calibrated

Remedy:

• calibrate the compass (Link)

Reason:

• A BL controller failed the self-test after power up and flashes red

Remedy:

• Disconnect the battery from the copter and reconnect it

• If the error persists, the controller has a defect
  Then please contact the MikroKopter-support: support@hisystems.de

Reason:

• The externally connected compass does not respond

Remedy:

• Check the molex cable between compass and FlightCtrl

• The molex cable between compass and FlightCtrl is too long

• Error remains with new short molex-cable => Compass has a defect -> exchange

Reason:

• The compass returns invalid data

Remedy:

• Compass has a defect -> exchange

Reason:

• "Failsafe" points were set via the KopterTool (MAP) and stored in the Kopter.
  During a "signal lost" or if the battery is empty the copter will fly automatically to the next set Failsafe-Position

INFO Message only if you use a redundant electronic!

Reason:

• Redundancy is not active

Remedy:

• Molex cable between BL-Ctrl board (connection->"UART") and Slave-FlightCtrl (connection->"BL") is not there or has an interruption

• Molex cable between Master-FlightCtrl and Slave-FlightCtrl (connection->"CAN" is not there or has an interruption

• Be sure that the right software for Master and Slave FlightCtrl is installed
  and the settings are in both the same

INFO Message only if you use a redundant electronic!

Reason:

• In the settings under "User" the "Parameter6" (master test Motor 1 off) /
  and / or "Parameter7" (master test I2C Bus failure) is set.
  => If you set here e.g. a switch for a Parameter you can switch this function ON/OFF

Remedy:

• Switch the function OFF

• Deactivate the function under "Parameter6/7" (0)

Reason:

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

Remedy:

• Maybe a loose contact / break in the Molex cable between GPS <-> FlightCtrl V3 / NaviCtrl

Reason:

• Interruption at the Canbus (connection "CAN" -> FlightCtrl V3)

Remedy:

• Possible loose contact / break in the Molex cable on the Can Bus

Reason:

• The 5V supply for the receiver or external components is missing

Remedy:

• Recom/Traco on your FlightCtrl is damaged

• Short circuit on 5V line

Reason:

• The supply voltage is below 5V

Remedy:

• Recom/Traco on FlightCtrl defective

• Maybe the connected receiver or a servo connected to the Tiny servo adapter or an external component not OK, defective

INFO The error message can also be displayed as "0x00 0x40"!

Reason:

• ACC not calibrated
  

Remedy:

• Calibrate ACC => Link

Reason:

• The input IO1 on the FlightCtrl V3 has been shorted and the motors are off immediately

Remedy:

• This is a security feature that needs to be unlocked by license
  In addition, the value "IO1_FUNCTION" (on the SD card in the "SETTINGS.INI") must be activated (9).
  If you then short the input "IO2", the motors will stop immediately.

Reason:

• A Flight Zone was set via the KopterTool (MAP) and stored in the Kopter
  The copter is outside the predetermined flight zone

Remedy:

• The copter was started outside the registered flight zone => Start your copter inside the flight zone

• By e.g. strong wind, the copter was pressed in flight over the flight zone => If possible, fly back

Reason:

• In the settings under "Misc" the function "not start without defined FlyZone" is activated

• and a Flight Zone was not set via the KopterTool (MAP) and stored in the Kopter

Remedy:

• Create the needed Flight Zone via the KopterTool (MAP) and store it into the Kopter

or

• deactivate the function "not start without defined FlyZone"

Reason:

• Every time when you connect ta Lipo to your copter you have to activate/calibrate the copter (throttle up + yaw left)
  You can also get this message if the copter is moving or wobbling during this calibration.

Remedy:

• Place the copter on a firm surface during calibration
• Wait until the copter stops moving / wobbling
• Recalibrate

Reason:

• An externally connected GNSS module has lost its fix

Remedy:

• Wait until the ext. Module has a GPS fix again

INFO

• These error codes are displayed when no NaviCtrl is connected. Typically, a hardware error is present here.
  Then please contact the MikroKopter-support: support@hisystems.de

HardwareError 1:1

Reason:

• Problem with sensor: Gyro Nick

Remedy:

• Replace Nick Gyro => Contact MikroKopter support for a repair: support@hisystems.de

HardwareError 1:2

Reason:

• Problem with sensor: Gyro Roll

Remedy:

• Replace Roll Gyro => Contact MikroKopter support for a repair: support@hisystems.de

HardwareError 1:4

Reason:

• Problem with sensor: Gyro Yaw

Remedy:

• Replace yaw Gyro => Contact MikroKopter support for a repair: support@hisystems.de

HardwareError 1:8

Reason:

• Problem with sensor: ACC Nick

Remedy:

• Replace ACC sensor => Contact MikroKopter support for a repair: support@hisystems.de

HardwareError 1:16

Reason:

• Problem with sensor: ACC Roll

Remedy:

• Replace ACC sensor => Contact MikroKopter support for a repair: support@hisystems.de

HardwareError 1:32

Reason:

• Problem with sensor: ACC Z

Remedy:

• Replace ACC sensor => Contact MikroKopter support for a repair: support@hisystems.de

HardwareError 1:64

Reason:

• Problem with air pressure sensor

Remedy:

• Replace air pressure sensor => Contact MikroKopter support for a repair: support@hisystems.de

HardwareError 1:128

Reason:

• Problem with compass or CareFree

Remedy:

• recalibrate the compass

• Replace compass => Contact MikroKopter support for a repair: support@hisystems.de