Got a couple of these, work exactly as advertised!
If anyone else is looking to modify the firmware and is unfamiliar with the workflow to get the serial bootloader working (like i was) then i can highly recommend Nate’s walkthrough of his process here:
http://www.sparkfun.com/commerce/tutorial_info.php?tutorials_id=142
(this took me heaps longer to find than it should have, and so i found lots of ways to not make it work in the meantime. Hopefully putting the link here saves someone else that pleasure…)

SPARKFUN
?Description: OpenLog is an open source data logger. Simple to use, simple to change. We wanted to create a serial logger that just worked. Power this device up and it will start logging any received serial data at 9600bps?
Datasheet (GITHUB)
?OpenLog is a simple serial logger based on the ATmega328 running at 16MHz. The ATmega328 should be able to talk to high capacity (larger than 2GB) SD cards. The whole purpose of this logger was to create a logger that just powered up and worked. OpenLog ships with a standard serial bootloader so you can load new firmware with a simple serial connection.?

I can?t get the darn thing to operate. I?m rather incompetent at some of this stuff . However, not just because of my incompetence, but also judging by the previous comments about the device, OpenLog is not as simple to get operating as stated.
PO?T

I’m trying my new OpenLog, but in Hyperterminal I see
12>
Why don’t start with
12<
????
I need the
New File Logging (default)
function.
Can you help me?

I haven’t been able to get mine working. Filed an issue over at the github page (http://github.com/nseidle/OpenLog/issues#issue/48)
Essentially the problem appears to be with activating the SD card, though the light that’s supposed to tell me it’s having trouble reading the SD card isn’t blinking.

Just bought one of these and I’m stunned by how simple is to set up and use. Just wire TX, RX, Vcc and GND; power it up and start sending data through the USART/UART interface of your microcontroller. Just be sure to cross the RX and TX lines. That’s it, you have a datalogger!

it is exactly what is written!! you have just to conect 3 wires. you dont have to write a single line of code in arduino. it is like a spy no the wires.

Got my OpenLog and it works perfect right out of the box. Logging data was cake! Using a PIC18F4620, basic UART at 9600. Works perfect.

Awesome product, I recommend it.

couple of questions, Is 8mA a constant current or Can it be turned off completely ?
Is there a website or project page to find more info or send patches?
Thank you,
Juan

There are some subtle changes between SD and SDHC. This page has a bit of information about it:
http://elm-chan.org/docs/mmc/mmc_e.html
Might be worth having a poke at the page here:
http://elm-chan.org/fsw/ff/00index_e.html
The sample projects may be of particular interest.

This is very nice, less than half the price of the logomatic, much tinier, and with the more familiar AVR.
It would be nice to see this grow and gain the same triggering-on-specified-character abilities as well, I see a lot of promise in this!

Just got it working! Very nice.
Couple of hints for others.
—Default baud is 9600 8n1.
—Make sure your card is formated as fat16.
—If you hook it directly up to FTDI Basic don’t forget to cross the rx and tx lines.

The schematic shows an AVR328, 3.3v and a 16Mhz crystal.
One of the three values is wrong or Atmel has a new version of the chip. A 3.3v 16Mhz arduino would be welcome…

Could someone try putting an SDHC formatted with just a FAT16 partition (I have several cards but they don’t have any more stock as I write this).
At least that would confirm the hardware would work without change.

I too am working on FAT32 – I won’t have one of these but I may try to do it on one of my arduinos.
Read works – I already have it scanning every partion (including an extended partition) for FAT32, then getting the boot sector and geometry, reading the root directory and able to read an entire file by following the FAT chain. In about 200 lines of code, 1 512 byte sector buffer, several limitations (512 byte sectors, no fs errors, short filenames only, etc.), but every FAT32 format I’ve seen does this.
I hope to get write working this weekend.

Another bit of strangeness – you have the reset circuit the same as the one on the arduino.
So connecting it to the arduino will result in the DTR line being functionally open – capacitor to capacitor.
Another (for me) annoyance is the inability to do binary. I suppose you could use a break condition to signal going back to command mode.

I have a 3.3v ftdi breakout (which works on all my arduinos).
I have it hooked up as in the datasheet on git, but avrdude can’t find it. Do I need 5v to do serial bootloading?
Nor can it find it if I connect it via ISP.
I can communicate fine in a terminal program and even work at different baud rates.
Does anyone have an avrdude command line that will recognize it?

To repeat for clarity -
It would help greatly if someone could give me an avrdude command line that will verify the above firmware’s hex file (I’m assuming that is what is in the unit), and one that will reflash it.
Also if there is anything tricky about using an ISP – the 4 data pins out of the six are on the other side. I’m using the sparkfun usbtiny but can try something else.

To use the firmware from the link on this page on a 3.3v arduino (e.g. pro mini) to the uSD breakout, you can flash directly using something like:
avrdude -c stk500v1 -b 57600 -P /dev/ttyUSB0 -p m328p -Uflash:w:main.hex
however the baud rates for the application will be off since the crystal is 8Mhz instead of 16. To fix that (so you can try enabling debug and SDHC) you need to add a line around line 76 of uart.c after it selects the baud rate by reading the eeprom.:

new_ubrr >>= 1;  

You will also need to adjust F_CPU to 8000000 in the makefile.
The breakout use CD. VCC and GND go to the 3.3 regulated out and grounds from the arduino.
The bottom four pins near the LED are the SPI.
From the bottom going up (10 going to 13):
pin func uSD
10 – SS – CS
11 – MOSI – DI
12 – MISO – DO
13 – SCK – SCK
SDHC cards are recognized if you set the option in sd_raw_config.h, and they can read FAT16, but doing ls, md, or trying to write will cause a reset (at least if debug is on).
2>disk
manuf: 0x03
oem: SD
prod: SU16G
rev: 80
serial: 0x7045eef6
date: 8/8
size: 15193MB
copy: 1
wr.pr.: 0/0
format: 0
free: 1029341184/1029816320

Now flashing the openLog – there seems to be a problem between avrdude – linux ftdi – 3.3v ftdi breakout – reset on the arduinos. Note I have 3 FTDI breakouts all 3.3v and it happens on all three.
I have a similar problem on my 3.3v arduinos (but they have a button and I’m used to pressing it). Fortunately the square framed hold is “reset” and shorting it to the uSD holder will ground it causing a reset – and releasing it will allow avrdude to flash.

Hi all, if any of you are trying to flash the firmware, i have written a short guide which is aimed at getting the OpenLog working with the UAV Dev Board, but includes information on getting new firmware onto the board. Unfortunately windows based, using winAVR, but the avrdude commands should be the same anywhere i guess. The guide is here:
http://code.google.com/p/gentlenav/wiki/OpenLogConnection
I have found the code to be very unstable in my environment for some reason. The code as supplied works fine, and simple changes (such as changing some baud rate stuff to enable 19200) work fine. But anything more complex seems to cause the code to fail in wierd ways. It still compiles and loads onto the OpenLog board fine, but code unrelated to the changes i have made will stop working. ie the ‘ls’ command will print out half the disk information table, then the device will crash and reboot. Seems like some sort of memory corruption, although i would have thought the stack and heap should be ok, as code use is only about 50% of capacity. Any thoughts?

1) Which one is STAT1 LED and STAT2 LED? I just wonder it be better if different color coding is used or label on PCB.
2) I just send out serial character “Hello” from Atmel to OpenLog. What should I expect as output? Will I see a text file if I read SD card from PC?
Thanks!

