Größe: 14693
Kommentar:
|
Größe: 19762
Kommentar:
|
Gelöschter Text ist auf diese Art markiert. | Hinzugefügter Text ist auf diese Art markiert. |
Zeile 1: | Zeile 1: |
## page was renamed from en/WaypointEvent ||<class="MK_TableNoBorder">This page as an '''PDF-Document'''? Click on that Symbol and wait a little moment... --->||<class="MK_TableNoBorder"><<PDFIcon>>|| |
|
Zeile 3: | Zeile 6: |
||<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 7: | Zeile 10: |
Zeile 9: | Zeile 11: |
* {{http://mikrokopter.de/images/fra.gif}} [[fr/WaypointEvent|français]] | |
Zeile 12: | Zeile 13: |
<<BR>><<BR>> | |
Zeile 15: | Zeile 17: |
##################################################################################################################################################################################### | ################################################################################ = Info = If you use a Shuttercable ([[https://www.mikrocontroller.com/index.php?main_page=index&cPath=110|Link]]) you can also trigger a camera with a push button or a 3-way switch on your transmitter.<<BR>> {{{#!wiki tip '''Tip''' A description how to connect and trigger a camera with a Shuttercable you can find here: [[CameraConnect|CameraConnect]]<<BR>><<BR>> }}} Also during a Way point flight you can automatically trigger your camera.<<BR>> For this we need 3 things: * Automatic * Bitmaske (switching pattern) * WP-Event (The following settings are valid from SW version 2.00) ################################################################################ = Automatic = To trigger a Camera with a Shuttercable or an IR-Ctrl during a Way point flight, you have to activate the Automatic. This can be done with an 3-way switch or also with a push button. <<BR>><<BR>> ################################################################################ ---- == Push button to trigger == If you use a push button to trigger the camera we have 2 positions => ||<class="MK_TableNoBorder" :>{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=144300&g2_serialNumber=2}}||<class="MK_TableNoBorder" :>without activation = OFF (0) <<BR>> Camera will not trigger.<<BR>>(No triggering during a WP-Event)||<class="MK_TableNoBorder" :>{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=144289&g2_serialNumber=2}}|| ||<class="MK_TableNoBorder" :>{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=144301&g2_serialNumber=2}}||<class="MK_TableNoBorder" :>with activation = ON (254) <<BR>>Trigger the camera manually||<class="MK_TableNoBorder" :>{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=144290&g2_serialNumber=2}}|| To use the Automatic during a Way point flight we have to change the settings for this channel on the transmitter. If you use e.g. a Graupner HoTT transmitter we find this setting under ''Servo adjustment'':<<BR>> (in this example we use channel 11 to trigger the camera)<<BR>> '''1. Change to ''Servo adjustment'': ''' ||<class="MK_TableNoBorder" :>{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=144292&g2_serialNumber=2}}|| '''2. Change the left servo travel of this channel from 104% ... to 0%: ''' ||<class="MK_TableNoBorder" :>{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=144295&g2_serialNumber=2}}||<class="MK_TableNoBorder" :>{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=144296&g2_serialNumber=2}}|| '''3. Now the Automatic is still activ. ''' ||<class="MK_TableNoBorder" :>{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=144300&g2_serialNumber=2}}||<class="MK_TableNoBorder" :>without activation = Automatic (126) <<BR>> Camera will not trigger.<<BR>>(Automatic triggering during a WP-Event)||<class="MK_TableNoBorder" :>{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=144291&g2_serialNumber=2}}|| ||<class="MK_TableNoBorder" :>{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=144301&g2_serialNumber=2}}||<class="MK_TableNoBorder" :>with activation = ON (254) <<BR>>Trigger the camera manually||<class="MK_TableNoBorder" :>{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=144290&g2_serialNumber=2}}|| '''Info'''<<BR>> The Automatic can be still ON. During a normal flight you will only trigger the camera when you push the button. During a Waypoint flight the camera will trigger automatically. ################################################################################ <<BR>><<BR>><<BR>><<BR>> ---- == 3-way switch to trigger == If you use a 3-way switch to trigger the camera you can switch between OFF/Automatic/Trigger: <<BR>> (in this example we use channel 11 to trigger the camera)<<BR>> ||<class="MK_TableNoBorder" :>{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=144297&g2_serialNumber=2}}||<class="MK_TableNoBorder" :>Position 1 = OFF (0) <<BR>> Camera will not trigger||<class="MK_TableNoBorder" :>{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=144289&g2_serialNumber=2}}|| ||<class="MK_TableNoBorder" :>{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=144298&g2_serialNumber=2}}||<class="MK_TableNoBorder" :>Position 2 = Automatic (126) <<BR>> Camera will not trigger <<BR>>Automatic triggering during a WP-Event||<class="MK_TableNoBorder" :>{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=144291&g2_serialNumber=2}}|| ||<class="MK_TableNoBorder" :>{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=144299&g2_serialNumber=2}}||<class="MK_TableNoBorder" :>Position 3 = An (254) <<BR>>Trigger the camera manually||<class="MK_TableNoBorder" :>{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=144290&g2_serialNumber=2}}|| ################################################################################ = Bitmaske (switching pattern) = In the settings of the KopterTool under ''Output'' you have to set:: ||<class="MK_TableNoBorder" :>[[http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=144210&g2_serialNumber=1|{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=144214&g2_serialNumber=2}}]]||<class="MK_TableNoBorder"> - ''combine with WP-Event''<<BR>>Activate this. So "Out1" will work automatically during a WP-Event.<<BR>><<BR>>- ''Out1 Bitmask''<<BR>>This one determines the switching interval of Out1<<BR>><<BR>>- ''Out1 Timing''<<BR>>Here you set the ''Poti1-8'' (channel) <<BR>>of the used push button / 3-way switch.|| <<BR>><<BR>> '''Bitmask - explanation''' <<BR>> With the 8 boxes of the Bitmask you will the switching sequence of Out1. How long a box will switch ON or OFF Out1 you will later set under the ''WP-Event''.<<BR>> <<BR>> '''Example:''' <<BR>> Under ''WP-Event'' you set for example a value of 100 (100 x 10ms = 1 Second). <<BR>> Each box under "Out1 Bitmask" is then working for this time (1 Second). <<BR>> So if the boxes are activated as you can see in the picture (the first 5 ON and the last OFF) the switching output 1 will work like this: <<BR>> 1second "ON" - 1second "ON" - 1second "ON" - 1second "ON" - 1second "ON" - 1second "OFF" - 1second "OFF" - 1second "OFF"<<BR>><<BR>> Output 1 is also ON for 5 seconds and then OFF for 3 seconds.<<BR>><<BR>> '''Please note:''' <<BR>> The program will processing the whole bitmask! If the ''Waitingtime'' for a Waypoint is longer, the bitmask will start again.<<BR>><<BR>> '''TIP''' <<BR>> A DSLR camera can also trigger very fast. So you better use a short time for the WP-event (e.g. 6-10). <<BR>><<BR>> (See also [[#Schaltbeispiele|Switch Examples]]) ################################################################################ |
Zeile 19: | Zeile 120: |
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 !WayPoint the Kopter stays there for the delay time set under the tab "Time".<<BR>> |
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 WayPoint the Kopter stays there for the delay time set under the tab "Time".<<BR>> |
Zeile 25: | Zeile 126: |
{{http://gallery.mikrokopter.de/main.php?g2_view=core.DownloadItem&g2_itemId=105996&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}} ##################################################################################################################################################################################### |
{{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: [[en/MikroKopterTool-OSD/MikroKopterTool-OSD]] ################################################################################ <<Anchor(Schaltbeispiele)>> |
Zeile 68: | Zeile 136: |
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>> |
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>> |
Zeile 78: | Zeile 143: |
The switching operation will be repeated as long until the set "Time" for the !WayPoint is counted down.<<BR>> Example: Is under "Time" a 10 entered the Kopter will stay for 10 sec. at that !WayPoint and during this time the value of the WP-Event will be transfered. <<BR>><<BR>> |
The switching operation will be repeated as long until the set "Time" for the WayPoint is counted down. Example: Is under "Time" a 10 entered the Kopter will stay for 10 sec. at that WayPoint and during this time the value of the WP-Event will be transfered. |
Zeile 92: | Zeile 157: |
Is a "200" enterd under WP-Event is the time per casket 2 seconds (200x10ms = 2000ms = 2sek). <<BR>><<BR>> | Is a "200" enterd under WP-Event is the time per casket 2 seconds (200x10ms = 2000ms = 2sek). <<BR>><<BR>> |
Zeile 173: | Zeile 238: |
= testing and simulation at home = Look [[en/WpEvent|here]] for further documentation and how to test that without flying <<BR>> <<BR>> |
Waypoint Event |
Inhaltsverzeichnis
Info
If you use a Shuttercable (Link) you can also trigger a camera with a push button or a 3-way switch on your transmitter.
Tip
A description how to connect and trigger a camera with a Shuttercable you can find here: CameraConnect
Also during a Way point flight you can automatically trigger your camera.
For this we need 3 things:
- Automatic
- Bitmaske (switching pattern)
- WP-Event
(The following settings are valid from SW version 2.00)
Automatic
To trigger a Camera with a Shuttercable or an IR-Ctrl during a Way point flight, you have to activate the Automatic. This can be done with an 3-way switch or also with a push button.
Push button to trigger
If you use a push button to trigger the camera we have 2 positions =>
without activation = OFF (0) |
||
with activation = ON (254) |
To use the Automatic during a Way point flight we have to change the settings for this channel on the transmitter. If you use e.g. a Graupner HoTT transmitter we find this setting under Servo adjustment:
(in this example we use channel 11 to trigger the camera)
1. Change to Servo adjustment:
2. Change the left servo travel of this channel from 104% ... to 0%:
3. Now the Automatic is still activ.
without activation = Automatic (126) |
||
with activation = ON (254) |
Info
The Automatic can be still ON. During a normal flight you will only trigger the camera when you push the button. During a Waypoint flight the camera will trigger automatically.
3-way switch to trigger
If you use a 3-way switch to trigger the camera you can switch between OFF/Automatic/Trigger:
(in this example we use channel 11 to trigger the camera)
Position 1 = OFF (0) |
Position 2 = Automatic (126) |
Position 3 = An (254) |
Bitmaske (switching pattern)
In the settings of the KopterTool under Output you have to set::
- combine with WP-Event |
Bitmask - explanation
With the 8 boxes of the Bitmask you will the switching sequence of Out1. How long a box will switch ON or OFF Out1 you will later set under the WP-Event.
Example:
Under WP-Event you set for example a value of 100 (100 x 10ms = 1 Second).
Each box under "Out1 Bitmask" is then working for this time (1 Second).
So if the boxes are activated as you can see in the picture (the first 5 ON and the last OFF) the switching output 1 will work like this:
1second "ON" - 1second "ON" - 1second "ON" - 1second "ON" - 1second "ON" - 1second "OFF" - 1second "OFF" - 1second "OFF"
Output 1 is also ON for 5 seconds and then OFF for 3 seconds.
Please note:
The program will processing the whole bitmask! If the Waitingtime for a Waypoint is longer, the bitmask will start again.
TIP
A DSLR camera can also trigger very fast. So you better use a short time for the WP-event (e.g. 6-10).
(See also Switch Examples)
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 WayPoint the 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: en/MikroKopterTool-OSD/MikroKopterTool-OSD
Switch Examples
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?
For Information:
The switching operation will be repeated as long until the set "Time" for the WayPoint is counted down. Example: Is under "Time" a 10 entered the Kopter will stay for 10 sec. at that WayPoint and during this time the value of the WP-Event will be transfered.
WP-Event = 0
Is a "0" entered under WP-Event the function is OFF. The output will be not switched and a camera will be not triggered.
WP-Event = 50
Is a "50" entered under WP-Event is the time per casket 0,5 seconds (50x10ms = 500ms = 0,5sek).
WP-Event = 100
Is a "100" entered under WP-Event is the time per casket 1 second (100x10ms = 1000ms = 1sek).
WP-Event = 200
Is a "200" enterd under WP-Event is the time per casket 2 seconds (200x10ms = 2000ms = 2sek).
Here are some examples how you could switch the caskets (other patterns are possible):
Bitmask = |
ON |
OFF |
OFF |
OFF |
OFF |
OFF |
OFF |
OFF |
WP-Event |
0,5sec |
0,5sec |
0,5sec |
0,5sec |
0,5sec |
0,5sec |
0,5sec |
0,5sec |
WP-Event |
1sec |
1sec |
1sec |
1sec |
1sec |
1sec |
1sec |
1sec |
WP-Event |
2sec |
2sec |
2sec |
2sec |
2sec |
2sec |
2sec |
2sec |
Out1 is: |
ON -> |
OFF -> |
||||||
Bitmask = |
ON |
OFF |
ON |
OFF |
ON |
OFF |
ON |
OFF |
WP-Event |
0,5sec |
0,5sec |
0,5sec |
0,5sec |
0,5sec |
0,5sec |
0,5sec |
0,5sec |
WP-Event |
1sec |
1sec |
1sec |
1sec |
1sec |
1sec |
1sec |
1sec |
WP-Event |
2sec |
2sec |
2sec |
2sec |
2sec |
2sec |
2sec |
2sec |
Out1 is: |
ON -> |
OFF -> |
ON -> |
OFF -> |
ON -> |
OFF -> |
ON -> |
OFF |
Bitmask = |
ON |
OFF |
OFF |
ON |
OFF |
OFF |
ON |
OFF |
WP-Event |
0,5sec |
0,5sec |
0,5sec |
0,5sec |
0,5sec |
0,5sec |
0,5sec |
0,5sec |
WP-Event |
1sec |
1sec |
1sec |
1sec |
1sec |
1sec |
1sec |
1sec |
WP-Event |
2sec |
2sec |
2sec |
2sec |
2sec |
2sec |
2sec |
2sec |
Out1 is: |
ON -> |
OFF -> |
ON -> |
OFF -> |
ON -> |
OFF |
||
Bitmask = |
ON |
OFF |
OFF |
OFF |
ON |
OFF |
OFF |
OFF |
WP-Event |
0,5sec |
0,5sec |
0,5sec |
0,5sec |
0,5sec |
0,5sec |
0,5sec |
0,5sec |
WP-Event |
1sec |
1sec |
1sec |
1sec |
1sec |
1sec |
1sec |
1sec |
WP-Event |
2sec |
2sec |
2sec |
2sec |
2sec |
2sec |
2sec |
2sec |
Out1 is: |
ON -> |
OFF -> |
ON -> |
OFF -> |
||||
Bitmask = |
ON |
ON |
OFF |
OFF |
ON |
ON |
OFF |
OFF |
WP-Event |
0,5sec |
0,5sec |
0,5sec |
0,5sec |
0,5sec |
0,5sec |
0,5sec |
0,5sec |
WP-Event |
1sec |
1sec |
1sec |
1sec |
1sec |
1sec |
1sec |
1sec |
WP-Event |
2sec |
2sec |
2sec |
2sec |
2sec |
2sec |
2sec |
2sec |
Out1 is: |
ON -> |
OFF -> |
ON -> |
OFF -> |
||||
Exception
If you use for the WP-Event a value of 250, Out1 (or Out2) is during the delay (Time) at the WayPoint still on or off.
Bitmask = |
on |
off |
off |
off |
off |
off |
off |
off |
WP-Event=250 |
on -> |
|||||||
The switching output is at the WayPoint still ON and during the rest of the time OFF. |
Bitmask = |
off |
on |
off |
off |
off |
off |
off |
off |
WP-Event=250 |
off -> |
|||||||
The switching output is at the WayPoint still OFF and during the rest of the time ON. |
testing and simulation at home
Look here for further documentation and how to test that without flying