Mission Planner 1.3.39 Dataflash log auto analysis broken

I just installed the update to MP 1.3.39 and realized that the Dataflash auto analysis is broken.

.bin files I could auto-analyze in the previous version of MP result in a "Failed to start LogAnalyzer" followed by a bad input file message wit this release.

I attached one of my .bin files in question

Any insights?

Views: 2213

Attachments:

Reply to This

Replies to This Discussion

I'm not having any issues with the auto analyizer myself on 1.3.39. A good little tool i use a lot is this though http://www.rcgroups.com/forums/showthread.php?t=2151318

that log is REALLY broken though.

but after extracting your 111.bin it loads fine in the auto analysis though

Log File C:\Program Files (x86)\Mission Planner\logs\111.log
Size (kb) 4104.859375
No of lines 52934
Duration 0:01:49
Vehicletype ArduCopter
Firmware Version solo-2.0.20
Firmware Hash 609645b5
Hardware Type
Free Mem 0
Skipped Lines 0

Test: Autotune = NA -
Test: Balance/Twist = NA -
Test: Brownout = GOOD -
Test: Compass = WARN - WARN: Large compass offset params (X:-49.85, Y:173.54, Z:299.15)
WARN: Large compass offset in MAG data (X:-49.00, Y:173.00, Z:299.00)
mag_field interference within limits (20.95%)
Max mag field length (699.78) > recommended (550.00)

Test: Dupe Log Data = GOOD -
Test: Empty = GOOD -
Test: Event/Failsafe = GOOD -
Test: GPS = FAIL - Min satellites: 0, Max HDop: 99.99
Test: IMU Mismatch = GOOD - (Mismatch: 0.49, WARN: 0.75, FAIL: 1.50)
Test: Parameters = GOOD -
Test: PM = NA -
Test: Pitch/Roll = NA -
Test: Thrust = NA -
Test: VCC = GOOD -

the issue it seems to me is you're running AC-SOLO and not a standard Adrucopter firmware which kind of messes with a lot of readers.

Thanks for having a look at that Craig.

Amazingly the error occurs to all logs I have, regardless if they are from Solo or my AC3.3 DIY drone....

The interactive review a log function works fine, though.

I'm seeing the same problem on Windows XP.  Any luck resolving this?

I seem to remember that XP is going to have many issues going forward because of the way it handles a few things that can not be fixed, Things such as low level web security [which is why it is having problems downloading previous firmwares], DotNet issues, and Mono issues [the crossplatform dotnet stuff]. None of these will likely be resolved as the OS is no longer supported by Microsoft and by a majority of developers. With issues related to XP you might as well be talking about Windows 3.1 or Windows 9x as they are now in the same boat. Since most of the issues now see on XP would require a patch to the OS itself and that is never going to happen.

Stephan, your issue seems to resolve around the way that the files need to be uncompressed, and maybe you have some stale dlls or other files that are conflicting with the decompressors used in mission planner.

I am on Windows 10.
Craig your response is a bit cryptic. The files are the same as the ones I could auto-analyze with the previous MP versions w/o problems right before the update to 1.3.39.
Since I am apparently not the only one I count this as a bug in MP

To your issues it very well may that Micheal changed how the files are uncompressed with 1.3.39 the rest went towards Chuck's post.

I was able to auto analyize your logs just fine using 1.3.39 myself



Stephan said:

I am on Windows 10.
Craig your response is a bit cryptic. The files are the same as the ones I could auto-analyze with the previous MP versions w/o problems right before the update to 1.3.39.
Since I am apparently not the only one I count this as a bug in MP

the key is x64.

ie xp is no longer supported. the reason behind this is the 2gb memory limit. a 40mb bin file was failing because of memory issues.

Thank you Mr. Oborne for chiming in. And since you're the actual author of said Mission Planner people don't have to take my word for it, they got it straight from the horse's mouth :)

So "technically" they could format and install XP64 and it should work? Even though XP64 really isn't XP, it's 2000 server with XP's skin, but still :)

Michael Oborne said:

the key is x64.

ie xp is no longer supported. the reason behind this is the 2gb memory limit. a 40mb bin file was failing because of memory issues.

Also you are saying that those that run Win7/8/8,1/10 X86 are going to have memory issues as well. That is good to know for future reference. Thanks for that tidbit of info.



Craig said:

Thank you Mr. Oborne for chiming in. And since you're the actual author of said Mission Planner people don't have to take my word for it, they got it straight from the horse's mouth :)

So "technically" they could format and install XP64 and it should work? Even though XP64 really isn't XP, it's 2000 server with XP's skin, but still :)

Michael Oborne said:

the key is x64.

ie xp is no longer supported. the reason behind this is the 2gb memory limit. a 40mb bin file was failing because of memory issues.



Michael Oborne said:

the key is x64.

ie xp is no longer supported. the reason behind this is the 2gb memory limit. a 40mb bin file was failing because of memory issues.

Thanks Michael. So what you are saying is that 32bit machines running Windows 10, not XP, are no longer supported by MP?
This would be a bummer.

"Mission Planner" works "fine" on 32 bit as a whole, but the Auto Log Analyzer portion doesn't work so well on larger logs on x86 and as more and more stuff gets logged then the size will grow and as the size grows it is no longer feasible to keep trying to "dumb" things down for older computer to be able to run it. Every day there are fewer and fewer older computers running x86 operating systems. ALL newer PC's are x64 capable and tend to come with x64 windows and only really OLD computers can't run x86 and only pretty much people who upgraded from an old x86 windows or bought an old PC with x86 windows already on it are today running x86 at all. 

It's almost selfish to expect the devs to have to write code that will run on old or outdated systems and x86 is an outdated architecture even if running on newer hardware that is capable of running x64, It holds them back and everyone suffers and let's face it 99% of current [within the last few years] computers are capable of running x64 so there is no incentive to pander to the 1%. Does it suck? Well it does if you're still the 1% but the 99% should not be punished for it.

This might be a silly question, but I note that my copy of Mission Planner is installed in the /Programs Files (x86) directory. For some reason I had it in my mind that this is where 32 bit versions of programs were typically installed. Is this correct ?

I also note that that the Auto Analysis seems to fail on larger files. Could they be related ?

If so, how do I get a 64 bit version of Mission Planner, or is the program the same and the discussion is solely about whether Windows is 64 Bit ?

Thanks

Reply to Discussion

RSS

© 2019   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service