Discussions

Mission Planner 1.3.31 Can't Geotag From Pixhawk Dataflash Logs

Posted by Jason Robinson on August 10, 2015 at 1:29pm

I have run into an issue on the most recent mission planner update. It does not occur when rolling back the software to previous versions. When attempting to geotag photos from the DataFlash log from a pixhawk I get an error message and a really odd offset. It appears that the "geotagger" is reading the gps time stamp incorrectly and sees it as some time in the year 1980. Any fixes for this issue?

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

Join diydrones

Email me when people reply –
Follow

Replies

  • Jason Robinson August 14, 2015 at 7:52am
    Rolling back the numbers helped, however, I cannot geotag the MSL elevation to the photos. It will only allow me to geotag with AGL altitudes regardless of the settings. Thanks again for your support!
  • Jason Robinson August 11, 2015 at 1:14pm

    3702068001?profile=originalThis is the error message that I keep getting.

    • Developer
      Michael Oborne > Jason Robinson August 11, 2015 at 4:32pm

      the numbers on the fields has change in this version of mission planner.

      decrease all of them by one.

      this is to get ready for the new code release

      • Roy Cheng > Michael Oborne August 11, 2015 at 8:11pm

        Hi Michael,

        Just FYI. Changing the "GPS Message Offsets" values back to the old default fixed the problem with tagging by "Time offset". But the "System.FormatException" is still there when using "CAM Message Synchro".

        3702714198?profile=original

      • Jason Robinson > Michael Oborne August 11, 2015 at 4:57pm

        Could you please elaborate on which fields? I tried decreasing all of them and continue to get the same error as above when I try to estimate offset.

        • Roy Cheng > Jason Robinson August 11, 2015 at 8:05pm

          Looking at the release note there was a change made to fix the issue #946. If you visit this link "https://github.com/diydrones/MissionPlanner/issues/946" you would see that all the fields in the "GPS Message Offsets" has been incremented by one in the second screenshot which is the default values for the current release v1.3.31. I think Michael was taking about those fields.

          I changed the "GPS Message Offsets" values back to the old default (Decrease by one) and tagging by "Time offset" works now but still error for the "CAM Message Synchro".

          3702794830?profile=original

  • Roy Cheng August 11, 2015 at 2:55am

    I got the same issue too. After upgrading to v1.3.31 it's no longer able to do the "Pre-process" of geo reference image. I've tried using both the time offset and CAM message Synchro. It says "No GPS match in the log file. Please take care" while choosing Time offset. It throws error when selecting CAM message Synchro (See the attached screenshot, "Sync by cam message.png", for detail).

    None of the above mentioned issues occurred after downgrading the Mission Planner back to v1.3.30. The Arducopter firmware used to generate the dataflash log is v3.2.1

    Sync by cam message.png

  • Jason Robinson August 10, 2015 at 3:59pm
    3dr X8 's with arducopter 3.2.1. I thought it might be something wrong with the gps receiver, but have encountered the problem on multiple units as well as on older files that worked perfectly with previous software versions.
  • Developer
    Michael Oborne August 10, 2015 at 3:55pm

    what vehicle type? and what version are you running?

This reply was deleted.

Activity

Neville Rodrigues liked Neville Rodrigues's profile
Jun 30
Santiago Perez liked Santiago Perez's profile
Jun 21
More…