2988
Kommentar:
|
10497
|
Gelöschter Text ist auf diese Art markiert. | Hinzugefügter Text ist auf diese Art markiert. |
Zeile 1: | Zeile 1: |
{{{#!wiki caution '''Info''' This page is currently under revision }}} |
|
Zeile 3: | Zeile 9: |
||<class="MK_Nav_left">||<class="MK_Nav_Header">'''Waypoint Event'''||<class="MK_Nav_left">|| | ||<class="MK_Nav_left">||<class="MK_Nav_Header">'''!WayPoint Event'''||<class="MK_Nav_left">|| |
Zeile 13: | Zeile 19: |
<<TableOfContents>> ##################################################################################################################################################################################### = WayPoint Event = Each scaled !WayPoint in the !MikroKopterTool-OSD has a field '''"WP-Event"''' (!WayPoint-Event). <<BR>> With each !WayPoint-Flight you can trigger i.e. a camera automatically after reaching the appropriate !WayPoint.<<BR>><<BR>> If the Kopter reaches the !WayPointthe Kopter stays there for the delay time set under the tab "Time".<<BR>> During the delay time the value will be transfered to the FlightCtrl entered under WP-Event. <<BR>><<BR>> {{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=103626&g2_serialNumber=1}}<<BR>><<BR>> The functions and the settings of the !WayPoints are described here: [[MikroKopterTool-OSD]] ##################################################################################################################################################################################### = The Settings = On the FlightCtrl you have two switch-output which can be controlled over the WP-Event. <<BR>> The transfered value determines here the switching time of each little casket under "Bitmask".<<BR>><<BR>> An add-on device attached to the switch output such as a !ShutterCable or an Extention Board can i.e. trigger a camera in appropriate intervalls.<<BR>> So that a switch output reacts to a WP-Event you need to make different settings. <<BR>><<BR>> It helps you alot if you can trigger the camera already over a button at your transmitter.<<BR>><<BR>> A describtion how to trigger a camera over a button you will find here: [[CameraConnect|CameraConnect]] <<BR>><<BR>> ##################################################################################################################################################################################### == The Channel Assignment == If you use a channel to trigger your camrea on your transmitter a function for this channel is assigned over the settings (POTI1-8).<<BR>> (KopterTool >Settings >Channels)<<BR>> This POTI will be assigned to the appropriate switch output.<<BR>> (KopterTool >Settings >Outputs)<<BR>><<BR>> Been able to use now the !WayPoint-Event we assign to the "POTI" the entry "WP-Event".<<BR>> In this example we want to use POTI8 which reacts normally to channel 12: <<BR>><<BR>> {{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=103727&g2_serialNumber=1}} <<BR>><<BR>> The function "POTI8" will be assigned now to the used switch output. <<BR>> In this example the !ShutterCable is connected to output1: <<BR>><<BR>> {{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=103633&g2_serialNumber=2}} ##################################################################################################################################################################################### = Switch Examples = Over each casket behind "Bitmask" you can determine the switch sequence of the output. <<BR>> The switch time of each casket will be determined with the value entered under WP-Event. <<BR>><<BR>> Let's take a few WP-Event values which are assigned for !WayPoints and let's have a look to the function of the switch output in some examples. <<BR>> How would the output switch with this values? <<BR>><<BR>> {{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=103626&g2_serialNumber=1}} <<BR>><<BR>> <!> Zur Information: <<BR>> Der Schaltvorgang wird solange wiederholt, bis die eingestellte "Zeit" für den Wegpunkt abgelaufen ist.<<BR>> Beispiel: Ist unter "Zeit" eine 10 eingetragen, bleibt der Kopter für 10sek an dem Wegpunkt stehen und während dieser 10sek wird der WP-Event Wert übertragen. <<BR>><<BR>> '''__WP-Event = 0__''' <<BR>> Ist unter WP-Event eine "0" eingetragen, ist die Funktion ausgeschaltet. Der Schaltausgang wird also nicht angesteuert und die Kamera löst nicht aus.<<BR>><<BR>> '''__WP-Event = 50__''' <<BR>> Wird unter WP-Event eine "50" eingetragen, ist die Zeit pro Kästchen 0,5 Sekunden (50x10ms = 500ms = 0,5sek). <<BR>><<BR>> '''__WP-Event = 100__''' <<BR>> Wird unter WP-Event eine "100" eingetragen, ist die Zeit pro Kästchen 1 Sekunden (100x10ms = 1000ms = 1sek). <<BR>><<BR>> '''__WP-Event = 200__''' <<BR>> Wird unter WP-Event eine "200" eingetragen, ist die Zeit pro Kästchen 2 Sekunden (200x10ms = 2000ms = 2sek). <<BR>><<BR>> Hier einige Beispiele, wie man die Kästchen schalten könnte (natürlich sind auch andere Muster möglich): <<BR>><<BR>> |
|
Zeile 15: | Zeile 103: |
<<Anchor(WP-Event)>> <<Anchor(Kamera)>> |
||||||||||||||||||<class="MK_THeader" tablewidth="750px">{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=103795&g2_serialNumber=1}}|| ||<class="MK_TBody">Bitmask = ||<#B4DC6C:>AN||<#FF7537:>AUS||<#FF7537:>AUS||<#FF7537:>AUS||<#FF7537:>AUS||<#FF7537:>AUS||<#FF7537:>AUS||<#FF7537:>AUS|| ||<class="MK_TBody">WP-Event<<BR>>= 50 ||<#B4DC6C:>0,5sek<<BR>>an||<#FF7537:>0,5sek<<BR>>aus||<#FF7537:>0,5sek<<BR>>aus||<#FF7537:>0,5sek<<BR>>aus||<#FF7537:>0,5sek<<BR>>aus||<#FF7537:>0,5sek<<BR>>aus||<#FF7537:>0,5sek<<BR>>aus||<#FF7537:>0,5sek<<BR>>aus|| ||<class="MK_TBody">WP-Event<<BR>>= 100 ||<#B4DC6C:>1sek<<BR>>an||<#FF7537:>1sek<<BR>>aus||<#FF7537:>1sek<<BR>>aus||<#FF7537:>1sek<<BR>>aus||<#FF7537:>1sek<<BR>>aus||<#FF7537:>1sek<<BR>>aus||<#FF7537:>1sek<<BR>>aus||<#FF7537:>1sek<<BR>>aus|| ||<class="MK_TBody">WP-Event<<BR>>= 200 ||<#B4DC6C:>2sek<<BR>>an||<#FF7537:>2sek<<BR>>aus||<#FF7537:>2sek<<BR>>aus||<#FF7537:>2sek<<BR>>aus||<#FF7537:>2sek<<BR>>aus||<#FF7537:>2sek<<BR>>aus||<#FF7537:>2sek<<BR>>aus||<#FF7537:>2sek<<BR>>aus|| <<BR>> |
Zeile 20: | Zeile 112: |
= WaypointEvent = ##include_event_begin The idea is, to trigger a camera (or similar) if the waypoint is reached. The camera can be connected on the bliking-outpots or can be controlled by a mechanical servo. If the waypoint is reached, a selectable value will be written into one virtual channel "WP-Event" - this can be used for blinking outouts or on a servo-outpot. {{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=70363&g2_serialNumber=2}} This value will be sent from the NaviControl to the FlightControl when the waypoint is reached. {{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=70364&g2_serialNumber=1}} The value is active during the waiting time on the waypoint. In the other time the value is zero. Now the Poti (here Poti 8) can be used for blinking pattern or the Servo output. == Excample == [[ShutterCable|{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=71747}}|ShutterCable}}]] |
||||||||||||||||||<class="MK_THeader" tablewidth="750px">{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=103798&g2_serialNumber=1}}|| ||<class="MK_TBody">Bitmask = ||<#B4DC6C:>AN||<#FF7537:>AUS||<#B4DC6C:>AN||<#FF7537:>AUS||<#B4DC6C:>AN||<#FF7537:>AUS||<#B4DC6C:>AN||<#FF7537:>AUS|| ||<class="MK_TBody">WP-Event<<BR>>= 50 ||<#B4DC6C:>0,5sek<<BR>>an||<#FF7537:>0,5sek<<BR>>aus||<#B4DC6C:>0,5sek<<BR>>an||<#FF7537:>0,5sek<<BR>>aus||<#B4DC6C:>0,5sek<<BR>>an||<#FF7537:>0,5sek<<BR>>aus||<#B4DC6C:>0,5sek<<BR>>an||<#FF7537:>0,5sek<<BR>>aus|| ||<class="MK_TBody">WP-Event<<BR>>= 100 ||<#B4DC6C:>1sek<<BR>>an||<#FF7537:>1sek<<BR>>aus||<#B4DC6C:>1sek<<BR>>an||<#FF7537:>1sek<<BR>>aus||<#B4DC6C:>1sek<<BR>>an||<#FF7537:>1sek<<BR>>aus||<#B4DC6C:>1sek<<BR>>an||<#FF7537:>1sek<<BR>>aus|| ||<class="MK_TBody">WP-Event<<BR>>= 200 ||<#B4DC6C:>2sek<<BR>>an||<#FF7537:>2sek<<BR>>aus||<#B4DC6C:>2sek<<BR>>an||<#FF7537:>2sek<<BR>>aus||<#B4DC6C:>2sek<<BR>>an||<#FF7537:>2sek<<BR>>aus||<#B4DC6C:>2sek<<BR>>an||<#FF7537:>2sek<<BR>>aus|| <<BR>> |
Zeile 43: | Zeile 120: |
A camera is connected via a ShutterCable and shall be triggered 5 times in 10 seconds. | |
Zeile 45: | Zeile 121: |
=== Step 1: select WP-Event-Value === We will use a value of 100 here |
||||||||||||||||||<class="MK_THeader" tablewidth="750px">{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=103801&g2_serialNumber=1}}|| ||<class="MK_TBody">Bitmask = ||<#B4DC6C:>AN||<#FF7537:>AUS||<#FF7537:>AUS||<#B4DC6C:>AN||<#FF7537:>AUS||<#FF7537:>AUS||<#B4DC6C:>AN||<#FF7537:>AUS|| ||<class="MK_TBody">WP-Event<<BR>>= 50 ||<#B4DC6C:>0,5sek<<BR>>an||<#FF7537:>0,5sek<<BR>>aus||<#FF7537:>0,5sek<<BR>>aus||<#B4DC6C:>0,5sek<<BR>>an||<#FF7537:>0,5sek<<BR>>aus||<#FF7537:>0,5sek<<BR>>aus||<#B4DC6C:>0,5sek<<BR>>an||<#FF7537:>0,5sek<<BR>>aus|| ||<class="MK_TBody">WP-Event<<BR>>= 100 ||<#B4DC6C:>1sek<<BR>>an||<#FF7537:>1sek<<BR>>aus||<#FF7537:>1sek<<BR>>aus||<#B4DC6C:>1sek<<BR>>an||<#FF7537:>1sek<<BR>>aus||<#FF7537:>1sek<<BR>>aus||<#B4DC6C:>1sek<<BR>>an||<#FF7537:>1sek<<BR>>aus|| ||<class="MK_TBody">WP-Event<<BR>>= 200 ||<#B4DC6C:>2sek<<BR>>an||<#FF7537:>2sek<<BR>>aus||<#FF7537:>2sek<<BR>>aus||<#B4DC6C:>2sek<<BR>>an||<#FF7537:>2sek<<BR>>aus||<#FF7537:>2sek<<BR>>aus||<#B4DC6C:>2sek<<BR>>an||<#FF7537:>2sek<<BR>>aus|| <<BR>> |
Zeile 48: | Zeile 128: |
{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=70370&g2_serialNumber=2}}<<BR>> (For the example of 10sec., the "Time" must be changed from 5 to 10. So the Kopter will stay for 10sec. at that waypoint.) |
|
Zeile 51: | Zeile 129: |
=== Step 2: use Poti8 === When reaching the waypoint, the value shall be stored in Poti8 |
|
Zeile 54: | Zeile 130: |
{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=70364&g2_serialNumber=1}} | ||||||||||||||||||<class="MK_THeader" tablewidth="750px">{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=103804&g2_serialNumber=1}}|| ||<class="MK_TBody">Bitmask = ||<#B4DC6C:>AN||<#FF7537:>AUS||<#FF7537:>AUS||<#FF7537:>AUS||<#B4DC6C:>AN||<#FF7537:>AUS||<#FF7537:>AUS||<#FF7537:>AUS|| ||<class="MK_TBody">WP-Event<<BR>>= 50 ||<#B4DC6C:>0,5sek<<BR>>an||<#FF7537:>0,5sek<<BR>>aus||<#FF7537:>0,5sek<<BR>>aus||<#FF7537:>0,5sek<<BR>>aus||<#B4DC6C:>0,5sek<<BR>>an||<#FF7537:>0,5sek<<BR>>aus||<#FF7537:>0,5sek<<BR>>aus||<#FF7537:>0,5sek<<BR>>aus|| ||<class="MK_TBody">WP-Event<<BR>>= 100 ||<#B4DC6C:>1sek<<BR>>an||<#FF7537:>1sek<<BR>>aus||<#FF7537:>1sek<<BR>>aus||<#FF7537:>1sek<<BR>>aus||<#B4DC6C:>1sek<<BR>>an||<#FF7537:>1sek<<BR>>aus||<#FF7537:>1sek<<BR>>aus||<#FF7537:>1sek<<BR>>aus|| ||<class="MK_TBody">WP-Event<<BR>>= 200 ||<#B4DC6C:>2sek<<BR>>an||<#FF7537:>2sek<<BR>>aus||<#FF7537:>2sek<<BR>>aus||<#FF7537:>2sek<<BR>>aus||<#B4DC6C:>2sek<<BR>>an||<#FF7537:>2sek<<BR>>aus||<#FF7537:>2sek<<BR>>aus||<#FF7537:>2sek<<BR>>aus|| <<BR>> |
Zeile 56: | Zeile 137: |
=== Step 3: Interval of the blinking pattern === The interval is now controlled via Poti8 (WP-Event) |
|
Zeile 59: | Zeile 138: |
{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=70366&g2_serialNumber=1}} | |
Zeile 61: | Zeile 139: |
When reaching the Waypoint, the trigger will be alternate between on and off with 1 second on (100) and 1 second off (100), because we selected the pattern: on,off,on,off,... /!\ Values below 6 and over 220 result in a static signal. If you need a blinking interval, please use values between 6-220 More information to the blinking pattern [[http://www.mikrokopter.de/ucwiki/en/Firmware-0.76#LED_Flashing|here]] or [[http://www.mikrokopter.de/ucwiki/ShutterCable#Ausl.2BAPY-sen|here]] '''Tip:''' You can also put the Poti8 (WP-Value) to a servo-output. In that case the servo will move after reaching the waypoint - for excample to control the camera mechanically. ##include_event_end ---- See also: [[en/Firmware-0.82|en/Firmware-0.82]] |
||||||||||||||||||<class="MK_THeader" tablewidth="750px">{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=103807&g2_serialNumber=1}}|| ||<class="MK_TBody">Bitmask = ||<#B4DC6C:>AN||<#B4DC6C:>AN||<#FF7537:>AUS||<#FF7537:>AUS||<#B4DC6C:>AN||<#B4DC6C:>AN||<#FF7537:>AUS||<#FF7537:>AUS|| ||<class="MK_TBody">WP-Event<<BR>>= 50 ||<#B4DC6C:>0,5sek<<BR>>an||<#B4DC6C:>0,5sek<<BR>>an||<#FF7537:>0,5sek<<BR>>aus||<#FF7537:>0,5sek<<BR>>aus||<#B4DC6C:>0,5sek<<BR>>an||<#B4DC6C:>0,5sek<<BR>>an||<#FF7537:>0,5sek<<BR>>aus||<#FF7537:>0,5sek<<BR>>aus|| ||<class="MK_TBody">WP-Event<<BR>>= 100 ||<#B4DC6C:>1sek<<BR>>an||<#B4DC6C:>1sek<<BR>>an||<#FF7537:>1sek<<BR>>aus||<#FF7537:>1sek<<BR>>aus||<#B4DC6C:>1sek<<BR>>an||<#B4DC6C:>1sek<<BR>>an||<#FF7537:>1sek<<BR>>aus||<#FF7537:>1sek<<BR>>aus|| ||<class="MK_TBody">WP-Event<<BR>>= 200 ||<#B4DC6C:>2sek<<BR>>an||<#B4DC6C:>2sek<<BR>>an||<#FF7537:>2sek<<BR>>aus||<#FF7537:>2sek<<BR>>aus||<#B4DC6C:>2sek<<BR>>an||<#B4DC6C:>2sek<<BR>>an||<#FF7537:>2sek<<BR>>aus||<#FF7537:>2sek<<BR>>aus|| <<BR>> |
Info
This page is currently under revision
WayPoint Event |
Inhaltsverzeichnis
WayPoint Event
Each scaled WayPoint in the MikroKopterTool-OSD has a field "WP-Event" (WayPoint-Event).
With each WayPoint-Flight you can trigger i.e. a camera automatically after reaching the appropriate WayPoint.
If the Kopter reaches the WayPointthe Kopter stays there for the delay time set under the tab "Time".
During the delay time the value will be transfered to the FlightCtrl entered under WP-Event.
The functions and the settings of the WayPoints are described here: MikroKopterTool-OSD
The Settings
On the FlightCtrl you have two switch-output which can be controlled over the WP-Event.
The transfered value determines here the switching time of each little casket under "Bitmask".
An add-on device attached to the switch output such as a ShutterCable or an Extention Board can i.e. trigger a camera in appropriate intervalls.
So that a switch output reacts to a WP-Event you need to make different settings.
It helps you alot if you can trigger the camera already over a button at your transmitter.
A describtion how to trigger a camera over a button you will find here: CameraConnect
The Channel Assignment
If you use a channel to trigger your camrea on your transmitter a function for this channel is assigned over the settings (POTI1-8).
(KopterTool >Settings >Channels)
This POTI will be assigned to the appropriate switch output.
(KopterTool >Settings >Outputs)
Been able to use now the WayPoint-Event we assign to the "POTI" the entry "WP-Event".
In this example we want to use POTI8 which reacts normally to channel 12:
The function "POTI8" will be assigned now to the used switch output.
In this example the ShutterCable is connected to output1:
Switch Examples
Over each casket behind "Bitmask" you can determine the switch sequence of the output.
The switch time of each casket will be determined with the value entered under WP-Event.
Let's take a few WP-Event values which are assigned for WayPoints and let's have a look to the function of the switch output in some examples.
How would the output switch with this values?
Zur Information:
Der Schaltvorgang wird solange wiederholt, bis die eingestellte "Zeit" für den Wegpunkt abgelaufen ist.
Beispiel: Ist unter "Zeit" eine 10 eingetragen, bleibt der Kopter für 10sek an dem Wegpunkt stehen und während dieser 10sek wird der WP-Event Wert übertragen.
WP-Event = 0
Ist unter WP-Event eine "0" eingetragen, ist die Funktion ausgeschaltet. Der Schaltausgang wird also nicht angesteuert und die Kamera löst nicht aus.
WP-Event = 50
Wird unter WP-Event eine "50" eingetragen, ist die Zeit pro Kästchen 0,5 Sekunden (50x10ms = 500ms = 0,5sek).
WP-Event = 100
Wird unter WP-Event eine "100" eingetragen, ist die Zeit pro Kästchen 1 Sekunden (100x10ms = 1000ms = 1sek).
WP-Event = 200
Wird unter WP-Event eine "200" eingetragen, ist die Zeit pro Kästchen 2 Sekunden (200x10ms = 2000ms = 2sek).
Hier einige Beispiele, wie man die Kästchen schalten könnte (natürlich sind auch andere Muster möglich):
Bitmask = |
AN |
AUS |
AUS |
AUS |
AUS |
AUS |
AUS |
AUS |
WP-Event |
0,5sek |
0,5sek |
0,5sek |
0,5sek |
0,5sek |
0,5sek |
0,5sek |
0,5sek |
WP-Event |
1sek |
1sek |
1sek |
1sek |
1sek |
1sek |
1sek |
1sek |
WP-Event |
2sek |
2sek |
2sek |
2sek |
2sek |
2sek |
2sek |
2sek |
Bitmask = |
AN |
AUS |
AN |
AUS |
AN |
AUS |
AN |
AUS |
WP-Event |
0,5sek |
0,5sek |
0,5sek |
0,5sek |
0,5sek |
0,5sek |
0,5sek |
0,5sek |
WP-Event |
1sek |
1sek |
1sek |
1sek |
1sek |
1sek |
1sek |
1sek |
WP-Event |
2sek |
2sek |
2sek |
2sek |
2sek |
2sek |
2sek |
2sek |
Bitmask = |
AN |
AUS |
AUS |
AN |
AUS |
AUS |
AN |
AUS |
WP-Event |
0,5sek |
0,5sek |
0,5sek |
0,5sek |
0,5sek |
0,5sek |
0,5sek |
0,5sek |
WP-Event |
1sek |
1sek |
1sek |
1sek |
1sek |
1sek |
1sek |
1sek |
WP-Event |
2sek |
2sek |
2sek |
2sek |
2sek |
2sek |
2sek |
2sek |
Bitmask = |
AN |
AUS |
AUS |
AUS |
AN |
AUS |
AUS |
AUS |
WP-Event |
0,5sek |
0,5sek |
0,5sek |
0,5sek |
0,5sek |
0,5sek |
0,5sek |
0,5sek |
WP-Event |
1sek |
1sek |
1sek |
1sek |
1sek |
1sek |
1sek |
1sek |
WP-Event |
2sek |
2sek |
2sek |
2sek |
2sek |
2sek |
2sek |
2sek |
Bitmask = |
AN |
AN |
AUS |
AUS |
AN |
AN |
AUS |
AUS |
WP-Event |
0,5sek |
0,5sek |
0,5sek |
0,5sek |
0,5sek |
0,5sek |
0,5sek |
0,5sek |
WP-Event |
1sek |
1sek |
1sek |
1sek |
1sek |
1sek |
1sek |
1sek |
WP-Event |
2sek |
2sek |
2sek |
2sek |
2sek |
2sek |
2sek |
2sek |