Unterschiede zwischen den Revisionen 44 und 52 (über 8 Versionen hinweg)
Revision 44 vom 28.12.2011 16:49
Größe: 15705
Autor: LotharF
Kommentar:
Revision 52 vom 18.01.2012 09:34
Größe: 15963
Autor: dl2yak
Kommentar:
Gelöschter Text ist auf diese Art markiert. Hinzugefügter Text ist auf diese Art markiert.
Zeile 29: Zeile 29:
With this function you can automatically generate any rectangular grid. Also, you can set any numbers of WayPoints (max. 200). <<BR>> With this function you can automatically generate any rectangular grid. Also, you can set any numbers of !WayPoints (max. 200). <<BR>>
Zeile 40: Zeile 40:
||<(#FFFFAA>'''Rotation [°]''' ||<(height= 30px>Orientation of the grid|| ||<(#FFFFAA>'''Grid Rotation [°]''' ||<(height= 30px>Orientation of the grid||
Zeile 43: Zeile 43:
||<(#FFFFAA>'''Height [m]''' ||<(height= 30px>Height of the Waypoint||
||<(#FFFFAA>'''Direction [°]''' ||<(height= 30px>Direction in which the Kopter points after reaching the Waypoint||
||<(#FFFFAA>'''Altitude [m]''' ||<(height= 30px>Height of the Waypoint||
||<(#FFFFAA>'''Heading [°]''' ||<(height= 30px>Direction in which the Kopter points after reaching the Waypoint||
Zeile 47: Zeile 47:
||<(#FFFFAA>'''Rate of climb [0.1m/s]''' ||<(height= 30px>Speed in which the Kopter climbs/falls between the Waypoints||
||<(#FFFFAA>'''Waiting period [s]''' ||<(height= 30px>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.||
||<(#FFFFAA>'''Climb rate [0.1m/s]''' ||<(height= 30px>Speed in which the Kopter climbs/falls between the Waypoints||
||<(#FFFFAA>'''Delay Time [s]''' ||<(height= 30px>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.||
Zeile 81: Zeile 81:
In this example we leave the "Rotation" on 0°.<<BR>>
 * '''"Rotation [°]"''' = 0°.
In this example we leave the "Grid Rotation" on 0°.<<BR>>
 * '''"Grid Rotation [°]"''' = 0°.
Zeile 85: Zeile 85:
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.<<BR>> 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.<<BR>>
Zeile 99: Zeile 99:
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°.<<BR>> 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°.<<BR>>
Zeile 101: Zeile 101:
 * '''Height[m]''' = 30  * '''Altitude[m]''' = 30
Zeile 103: Zeile 103:
 * '''Direction[°]''' = 180  * '''Heading[°]''' = 180
Zeile 106: Zeile 106:
 * '''Waiting Time:[s]''' = 10  * '''Delay Time:[s]''' = 10
Zeile 116: Zeile 116:
  * 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.
  * 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.
Zeile 120: Zeile 120:
 * '''Elevation rate[0.1m/s]''' = 30  * '''Climb rate[0.1m/s]''' = 30
Zeile 124: Zeile 124:
Those set up Waypoints need to be generated now. It all takes is a "click" on '''"Create"'''. Those set up !WayPoints need to be generated now. It all takes is a "click" on '''"Create"'''.
Zeile 127: Zeile 127:
 Is '''"Delete existing WPs"''' marked, with each "click" on "Create" the already existing Waypoints will be deleted on the map.<<BR>>  Is '''"Delete existing WPs"''' marked, with each "click" on "Create" the already existing !WayPoints will be deleted on the map.<<BR>>
Zeile 135: Zeile 135:
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 141: Zeile 141:
(On the right you can see the directions in which the Kopter flies along the Waypoints.)<<BR>><<BR>> (On the right you can see the directions in which the Kopter flies along the !WayPoints.)<<BR>><<BR>>
Zeile 145: Zeile 145:

Now we can send the !WayPoints to the Kopter. How this works you can read here: [[#Wegpunkteflug|The Waypoint Flight]]
<<BR>><<BR>>
Zeile 148: Zeile 152:
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>>
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/34 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>>
Zeile 160: Zeile 164:
Why is the last waypoint approached again when you restart the Kopter? <<BR>> Why is the last !WayPoint approached again when you restart the Kopter? <<BR>>
Zeile 162: Zeile 166:
But it shouldn't be done in this way. It can also be flown, beginning from the following waypoint.<<BR>><<BR>> But it shouldn't be done in this way. It can also be flown, beginning from the following !WayPoint.<<BR>><<BR>>
Zeile 170: Zeile 174:
[[http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=100408&g2_GALLERYSID=2eba5a1c4dc1a8fda43ef9e9514df9ab|Flight Time - Download]] [[http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=101289&g2_GALLERYSID=75a1559a8a40daf94361cdb67b768ffd|Flight Time - Download]]
Zeile 181: Zeile 185:
The Kopter should'n stop at each Waypoint and should continue flying without a stop from one Waypoint to the next instead.<<BR>> The Kopter should'n stop at each !WayPoint and should continue flying without a stop from one !WayPoint to the next instead.<<BR>>
Zeile 184: Zeile 188:
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>>
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>>
Zeile 191: Zeile 195:
 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>>
 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. <<BR>><<BR>>

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.<<BR>><<BR>>
Zeile 203: Zeile 207:
 * '''Height[m]''' = 30
 * '''Direction[°]''' = 180
 * '''Altitude[m]''' = 30
 * '''Heading[°]''' = 180
Zeile 209: Zeile 213:
 * '''Waiting Time:[s]''' = 0  * '''Delay Time:[s]''' = 0
Zeile 213: Zeile 217:
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 217: Zeile 221:
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 !WayPoints settings into the '''Waypoint-Editor''': <<BR>><<BR>>
Zeile 222: Zeile 226:
(On the right you can see the directions in which the Kopter flies along the Waypoints.)<<BR>><<BR>> (On the right you can see the directions in which the Kopter flies along the !WayPoints.)<<BR>><<BR>>
Zeile 227: Zeile 231:
Now we can send the !WayPoints to the Kopter. How this works you can read here: [[#Wegpunkteflug|The Waypoint Flight]]
<<BR>><<BR>>

Zeile 228: Zeile 236:
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>>
With so many !WayPoints the Kopter needs a long time until all !WayPoints are flown by. <<BR>>
For this example it takes only '''57 Minutes'''! (Exactly 56 Min/48 Sec.) <<BR>><<BR>>

Also here you should fly a !WayPoint flight in several laps. <<BR>>
Zeile 237: Zeile 245:
<<Anchor(WP-Event)>>
Those settings are described here: [[en/MikroKopterTool-OSD/WP-Event#WP-Event|WP-Event camera triggering]]<<BR>><<BR>>

Those settings are described here: [[en/WaypointEvent#WP-Event|WP-Event camera triggering]]<<BR>><<BR>>
Zeile 242: Zeile 250:
<<Anchor(Kamera)>>
Those settings are described here: [[en/MikroKopterTool-OSD/WP-Event#Kamera|Permanently camera triggering]]

Those settings are described here: [[en/WaypointEvent#Kamera|Permanently camera triggering]]


<<Anchor(Wegpunkteflug)>>
Zeile 247: Zeile 256:
The settings are made and rhe Waypoints generated.<<BR>><<BR>> The settings are made and the !WayPoints generated.<<BR>><<BR>>
Zeile 256: Zeile 265:
So that the Waypoint Flight can start up you need to set the GPS-Switch on '''"!ComingHome"'''. So that the !WayPoint-Flight can start up you need to set the GPS-Switch on '''"!ComingHome"'''.
Zeile 258: Zeile 267:
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>>

INTERNE SEITE - vertraulich

Area

Into the MikroKopter-OSD you will come with a "Click" on the tab "WayPoints" and on "Generator..." into the WayPoint-Generator.

https://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=100814&g2_serialNumber=1

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.

https://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=100081&g2_serialNumber=3

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

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 https://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=100161&g2_serialNumber=1.

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°.

(!) 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 Grid Rotation [°] as you want.
Here now some examples:

Example: 58°

Example: 90°

http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=100383&g2_serialNumber=1

http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=100103&g2_serialNumber=5

To enlarge click on the pictures


Example: 180°

Example: 270°

http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=100113&g2_serialNumber=5

http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=100118&g2_serialNumber=5

To enlarge click on the pictures

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. 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 "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".

(!) 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.


Example View:
http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=100802&g2_serialNumber=1

After a "click" on the button "Create" those WayPoints will be entered automatically into the WayPoint-Editor:

http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=100796&g2_serialNumber=1

After that into the map:
(On the right you can see the directions in which the Kopter flies along the WayPoints.)

http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=100377&g2_serialNumber=1

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.

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 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".

{i} (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:

http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=100808&g2_serialNumber=1

After a "Click" on the button "Create" you need to enter those WayPoints settings into the Waypoint-Editor:

http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=100790&g2_serialNumber=1

After that into the map:
(On the right you can see the directions in which the Kopter flies along the WayPoints.)

http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=100371&g2_serialNumber=1

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.)

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 the 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.