Ah, the secret "Ctrl+F". That's one way, it calculates the offset between camera time and onboard time.
If you go into the "logging configuration" menu on the console (not the config pages in mission planner), then you can also set an option to record the cam position when the trigger went out.
In my experience a more accurate way of putting the positions in, because you don't need to figure out the time offset, just figure out the photo # offset.
There doesn't seem to be a way to show what's not being logged, so you may have to "enable all" first, which shows you what's turned on and then turn off those things you don't want.
Replies
Ah, the secret "Ctrl+F". That's one way, it calculates the offset between camera time and onboard time.
If you go into the "logging configuration" menu on the console (not the config pages in mission planner), then you can also set an option to record the cam position when the trigger went out.
In my experience a more accurate way of putting the positions in, because you don't need to figure out the time offset, just figure out the photo # offset.
Tuning what's logged: http://code.google.com/p/arducopter/wiki/AC2_Datalogging
There doesn't seem to be a way to show what's not being logged, so you may have to "enable all" first, which shows you what's turned on and then turn off those things you don't want.
To match GPS coordonnates : http://copter.ardupilot.com/wiki/common-geotagging-images-with-miss...