Hi,
I have upgraded from1.3.5 to 1.3.9 and when attempting to georef my images I am getting the below error when using estimate offset:
Also when adding in what I think the offset to be and trying to pre-process anyway, I get the below:
Reading log for GPS-ATT Messages
Error System.FormatException: Input string was not in a correct format.
at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
at System.Int32.Parse(String s, IFormatProvider provider)
at MissionPlanner.Georefimage.readGPSMsgInLog(String fn) in c:\Users\hog\Documents\Visual Studio 2010\Projects\ArdupilotMega\ArdupilotMega\georefimage.cs:line 421
at MissionPlanner.Georefimage.doworkGPSOFFSET(String logFile, String dirWithImages, Single offset) in c:\Users\hog\Documents\Visual Studio 2010\Projects\ArdupilotMega\ArdupilotMega\georefimage.cs:line 868
at MissionPlanner.Georefimage.BUT_doit_Click(Object sender, EventArgs e) in c:\Users\hog\Documents\Visual Studio 2010\Projects\ArdupilotMega\ArdupilotMega\georefimage.cs:line 2187
This if from logs taken from an APM 2.5 (3DR) using firmare 3.1.5.
Anyone got ay ideas as to how to fix it?
Thanks,
S.
Replies
Ahha ... fixed it myself :)
For some reason the log file had a single malformed line in it, in this case it was line 12903 which was a CTUN message that was spread over two rows and had some very large numbers in sonar alt (which was not being used) and bar alt (see attached log). Below is an example of the malformed row from the attached log:
CTUN, 583, 00.530000, 384825
00, 0.00, 1, -44, 638, 0
With these two rows removed and replaced with a single row (copied from the next CTUN message down), both the georef and log analyzer worked without giving an error (in fact the analyzer is the one that pointed me in the direction of the badly formatted line in the first place as it was specific about the line causing it an issue).
It seems that four of the five flights that day all have bad dataflash logs which is odd as all of the flights were flawless, and strangely it was the last flight of the day that had a log file with no issues. Any ideas anyone?
Regards,
S.
2014-08-22 14-19-29 - Copy.log