Discussions

Hello everyone,

i work on a project to calibrate an ArduIMU platform. The idea is to log the raw measurements with a high sampling rate in an binary format and determine the sensor errors in postprocessing.

The system consists of an arduimu v3 board, an ublox 3dr gps lea6 reciever
and an OpenLog to log data on a micro SD card.

For a while it worked fine, but for some reasons now it doesn't log data any more, instead the OpenLog creates new files of 0 bytes size. The content of the SD card looks like this, while the number of new files differs from time to time:

CONFIG.TXT       48 bytes
LOG01109.TXT      0 bytes
LOG01110.TXT      0 bytes
LOG01111.TXT      0 bytes
LOG01112.TXT      0 bytes
...

First I upload the original code (1.9) from the google pages and reset the CONFIG.TXT on the SD card to exclude the chance the problem is caused by my own code, but the problem still exist. Without Openlog connected with a FTDI cable the Arduino serial monitor shows normal activity and the blue and red led are flashing. With OpenLog instead only the yellow led is flashing. Another try with a simplified code produce the same strange results.

I found a hint that some cards cause problems, so I tried to use different cards and also formatted them - no effect.

Is there a chance that the OpenLog changed to command mode and rest there?
A month ago I had problems caused by the esc sequence, when it appears randomly three times during the raw data. I solved the problem by setting the esc# up to 10.

Unfortunately the openlog example code pages on github are down.

So far, I don't know how i can test the OpenLog. Can I test the OpenLog directly with an FTDI cable without using the ArduIMU? Any other ideas?