Remember, if you get OpenLog stuck into an unknown baud rate, there is a safety mechanism built-in. Tie the RX pin to ground and power up OpenLog. You should see the LEDs blink back and forth for 2 seconds, then blink in unison. Now power down OpenLog and remove the RX/GND jumper. OpenLog is now reset to 9600bps with an escape character of ‘ctrl+z’ pressed three consecutive times.
I also would like to see more information from anyone who has sucessfully used OpenLog as a stand alone logging device. I am having significant issues using a seperate RTC(SPI) and Openlog to try to make a standalone logger capable of timestamping.
There is very little informtation or examples (any?) of a modified firmware for openlog.
I know this thread is 7 months old with no activity, but hopefully someone will see this.
Sadly to large a form factor for my needs. I appreciate the information, I do hope someone who has been able to actually get a moddded OpenLog working will chime in.
I just would like to see some examples, especially of multiple SPI devices.
I have modified the OpenLog firmware to make a portable serial uSD card data logger. This was relatively easy using the sources from the SparkFun OpenLog GitHub.
On the SparkFun Flashing Firmware web page (Flashing Firmware · sparkfun/OpenLog Wiki · GitHub), they suggest using their FTDI Basic and Crossover Breakout for FTDI boards to connect to the OpenLog board. I just used a RS-232 serial-to-TTL adapter I had instead (in the schematic on my web page for the portable serial data logger, you can see I used a MAX233 device - note, it is wired as a DTE so a null-modem adapter is needed to connect the correct signals on the DB-9 to the COM port on the PC). The signals that need to be connected are: Rx, Tx, DTR, and GND.
Anyway, after connecting the OpenLog to the PC, the Arduino software environment (Arduino 1.0 or later) is used to reprogram the OpenLog device similar to what would be done if you were programming/uploading to a standard Arduino board. In fact, the OpenLog appears to operate as an Arduino Uno, so, in the Arduino software environment, set the board under Tools->Board to Arduino Uno.
All of this is spelled out reasonably well in the Updating Firmware on OpenLog v3 section on their Flashing Firmware web page. If you follow their instructions, including obtaining the needed SerialPort and SdFat libraries, you should be able to recompile the OpenLog_v3.ino from their GitHub site and load that on your OpenLog device as a start. From there, its just a matter of modifying the original source for the feature changes you need. (If you look at the source files on my web site, you will notice I split the original OpenLog_v3.ino into multiple .ino files to make it easier to manage as separate functional modules that all get compiled into one executable by the Arduino software environment.)
i just tried compiling with 1.0.5r2 and no issues. it ONLY uses the SD.h from the standard Arduino library, so you should not need to worry about any other code.