Größe: 16162
Kommentar:
|
Größe: 15704
Kommentar:
|
Gelöschter Text ist auf diese Art markiert. | Hinzugefügter Text ist auf diese Art markiert. |
Zeile 105: | Zeile 105: |
Damit der Kopter auch ein paar Fotos aufnehmen kann, soll er an jedem Wegpunkt 10sec. bleiben: * '''Wartezeit:[s]''' = 10 Damit die Kamera z.B. über ein angeschlossenes [[en/ShutterCable|ShutterCable]] ausgelöst werden kann, muss hier noch ein "WP event" eingestellt werden. <<BR>> Wenn der Auslöser ungefähr jede Sekunde ausgelöst werden soll, muss hier ein Wert von 100 eingetragen werden: <<BR>> (siehe auch [[en/MikroKopterTool-OSD/WP-Event|WP-Event]]) |
So that the Kopter can take some photos it should remain/wait 10sec. at each Waypoint: * '''Waiting Time:[s]''' = 10 To trigger the camera i.e. over a connected [[en/ShutterCable|ShutterCable]] you need to set also a "WP event". <<BR>> If the trigger should be triggered around each second you need to set here a value of 100: <<BR>> (see also [[en/MikroKopterTool-OSD/WP-Event|WP-Event]]) |
Zeile 114: | Zeile 114: |
Die Restlichen Werte sagen aus: <<BR>> | The remaining values are indicating: <<BR>> |
Zeile 116: | Zeile 116: |
* Damit der Kopter auch bei windigem Wetter dem Wegpunkt erreichen kann, sollte hier ein nicht zu kleiner Radius eingestellt sein. * Sobald der Kopter den Radius des Wegpunktes erreicht, beginnt zudem die "Wartezeit" für den Wegpunkt abzulaufen. |
* So that the Kopter can reach, even in windy weather, the Waypoint you shouldn't set a too small radius. * Once the Kopter reaches the radius of the waypoint it also begins the "waiting period" for the waypoint to expire. |
Zeile 119: | Zeile 119: |
* Dies ist die Geschwindigkeit, in der der Kopter die Wegpunkte anfliegt. * '''Steigrate[0.1m/s]''' = 30 * Hat hier jetzt keinen Einfluss. |
* That is the speed the Kopter flies to the waypoints. * '''Elevation rate[0.1m/s]''' = 30 * Has got no influence right now. |
Zeile 124: | Zeile 124: |
Die so eingestellten Wegpunkte müssen nun erzeugt werden. Dazu reicht ein "Klick" auf '''"Erstelle"'''. '''__Tipp__'''<<BR>> Ist '''"Delete existing WPs"''' markiert, werden bei jedem "Klick" auf "Erstelle" bereits vorhandene Wegpunkte auf der Karte gelöscht.<<BR>> Nimmt man den Haken heraus können so z.B. mehrere Raster übereinander oder an verschiedenen Stellen auf der Karte gesetzt werden.<<BR>><<BR>><<BR>> |
Those set up Waypoints need to be generated now. It all takes is a "click" on '''"Create"'''. (!) '''__Tipp__'''<<BR>> Is '''"Delete existing WPs"''' marked, with each "click" on "Create" the already existing Waypoints will be deleted on the map.<<BR>> If you take the mark out of the check-box you can place i.e. several grids one above the other or at different places on the map. <<BR>><<BR>><<BR>> |
Zeile 135: | Zeile 135: |
Nach dem "Klick" auf den Button '''"Erstelle"''' werden zuerst automatisch diese Wegpunkte mit den Einstellungen in den '''Wegpunkte-Editor''' eingetragen: <<BR>><<BR>> | After a "click" on the button '''"Create"''' those Waypoints will be entered automatically into the '''Waypoint-Editor''': <<BR>><<BR>> |
Zeile 140: | Zeile 140: |
Danach in die Karte: <<BR>> (Rechts sieht man die Richtungen, in die der Kopter die Wegpunkte dann abfliegt.)<<BR>><<BR>> |
After that into the map: <<BR>> (On the right you can see the directions in which the Kopter flies along the Waypoints.)<<BR>><<BR>> |
Zeile 147: | Zeile 147: |
/!\ '''Achtung:''' <<BR>> Bei so vielen Wegpunkten und einer Verweildauer bei jedem Wegpunkt, benötigt der Kopter eine lange Zeit bis alle Wegpunkte abgeflogen sind.<<BR>> Für dieses Beispiel sind es ganze '''57 Minuten'''! (Genau sind es 56 Min/36 Sec.)<<BR>><<BR>> Da der Kopter je nach Gesamtgewicht mit Kamera aber nur ungefähr 8-20 Minuten fliegt, sollte man solch einen Wegpunkteflug in mehreren Etappen fliegen. <<BR>> Wenn wir von einer durchschnittlichen Flugdauer von 12 Minuten unter Last ausgehen, wären es insgesamt 5 Etappen.<<BR>> Die Reihenfolge wäre dann so: <<BR>> * Wegpunkte P1 - P34 an den Kopter übertragen. Abfliegen, danach Kopter landen, Akku wechseln. * Wegpunkte P34 - P68 an den Kopter übertragen. Abfliegen, danach Kopter landen, Akku wechseln. * Wegpunkte P68 - P102 an den Kopter übertragen. Abfliegen, danach Kopter landen, Akku wechseln. * Wegpunkte P102 - P136 an den Kopter übertragen. Abfliegen, danach Kopter landen, Akku wechseln. * Wegpunkte P136 - P169 an den Kopter übertragen. Abfliegen, danach Kopter landen, fertig. Warum wird der letzte Wegpunkt beim Neustart noch einmal angeflogen?<<BR>> Dies ist eine reine Sicherheitsmaßnahme um eine Überlappung der Bilder zu gewährleisten.<<BR>> Es muss aber nicht so gemacht werden. Es kann auch beim nachfolgenden Wegpunkt weitergeflogen werden.<<BR>><<BR>> |
/!\ '''ATTENTION:''' <<BR>> With so many Waypoints and a dwell time at each Waypoint the Kopter needs a long time until all Waypoints been flown.<<BR>> For this example it takes whole '''57 Minutes'''! (Exactly it's 56 Min/36 Sec.)<<BR>><<BR>> For that reason that the Kopter flies round about 8-20 minutes depending on the total weight with camera you should fly a Waypoint-Flight like this in more laps. <<BR>> If we assume an average flight time of 12 minutes under load that would be all together a total of 5 laps.<<BR>> The order would be in that way: <<BR>> * Waypoints P1 - P34 Transfered to Kopter. Lift off, after that land Kopter, change battery. * Waypoints P34 - P68 Transfered to Kopter. Lift off, after that land Kopter, change battery. * Waypoints P68 - P102 Transfered to Kopter. Lift off, after that land Kopter, change battery. * Waypoints P102 - P136 Transfered to Kopter. Lift off, after that land Kopter, change battery. * Waypoints P136 - P169 Transfered to Kopter. Lift off, after that land Kopter. DONE! Why is the last waypoint approached again when you restart the Kopter? <<BR>> This is purely a safety rule to ensure an overlap of the images.<<BR>> But it shouldn't be done in this way. It can also be flown, beginning from the following waypoint.<<BR>><<BR>> |
Zeile 168: | Zeile 168: |
Wer nicht ausrechnen möchte wie lange ein Überflug mit den Einstellungen dauert, kann diese Excel-Tabelle nutzen.<<BR>> Hiermit wir einem die Flugdauer automatisch errechnet. [[http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=100408&g2_GALLERYSID=2eba5a1c4dc1a8fda43ef9e9514df9ab|Flugauer - Download]] |
Who don't wants to calculate how long a flyover takes with those settings can use this Excel spreadsheet.<<BR>> The flight time will be calculated automatically. [[http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=100408&g2_GALLERYSID=2eba5a1c4dc1a8fda43ef9e9514df9ab|Flight Time - Download]] |
Zeile 178: | Zeile 178: |
= Example 2 - Wegpunkte Erzeugen + Kamera ununterbrochen auslösen = In diesem Beispiel soll wieder ein Feld in der Größe von ungefähr 120mtr x 144mtr in einer Höhe von 30mtr. überflogen werden. <<BR>><<BR>> Der Kopter soll allerdings nicht bei jedem Wegpunkt stehen bleiben, sondern ohne halt von einem Wegpunkt zum anderen fliegen.<<BR>> Dabei sollen während des gesamten Fluges die Kamera ununterbrochen im Intervall ausgelöst werden.<<BR>><<BR>> Die Einstellungen sind fast genauso wie beim Beispiel 1. Es werden allerdings deutlich weniger Wegpunkte benötigt. Es werden lediglich pro Reihe 2 Wegpunkte benötigt.<<BR>> Das macht bei 13 Reihen ganze 26 Wegpunkte (gegenüber 169 aus dem vorherigen Beispiel).<<BR>><<BR>> Da die Kamera während des Fluges ausgelöst werden soll, wählen wir eine langsamere Fluggeschwindigkeit ('''Speed[0.1m/s]'''), damit die Bilder nicht unscharf werden.<<BR>> In diesem Beispiel wird eine Geschwindigkeit von 0.5mtr/s (~1.8km/h) eingestellt.<<BR>><<BR>> '''__Tipp__:''' <<BR>> Da nicht jede Kamera gleich ist, sollte die passende Geschwindigkeit für deutliche Fotos individuell mit einigen Testflügen und unterschiedlichen Geschwindigkeiten ermittelt werden.<<BR>><<BR>> Zusätzlich wird die '''Wartezeit:[s]''' auf '''"0"''' gestellt. Hierbei hält der Kopter nicht mehr am Wegpunkt, sondern fliegt ohne halt direkt weiter zum Nächsten.<<BR>><<BR>> Da der Kopter währen des gesamten Fluges ausgelöst werden soll, wird hier das '''WP event''' nicht benötigt und kann auf "0" gestellt werden.<<BR>> (Einstellungserklärung weiter unten.) <<BR>><<BR>> Die Einstellungen sind dann wie folgt: <<BR>> * '''AbstandX[m]''' = 120 |
= Example 2 - Generate Waypoints + Trigger camera permanently = In this example should be also a field been overflown in a range of approx. 120mtr x 144mtr and a height of 30mtr.. <<BR>><<BR>> The Kopter should'n stop at each Waypoint and should continue flying without a stop from one Waypoint to the next instead.<<BR>> Throughout the flight the camera should be triggered continuously in intervals.<<BR>><<BR>> The settings are almost the same as in example 1. But you need definetely less Waypoints. You just need only 2 Waypoints for each row. <<BR>> That means you need 26 Waypoints for 13 rows (compared to 169 from the previous example).<<BR>><<BR>> Since the camera is triggered during the flight we need to choose a slower airspeed ('''Speed[0.1m/s]''') so that the images are not getting fuzzy.<<BR>> In this example we take a speed of 0.5mtr/s (~1.8km/h). <<BR>><<BR>> (!) '''__Tipp__:''' <<BR>> For that reason that not every camera is the same the appropriate speed for clear photos should be individually identified with some test flights and at different speeds. <<BR>><<BR>> In addition you need to set the '''Waiting Time:[s]''' to '''"0"'''. Hierbei hält der Kopter nicht mehr am Wegpunkt, sondern fliegt ohne halt direkt weiter zum Nächsten.<<BR>><<BR>> Since the camera is triggered during the entire flight the '''WP event''' is here not needed and you can set it to "0". <<BR>><<BR>> {i} (Explainations about the settings further down.) <<BR>><<BR>> The settings are as follows: <<BR>> * '''DistanceX[m]''' = 120 |
Zeile 200: | Zeile 200: |
* '''AbstandY[m]''' = 12 | * '''DistanceY[m]''' = 12 |
Zeile 203: | Zeile 203: |
* '''Höhe[m]''' = 30 * '''Richtung[°]''' = 180 |
* '''Height[m]''' = 30 * '''Direction[°]''' = 180 |
Zeile 209: | Zeile 209: |
* '''Wartezeit:[s]''' = 0 | * '''Waiting Time:[s]''' = 0 |
Zeile 213: | Zeile 213: |
Zuerst werden diese Wegpunkte mit den Einstellungen wieder in den Wegpunkte-Editor eingetragen: <<BR>><<BR>> [[http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=100263&g2_serialNumber=1|{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=100265&g2_serialNumber=2}}]]<<BR>><<BR>> Nach dem "Klick" auf den Button '''"Erstelle"''' werden zuerst diese Wegpunkte mit den Einstellungen in den '''Wegpunkte-Editor''' eingetragen: <<BR>><<BR>> |
First at all you need to enter those Waypoint settings into the Waypoint-Editor: <<BR>><<BR>> [[http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=100263&g2_serialNumber=1|{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=100265&g2_serialNumber=2}}]] <<BR>><<BR>> After a "Click" on the button '''"Create"''' you need to enter those Waypoints settings into the '''Waypoint-Editor''': <<BR>><<BR>> |
Zeile 221: | Zeile 221: |
Danach in die Karte: <<BR>> (Rechts sieht man die Richtungen, in die der Kopter die Wegpunkte dann abfliegt.)<<BR>><<BR>> |
After that into the map: <<BR>> (On the right you can see the directions in which the Kopter flies along the Waypoints.)<<BR>><<BR>> |
Zeile 228: | Zeile 228: |
Bei so vielen Wegpunkten, benötigt der Kopter eine lange Zeit bis alle Wegpunkte abgeflogen sind.<<BR>> Für dieses Beispiel sind es ganze '''29 Minuten'''! (Genau sind es 28 Min/24 Sec.)<<BR>><<BR>> Auch hier sollte man solch einen Wegpunkteflug in mehreren Etappen fliegen. <<BR>> = Einstellungen Kameraauslösung = Im '''Beispiel 1''' wurde die Kamera pro Wegpunkt ausgelöst. Hierzu wurde unter '''WP event''' die Zeit vorgegeben.<<BR>><<BR>> |
With so many waypoints the Kopter needs a long time until all Waypoints are flown by. <<BR>> For this example it takes only '''29 Minutes'''! (Exactly 28 Min/24 Sec.) <<BR>><<BR>> Also here you should fly a Waypoint flight in several laps. <<BR>> = Settings Camera triggering = In '''Example 1''' the camera was triggered at each Waypoint. Here the time was given to the '''WP event'''.<<BR>><<BR>> |
Zeile 238: | Zeile 238: |
Diese Einstellungen sind hier beschrieben: [[en/MikroKopterTool-OSD/WP-Event#WP-Event|WP-Event Kameraauslösung]]<<BR>><<BR>> Damit die Kamera im '''Beispiel 2''' währen des gesamten Fluges auslöst, müssen wir im '''!KopterTool''' in den Einstellungen unter dem Reiter '''Ausgänge''' zwei Einstellungen vornehmen.<<BR>><<BR>> |
Those settings are described here: [[en/MikroKopterTool-OSD/WP-Event#WP-Event|WP-Event Camera triggering]]<<BR>><<BR>> So that the camera in '''Example 2''' is triggering during the entire flight we need to make two settings in the '''!KopterTool''' and under the tab '''Outputs'''.<<BR>><<BR>> |
Zeile 243: | Zeile 243: |
Diese Einstellungen sind hier beschrieben: [[en/MikroKopterTool-OSD/WP-Event#Kamera|Ununterbrochene Kameraauslösung]] = Der Wegpunkteflug = Die Einstellungen sind nun gemacht und die Wegpunkte erzeugt.<<BR>> Als nächstes müssen die Wegpunkte an den Kopter übertragen werden. (Link: Siehe Wegpunkte übertragen)<<BR>><<BR>> Jetzt kann der Kopter gestartet und in der Luft "geparkt" werden. Dazu wird die Funktion '''"Höhe halten"''' und '''"!PositionHold"''' eingeschaltet. <<BR>><<BR>> Damit der Kopter sich jetzt selbstständig ausrichtet (Kopter soll in dem Beispiel nach Süden sehen) wird die Funktion '''"!CareFree"''' eingeschaltet.<<BR>><<BR>> Damit der Wegpunkteflug jetzt starten kann, muss der GPS-Schalter auf '''"!ComingHome"''' gestellt werden.<<BR>> Direkt nach Umlegen des Schalters beginnt der Kopter nun mit dem Wegpunkteflug.<<BR>><<BR>> Ist der Wegpunkteflug abgeschlossen, bleibt der Kopter an dem letzten Wegpunkt stehen. Nun kann der Kopter manuell wieder zurückgeflogen und gelandet werden.<<BR>> Es kann natürlich auch der GPS-Schalter auf "Aus" und dann wieder auf "!ComingHome" gestellt werden. Dann fliegt der Kopter automatisch wieder zum Startpunkt zurück. |
Those settings are described here: [[en/MikroKopterTool-OSD/WP-Event#Kamera|Permanently camera triggering]] = The Waypoint Flight = The settings are made and rhe Waypoints generated.<<BR>><<BR>> In the next step you can transfer the Waypoints to the Kopter. (Link: See Waypoint transfer) <<BR>> At next you have to set the camera mount so that the camera is looking straight ahead (horizontal). <<BR>><<BR>> Now you can start the Kopter and you can "park" it in the air. Here you need to activate the function '''"Hold Height"''' and '''"!PositionHold"'''. <<BR>><<BR>> So that the Kopter can align itself (In this example the Kopter should point to the south) you need to activate the function '''"!CareFree"'''.<<BR>><<BR>> So that the Waypoint Flight can start up you need to set the GPS-Switch on '''"!ComingHome"'''. <<BR>> Directly after you have switched the Kopter starts with the Waypoint Flight. <<BR>><<BR>> Is the Waypoint Flight done the Kopter parks at the last Waypoint. After that you can fly back and land the Kopter manually.<<BR>> You also can switch the GPS to "OFF" and after that you switch back to "!ComingHome". The Kopter will fly automatically back to the start point. <<BR>> |
Inhaltsverzeichnis
Area
Into the MikroKopter-OSD you will come with a "Click" on the tab "WayPoints" and on "Generator..." into the WayPoint-Generator.
Here now you can choose the tab "Area".
With this function you can automatically generate any rectangular grid. Also, you can set any numbers of WayPoints (max. 200).
In example you could fly over an area systematically where you "lost" your Kopter before.
Or an excavation is getting mapped from the air. Also here you could fly over the area systematically and take photos.
Describtion of the function: |
||
Area |
||
Distance X[m]: |
This is the distance in meter between each Waypoints in X-Direction |
|
#WPs in X: |
Number of Waypoints in X-Direction |
|
Distance Y[m]: |
This is the distance in meter between each Waypoints in Y-Direction |
|
#WPs in Y: |
Number of Waypoints in Y-Direction |
|
Rotation [°] |
Orientation of the grid |
|
Waypoint |
||
Radius [m] |
Radius around each Waypoint |
|
Height [m] |
Height of the Waypoint |
|
Direction [°] |
Direction in which the Kopter points after reaching the Waypoint |
|
Cam-Nick [°] |
Tilt of the camera while reaching the Waypoint |
|
Speed [0.1m/s] |
Speed in which the Waypoints are flown |
|
Rate of climb [0.1m/s] |
Speed in which the Kopter climbs/falls between the Waypoints |
|
Waiting period [s] |
Waiting period per Waypoint. If you enter a "0" here the Kopter will not stop at that Waypoint instead the Kopter flies to the next one. |
|
WP event |
Here you can enter the trigger time for example a camera trigger (see also WP-Event) |
|
Delete existing WPs |
When creating new Waypoints the previous ones will be deleted |
|
Create |
Create Waypoints with the set values |
Example 1 - Generate Waypoints + trigger camera at each Waypoint
In this example:
- An area of approx. 120mtr x 144mtr should be overflown.
- To fly over should be in a height of 30mtr. and with a speed of 1mtr/sec. .
- The rows of the Waypoints flown by the Kopter should have a distance of 12mtr to each other.
- The Kopter should stop in the rows each 10mtr. to take several pictures (for that reason that a few pictures are unclear).
- The camera should look down.
- The Kopter should point with the front (red outrigger) to the south.
Step 1
First at all you mark on the map the starting point. You can do that with a "left-click" on the chosen spot.
At this spot appears a marking point .
Step 2
For that reason that the Kopter should take each 10mtr a photo and the rows should have a distance of 12mtr to each other you need to set the appropriate Waypoints.
That are for the 120mtr 13 Waypoints (0mtr - 10mtr - 20mtr ... 120mtr) and for the 145mtr 13 Waypoints (0mtr - 12mtr - 24mtr ... 144mtr).
All together 169 Waypoints (of possible 200).
The settings are as follows:
DistanceX[m] = 10
#WPs in X = 13
DistanceY[m] = 12
#WPs in Y = 13
Step 3
The generated grid can be placed on the map in any orientation you like. Here you can, for example, align the orientation of the grid to a road or on the course of a field.
In this example we leave the "Rotation" on 0°.
"Rotation [°]" = 0°.
Tipp
If you want to align the flight directions of the grid in different directions or set along a field you can change the value for the Rotation[°] as you want.
Here now some examples:
Step 4
Now you can set the height (30mtr) and the camrea tilt (downwards = 90°). For that reason that the Kopter need to point southwards you have to set a value of 180°.
You need to enter the values in that way:
Height[m] = 30
Cam-Nick[°] = 90
Direction[°] = 180
So that the Kopter can take some photos it should remain/wait 10sec. at each Waypoint:
Waiting Time:[s] = 10
To trigger the camera i.e. over a connected ShutterCable you need to set also a "WP event".
If the trigger should be triggered around each second you need to set here a value of 100:
(see also WP-Event)
WP event = 100
The remaining values are indicating:
Radius[m] = 10 =>
- So that the Kopter can reach, even in windy weather, the Waypoint you shouldn't set a too small radius.
- Once the Kopter reaches the radius of the waypoint it also begins the "waiting period" for the waypoint to expire.
Speed[0.1m/s] = 10
- That is the speed the Kopter flies to the waypoints.
Elevation rate[0.1m/s] = 30
- Has got no influence right now.
Step 5
Those set up Waypoints need to be generated now. It all takes is a "click" on "Create".
Tipp
Is "Delete existing WPs" marked, with each "click" on "Create" the already existing Waypoints will be deleted on the map.
If you take the mark out of the check-box you can place i.e. several grids one above the other or at different places on the map.
After a "click" on the button "Create" those Waypoints will be entered automatically into the Waypoint-Editor:
After that into the map:
(On the right you can see the directions in which the Kopter flies along the Waypoints.)
Flight time
ATTENTION:
With so many Waypoints and a dwell time at each Waypoint the Kopter needs a long time until all Waypoints been flown.
For this example it takes whole 57 Minutes! (Exactly it's 56 Min/36 Sec.)
For that reason that the Kopter flies round about 8-20 minutes depending on the total weight with camera you should fly a Waypoint-Flight like this in more laps.
If we assume an average flight time of 12 minutes under load that would be all together a total of 5 laps.
The order would be in that way:
- Waypoints P1 - P34 Transfered to Kopter. Lift off, after that land Kopter, change battery.
- Waypoints P34 - P68 Transfered to Kopter. Lift off, after that land Kopter, change battery.
- Waypoints P68 - P102 Transfered to Kopter. Lift off, after that land Kopter, change battery.
- Waypoints P102 - P136 Transfered to Kopter. Lift off, after that land Kopter, change battery.
- Waypoints P136 - P169 Transfered to Kopter. Lift off, after that land Kopter. DONE!
Why is the last waypoint approached again when you restart the Kopter?
This is purely a safety rule to ensure an overlap of the images.
But it shouldn't be done in this way. It can also be flown, beginning from the following waypoint.
TIPP
Who don't wants to calculate how long a flyover takes with those settings can use this Excel spreadsheet.
The flight time will be calculated automatically. Flight Time - Download
Example 2 - Generate Waypoints + Trigger camera permanently
In this example should be also a field been overflown in a range of approx. 120mtr x 144mtr and a height of 30mtr..
The Kopter should'n stop at each Waypoint and should continue flying without a stop from one Waypoint to the next instead.
Throughout the flight the camera should be triggered continuously in intervals.
The settings are almost the same as in example 1. But you need definetely less Waypoints. You just need only 2 Waypoints for each row.
That means you need 26 Waypoints for 13 rows (compared to 169 from the previous example).
Since the camera is triggered during the flight we need to choose a slower airspeed (Speed[0.1m/s]) so that the images are not getting fuzzy.
In this example we take a speed of 0.5mtr/s (~1.8km/h).
Tipp:
For that reason that not every camera is the same the appropriate speed for clear photos should be individually identified with some test flights and at different speeds.
In addition you need to set the Waiting Time:[s] to "0". Hierbei hält der Kopter nicht mehr am Wegpunkt, sondern fliegt ohne halt direkt weiter zum Nächsten.
Since the camera is triggered during the entire flight the WP event is here not needed and you can set it to "0".
(Explainations about the settings further down.)
The settings are as follows:
DistanceX[m] = 120
#WPs in X = 2
DistanceY[m] = 12
#WPs in Y = 13
Height[m] = 30
Direction[°] = 180
Cam-Nick[°] = 90
Speed[0.1m/s] = 5
Waiting Time:[s] = 0
WP event = 0
First at all you need to enter those Waypoint settings into the Waypoint-Editor:
After a "Click" on the button "Create" you need to enter those Waypoints settings into the Waypoint-Editor:
After that into the map:
(On the right you can see the directions in which the Kopter flies along the Waypoints.)
Flight Time
With so many waypoints the Kopter needs a long time until all Waypoints are flown by.
For this example it takes only 29 Minutes! (Exactly 28 Min/24 Sec.)
Also here you should fly a Waypoint flight in several laps.
Settings Camera triggering
In Example 1 the camera was triggered at each Waypoint. Here the time was given to the WP event.
Those settings are described here: WP-Event Camera triggering
So that the camera in Example 2 is triggering during the entire flight we need to make two settings in the KopterTool and under the tab Outputs.
Those settings are described here: Permanently camera triggering
The Waypoint Flight
The settings are made and rhe Waypoints generated.
In the next step you can transfer the Waypoints to the Kopter. (Link: See Waypoint transfer)
At next you have to set the camera mount so that the camera is looking straight ahead (horizontal).
Now you can start the Kopter and you can "park" it in the air. Here you need to activate the function "Hold Height" and "PositionHold".
So that the Kopter can align itself (In this example the Kopter should point to the south) you need to activate the function "CareFree".
So that the Waypoint Flight can start up you need to set the GPS-Switch on "ComingHome".
Directly after you have switched the Kopter starts with the Waypoint Flight.
Is the Waypoint Flight done the Kopter parks at the last Waypoint. After that you can fly back and land the Kopter manually.
You also can switch the GPS to "OFF" and after that you switch back to "ComingHome". The Kopter will fly automatically back to the start point.