15011
Kommentar:
|
14932
|
Gelöschter Text ist auf diese Art markiert. | Hinzugefügter Text ist auf diese Art markiert. |
Zeile 9: | Zeile 9: |
Zeile 11: | Zeile 10: |
* {{http://mikrokopter.de/images/fra.gif}} [[fr/WaypointEvent|français]] |
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 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: 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?
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