I successfully fed data into the logger and it works as expected.
Is it a “must” to read out the logger with a separate FTDI breakout or is there a way of using the Arduino for that? I can’t find a hint or even a tutorial.

http://harleyhacking.blogspot.com/2010/01/fat32lib-01-zap-your-card-edition.html
Alpha quality, but for really early adopters…
Flashable firmware, source with build-able library and sdhc driver. FAT32 only with 8.3 names only, but 11k for the lib and sd/sdhc driver.
Direct link: http://www.zdez.org/fat32lib-0.1.zip

The addition of a real-time clock would make this perfect for some apps I have in mind. Even if the clock’s only function is to put a timestamp on the log files.

I was wondering if anyone ran into the issue of a microSD card not support SPI mode?
I was reading that this is optional for microSD cards is this true?

Hi
How do I connect this to Arduino Duemilanove?
for mini:
GRN: Reset pin and connects to the GRN pin on the Arduino Pro Mini. Pulling this line low will reset the ATmega328. Because there is a capacitor on this line, holding this line low will not keep OpenLog in reset.
RXI: Serial input into OpenLog.
TXO: Serial output from OpenLog.
VCC: 3.3V to 12V input.
GND: Ground
BLK: This pin is connected to GND. Connect this pin to BLK on the Arduino Pro Mini.
Thanks

