mismatch images to CAM messages in georef

I am sure many of you have had the same issue but I am wondering what strategies you take to minimise this issue.

To illustrate. I have a flight with 312 images (taken with a sony a5100 from a skywalker 1900 and pixhawk fc).  When using georef I get the mismatch with the log file recognising 307 images. Now there are spurious images which were taken using 'trigger now' to test before flight, but when I remove these I still have 308 images.  I removed the first image and went through the processing (and then on to Photoscan Pro) and the positional accuracy is poor. I suspect the 'off by one' quick fix did not work!  I could do the same again by removing the last image but it looks relevant so I am reluctant to remove it.  How do I determine which image is missing?  I am assuming the camera failed to fire on one occasion - albeit that seems unlikely.

Any suggestions for an efficient way forward would be very welcome.

Thanks

Darrel

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –

Replies

  • Hey Jay

    Sounds complicated to use, but how good is this tool?

    Thanks

    Jay Case said:

    Try Swift Tag in the future. It handles cam/photo mismatch scenarios and adds additional features.

     

    http://swiftradioplanes.com/swifttag/

  • Try Swift Tag in the future. It handles cam/photo mismatch scenarios and adds additional features.

     

    http://swiftradioplanes.com/swifttag/

  • Moderator
    No problem, I'm glad it helped.
  • Mario,

    Thanks a bunch for posting this video. We just added one more setup to our QC process. Thanks again.

    cheers,

    Will F


    MarioSpeedwagon said:

    I don't know if I would word it that way. Mission planner works, but it messes up often enough that I abandoned it. 

    Here, try this. Seems a little intimidating at first, but go through it a few times and it'll only take you about 3-5 minutes to do it when you're familiar. 


    Harry Courter said:

    So tagging with mission planner just is not a realistic goal?

    and I should look for an outside method for geo tagging.

  • Thanks Mario - that is also a very useful video for me. I will try using geosetter also :)

  • Mario,

    That's a good video. Actually very helpful.  I will try this and let you know my result.

    Thank You.

  • Moderator

    I don't know if I would word it that way. Mission planner works, but it messes up often enough that I abandoned it. 

    Here, try this. Seems a little intimidating at first, but go through it a few times and it'll only take you about 3-5 minutes to do it when you're familiar. 


    Harry Courter said:

    So tagging with mission planner just is not a realistic goal?

    and I should look for an outside method for geo tagging.

  • So tagging with mission planner just is not a realistic goal?

    and I should look for an outside method for geo tagging.

  • Moderator
    I know this isn't really the "fix" you're looking for, but just wanted to throw in my 2cents.

    I've never had consistent, reliable results when tagging using mission planner. CAM messages OR time offset.

    I use geosetter, and results have been much better. After about the 5th time, it doesn't take me any longer than using mission planner, but the results are much better.

    Peau Productions / Mapir put out a good instructional video. The only difference is I use "assign exactly as found" with the .bin file.
  • Darrel:

    I have a similar issue, after a short survey grid mission I will have 30 pica and only 12 cam messages.  Telemetry logs show the locations of all 30 cam trigger locations but the log files don't come up with the geo ref data.

    A few basic issues I'm currently learning.  

    The time assigned by the pixhawk is ahead of the camera time by 1 1/2 hours.  My impression was that the pixhawk acquired the time from the GPS.  Do I need to somehow set the time? Or perhaps the time zone?

    When I review the log file what setting actually shows the cam trigger data?  

    I have reviewed all the wiki files I can find, and these items don't seem to be included.

    I can post log and telemetry files tonight.

    Any help would be much appreciated. 

This reply was deleted.

Activity

DIY Robocars via Twitter
RT @TinkerGen_: "The Tinkergen MARK ($199) is my new favorite starter robocar. It’s got everything — computer vision, deep learning, sensor…
23 hours ago
DIY Robocars via Twitter
23 hours ago
DIY Robocars via Twitter
RT @roboton_io: Join our FREE Sumo Competition 🤖🏆 👉 https://roboton.io/ranking/vsc2020 #sumo #robot #edtech #competition #games4ed https://t.co/WOx…
Nov 16
DIY Drones via Twitter
First impressions of Tinkergen MARK robocar https://ift.tt/36IeZHc
Nov 16
DIY Robocars via Twitter
Our review of the @TinkerGen_ MARK robocar, which is the best on the market right now https://diyrobocars.com/2020/11/15/first-impressions-of-tinkergen-mark-robocar/ https://t.co/ENIlU5SfZ2
Nov 15
DIY Robocars via Twitter
RT @Ingmar_Stapel: I have now explained the OpenBot project in great detail on my blog with 12 articles step by step. I hope you enjoy read…
Nov 15
DIY Robocars via Twitter
RT @DAVGtech: This is a must attend. Click the link, follow link to read the story, sign up. #chaos2020 #digitalconnection #digitalworld ht…
Nov 15
DIY Robocars via Twitter
RT @a1k0n: Got a new chassis for outdoor races (hobbyking Quantum Vandal) but I totally didn't expect that it might cause problems for my g…
Nov 11
DIY Drones via Twitter
First impressions of the Intel OpenBot https://ift.tt/36qkVV4
Nov 10
DIY Robocars via Twitter
Nov 9
DIY Robocars via Twitter
Excellent use of cardboard instead of 3D printing! https://twitter.com/Ingmar_Stapel/status/1324960595318333441
Nov 7
DIY Robocars via Twitter
RT @chr1sa: We've got a record 50 teams competing in this month's @DIYRobocars @donkey_car virtual AI car race. Starting today at 10:00am…
Nov 7
DIY Robocars via Twitter
Nov 6
DIY Robocars via Twitter
RT @a1k0n: Car's view, using a fisheye camera. The ceiling light tracking algorithm gave me some ideas to improve ConeSLAM, and having grou…
Nov 5
DIY Robocars via Twitter
RT @a1k0n: To get ground truth I measured the rug, found the pixel coordinates of its corners, calibrated my phone camera with my standard…
Nov 5
DIY Robocars via Twitter
RT @a1k0n: @DIYRobocars is back in December, but outside. Time to reinvestigate ConeSLAM! I rigged up a quick and dirty ground-truth captur…
Nov 5
More…