Just got around to doing this.  There’s a lot of logging that goes on by default on a Linux box, and every log message that gets committed to disk shortens the life of the USB key you’re driving your Microserver with.  As such, suppressing spurious logging is fairly important.

Whew, been a while.  I’ve been a bit slack with keeping up with my projects lately - too busy with other things.  However, I have a few updates.

Well, it only took three months, but the USB key I was driving my Microserver from went bang over the weekend.  It started accumulating a lot of errors, and fsck fixed the errors, but they just came back again.  Doing some analysis, I don’t believe that I was committing too many writes to the key - I only would have made under 1Gb worth of writes, and with a 16Gb USB key, there’s no way I should have committed enough writes to be able to blow the read/write cycle limit of even one block on the key.

Assembled the Arduinoven board over the weekend. It wound out being that one of the boards I received had a manufacturing defect, but the other two didn’t.  While it would be pretty straightforward to correct the defect with a craft knife, I decided to just use one of the other boards.  I guess that’s why they sent me three boards and it’s also why you should check over a new board with a continuity tester…  Anyway, after all that, IT WORKS.

Yesterday, I received my delivery of my Arduinoven boards from MakePCB.  Package arrived slightly under a month from when I ordered it, and I got a nice surprise - I’d ordered one, but I was sent three!

So I’ve been fooling with the new AeroQuad 2.5.1 code, and I’ve integrated some fixes posted by Kenny9999 (an AeroQuad.com forum user), as well as integrated my battery level compensation code.  Unfortunately though, putting in both makes the code a little too big to fit into the 32256 bytes you have available on the Uno with the Optiboot bootloader.