For the adventurous:
http://github.com/tz1/hyperlog
Works at 57600 default. Other baud rates by adding a 1-line (with line ending) HYPERLOG.CFG file containing the baud rate, e.g. “115200”.
Boots and starts logging. Break flushes, plus flush timer.

I’ve been testing these modules prior to installing in some equipment, ready to log long term on a beta product.
Apart from teething trouble at the start (the instructions for flashing are now out of date), I have managed to recompile and flash the firmware correctly. I have changed the code to 115200 in all cases.
I am using a 2gig SD card (not SDHC). Amongst other testing, I tested the open log by filling the card with 1.6gig of data (a 1.6gig file), then inserted the card into the openlog device. It fails to log with an “error writing to file” always. If I reformat and do not put 1.6gb data into the card, it always works correctly, it can log data.
My query is, has the openlog been tested to capacity of a 2gig SD card. Has anyone actually managed to fill a 2 gig card without errors?
I’m wondering at what point the logger starts to fail?
Any ideas?

Can the something like the Arduino read the file from this card and be able to transmit the information over an xbee to another xbee to store on another open log device?

I finaly got arround to tinkering with this. I connected it to my openlog with a 5v regulator and heat sink to power the vcc on both and so far the results are amazing. It was a bit of a challange to build a box but I have replaced a serial printer on a phone system with the openlog a 2GB SD card this RS232 Shifter SMD, project case. I reccomend a 5v power regulator and heat sink even if you have a 5v power supply because a quick test of any power supply on a multimeter will show you they all lie and with the high side of the openlog at 5v there’s just no point risking it all for a 2 dollar part.
If I could change anything about the openlog I would give it the option to write/read it’s settings to the flash card so they could be backed up, would not constantly write flash for file name incraments, could switched easily by swaping cards with two different pourposes, could easily be reset if bodrate etc was forgotten you could just format the sd card.

I’m having trouble withe the OpenLog dropping data. I’ve seen the problem at 57600 and 115200 baud. Here’s an example of the problem. I’m trying to log the sensor data for my AVC entry. The first column is the data point number and the second column is the time in ms.
2634, 134048, 80, 309.7, 512, 0, 0, 39.98120880, -105.24263000, 11.1460, 0.3200, 2.4900, 0.0000, 94.6021, 3
2635, 134098, 16, 310.3, 510, 0, 0, 39.98120880, -105.24263000, 11.090, 39.98121261, -105.24263000, 11.0720, 0.3500, 2.0600, 0.0000, 94.6038, 3
2641, 134398, 0, 309.7, 522, 0, 0, 39.98121261, -105.24263000, 11.0720, 0.3500, 2.0600, 0.0000, 94.6038, 3
2642, 134448, 0, 309.7, 510, 0, 0, 39.98121261, -105.24263000, 11.0720, 0.3500, 2.0600, 0.0000, 94.6038, 3
Sorry for the long lines, but you can see that data points between #2635-#2641 are missing and the dropout takes about 300 ms. This test was done at 115200, but I see the same thing at 57600. These sorts of dropouts appear in my data stream about every 0.5 to 1 second.
I’ve got the OpenLog hooked up to the Serial Tx of an Arduino Mega. If I look at the data stream via USB, it’s rock solid. No dropouts.
Any ideas?

Hi there.
Bought one time ago but I would need the new “read” command to avoid removing the card everytime.
I found the source code on the site but…
can someone help me in the whole process? compiling and bootloading?
No way to have the hex files ready to be bootloaded?
Forgive me. I a beginner, never used winavr or whatever.
Any help would be appreciated.
Many thanks in advance.

My Openlog works well when connected via a FTDI Basic to Hyperterminal at 9600 baud. However I want to connect to TTL feeds at 4800 baud. Can anyone provide the firmware update that will (say) replace the currently available 2400 baud option with 4800 ? Thanks

Hi,
I just received my openLog. Unfortunately, I see only empty files or files with 32kb of giberish (as seen in emacs). I am using 2Gb microSD card from Samsung. At the power-up the first led flashes and then he second flashes and stays on. I did verify that the card is FAT16 formated.
I do not have FTDI Basic so I can’t really debug with a terminal.
Question: is the default to start logging data or to wait for a command from terminal?

Thanks Nate, 4800 baud works well. I had a few teething problems with avrdude and finally found that I needed to get a copy of libusb0.dll and add it to the Win32 folder. After that it all worked as your upgrade firmware sheet said. Many thanks a great result for me. John W

