Hello,

I use APM 2.0 with 2.7 firmware. I noticed that log erase works strangely. In fact it doesn't work. I erased all files from CLI. Then powered on, armed and switched off after couple of seconds. Then downloaded new log file. It appeared  3+ Mb of size and included 45 of my past missions.

Questions:
1. How to properly remove logs (or clean logging area on EEPROM?)

2. When the new on-board file supposed to be created? After re-powering the board? Certainly all missions withing one power cycle get written into the same large file. Which is hugely inconvenient for analyzing problems.

Appreciate any help.

Tags: APM2, logging

Views: 152

Reply to This

Replies to This Discussion

The "chip erase" function doesn't work as advertised by the chip manf. Many chips fail to erase. The latest version falls back on the old 1 byte at a time method.

Jason

>old 1 byte at a time method

Thanks for the reply, but sorry what does it mean?

Is there workaround for removing old files?

And how to isolate latest missions from the log?

I think Jason means upgrade to 2.7.1 and the erase should work.

or falll back to an eariler relase (say 2.5.5), do the ease and then upgrade to 2.7.1 and try erase.  That should work too.  I'd first upgrade to 2.7.1 and try the earse.  It workks fine for me.

I tried 2.7.1 and erase didn't work. I am wondering how many of APM 2 boards having this kind of bug.

Jason, Is this corrected in APM 2.5 which has a chip to replace the dataFlash?

Well I've come to the conclusion that this is something that we are stuck with, at least with this version of dataFlash.

I have the same problems, current logs get appended to old, in an ever growing multi-log file!

But thankfully they also get written separately, so the large file can be ignored...

I wonder what will happen when the log file fills the dataFlash memory!

Having trolled through the atmel datasheets, and var forums, it looks like the atmel erase process only works on some batches of dataFlash, add to that, the problems of a possible ill fitting card or damaged contacts, makes for a not-so-reliable device. It appears that atmel has quickly resolved this problem by producing an ic version of the dataFlash so hopefully that will have fully functional commands.

Reposting answer from Chris on APM 2.5 thread:

Max: That's fixed in the latest code (ArduCopter 2.7.2, ArduPlane 2.6). It's in the dev trunk now and will be pushed to the Mission Planner for public release in the next week or so.

Hooray! Impatiently wait for 2.7.2.

After using 2.7.3 for while I can confirm that "log erase" issue is fixed. Thanks!!!

RSS

Social Networking

Contests

Season Two of the Trust Time Trial (T3) Contest has now begun. The fourth round is an accuracy round for multicopters, which requires contestants to fly a cube. The deadline is April 14th.

A list of all T3 contests is here

Groups

Advertisement

© 2013   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service