Größe: 16064
Kommentar:
|
Größe: 16148
Kommentar:
|
Gelöschter Text ist auf diese Art markiert. | Hinzugefügter Text ist auf diese Art markiert. |
Zeile 1: | Zeile 1: |
#acl AdminGroup:read,write,revert dl2yak:read,write,revert All:read | ||<class="MK_TableNoBorder">This page as an '''PDF-Document'''? Click on that Symbol and wait a little moment... ---> ||<class="MK_TableNoBorder"><<PDFIcon>>|| |
Zeile 21: | Zeile 21: |
Into the '''!MikroKopter-OSD''' you will come with a "Click" on the tab '''"!WayPoints"''' and on '''"Generator..."''' into the !WayPoint-Generator.<<BR>><<BR>> | In the '''!MikroKopter-OSD''' you get with a "Click" on the tab '''"!WayPoints"''' and on '''"Generator..."''' into the !WayPoint-Generator.<<BR>><<BR>> |
Zeile 29: | Zeile 29: |
Or an excavation is getting mapped from the air. Also here you could fly over the area systematically and take photos. <<BR>><<BR>> | Or an excavation should be mapped from the air. Also here you could fly over the area systematically and take photos. <<BR>><<BR>> |
Zeile 55: | Zeile 55: |
* To fly over should be in a height of 30mtr. and with a speed of 1mtr/sec. . | * The flight should be in a height of 30mtr. and with a speed of 1mtr/sec. |
Zeile 59: | Zeile 59: |
* The Kopter should point with the front (red outrigger) to the south. | * The Kopter should point with the front (red rigger) to the south. |
Zeile 82: | Zeile 82: |
(!) '''__Tipp__'''<<BR>> | (!) '''__Hint__'''<<BR>> |
Zeile 106: | Zeile 106: |
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>> |
To trigger the camera i.e. via 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>> |
Zeile 124: | Zeile 124: |
(!) '''__Tipp__'''<<BR>> | (!) '''__Hint__'''<<BR>> |
Zeile 133: | Zeile 133: |
After a "click" on the button '''"Create"''' those !WayPoints will be entered automatically into the '''WayPoint-Editor''': <<BR>><<BR>> | After a "click" on the button '''"Create"''' those !WayPoints will be entered automatically into the '''!WayPoint-Editor''': <<BR>><<BR>> |
Zeile 168: | Zeile 168: |
'''__TIPP__''' | '''__HINT__''' |
Zeile 184: | Zeile 184: |
* To fly over should be in a height of 30mtr. and with a speed of 0,5mtr/sec. . | * The flight should be in a height of 30mtr. and with a speed of 0,5mtr/sec. |
Zeile 195: | Zeile 195: |
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>> | Since the camera is triggered during the flight we need to choose a slower speed ('''Speed[0.1m/s]''') so that the images are not getting blurred.<<BR>> |
Zeile 198: | Zeile 198: |
(!) '''__Tipp__:''' <<BR>> | (!) '''__Hint__:''' <<BR>> |
Zeile 221: | Zeile 221: |
First at all you need to enter those !WayPoint settings into the !Waypoint-Editor: <<BR>><<BR>> | First at all you need to enter those !WayPoint settings into the !WayPoint-Editor: <<BR>><<BR>> |
Zeile 225: | Zeile 225: |
After a "Click" on the button '''"Create"''' you need to enter those !WayPoints settings into the '''Waypoint-Editor''': <<BR>><<BR>> | After a "Click" on the button '''"Create"''' you need to enter those !WayPoint settings into the '''Waypoint-Editor''': <<BR>><<BR>> |
Zeile 243: | Zeile 243: |
Also here you should fly a !WayPoint flight in several laps. <<BR>> | Here you should fly a !WayPoint flight in several laps as well. <<BR>> |
Zeile 247: | Zeile 247: |
In '''Example 1''' the camera was triggered at each !Waypoint. Here the time was given to the '''WP event'''.<<BR>><<BR>> | In '''Example 1''' the camera was triggered at each !WayPoint. Here the time was given to the '''WP event'''.<<BR>><<BR>> |
Zeile 260: | Zeile 260: |
The settings are made and the !WayPoints generated.<<BR>><<BR>> In the next step you can transfer the !Waypoints to the Kopter. (Link: [[MikroKopterTool-OSD#Transfer_WayPoints_to_the_Kopter|See transfered WayPoints]]) <<BR>> |
The settings are made and the !WayPoints are generated.<<BR>><<BR>> In the next step you can transfer the !WayPoints to the Kopter. (Link: [[en/MikroKopterTool-OSD#Transfer_WayPoints_to_the_Kopter|See transfered WayPoints]]) <<BR>> |
Zeile 271: | Zeile 271: |
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>> |
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>> |
Inhaltsverzeichnis
Area
In the MikroKopter-OSD you get 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 should be 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 |
|
Grid Rotation [°] |
Orientation of the grid |
|
Waypoint |
||
Radius [m] |
Radius around each Waypoint |
|
Altitude [m] |
Height of the Waypoint |
|
Heading [°] |
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 |
|
Climb rate [0.1m/s] |
Speed in which the Kopter climbs/falls between the Waypoints |
|
Delay Time [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 |
|
Generate |
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.
- The flight 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 rigger) 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 "Grid Rotation" on 0°.
"Grid Rotation [°]" = 0°.
Hint
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 Grid Rotation [°] as you want.
Here now some examples:
Step 4
Now you can set the altitude (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:
Altitude[m] = 30
Cam-Nick[°] = 90
Heading[°] = 180
So that the Kopter can take some photos it should remain/wait 10sec. at each Waypoint:
Delay Time:[s] = 10
To trigger the camera i.e. via 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 "Delay Time" for the WayPoint to expire.
Speed[0.1m/s] = 10
- That is the speed the Kopter flies to the waypoints.
Climb 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".
Hint
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.)
Now we can send the WayPoints to the Kopter. How this works you can read here: The Waypoint Flight
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/34 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.
HINT
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:
- An area of approx. 120mtr x 144mtr should be overflown.
- The flight should be in a height of 30mtr. and with a speed of 0,5mtr/sec.
- The rows of the !Waypoints flown by the Kopter should have a distance of 12mtr to each other.
- The Kopter should fly without a stop from WP to WP and shout nonstop pictures.
- The camera should look down.
- The Kopter should point with the front (red outrigger) to the south.
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 speed (Speed[0.1m/s]) so that the images are not getting blurred.
In this example we take a speed of 0.5mtr/s (~1.8km/h).
Hint:
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 with different speeds.
In addition you need to set the Delay Time:[s] to "0". The Kopter will not stop at the WayPoint but it's flying directly to the next one instead.
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
Altitude[m] = 30
Heading[°] = 180
Cam-Nick[°] = 90
Speed[0.1m/s] = 5
Delay 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 WayPoint 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.)
Now we can send the WayPoints to the Kopter. How this works you can read here: The Waypoint Flight
Flight Time
With so many WayPoints the Kopter needs a long time until all WayPoints are flown by.
For this example it takes only 57 Minutes! (Exactly 56 Min/48 Sec.)
Here you should fly a WayPoint flight in several laps as well.
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 the WayPoints are generated.
In the next step you can transfer the WayPoints to the Kopter. (Link: See transfered WayPoints)
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.