= Firmware 0.84 = || {{http://mikrokopter.de/images/eng.gif}} Page in [[en/Firmware-0.84|english]] ||<#ffffa0> {{http://mikrokopter.de/images/fra.gif}} Page en [[fr/Firmware-0.84|français]] ||<#ffffa0> {{http://mikrokopter.de/images/deu.gif}} Seite in [[Firmware-0.84|Deutsch]] || . <> . {i} This page as PDF-Document: klick on the PDF-symbol on the right side --> . <
> . <> ''' Release Date: ''' 30th march 2011 '''License: ''' [[http://svn.mikrokopter.de/mikrowebsvn/filedetails.php?repname=FlightCtrl&path=/LICENSE.TXT|LICENSE.TXT]] . '''Forum-Link:''' http://forum.mikrokopter.de/topic-XXXXX.html <
> <
> '''Download:''' * [[http://svn.mikrokopter.de/filedetails.php?repname=FlightCtrl&path=/tags/V0.84a/Hex-Files/Flight-Ctrl_MEGA644_V0_84a.hex|FlightControl V0.84a (FC1.0 .. FC2.0)]] '''(MEGA644)''' * [[http://svn.mikrokopter.de/filedetails.php?repname=FlightCtrl&path=/tags/V0.84a/Hex-Files/Flight-Ctrl_MEGA1284p_V0_84a.hex|FlightControl V0.84a (since FC2.1)]] '''(MEGA1284)''' * [[http://svn.mikrokopter.de/filedetails.php?repname=NaviCtrl&path=/tags/V0.24f/Hex-Files/Navi-Ctrl_STR9_V0_24f.hex|Navi-Ctrl V0.24f]] * [[http://svn.mikrokopter.de/filedetails.php?repname=FlightCtrl&path=/MikroKopter-Tool/Kopter_Tool_V1_74b.zip|MikroKopter-Tool V1.74b]] == Version for ACT-2,4GHz S3D-Receivers == * [[http://svn.mikrokopter.de/filedetails.php?repname=FlightCtrl&path=%2Ftags%2FV0.84a%2FHex-Files%2FFlight-Ctrl_MEGA644_V0_84a_S3D.hex|FlightControl until FC2.0 V0.84a - only for ACT-S3D 2.4GHz Receivers]] * [[http://svn.mikrokopter.de/filedetails.php?repname=FlightCtrl&path=%2Ftags%2FV0.84a%2FHex-Files%2FFlight-Ctrl_MEGA1284p_V0_84a_S3D.hex|FlightControl since FC2.1 V0.84a - nur für ACT-S3D 2.4GHz Receivers]] /!\ only for this receiver-version = Compatibility = * There is a change in the SPI protocol between NC and FC. The result is that the boards will report "communication error" instead of "incompatibel" in case of incompatible firmware versions * The FC-Settings of the FC-Version 0.82 are compatible and will not be overwritten * As usual: do not install old settings (<0.82) saved via Koptertool. * MK3Mag remains on the old version. Do not update it! = Point of Interest = <> = New method to calibrate the compass = Thanks to a clicking sound, it is now much easier to calibrate the compass properly. This method has the advantage that when calibrating the MK does not have to aligned exactly horizontal. == Video for calibrating == <> 1. Start as Compass Calibration usual - (like you would select setting 7) 2. Move the Nick stick to bottom to go into Step 2 of the calibration (the klicking sound starts) 3. Turn the MikroKopter a few times in direction of the nick axis (with axis orientation to North / South) until the Summer stops beeping 4. Turn the MikroKopter a few times in direction of the roll axis (with axis orientation to North / South) until the Summer stops beeping * (you could also mix step 3 and 4, so you could also start with the roll-axis) 5. Pull the Nick stick down to move from Step 2 to Step 3 6. Once again, pull the Nick-pull stick down to start the Z-axis calibration (goint into Step 4) 7. Turn the MikroKopter a few times in direction of the roll or nick axis (with axis orientation to North / South) until the Summer stops beeping 8. Pull the Nick stick down -> end of the calibration and store the calibration data The process also works in older firmware versions, but then without the clicking sound. = Yaw / Compass - Control = * Revision of the compass-routines in the FC and NC * If the MK is rotated by external influences to the yaw axis, it now steers back more firmly. * Yawing to a specific angle is now possible from the Navi via serial commands (only if CareFree is active) * The threshold value for the yaw stick (logging out from the compass-mode) is now smaller. Now smaller stick movements are possible for yaw. Now more sensitive turning is possible. = waypoints with altitude = {{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=78599&g2_serialNumber=1}} * For each waypoint now an altitude (height) and a climb rate can be defined * The altitude is in meters and the climb rate in 0.1m/sec (10 -> 1m/sec) * The rising or sinking starts when switching to that waypoint * If a climbing rate is defined, the target radius is a 3D spere (ball) in the sky. So the coordinate AND the altitude must be inside the desired radius * If the climb rate is zero, the altitude will be ignored for the target position. In that case the MK flys in the actual altitude * In field 2 (see picture) you can set the default setting when you place the waypoint. * You can first place all the waypoints on the map and then modify the clime rate ot altitude * Multiple waypoints with different altitudes can be placed onto the same spot. E.g. for a virtual "elivator" * The altitude control works only in vario-mode of the hight control. The gas-stick must be in the hoovering position in that case. == Display on the JetiBox == In the JetiBox there is a sign behind the altitude value. '''Characters:''' || '''Jeti display''' || '''meaning'''|| || = || Constant height || || + || rising manually || || - || sinking manually (descending)|| || ^ || Climbing by Waypoint || || V || Sinking by Waypoint || == Autolanding == In the video (above) an autonomous landing is shown. Therefore the following tips: * Two waypoints are placed on the same position. The first e.g. at a height of 8m. This ensures that the MK is flying perpendicular to the last waypoint (sinking) * The landing waypoint is set very low (below the earth's surface) as example -30m. This ensures that the MK will be stand safe in the end and will not lift off again in case of air-pressure fluctuation. * The you probably have to try different rates of sinking. A value of 10 (1m/sec) works usually quite well. * When touching the ground, the MK jumps usually something a bit. This is due to the dynamic pressure of the propeller that influences the pressure sensor. High landing legs help to reduce the effect. * It is best to land on the grass and keep well clear of obstacles and people. = viewing direction for waypoints = {{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=78596&g2_serialNumber=1}} For each waypoint a viewing direction can be selected. || display || value || sight direction || || "-" || 0 || free direction || || 1-360 || 1-360 | | fixed direction (360 = North) (180 = South)|| || "POI" || -1 || points towards the POI || || WP1 WP9 .. || -2 ...- x || points towards a Waypoint || == Notes regarding view direction (POI) == === What is the direction of view? === The camera direction is the view direction. When a camera is mounted in rotated direction (i.e. 45°) (FlightControl-settings: Camera-direction), this would be the sight direction === How to enable or disable it? === * The NC has access to the compass direction only when free care is on. * If a POI (or WP1 WP9 ..) is selected, then the MK constantly corrects the yaw direction regarding the GPS-positions. * If controlled manually (using yaw stick), the MK goes back to automatic yaw-mode after 1 second (only when POI or WP1..WP9 is used) * If a fixed view direction is set (numbers 1-360), then the MK uses this value only once when switching to this new waypoint. If the pilot manually rotates, the MK does '''not''' go back to the fixed direction === When is the view direction active? === * The new direction of view is used when switching to that waypoint === What happens if the MK is directly over the POI? === * Directly above the POI, it may happen that the MK turns always around. This happens every time it is >2 meters away from the POI. In the area of <2m to the POI, the POI yaw control is off. === WP1...WP9 === You can also use a waypoint as POI. I.e. MK can also look in the direction of any waypoint. /!\ If the MK is looking towards its own waypoint, then it would happen that it starts rotating around itself when reaching that point (see previous note) === Height of the POI === * When using the POI, a altitude of the POI can also be selected (example: clock on a church tower) * This feature is only possible for the POIs. For a fixed sight or WP1...WP9 you can not use the camera nick function. = Indicator of active carefree and height control = {{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=78602&g2_serialNumber=1}} * The character "CF" is now yellow when free care is active. * The word "Altitude" is now lighted when active = Right click on analog values = {{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=78657&g2_serialNumber=2}} * You can now click the right mouse button on the name of the analog data to use the value in the Scope display. The active values are also now highlighted in yellow. = Offset in the Poti-channels = There was a difference in the display of Poti values in the virtual LCD and MK Koptertool display. To correct this the poti-offset was increased from 110 to 127. In practice this means that the same poti-position results in a different value compared to older firmwares. The difference in the value is 17 (the new value is smaller by 17). In general, this should not really be noticed. = Other changes = * No changes in the altitude-stabilisation or flight-feeling (beside the changes in yaw) * Beeping when you switch the carefree switch -> long beep = on, short = off (also comes once after calibration) * You can start the engines until the NC "No Error" reports. Is there an error code, it only Beeps. You probably have to wait a few seconds before you can start the engines after sensor calibration. * Varible "JetiBeep" added for acces to the Jeti-buzzer in own changes to the FC-sources * Default Values for Servo-Min/Max adjusted in the settings (for MKDS18-Servo) * Default receiver is now Jeti or PPM after a setting reset * When running engines, new settings (via Koptertool) not accepted * Koptertool: When you click in the waypoint-table onto a point, this flashes on the map and gets into the foreground (handy if several points are aligned on the same spot) * If the MK shall fly to waypoints, the GPS-mode switch has to be moved once after starting. If the switch was already on CH, you must switch it to PH and back to CH to activate the waypoint list. This prevents the MK to fly towards a waypoint immediately after the lift off and so prevents hitting obsticlas in the way in low altitudes. = Bugfixes = == MikroKopter Tool V1.74b == * waypoint reading from Mikrokopter fixed (Heading was wrong) == Navicontrol == * Blinking frequency for Waypoint event was wrong (fixed in 0.24c) ---- . KategorieFirmware