Separate names with a comma.
Discussion in 'Cinestar 8' started by Derek Cooper, Apr 15, 2015.
Hmmm. That's disappointing -- did you not get a response?
There is this: http://wiki.mikrokopter.de/GPX
It might be one of these:
<FCFlags2>0x00,0x00</FCFlags2> --> Flight control status flags 1 and 2
Flight control status flags 1
Flight control status flags 2
FC_STATUS2_OUT1_ACTIVE 0x08 --> The Output 1 of the FC is active
FC_STATUS2_OUT2_ACTIVE 0x10 --> The Output 2 of the FC is active
Saw that, but there is no instance of that in the GPX file and we know it fired 5 times.
Hmm. That suggests that it might not be even recorded in the flight log, doesn't it?
We are hoping they used a different flag.
But you could indeed be right. Hoping that is not the issue.
I have the same issues. 1.5.5 will not handle any of my GPX files generated with 2.09i or higher. I can give you examples if you need them.
Does it auto trigger on the waypoint or were you able to get it to autotrigger between the waypoints. I have been able to get it to trigger on the waypoints but not in between way points.
On waypoints - we are going to test between next, although we haven't decided if we will use that mode for flying jobs for clients just yet.
I've emailed Franco (the author of MK_GPXTOOL) about the problem. Hopefully he can fix it -- unfortunately, it appears that MK may not be telling him in advance what they are going to change in the GPX file.
I'll let you know if I get a response from Franco.
But honestly all we care about is the flag in the GPX file identifying a trigger of the shutter. We strip out just those rows, associate them with the images and flip that data over to our mapping application that generates the GEO tagged 3D images for clients.
Without the trigger flag, we are dead in the water.
No response to my question on the MK forum as of yet, which isn't great!
I know Jeff Scholl hasn't had a chance to play w it yet - he hopes to do some testing Friday w the new firmware.
Right. I figured you wanted the data for geotagging. Worst case (which is if the GPX file doesn't contain the data), can you use a camera that does the geotagging by itself (assuming it has a good enough sky-view from under the copter to get GPS signal)?
Cameras we use don't have GPS that is accurate enough.
Let the record show that another of my allegedly bright ideas cratered again!
You're the best Andy! *group hug*
Check the FCFlags2 at row 308 of your GPX file. You will see that it has the status O1. Output 1. That's the camera being triggered. It shows for several rows because the log file is being written at 500 millisecond intervals. I presume there are other trigger points too (e.g. row 514).
Also see Holger's response to you at http://forum.mikrokopter.de/topic-post538152.html#post538152
I used MK's simple GPX Viewer to examine the log file as MK_GPXTOOL is broken. Franco Scapin is currently working on a new version of MK_GPXTOOL to correct this problem.
Hope this helps...
Derek: Could you check the SETTTINGS.INI file on the microSD card in your Navigation Controller. It looks like it's set to have the GPX file update every 100 milliseconds -- ten times per second. That seems way too fast. If I'm not mistaken the default is 500 milliseconds.
Did you happen to change that?
EDIT: It could be that the new default is 100 milliseconds....and I've overlooked that fact in the change logs from MK.
Version 1.5.6 is now available at http://wiki.mikrokopter.de/en/MKGPXTool
Franco says that this works with the latest MK GPX files...
Just curious what programs you guys are using to geo tag their pictures?