Hi,
We’re using a few of these to log RFID via an Arduino Nano – in most cases this is working great, but a couple of the OpenLogs seem to have fallen into an unresponsive state – no serial response, no LEDs, no reset response. Connections look fine, no apparent damage on board. Any thoughts?
Rob

Have done, thanks

I’m using a FTDI 3.3v (DEV-09717) cable connected to my OpenLog. Using teraterm on COM10 I can make a connection to the device. all is good.
to upgrade the firmware I’m using the follow cmd:
avrdude.exe -p atmega328p -P COM10 -c stk500v1 -b 57600 -Cavrdude.conf -U flash:w:main.hex
and get this response:
avrdude.exe: ser_open(): can’t open device “COM10”: The system cannot find the file specified.
I have put libusb0.dll in the system32 directory.
is the problem that arvdude can’t handle high number com ports?
thank you
gek

I’ve got a wiring question about the openlog unit I just ordered and received. I currently have a daq unit set up to receive data from a few instruments and send it on request as a serial data stream via a usb connection on a com port I manage with a basic hyperterminal-like program (only in windows 7).
What I’d like to do, is initiate the daq unit’s serial data stream from the instruments by laptop and have openlog record the data to SD while I leave the whole unit unattended for a couple days.
what I’m wondering is if I can just clip the signal wire between the daq unit and the usb terminal and solder the open log in at that point and let it run (assuming I’ve wired up the vcc and gnd too).
Will that work? also, will my data “flow through” the openlog and be able to still be accessed by usb too? I’d rather not have to interface with the openlog if I don’t have to and I have very little experience with electronics or programing.
thanks for your help,
Justin

Gentlemen!
I am trying (unsuccessfully) to flash the firmware in my OpenLog using usbtiny.
I have connected MISO, MOSI SCK, VCC, and GND pins of OpenLog to corresponding pins of the programming cable. I am using this avrdude syntax:
avrdude -c usbtiny -p atmega328p -P usb -F -U flash:w:main.hex:i
And getting this:

avrdude: initialization failed, rc=-1
avrdude: AVR device initialized and ready to accept instructions
avrdude: Device signature = 0x000000
avrdude: Yikes! Invalid device signature.
avrdude: Expected signature for ATMEGA328P is 1E 95 0F
avrdude: NOTE: FLASH memory has been specified, an erase cycle will be performed

     To disable this feature, specify the -D option.  

avrdude done. Thank you.

I have noticed that we have 1k resistor on SCK pin (17). Is it the reason? will simply removing it fix the problem? or should I somehow remove the bootloader first?
Thank you,
James
N.B. I can program stand alone AVR’s…

Alright, finally got mine to work with the bus pirate. Here is what I found out:
to format FAT16 with dos in xp:
c:>format e: /fs:fat
*where e: was my removable uSD drive
fat can only handle up to 4GB, i was able to try both 2GB and 8GB. I could not figure out how to partition the 8GB with XP and could not format the 8GB. The 2GB worked fine.
I was not able to get to command mode with the bus pirate. Ctrl+z or decimal equivalent 26 or 0x1A three times only result in garbage output. I will try directly connecting to the rs232 of my pc later to see if this gives me different results. I’m a little sick of decrypting hex input and output from bus pirate.

Hi there,
the OpenLog makes my current project a lot easier than expected, but there is one thing that could be optimized, maybe you know more:
Is there any possibility to reduce the bootup time of the OpenLog, for example by bypassing the bootloader or something.
I only want to read from the module, ideally as fast as possible after startup.
What do you think?
Martin

Hi, I need to record rs232 serial data from a pc then play it back through a servo controller. I figure this will record the data but can I play it back directly into my servo controller. Normally the PC goes straight to the controller card but I want to eliminate the pc in the field and just play back a recorded sequence from this card. Anyone know if this would work? Or a better idea?
Thanks

Can the Atmega328p take a 5V signal on its serial in, or is it only 3.3V? I don’t want to fry this little logger…

What is the status on the FAT32 support? I have noticed that tz has created something, do I flash the openlog as if I were updating the firmware? Possible link to the most up to date version of tz’s FAT32 SDHC code?
Thanks

Updated to V2.1 w/ Arduino 00118 after having the repeated 12< problem. The logger creates new files, and can be interfaced over the serial port, but the log files are always empty. Connecting to an Arduino Pro Mini 328 5V 16Hz.
Also, the reference to how to upgrade the firmware should be taken off, I only figured out that flashing the Open Log was no longer necessary when it was discovered that there is no main.hex file anywhere to be found…
I still hope that I can get my Open Log to work!

