#acl AdminGroup:read,write,revert All:read {{{#!wiki MK_Nav ||{{attachment:symbols/Help.png}}||Step - HELP||{{attachment:symbols/Help.png}}|| }}} {{{#!wiki MK_select1 * {{http://mikrokopter.de/images/deu.gif}} [[Erstinbetriebnahme/Help|deutsch]] * {{http://mikrokopter.de/images/fra.gif}} [[fr/Erstinbetriebnahme/Help|français]] }}} <> ####################################################################################################################################################################################### <> = Soldered joints and checking wires = A clean and proper assembling and soldering of the Kopter is very important. Only in that way a function without failures can be guaranteed.<
> The cables should not be stripped too far, solder-pads should be used completely and through hole joints should be soldered on both sides. <
><
> Here are some examples of how it is wrong and right: <
><
> [[http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=100062&g2_serialNumber=2|{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=100061&g2_serialNumber=2}}]] [[http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=100067&g2_serialNumber=2|{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=100066&g2_serialNumber=2}}]] [[http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=100072&g2_serialNumber=2|{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=100071&g2_serialNumber=2}}]] <
><
><
> Everything OK? Then it goes back here to Step 1: [[Erstinbetriebnahme/Step1#Step1-1|{{attachment:symbols/Pfeil_rechts.png}}]] <
><
><
> ####################################################################################################################################################################################### <> = Check power distributor for short circuits = If you equip a power distribution board with BL-Ctrl's by yourself you should check afterwards for short circuits.<
> Here you can use either way a multimeter or a continuity tester.<
><
> For that reason that the distributor is a parallel circuit it's enough you measure at one BL-Ctrl.<
> [[http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=99664&g2_serialNumber=1|{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=99667&g2_serialNumber=2}}]] <
><
><
> At this specific points of the BL-Ctrl you should measure: <
><
> [[http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=99635&g2_serialNumber=1|{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=99638&g2_serialNumber=2}}]]<
><
> '''Example view: Measuring points BL-Ctrl in the distributor:''' <
> {{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=74605&g2_serialNumber=1}} While measuring between this points you should __not__ get any shorts (0 Ohm): * '''+''' and '''-''' * '''C''' and '''D''' * '''+''' and '''C''' * '''+''' and '''D''' * '''-''' and '''C''' * '''-''' and '''D''' '''ATTENTION:''' If you measure with a continuity tester (or the diode tester on the multimeter) between "+" and "-" it will beep for a short moment. <
> This is not a short circuit. The short "beeping" is caused throughout the Elkos. <
><
> If there is a short circuit the entire distribution board need to be checked or if necessary completely disassembled.<
> <
><
><
> Everything OK? Then it goes back here to Step 1: [[en/Erstinbetriebnahme/Step1#Step1-1|{{attachment:symbols/Pfeil_rechts.png}}]] <
><
><
> ####################################################################################################################################################################################### <> = I2C error = If you get an '''I2C Error''' displayed in the virtual display mostly you have soldering defects/short circuits at the I2C Bus (C/D) or a defect on a BL-Ctrl.<
> An I2C error is also indicated if the Kopter is powered only by the MK-USB with closed jumper. Here the power supply for the BL-Ctrl is missing.<
> If you have an error like that you shoud go ahead systematically.<
> All BL-Ctrl's in the distributor are connected in parallel circuits. Has a BL-Ctrl now a soldering defect, a short circuit or is defect by itself this effects the whole I2C Bus (distributor). <
><
> To figure out where the I2C Error comes from you need to partially disassemble the distributor and remove parts of them.<
> In the first step you should disconnect from all BL-Ctrl's the I2C connection to the distributor. Here you need to solder out the headers on C and D of each BL-Ctrl. <
> The easiest way is to use desoldering braid. A desoldering sucker shouldn't be used because it can damgage the pads/traces.<
><
> '''To avoid damaging the components throughout solder bridges or other failures you should use a regulated power supply (12V/500mAh).''' <
><
><
> '''Step 1:''' To the distributor (it doesn't matter which one) the BL-Ctrl are soldered on following spots to the I2C Bus: <
> ||'''Example View:''' <
>BL-Ctrl1.2 + Distributor with I2C-Bridges in the distributor||'''Example View:''' <
>BL-Ctrl2.0 + XL-Distributor|| ||{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=99671&g2_serialNumber=2}}||{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=99691&g2_serialNumber=2}}|| <
><
> '''Step 2:''' The connection of the I2C Bus to the distributor is now completely separated from '''__all__''' BL-Ctrl's: <
> ||'''Example View:''' <
>The solder bridges are removed||'''Example View:''' <
>The solder bridges are removed|| ||{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=99681&g2_serialNumber=2}}||{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=99701&g2_serialNumber=2}}|| (At the XL-Distributor a thin piece of cardboard was placed between the contacts to protect it against short circuits) <
><
> '''Step 3:''' Now you need to measure again with a multimeter between the contacts (Like described under ''"Check power distributor for short circuits"'').<
> If there is no short circuit you can connect the distributor back to the FlightCtrl.<
> For that you can take the FlightCtrl from the Kopter.<
> '''Step 4:''' The distributor with the connected FlightCtrl can now be hooked up to the KopterTool and powered.<
> Is everything OK you should see in the virtual display '''"Missing BL-Ctrl:1!!"''' <
><
> If there is still an "I2C error" displayed there is certainly a connection from "C" or "D" to GND (-) or PLUS (+).<
> If you have a distributor with I2C-Bus solder bridges on the distributor you need to remove them and clean the contacts with desoldering braid from solder: <
> ||'''Example View:''' <
>The solder bridges are removed|| ||{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=99686&g2_serialNumber=2}}|| '''Step 5:''' If instead of an "I2C error" a "Missing BL-Ctrl:1!!" is displayed the I2C-Bus from the __first__ BL-Ctrl can be soldered back nicely. (all others stay open!). '''Step 6:''' Connect the distributor back to the FlightCtrl. After the volktage is supplied to the distributor you should see in the virtual display: '''"Missing BL-Ctrl:2!!"'''.<
><
> {{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=99722&g2_serialNumber=1}}<
><
> If you click under the virtual display on the arrow right or left you will be in the window '''BL-Ctrl found'''. The detected BL-Ctrl No. 1 should be displayed: <
><
> {{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=99718&g2_serialNumber=1}} '''Step 7:''' Now the I2C-Bus from the __second__ BL-Ctrl can be soldered back nicely (all others stay open!). '''Step 8:''' Connect the distributor again to the FlightCtrl and supply power. In the virtual display '''"Missing BL-Ctrl:3!!"''' should be displayed.<
><
> {{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=99726&g2_serialNumber=1}}<
><
> In the window '''BL-Ctrl found''' both BL-Ctrl's No. 1+2 should be displayed: <
><
> {{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=99724&g2_serialNumber=1}} '''Step 9:''' Now the I2C-Bus from the __third__ BL-Ctrl can be soldered back nicely (all others stay open!). ....and so on... <
> The next step is always like the previous - connect distributor, check, solder next BL-Ctrl to the I2C, connect distributor again, check, ... etc. <
><
> If you had just a soldering defect all BL-Ctrl's should be detected now due to clean new soldering. Also, no I2C Error should be displayed.<
><
> If you get, after re-soldering a BL-Ctrl, again an I2C Error the last connected BL-Ctrl will be defective.<
> This one should be taken out of the distributer, been changed or repaired. <
><
><
> Everything OK? Then it goes back here to Step 5: [[en/Erstinbetriebnahme/Step5#Step5|{{attachment:symbols/Pfeil_rechts.png}}]] <
><
><
> ####################################################################################################################################################################################### <> = Set up transmitter = Before you can use the transmitter and the appropriate receiver on the MikroKopter you should note the following: <
><
> __35MHz/40MHz Transmitter/Receiver__ * Transmitter and receiver should be equipped with the appropriate crystal (same channel). * The receiver need to give a PPM Sum-signal. <
> __2.4GHz Transmitter/Receiver__ * Transmitter and receiver have to be "paired" to each other. * The receiver need to give a PPM Sum-signal or (if possible) switched to it. <
> A transmitter you can use in 4 modes. The assignment of the functions Throttle, Yaw, Nick and Roll are assigned differently to the sticks.<
><
> Here now the assignment of the sticks for the 4 different modes: ||'''Mode 1'''||'''Mode2'''||'''Mode3'''||'''Mode4'''|| ||[[http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=93401&g2_serialNumber=2|{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=93570&g2_serialNumber=6}}]]||[[http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=93434&g2_serialNumber=2|{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=93580&g2_serialNumber=6}}]]||[[http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=93607&g2_serialNumber=2|{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=93611&g2_serialNumber=4}}]]||[[http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=93497&g2_serialNumber=2|{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=93601&g2_serialNumber=6}}]]|| <
> (!) For the !MikroKopter is '''Mode 2''' the perfect mode. <
><
> On the !MikroKopter channels for specific functions are already preset.<
> The first 4 channels are assigned for the control.<
> The remaining channels can be set up on the transmitter as follows: <
> * Channel 1 -> Throttle (Function on stick) * Stick up - Kopter lifts off/increases * Stick down - Kopter decreases * Stick middle - Kopter holds the height <
> * Channel 2 -> Roll (Function on stick) * Stick to the left - Kopter flies to the left * Stick to the right - Kopter flies to the right <
> * Channel 3 -> Nick (Function on stick) * Stick up - Kopter flies forward * Stick down - Kopter flies backward <
> * Channel 4 -> Yaw (Function on stick) * Stick to the left - Kopter rotates anticlockwise * Stick to the right - Kopter rotates clockwise <
> * Channel 5 -> Height switch (two-way switch * ON/OFF) * Switch OFF - Kopter holds the height manually * Switch ON - Kopter holds automatically the height while stick is in middle-position <
> * Channel 6 -> GPS (three-way switch * OFF/PH/CH) * Switch OFF - Kopter without GPS function * Switch middle position - Kopter holds position automatically * Switch ON - Kopter flies back to the start point <
> * Channel 7 -> Camera tilt (rotary potentiometer) * With a rotary potentiometer on the transmitter the camera mount is infinitely adjustable for the tilt. <
> * Channel 8 -> !CareFree (two-way switch * ON/OFF) * Switch OFF - Front of the Kopter (red outrigger) is ahead * Switch ON - Keeps the last direction for the control; independently in which direction shows the front of the kopter (red outrigger) * More specific describtion of the function: CareFree <
> * Channel 9 -> not assigned <
> * Channel 10 -> Lighting (two-way switch * ON/OFF) * In conjunction with an [[ExtensionPCB]] you can switch i.e. the lighting ON/OFF. <
> * Channel 11 -> Camera "Roll" (rotary potentiometer) * With a rotary potentiometer on the transmitter you can infinitely adjust the Roll direction of the camrea mount. <
> * Channel 12 -> Camera trigger (button) * With the [[ShutterCable]] you can trigger the connected camera. <
> How the channels, like a switch/button/poti, are assigned to the transmitter is described in the instructions of the appropriate trensmitter.<
><
> For the transmitter Graupner MX-20 HoTT is the set up described on the HoTT-Wikipage. <
> In addition you can download there the ready channel set-up for this transmitter. Wikilink: [[HoTT#Kan.2BAOQ-le_zuordnen|HoTT]] <
><
><
> Everything OK? Then it goes back here to Step 1: [[en/Erstinbetriebnahme/Step1#Step1-2|{{attachment:symbols/Pfeil_rechts.png}}]] <
><
><
> ####################################################################################################################################################################################### <> = Kopter beeps continuously after switching ON = There are a bunch of possibilities why the Kopter still "beeps" after switching ON and initializing.<
><
> '''__Possibility 1__'''<
><
> The Kopter "beeps" continuously '''1x short and 3x long ...'''. <
><
> That is the message for the '''Loss of receiving signal'''. <
> On the !FlightCtrl the red LED is '''ON'''. This can have i.e. following reasons: <
> * There is no receiver connected or hooked up wrong to the !FlightCtrl. (Connection opportunities: [[http://mikrokopter.de/ucwiki/FlightCtrl_ME_2_1#Empf.2BAOQ-ngeranschl.2BAPw-sse|Link]]) * The transmitter is switched OFF.____ * The transmitter is not connected with the receiver. ____ * The receiver is not switched to PPM Sum-signal. (i.e. necessary for the HoTT receiver: [[http://www.mikrokopter.de/ucwiki/HoTT#Empf.2BAOQ-nger_auf_Summensignal_stellen|Link]]) * The wrong receiver has been chosen in the !KopterTool. (This can be set over the EasySetup: [[http://www.mikrokopter.de/ucwiki/EasySetup/Kanaele|Link]] <
><
> '''__Possibility 2__'''<
><
> The Kopter "beeps" continuously '''short'''. <
><
> This indicates a '''Battery Warning'''. <
> On the !FlightCtrl the red LED is '''OFF'''. This can have several reasons: <
> * The connected Lipo is not charged and should be charged immediatly. (Infos about Lipos you can find here: [[http://mikrokopter.de/ucwiki/LiPo|Link]]) * The connected power supply is set wrong. (Using 12-14V it shouldn't be in that way) <
><
> '''__Possibility 3__'''<
><
> The Kopter "beeps" continuously '''1x per second, short'''. <
><
> This indicates a '''GPS-message'''. That you will hear __only__ with the assembled GPS-System (NaviCtrl with compass and MKGPS).<
><
> This "beeping" is caused by following reasons: <
> In the software of the FlightCtrl channel 6 is already set for the GPS. Here you can choose over a 3-way switch at your transmitter between the functions "Free - PositionHold - ComingHome".<
> As long as the MKGPS has no Satfix (the LED on the MKGPS is __not__ flashing) and in addition channel 6 is activated the buzzer beeps in intervals of a second. <
><
> If the transmitter has been set already, means the switches are assigned to the right channels, the 3-way switch should be set on "Free". After that the buzzer should be silent.<
> Are the channels not set at your transmitter, channel 6 can be assigned to a different switch. Here you need to check on each switch until the buzzer is silent. <
><
><
> Everything OK? Then it goes back to 4: [[en/Erstinbetriebnahme/Step4#Step4-1|{{attachment:symbols/Pfeil_rechts.png}}]] <
><
><
> ############################################################################################################################ <> = BL-Ctrl - the red LED is flashing = If on a BL-Ctrl the red LED is __flashing__, or both LED's are OFF or only on one BL-Ctrl the green and red LED is ON then you can determine a failure. <
><
><
> '''__Possibility 1: Both LEDs are not lighting__'''<
><
> * There is no voltage at the controls. * Controller not connected; Wires are not soldered correctly; Controller are not soldered correctly into the distributor. * Atmega has a defect. * Incorrect polarity at the controller; Short circuits throughout solder bridges on the controller; Atmega has been wrong programmed. * Controller not or wrong programmed. * That can be happen with self-assembled BL-Ctrl's or while trying to download new software into the controller. <
><
> '''__Possibility 2: Both LEDs are lighting permanently__'''<
><
> As you can read in "Step 4" with a not correct set up mixer all BL-Ctrl's from address "5" up are lighting. After choosing the right mixer the red LEDs are OFF.<
> If still one of the BL-Ctrl's (or all BL-Ctrl's) are lighting green and red that indicates an error.<
> * The BL-Ctrl is not connected to the FlightCtrl; I2C Bus not (or not correct) connected to the FlightCtrl or to the distributor. <
><
> '''__Possibility 3: Red LED is OFF but the green one shows pulses__'''<
><
> * Therefore the controller is OK and connected right but there is no engine connected. <
><
> '''__Possibility 4: Red LED flashes in intervals__'''<
><
> The BL-Ctrl is controlling itself for errors while starting. If an error occurs the red LED is blinking after the start.<
> With the flashing sequence you can figure out what is defect. However, the controller __must__ be checked, replaced or repaired.<
><
> The flashing indicates: <
> * 1 x : Phase A defect * 2 x : Phase B defect * 3 x : Phase C defect There can be also different flashing sequences. A detailed and exact error message will be displayed in the '''Terminal Window''' of the KopterTool.<
> For that reason the BL-Ctrl __must__ be connected directly to the MK-USB. Over the FlightCtrl the failures of the BL-Ctrl will be '''__NOT__''' displayed.<
><
> Here you can make i.e. your own connection cable: <
><
> {{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=90277&g2_serialNumber=2}} {i} The top bar contains the odd numbers, the bottom bar the even numbers. <
><
> Connected will be the BL-Ctrl in that way: <
><
> [[http://gallery.mikrokopter.de/main.php/v/tech/MKUSB-BL-Ctrl.jpg.html|{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=77841}}]]<
> (If only the BL-Ctrl will be connected to the MK-USB you just need to close the jumper on the MK-USB to supply power. <
> Is the BL-Ctrl still in the distributor or directly connected with wires to the power supply of the Kopter, you can use the power supply of the Kopter.) <
><
><
> The error messages are as follows: <
> * 1 => Short circuit Phase A ( against B ) -> Controller not ready * 2 => Short circuit Phase B ( against A ) -> Controller not ready * 3 => Short circuit Phase C ( against B ) -> Controller not ready * 4 => Mosfet NA- not always switching off * 5 => Mosfet NB- not always switching off * 6 => Mosfet NC- not always switching off * 7 => Short circuit Phase C ( against A ) -> Controller not ready * A => NA+ not switching on * B => NB+ not switching on * C => NC+ not switching on * a => NA- not switching on * b => NB- not switching on * c => NC- not switching on More support to additional error messages and to test the controllers you can find here: [[http://mikrokopter.de/ucwiki/BL-Ctrl_Fehlerbeseitigung|BL-Ctrl Fehlerbeseitigung]] <
><
><
> Everything OK? Then it goes back here to Step 4: [[en/Erstinbetriebnahme/Step4#Step4-2|{{attachment:symbols/Pfeil_rechts.png}}]] <
><
><
> ####################################################################################################################################################################################### <> = Info window appears: "FlightCtrl is not compatible" = If after a "click" on {{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=95126&g2_serialNumber=1}} this window appears ... <
><
> {{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=94162&g2_serialNumber=1}}<
><
> ... is the software version on the !FlightCtrl/NaviCtrl __NOT__ compatible with the version of the used !KopterTool.<
> This can either be an older software version of the FlightCtrl or the NaviCtrl. The same error you will get if using an older version of the !KopterTool.<
><
> The used software versions should have the same ending numbers. <
> Using the !KopterTool version V1.7'''__6__''' the !FlightCtrl should have version 0.8'''__6__''' and the !NaviCtrl the version 0.2'''6'''.<
><
> Has in example the !FlightCtrl the version 0.8'''__4__''' is that one __NOT__ compatible with the KopterTool version V1.7'''__6__''' and the !NaviCtrl with version 0.2'''6'''.<
> Here you need to download into the !FlightCtrl the appropriate software.<
><
> == Checking Software versions == In the first step you can see which software is installed. <
><
> The version of the KopterTool will be displayed on the upper side to the left: <
><
> {{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=96258&g2_serialNumber=1}}<
> (Example: !KopterTool Version 1.7'''6'''b)<
><
> In the virtual display of the !KopterTool you can check on the versions of the !FlightCtrl and the !NaviCtrl.<
><
> One "click" on the button {{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=96260&g2_serialNumber=1}} shows you the information of the FlightCtrl: <
><
> {{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=96254&g2_serialNumber=1}}<
> (Example: !FlightCtrl2.1 Version 0.8'''6'''d)<
><
> One "click" on the botton {{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=96266&g2_serialNumber=1}} shows you the information of the NaviCtrl: <
><
> {{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=96256&g2_serialNumber=1}}<
> (Example: !NaviCtrl2.0 Version 0.2'''6'''f)<
><
> == Download software == With the KopterTool you can download easily and quick the actual software for the MikroKopter, the modules and also for the actual KopterTool.<
><
> How this works is described here: [[en/SoftwareDownload|SoftwareDownload]] == Install software == If you have successfully downloaded the software you can install and update it into the appropriate module.<
><
> How this works is described here: [[en/SoftwareUpdate|SoftwareUpdate]] <
><
><
> Everythin OK? Then it goes back here to Step 6: [[en/Erstinbetriebnahme/Step6#Step6|{{attachment:symbols/Pfeil_rechts.png}}]] <
><
><
> #######################################################################################################################################################################################