The v2 code is just awesome! Now I have the ability to eliminate the Arduino that I had use to sort through the data stream. Question: If I were to add some code that would analyze the data, and choose what to log. Which loop would that go in? (I am not a strong coder)

Hi, great stuff, already started to assemble five Razor 9DOF+OpenLog for my experiments ;–)
However, I struggle to get this combination working and hope somebody is able to help me with this. I can connect to the OpenLog with the FTDI cable but “disk” only returns a “error reading disk info” and recording fails as no logfiles are created.
I’m using the 1.61 firmware with a 2GB card from SanDisk.
I already had to format the card once with a FAT 16 filesystem and also tried to repartition under Linux (mkfs.msdos)
Any ideas what could cause these troubles?
Thanks!

Different question concerning the latest 2.2 firmware:
I just tried to use that firmware trying to solve my problem mentioned earlier and found something weird: Although the baud rate is set to 9600 (no config.txt on the card, menu output) I have to connect to the OpenLog with 19200 bps…

This works great!!! — but is there a way to stop the blue LED (STAT1, to the right of the ‘g’ in “openLog” written on the board)?
It keeps flashing, perhaps to indicate serial communication between my arduino board and the openLog.
I want to do day-long logging of biometric signals (initially at a high data rate, to figure out what is going on, then hopefully at a lower rate) – and I wonder how much of the battery gets used up by the blue LED flashing non-stop.
Right now I am just using an Arduino mini, an openLog, and a 3-axis accelerometer, and logging x,y,z at 4Hz draws 10mA from the battery!
Thanks,
PLM.

Is there a way to use an RTC with this device simply to get a time and date stamp for free running logging operations? Has someone done this?
Thanks,
KB

One problem with my Logging V1.61:
I can not use any set Command. I sent:
“set New File Number”. And it replied:
System Configuration
Current boot mode: Command
Current escape character and amount: 26 x 3
Change to:
1) New file logging
2) Append file logging
3) Command prompt
4) Reset new file number
5) New escape character
6) Number of escape characters
x) Exit

I’ve tried with “set 4)”, “set 4) Reset new file number” but nothing work. Please help me, Thanks!

Hi guys,
I’m having some troubles with my OpenLog.
Here’s the setup:
OpenLog FW:2.21
PC –> FTDI basic breakout –> OpenLog.
2Go micro-SD formated FAT32, with only 2 files : config.txt and settings.txt (406 bytes long).
I open a terminal app (TeraTerm) on COM3, 9600,8N1.
I can read both files with the read command.
But, if I first try to get the size of a file (ex. “size settings.txt”), and then try to read the same file (with or without any parameter), it ends with an error to open the file… ;(
Then, I have to switch off and on the OpenLog to be able to read a file again… the “init” command doesn’t change anything.
Any idea ?
thanks.
P.S: I tried to restore FW 1.61, but each time avrdude says everything is ok, but I get the blue led dimmed (like pwm'ed at ~20%), and no communication at all …

I am having an issue with my openlog, it stops logging after about 15 to 20 minutes even though the blue status light still blinks. I am using a 2GB card, and have it hooked up to a Lilypad. Does anyone have an idea of what could be happening? It did seem to work longer on the first day that I used it. Any help would be much appreciated.
Thanks, Julio.

Has anybody used this for over a few days without stopping? I have found a problem that after about 10 hours or 5 mb of data some numbers start to be replaced by letters. The replacements are always the same eg. 0 turns into p.
Any thoughts on this?

Bought the OpenLog a few months ago and left it in a drawer. I finally found the time to try it out this week and I cannot get it to work to save my life…
Basically the green LED blinks three times indicating no SD card initialized constantly. I have tried several different SDs (SanDisk @2G, PNY @2G and 4G), made a point of formatting them to FAT16 (using a number of different methods), all to no avail. I reflashed the OpenLog to the latest firmware, now I can see a “1 error card.init” on power up.
This almost appears to be a hardware issue – has anybody else had similar issues?

I just hooked up a OPenLog to my Arduino Duemilano .
I tried the OpenLogTest.pde file. The led on the OpenLog indicates it is getting data but I see no files being created.
I even created a CONFIG.TXT file — It did not create one.
I am using a 2GB card. I did not format it , but my PC reads it just fine…
Any ideas?
Could I have overwritten the Flash, if it was connected when I downloaded a sketch to my duemilano. It seems to use the same I/O pins??
Thanks

HardWare keylogger, anyone?

Been using OpenLog for 3 days now. It’s exactly what I was looking for. Works like a charm (once I understood how to enter command mode ;–)). I am using Kubuntu with a Seeeduino V328.
This is an excellent example of a product which simply works, period. Thanks Nate.
Regards, Garry

Sorry, I forgot!, Merry christmas.

Can I flash version firmware 2,41 while connected to my Seeduino, or will this only work with an FTDI board
regards, Garry

How easy is it to wire this up to the SD card socket break out board? http://www.sparkfun.com/products/204
A royal PITA? I’d rather not have to get the MicroSD socket BOB, too.

I bought one of these.. but cannot get it to work.
I dont have the FDTI cable, so I cant use any of the commands. I’m just sending text to the serial monitor, is it just supposed log? or is anything additional that needs to be done? as far as wiring the rx on openlog should be connected to the tx on the arduino?

How is long term (months) stability at low/moderate logging speed? I see some comments having problem with this.
/

I need to transmit the data stored in a SD card that is inside a datalogger Openlog with xbee, How can I read the data remotely through openlog?

Just tested my OpenLog device. Works great at first step but pushing it up a little makes it losing data quickly…
Sending a continuous data flow to the OpenLog at 9600bps is ok. But it starts loosing some bytes at 19200bps.
I am quite disappointed as the description & datasheet pages say that it’s working at 57600bps and even at 115200bps! :–(

It says that the chip has:
“Configurable baud rates (2400 to 115200bps)"
but
"Doesn’t drop characters even at full-blast 57600bp"
So what is the maximum baud rate that this chip can take without dropping characters? Has anyone tested this chip and found the the actual max baud rate and storage capacity?

Can I use this with 9 Degrees of Freedom – Sensor Stick
sku: SEN-10321?

Hi – I am trying to use this board along with a the 9DOF Serial AHRS board. The 9DOF is putting out what I expect over the serial port. When I connect the OpenLog, the blue light blinks and it appears to try to read, but I get mostly glitchy output at 57600. Any suggestions? (sample output below). OpenLog reads the CONFIG file correctly and makes a new file for the data but it’s glitchy… (though it looks OK when I read the serial port not through OpenLogger – gives good 9DOF outputs in Arduino Serial Monitor).
372
38SH¯416
·j
5SH®Ÿ≤j
!ANîjÇ.0L r72 r∫4C·!ANG:Krí2,1.78,1.sLC·!AÍÈ-1.05,3.0&˘&)Ój
!ANG:K& íbìâ.b˛&)Çj
!ANîjíríÆb~M Vb˛&)éj
!ANîjNräÇ,6.79,4.73
!ANGßIríÇbÓr≤Çb5.12

Usefull thing!

I was wondering if there is any way to set this up to transmit data on startup.
My project idea is a gps logger, but it looks like the gps has to be initialized first. I imagine it would be easy enough to edit the firmware but only the hex file is posted.
Thanks

I’m having a huge problem with one on firmware 1.6. It just keeps giving me ‘cannot create config file’ and ‘too many logs’ even with a clean formattted, SMALL card (16 MB). SOme other cards simply cause it to send a series of 1’s.

Hello,
I got one openlog, but I currently am unable to get it to work. When I power it up, it outputs the 1 over an FTDI converter and then it stops. Blue LED will blink 3 times after a while (= problems initializing the card). So far so good. I tried to update the firmware to the newest 2.41 version, as I’m using a 4GB SDHC (Toshiba) card (formatted FAT16 and FAT32, both didn’t work). I’ve downloaded the newest firmware from the github and tried to bootload it. The bootloading seems to work as V1 can be bootloaded without any problems, but when loading V2 avrdude reports me an error. It starts programming 32768 bytes (which is maximum of the ATMega) and during verifing I’m getting the error:
avrdude.exe: verification error, first mismatch at byte 0x7800

         0x32 != 0x0c  

Strange is also, that the file sizes between V1 and V2 are very different. The current V1 hex file has 69.108 bytes and the V2 hex file (filename: OpenLog_v2.cpp.hex) has 247.589 Bytes?!
Anyone any ideas?
Greetings from Germany,
Mike

I’m not sure if mine is bad or not. I plug it into power, and the serial terminal receives a 1 repeated every second with a sdhc card plugged in. When I unplug the sdhc card, the character changes to the ‘n’ and when a character is typed into the terminal (putty) it changes to the ‘u’. I think I may have broken it, however, the fact that the output changes when I modify conditions makes me think that it is still functional.
I have attempted to re-flash it using the command prompt utility, however no luck.
any help?
-Alex

what oscillator is on the board. It’s tiny! Can I get a part number?

Hi,
Anyone encountered this problem while flashing the firmware? Thanks!

Bryan

C:\openlog>avrdude.exe -p atmega328p -P COM6 -c stk500v1 -b 57600 -Cavrdude.conf
-U flash:w:main.hex
avrdude.exe: stk500_getsync(): not in sync: resp=0x00
avrdude.exe: stk500_disable(): protocol error, expect=0x14, resp=0x51

avrdude.exe done. Thank you.

Hi,
Does anyone encounter this error while flashing firmware? Thanks!

Bryan

C:\openlog>avrdude.exe -p atmega328p -P COM6 -c stk500v1 -b 57600 -Cavrdude.conf
-U flash:w:main.hex
avrdude.exe: stk500_getsync(): not in sync: resp=0x00
avrdude.exe: stk500_disable(): protocol error, expect=0x14, resp=0x51

avrdude.exe done. Thank you.

Is there a way to start logging to the OpenLog based on an external trigger? if yes, how?

When the stock will be available?

I ordered two Openlogs. One came with firmware v2.5 and supports the ‘reset’-command in commandmode. The other (as I figured out after some hours of testing around and cursing (g) was only firmware v2.41 which doesn’t support resetting.
I tried to compile v2.5 using the latest Arduino-IDE and following the steps explained on the datasheet precisely.
At the first try my OpenLog suddenly only logged chinese characters (which were definitively not “thrown” at him). Now after a reboot of my computer v2.5 won’t even compile because some error in the ‘special’ HardwareSerial.cpp supplied for programming v2 onto OpenLog using the Arduino-IDE.
I then tried to upload the latest .hex file using avrdude. But the latest .hex-file on GitHub is v2.41. Could you please make a .hex for v2.5 available? Thanks in advance.

This is somewhat new to me so excuse by basic questions. I have a system on my airplane that displays all the engine temps and pressures but does not record data. It does have a serial data out line so I bought an OpenLog, made up a 5 volt power supply using a 7805 voltage regulator, and wired it up. I then formatted the card using my laptop, plugged it into OpenLog, and turned on the electrical system and data display system for a few minutes. Then I took the card to my laptop to see what had been generated.
OpenLog made a CONFIG.TXT file and a data file named LOGO0015.TXT. The CONFIG file is fine and reads 9600, 26, 3, 0, but the LOGO file is not text, it’s lots of funny characters.
So how do I convert everything to text I can parse into a spreadsheet?
Here is what the data looks like:
úþþþþþ.þþžÆþþnþþÖ 1 1žžîüþþþþþþþ þþþ2 þþþþþþþþþþþþþþ²þ®þ²þÒþº

SALUT
JE VOUDRAIT ACHETER UN OPENLOG
POUR TRANSFERER LES DONNEES COMME EX:2235687611234567//2345678987654324567 AVEC LE OPENLOG UNIQUEMENT ET LIRE DONNé simplement comme avec l'exaple project sensor sur sparkfun
mais juste ce que je veut faire c'es la meme chose sauf que c'est avec une tete magnetic que je veus utiliser avec le openlog;quelq'un peut aider ?

SALVATION
I would buy a OPENLOG FOR TRANSFERRING DATA AS EX: 2235687611234567 / / 2345678987654324567 WITH OPENLOG just as with the example project on sensor Sparkfun but just what I want to do the same thing c'es but with a magnetic head that I veus Use with openlog, I am not very strong in electronics, can you help if possible thanks

I’m having problems dropping my OpenLogs into command mode from my Arduino. The Arduino is connected to a GPS so it knows the time and date; i would like OpenLog to name a new file with this information. I have tried multiple ways of sending character “26,” BYTE, BIN, HEX, OCT, DEC, line feeds between each send, no line feeds… maybe i’m just not doing something right; but does anyone know how I can drop it into command mode? Also, is it capable of logging to two files, if it enters command mode and alternates between these two files? does anyone know how long it takes to switch between two files?
Any and all responses appreciated.

EXCUSE ME IF I HAVE DONE WRONG UNDERSTANDING.
WHAT I WANTED TO SAY MY QUESTION IS:
I would like to directly connect a magnetic head (read magnetic tracks) with openlog and read the data without basic module, with only the console log and a magnetic head, I hope you understand me thank you for your help

I am having trouble using the openLog with NewSoftSerial on an Arduino Uno. It seems to log alright and I can get the openLog into command mode but when I have openLog return serial data (with commands like ls or ?) there are random characters missing. For example ? returns:
OpenLog v2.5
Basic commands:
new : Creates
append : Appends text to end of . The texti edfo h ATi temadi o cod iihb edn tlz(SI 6
m drcoy rae ietr ald
…
I have rx set to pin 6 and tx set to pin 7. GRN connected to reset on the Arduino. Otherwise I have GND and VCC to 5V connected. Changing the baud rate does not improve things.
Any advice? Is NewSoftSerial not capable to receive the serial data correctly or do I need additional settings?
Thanks in advance.

I need MMC support to run project in Proteus (SD/SDHC doesn’t work with it)
And how i can compile this project without arduino IDE?

How does the soldering work on a board like this which has components to be mounted to both sides? can you still use the hot plate method?

How many channels can this thing do?
Can I simultaneously log data from 3,4,5 etc inputs?

Is there a chance that you’ll carry just the bare ATmega preprogrammed with the OpenLog firmware?

Recently got some of these, and found with an ISP that the efuse was invalid. The brownout bits were 000. That is listed as “reserved” in the datasheet, wonder what it does? I think they are supposed to be 101, or “5”. Was it shipped that way I assume? By the way, hooking a pod to openLog is a bit of a pain…

The GitHub has ver 2 firmware sources available.
Are the ver 1.61 firmware sources available ??
thanks

Has anyone besides me noticed the 3M logo on the slot?

I ovewrwrite the program in the microcontroller chip. How do I restore it. I want the old program back. I am using SPI programming method by codeVision software

Can we edit files on this from an arduino? I was going to try and use this as a hard drive with the arduino pro mini.

Using this to test:
https://github.com/nseidle/OpenLog/tree/master/OpenLog_Test_Sketch
It drops 40-80 consecutive characters
every 100 lines or so at 115kbaud.
What good is this?
If it consistently fails?
Am I doing something wrong?
Can I add a delay to cure it?

I could not get 57600 to work. But it wouldn’t be fast enough for my application anyway, so I stopped trying. Instead at 115 kbaud this works for awhile:
delayMicroseconds(80)
I’m happy with that EXCEPT…
About every 60-100K the data is corrupted. 10 files are created. Normally the blue light appears solid, instead it flashes slowly alternating with the yellow light. This is not acceptable. Even using a delay of 800 it happens less often. This is very slow.
Please help!

This is related to a delay allocating the next cluster from the FAT. How can we work around it?

Got it to work kinda by delaying 30ms every 600 bytes using Serial.write. Trial and error. This is about 7K/sec. Usually it’ll go 1-2GB before it misses a single byte, then it misses 100+. That’s the best I can do. Only a little bit better then 57600 baud in theory. Which I have not tried. For a short while I can write at 8K/sec. Keep in mind I’m using an old slow SD card.

Still missing characters when trying to send 8K/sec at 115kbaud. After a year of this problem it’s still not resolved? Using trial and error I’ve found some delays that seem to work. This took hours of experimenting to resolve. Great I thought! Then I tried a different (faster) SD card. I’m back to square one. It misses 10-500 characters in a row about ever 1000. Which firmware will resolve this? Is there any way to work around it? If I knew when it was about to miss, I would wait. But there seems to be no pattern it’s different every time. Please help!

I Have loaded Version 2 in my new open log hardware and on power up i am getting 12< but after that i am logging data with 9600 baud rate and i am unable to log it and not getting echo too.
Please help me what should be the problem?
Thanks
Priyank Patel.

I’m trying to find or make something that will log serial data out of an controller. The controller will output serial data, but needs to be asked to send it. I’ve looked through all the documentation but can’t find the answer anywhere…

Can the OpenLog send a command to trigger some data? As an example, I’d want to send 02 0A 41 01 00 02 69 01 00 69 02 00 03 19 01 as a hex string which should then give back something like 02 03 40 01 21 41 01 02 16 03 5A.

I then would need to check the last few bytes to see if it’s an error and if not, store the data from some bytes further back in the string.

If I haven’t asked in the right place or you need some clarification, please shout :)

I set the config system mode to 2,my Hyperterminal start with 12>,but when I enter ‘new a.txt’ ,nothing has happen,why can’t I creat a new a.txt .

why my command is no use?