NEW OPEN LOG FROM SPARKFUN (VER 1.1)

[SIDDHARTH]

Dear All  / Adam ,

 

                                    Hi  , I have received openlog (with new 1.1 firmware version) from sparkfun and 5V ftdi as well. As per the instruction below on the wiki  “ Note: (04Jan2010) The latest OpenLog firmware (v1.1) which is shipping on any new devices sold by sparkfun fixes a number of isses, and changes its default behaviour slightly from that described in this document (v1.0). This document will be updated shortly to reflect this fact. If you need to get one of these devices working in the meantime, contact Adam Bellchambers via the uavdevboard Google Groups mailing list. “

 

            I connected openlog with 5V ftdi cable and found that the Version is 1.1. With the note below on the Sparkfun page

 

Upon power up, in default ‘NewLog’ mode, OpenLog will output ‘12<’ (note the less than sign) at which time you can start throwing characters at it. Those characters will be recorded to LOG###.txt. You can press Ctrl+z at any time and OpenLog will exit record mode and drop into command mode. Command mode is signified with a ‘>’ (greater than) sign. You can then enter the following commands:  http://wiki.github.com/nseidle/OpenLog/command-set

 

Hyper Term Screen below :-

 

12<~>?

 

OpenLog v1.1

Available commands:

new <file>              : Creates <file>

append <file>           : Appends text to end of <file>. The text is read from t

he UART in a stream and is not echoed. Finish by sending Ctrl+z (ASCII 26)

write <file> <offset>   : Writes text to <file>, starting from <offset>. The tex

t is read from the UART, line by line. Finish with an empty line

rm <file>               : Deletes <file>

md <directory>  : Creates a directory called <directory>

cd <directory>          : Changes current working directory to <directory>

cd ..           : Changes to lower directory in tree

ls                      : Shows the content of the current directory

cat <file>              : Writes a hexdump of <file> to the terminal

disk                    : Shows card manufacturer, status, filesystem capacity a

nd free storage space

init                    : Reinitializes and reopens the memory card

sync                    : Ensures all buffered data is written to the card

 

Menus:

set                     : Menu to configure system boot mode

baud                    : Menu to configure baud rate

> 

 

 

 it is stated that openlog will start recording any  incoming serial data on power up and at every power up it will record a new file.. I think the previous issue of start recording on file is resolved with the new version. The only issue remains is now the baud rate (our requirement is 19200 which is not there in the setup menu.

 

            Since I am not a programmer but with some hard way research I found below setting in serial I/O. Since Remzibi can accept @ 9600 bps .. If we do the necessary changes below to output extra serial port @ 9600..Will it affect anything else or degrade any performance of UDB ? If below is fine then we do not need to modify the firmware of OPENLOG and it will run straight out of the box.

 

            Or should we wait for the new openlog firmware modification ?

 

SerialIo.c changes :-

 

            // Otherwise, the baud rate is set as specified below

//          U1BRG =  51 ; // 4800 baud

//          U1BRG =  25 ; // 9600 baud

            U1BRG =  12 ; // 19200 baud

 

            Comments from ADAM and everyone awaited.

 

Regards

SID  

[Adam Barrow]

SID,

 your analysis is spot on! We have two choices at the moment, to either update the UDB to run the 'telemetry' serial port @ 9600 or update the OpenLog firmware to run at 19200 (I and I think Adam Bellchambers have been running our OpenLog modules with the later option). 

We have seen some dropped telemetry even at 19200 but I'm not sure yet of the actual cause. If you'd like to run with 9600 baud on your UDB, the worst case would be that some of the telemetry lines are incomplete (dropped) and perhaps some of the output to the Remzibi OSD. To make that change, comment out (add // at the beginning of the line) the U1BRG=12; line and the uncomment (remove the // at the beginning of the line) the U1BRG=25; line. If you are using the Remzibi serial format, however, there is a U1BRG line just above these three that is used (this block of code applies to everything except SERIAL_Remzibi) and changing this line doesn't have any effect. If so, set that line (just above this block) to 25 (U1BRG=25;) for 9600 baud or 12 (U1BRG=12;) for 19200 baud.

If you want to run the OpenLog module at 19200 baud (as I have been) you need to update the OpenLog firmware with the modifications developed by Adam Bellchambers. The process is mostly as described on the wiki, just updated since the OpenLog modules shipping from SparkFun now come with firmware v1.1. Note that this procedure puts a modified version of OpenLog firmware v1.0 that supports 19200 baud on the module (I'll try to port the 19200 changes to v1.1 soon) but that also is a proven configuration and matches the way the current OpenLog support in the UDB is coded.

Here's what I had to do, starting with an OpenLog module using firmware version 1.1 (Adam Bellchambers, please feel free to update your wiki page with these steps if you'd like):

1. Install WinAVR (per the current wiki directions)
2. Install Arduino sofware (per the current wiki directions -- I downloaded 0018 this time)
1. Make a note of where you extract the Arduino zip file (mine was c:\arduino\0018)
3. Update the 'shortcut' in Programmers Notepad to make and program the AVR (per Nate's tutorial, referenced from the current wiki directions)
1. Open Programmer's Notepad (under the WinAVR folder in your start menu)
2. Select Options from the Tools menu
3. Click on tools in the treeview on the left of the options panel
4. Click on the 'add' button
5. Fill in "Program Serial" (or whatever you'd like) for the name
6. Fill in "make" for the command
7. Fill in "program_serial" for the parameters
8. Set the shortcut (if you'd like) by clicking in the shortcut field and hitting a key (F5 for example)
9. Hit OK and OK again (closing the options dialog)
4. Connect to the OpenLog using HyperTerm
1. Make the connections between your USB serial adapter (I'm using an FTDI 5v) and all six pins of the OpenLog (per the wiki directions)
2. The initial HyperTerm settings are 9600 baud, no flow control, and the appropriate serial port for your setup (per the wiki directions)
3. When you connect, you should be greeted by the 12< prompt
• This is different that v1.0 (the < prompt indicates that the OpenLog is capturing to a file)
• If you only get a 1 then make sure there is a MicroSD card inserted (the OpenLog won't continue without this)
1. Hit CTRL-Z (control and Z) to close the log file and go to command mode
2. You should now have a > prompt (> indicates the OpenLog is in 'command' mode)
3. Type ? and ENTER to get a list of commands and confirm the firmware version (which should match the screenshot below)
4. Type "baud" (no quotes) and ENTER to set the baud rate
5. Type 3 and then ENTER to set the baud rate to 56700, and your screen should look like the following
6. Restart HyperTerm at 56700 baud and reset your OpenLog module (I disconnect and reconnect the GND) to confirm that communications are working
7. Close HyperTerm
5. Download and unzip the OLFWforUDBv1 file from the wiki (this is Adam Bellchambers' custom firmware)
6. From progammer's notepad, open the Makefile in that directory (where you unziped OLFWforUDBv1)
1. Under the file menu, choose open... and browse for the directory where you unziped the firmware
2. Select the file named "Makefile" in that directory and open it
7. Customize the makefile for your environment
1. Scroll down through the makefile to find the section that begins with the line "#---------------- Programming Options (avrdude serial bootloader) ----------------"
2. Update the line that starts "SERIAL_AVRDUDE" to match where you installed (extracted) Arduino in step 2 above (in my case, this was "SERIAL_AVRDUDE = C:\Arduino\0018\hardware\tools\avr\bin\avrdude")
3. Update the line that starts "SERIAL_AVRDUDE_CONFIG" to match where you installed Arduino in step 2 above (mine was "SERIAL_AVRDUDE_CONFIG = C:\Arduino\0018\hardware\tools\avr\etc\avrdude.conf")
4. Update the line that starts "SERIAL_AVRDUDE_PORT" to match the COM port on your system (mine was "SERIAL_AVRDUDE_PORT = COM3")
5. Save the updated makefile (file menu -> save)
8. Build and program the new OpenLog firmware
1. Under the tools menu, select the new shortcut you created in step 3 above ("Program Serial")
2. After compiling the firmware, the AVRDude tool should start programming the module with the new firmware
3. There will be two progress bars as the module is first programed and then verified 
4. Make sure the output window ends with "avrdude.exe done.  Thank you." and then "> Process Exit Code: 0" (see screen shot) 
1. If it doesn't the process is either not complete or had some issue
2. If you need help, copy and paste the complete contents of the output window into an email and we can try to help out

1. Confirm the OpenLog is set to 19200 baud
1. Open a new HyperTerm connection at 19200 baud, no flow control, your COM port as appropriate
2. You should be greeted with "12>"
3. Type ? and ENTER, you should have a screen similar to the following 
4. Close HyperTerm
2. Connect the OpenLog module to your UDB (as documented on the wiki -- only VCC, GND, and RX are required on the OpenLog)

Hopefully this helps anyone who is trying to use an OpenLog module with the UDB. If you have any questions, please don't hesitate to ask.

Regards,

Adam Barrow

[ben levitt]

We should add this to the wiki!  :)

Ben

To unsubscribe from this group, send email to uavdevboard+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.

[Netfoot]

I converted my OpenLog for 19200 on Slackware with little difficulty, thanks to having previously installed the Arduino 0017 tools.

I downloaded and unzipped the OLFWforUDBv1 file from the wiki into a temporary directory

mkdir OLFWforUDBv1
cd OLFWforUDBv1
wget http://gentlenav.googlecode.com/files/OLFWforUDBv1.zip
unzip OLFWforUDBv1.zip

then I set the path to include the directory where avr-gcc lives, and ran the Makefile:

export PATH=$PATH:/home/netfoot/local/avr/bin/
make

This built the main.hex file for me.   (Any good reason why the mods couldn't have been distributed as a ready-compiled HEX file?)

Then as root, I ran minicom and set the default baud rate and serial port

minicom -s

I set the baud rate to 9600 and the device to /dev/ttyUSB0, saved these settings and exited the program.

I plug the OpenLog into a 3.3v FTDI cable (via a homemade harness) and restart minicom without initializing:

minicom -o

I checked that I was talking to the OpenLog by looking for the 12> prompt and running disk command.
Then I set the baud rate of the OpenLog to 57600 and exited minicom without resetting.

Now to program the Openlog!  I ran avrdude from the command line as follows:

/home/netfoot/arduino-0017/hardware/tools/avrdude \
    -C /home/netfoot/arduino-0017/hardware/tools/avrdude.conf \
        -p atmega328p -P /dev/ttyUSB0 -c stk500v1 -b 57600 -U flash:w:main.hex

This produced three progress bars, and some status messages, ending in "avrdude done.  Thank you." in a total of about 16 seconds.  I then ran minicom (without initialization) again:

minicom -o

connected to OpenLog, ran the set command and selected the 19200 baud option.  The OpenLog responded with something like "Going to 57600bps..." (not 19200 as expected -- suspect the message text was not updated to reflect the 19200 baud changes).

I disconnected minicom, reconnected at 19200 and I was able to talk to the OpenLog just fine.

The only trouble is, I've lost my other OpenLog!  It's somewhere on this desk... (They make these things too damned small...)

[Peter Hollands]

Angus,

Thanks for the detailed instructions for success with OpenLog.
I am going to buy a few of those as well. They sound great.

I take it that the instructions are for some one that is running a version of Linux.

Best wishes,

Pete

[Netfoot]

On Tue, Mar 30, 2010 at 2:31 AM, Peter Hollands <peter.h...@gmail.com> wrote:

I take it that the instructions are for some one that is running a version of Linux.

Sorry Pete, I should have made that clear.  Yes, it was done on Slackware Linux.
---
Angus

[Riccardo]

Hi,

I need some help with Openlog.

I connected it with FTDI cable (TTL232R 3V3, DIYDrones store) on
Hyperterminal, but I get nothing.
I set 9600,8,none,1,none, card inserted and right COM port. Openlog
led lights briefly, but no data.

Could someone help, please ?

Thanks a lot !

Ric

On 30 Mar, 14:06, Netfoot <netf...@gmail.com> wrote:

[SIDDHARTH]

Ric.. You need 5V FTDI not 3v3.. It will work out of the box..

SID

[Riccardo Kuebler]

Sid,

this cable has Vc 5V. Signal is 3.3V.

Are you sure the problem is the FTDI cable ?

Ric

2010/5/14 SIDDHARTH <sysn...@sify.com>

[Riccardo Kuebler]

I think I've found the problem. Reading the schematics it seems I have to build a cable that invert TX and RX.

Ric

2010/5/14 Riccardo Kuebler <kue...@ticino.com>

[Adam Barrow]

Ric,

 everyone I know of has used the 5v FTDI with the OpenLog. I'm not saying that it won't work with 3v, but that I know it has worked with 5v.

When did you get this new module? Starting with firmware 1.5 the default settings are to automatically start logging (it's almost plug and play) to get into command mode you have to send 3 CTRL-Z codes. Starting with firmware 1.6, you still have to do that, but the OpenLog will also read and write it's config on the SD card. 

Another thing you can try (assuming the FTDI cable isn't an issue) is to reset the OpenLog. 

Regards,

Adam Barrow

[Adam Barrow]

Ric,

 yes - the pinout on the OpenLog is reverse of the FTDI (you can use the OpenLog as a drop in replacement for an FTDI connection in this case ). 

Before you make the cable, can you read my other email? If your OpenLog is brand new it might have firmware 1.6. If it does, you can set the configuration by making a CONFIG.txt on the SD card with this line in it: "19200,26,1,0" (no quotes). Details on the features can be found from http://wiki.github.com/nseidle/OpenLog/command-set.

If your module has FW 1.6 or newer on it already, you can tell by just looking at the SD card in a PC. The OpenLog module will have created a CONFIG.txt for you when it was powered up.

Regards,

Adam Barrow

PS: Yes, I really need to update the wiki with this information -- I'll try to get to it this weekend!

[Netfoot]

On Fri, May 14, 2010 at 7:11 AM, Adam Barrow <adam....@gmail.com> wrote:

everyone I know of has used the 5v FTDI with the OpenLog. I'm not saying that it won't work with 3v, but that I know it has worked with 5v.

I have both.  It works with both.

[SIDDHARTH]

Ric,

            I think so , since I have 5V ftdi only and not 3.3 one.. It has worked great with 5V one.. BTW you also need to insert 1 or max 2GB sd card in it to make it work.. perhaps.. If the card is there one of the LED becomes steady.. Did you wire the same as per the wiki  (http://code.google.com/p/gentlenav/wiki/OpenLogConnection)  …for open log as below..?

 

FTDI	OpenLog
RX	TX
TX	RX
VCC	VCC
GND	GND
DTR	DTR*

 

            If everything is right you will get 12> prompt in hyper term.. Then you press control Z and use commands as per the wiki..

 

            I hope this will help.

 

Regards

SID

---

[JERRY CHAPMAN]

Ric,
I just got a openlog and FTDI 5V yesterday.  I had to swap RX and TX.  After plugging it in the left led should come on, then go off.  The right led comes on for a short period and then goes off.  If there is no SD card the right led will double blink until you insert one.  Hooked up with Hyperterminal I could not get the 12 command prompt, after playing around I figure out I had to disconnect hyperterminal then select call in hyperterminal to get the 12 prompt.  After that everything worked fine and the right led blinks whenever a character is received.  Openlog also works with 3.3v.  I didn't notice what version of openlog I was running.
 
Jerry
 

---

From: sysn...@sify.com
To: uavde...@googlegroups.com
Subject: RE: NEW OPEN LOG FROM SPARKFUN (VER 1.1)
Date: Fri, 14 May 2010 16:53:31 +0530

---

The New Busy think 9 to 5 is a cute idea. Combine multiple calendars with Hotmail. Get busy.

[Riccardo Kuebler]

Hi Adam,

thanks a lot for help. Cable is already half done :(

Openlog just arrived today (with Openservo ;)).

Now I have to decide if continue with the cable or write the config file on the card: nice to have alternatives :D

Thanks Sid and Netfoot too :)

Ric

2010/5/14 Adam Barrow <adam....@gmail.com>

[Adam Barrow]

Ric,

 if your SD card does have the config file on it (indicating that you have the 1.6 or newer firmware) I would be very interested in how that works out. If you don't feel like doing it, that's fine, I will probably upgrade my OpenLog modules to 1.6 and test it here this weekend.

Regards,

Adam Barrow

Sent from my mobile phone.

[Riccardo Kuebler]

Adam,

I choose hardware, I have with it a better feeling than with software.

Cable done and it works !

Firmware is 1.5 :(

On the card there is nothing.

Thanks Jerry too :)

[Riccardo Kuebler]

Hi,

I reprogrammed Openlog, following the instructions on the above post, but it does not record any data: why ?

UDB on Serial UDB, micro SD 2GB. Led works when UDB is in action, but no data at all on the card.

I verified communication baud rate, it is 19200. On Hyper terminal I get this:

Available commands:

new <file>              : Creates <file>

append <file>           : Appends text to end of <file>. The text is read from t

he UART in a stream and is not echoed. Finish by sending Ctrl+z (ASCII 26)

write <file> <offset>   : Writes text to <file>, starting from <offset>. The tex

t is read from the UART, line by line. Finish with an empty line

rm <file>               : Deletes <file>

md <directory>  : Creates a directory called <directory>

cd <directory>          : Changes current working directory to <directory>

cd ..           : Changes to lower directory in tree

ls                      : Shows the content of the current directory

cat <file>              : Writes a hexdump of <file> to the terminal

disk                    : Shows card manufacturer, status, filesystem capacity a

nd free storage space

init                    : Reinitializes and reopens the memory card

sync                    : Ensures all buffered data is written to the card

set                     : Menu to configure baud rate

Thanks for help !

[Adam Barrow]

Ric,
What instructions did you follow? With my modules (FW 1.5) I just change the baud rate and leave everything else at the defaults. In that configuration, the OpenLog will create a new file each time it powers up and start logging into it. You want to disable the openlog feature in the UDB - Ben and I are planning to remove it soon.

Please remember that the OpenLog has a buffer too, so it will take a while before the buffer fills up to be flushed to the card.

Regards,
Adam Barrow
Sent from my mobile phone.

On May 14, 2010 10:43 AM, "Riccardo Kuebler" <kue...@ticino.com> wrote:

Hi,

I reprogrammed Openlog, following the instructions on the above post, but it does not record any data: why ?

UDB on Serial UDB, micro SD 2GB. Led works when UDB is in action, but no data at all on the card.

I verified communication baud rate, it is 19200. On Hyper terminal I get this:

Available commands:
new <file>              : Creates <file>

append <file>           : Appends text ...

set                     : Menu to configure baud rate

Thanks for help !

Ric

2010/5/14 Riccardo Kuebler <kue...@ticino.com>
>
> Adam,
>

> I choose hardware, I have with ...

[Murali- VU3MUV]

Hi Adam , Ben,
If open log is going to be removed soon, then what is the alternative for on board logging( with out using stand alone logger)? Thanks

Best Regards
Morli

[ben levitt]

Hi Morli,

I removed support for the OpenLog 1.0 firmware earlier today. Newer
OpenLog firmware versions will work without any special UDB settings.

Since you're using v 1.5 of the OpenLog firmware, you should either
upgrade to the latest version is svn, or set OPEN_LOG to 0 since that
setting was only for OpenLog 1.0.

Ben

[Murali- VU3MUV]

Hi Ben,
Thanks for the clarification. I thought/misunderstood  that Openlog support is going to be removed completely  and I was going to order it in my next order. :)
Meanwhile I am going to test UDB with all extras  in new version of skywalker soon, will keep the gang informed of the progress.

Best regards & 73s
Morli

[Peter Hollands]

Hi Morli,

Look forward to hearing about the UAV DevBoard  the skywalker. It is a tempting platform conceptually for camera work.

I have been following the RC Groups on skywalker quite carefully and have seen how the wings have been failing and snapping close to where the ailerons start. I hope you can find a good way of extending the carbon spar and / or making the wings stronger.

Best wishes, Pete

[Murali- VU3MUV]

Hi Pete,
Thanks for lead. I have been following this guy " Fergus" too from the day he got his( a month before mine). He got the last  ver made with EPS material. The current version is EPO and the FPVFlying) web site show the wings being bent  really bad( sales pitch?) to show the flexibility .  I am doing some mod to the tail vertical stabizer part but not the wing. I am not sure if we need to add another spar extending it but I have an idea if  adviced to do so.   I think the crash is due to

1. Material failure at the end of wing carbon  spar , but why??!  , was the model loaded?
2. He pushed the limits of  wing by doing a loop or some high G stuff ( even with EPS)  it should not have failed the way it looks. If so either the spar should be extended or shortened( as it does not flex at polyhidral point)

My build is purely focused on  it for UDB usage.  Chris is building one too and should be up soon. Mine will take time as I am on move.  I sincerely hope  mine will not encounter similar fate( as Fergus).  I plan to take it with slow  steps adding components after each sucessful flights.  My issue is to figure out the best way to place each  battery and all other components in such a way that we don't have any RF intereference ,  CG gets messed up,  incase of crash  battery does not crush the UDB and other delicate electronics.
Step 1 of Mod:  Spectrum AR7000 slave RX is extended and fitted inside the vertical stabilizer. The extention passes through the tail carbon tube to avoid any RF influx from Video/data telemetry radio fitted on the tail just behind the Prop. Entry andexit of the extention wire is protected from getting nicked/cut by carbon .
Step 2.  One  carbon 2mm flat rod will be glued to inside of leading  edge of vertical stabilizer and will pass/epoxied into tail  carbon tube ( like vertical spar)
Step3 :  Clear canopy will not be used for now. They serve no purpose ( may be bit of  streamlining the airflow).
Step 4: ??

Wish me luck. Cheers.

Best  regards
Morli

[Riccardo Kuebler]

Hi Adam,

I reprogrammed the Openlog following your instructions of this post (the second of this thread).

I searched for info on github and found that Openlog seems to work only with FAT card (not FAT 32). I formatted then the card to FAT, but it still does not record anything. I know that it needs some time to write from the buffer. When I tried yesterday I rebooted UDB to be sure it was all written.

Do you have the full firmware, so I can reflash it, please ?

Thanks,

Ric

2010/3/29 Adam Barrow <adam....@gmail.com>

[Adam Barrow]

Ric,

 Sorry for not replying sooner, I'd missed this email earlier.

Since I wrote the first post, Nathan has updated the project page with a much simpler firmware upgrade process. You can find it here. Besides being a lot simpler to program the firmware, it has a download of the compiled firmware HEX file (main.hex).

I'm a little interested about what is going on with the OpenLog module, however. If you are interested, here are the steps I'd use to troubleshoot:

1) Connect the OpenLog to your PC using the FTDI cable. Using HyperTerm (or a similar Terminal program) I would try to connect. For use with the UDB, it should be set to 19200 baud, but I would also try 9600 baud to be sure. What you want to see is the "12<" output from the OpenLog. The module must have an SD card installed or it won't go past the 1. If you can't get the output to come up, I would check that the module is connected properly. I would then also check that the SD card was installed properly and probably reseat it.

2) Assuming the output shows up correctly above, I would then try and type in something (bang keys). After at least a few keys, hit ctrl-z a couple of times (3 by default) to get to the 'command' prompt (>). Try typing a ? to get the list of commands supported by the module. Then try doing an LS to see the files on the SD card. There should be at least one file with the text you typed in earlier. You can examine the files using the cat command (cat myfile.txt).

3) If both of the above worked, I'd put the card into my PC and confirm that I can see the same file(s) as the OpenLog module did. If that doesn't work, then I would check on the PC.

4) Once you get this far, check the UDB connections. You want to connect the RX to the TX and vis-versa, as described on the wiki (http://picasaweb.google.com.au/lh/photo/IvdY89ZTeGSe0rW_UGt1kn09kvwp_U4oewoS3Qab7GU?feat=embedwebsite). If the connections are good, then I would connect the FTDI cable to the UDB and verify that the UDB is outputting the serial data correctly.

If all of the above steps don't help to get this figured out, please let me know and we can keep trying to get to the bottom of this.

Good luck,

Adam Barrow

[SIDDHARTH]

Hi Adam,

                        Just for the interest, are there any added features in the latest firmware for Open-log? The most desired one is to have a date and time stamp. Next would be if the data card is full then first in first out file feature.. Of course we need date and time for this.   Can we modify the same?

 

Regards

SID

---

From: uavde...@googlegroups.com [mailto:uavde...@googlegroups.com] On Behalf Of Adam Barrow
Sent: Monday, May 17, 2010 5:40 AM
To: uavde...@googlegroups.com
Subject: Re: NEW OPEN LOG FROM SPARKFUN (VER 1.1)

 

Ric,

Adam Barrow

Ric

2010/3/29 Adam Barrow <adam....@gmail.com>

3.      Hit CTRL-Z (control and Z) to close the log file and go to command mode

4.      You should now have a > prompt (> indicates the OpenLog is in 'command' mode)

5.      Type ? and ENTER to get a list of commands and confirm the firmware version (which should match the screenshot below)

6.      Type "baud" (no quotes) and ENTER to set the baud rate

7.      Type 3 and then ENTER to set the baud rate to 56700, and your screen should look like the following

8.      Restart HyperTerm at 56700 baud and reset your OpenLog module (I disconnect and reconnect the GND) to confirm that communications are working

9.      Close HyperTerm

5. Download and unzip the OLFWforUDBv1 file from the wiki (this is Adam Bellchambers' custom firmware)
6. From progammer's notepad, open the Makefile in that directory (where you unziped OLFWforUDBv1)

1. Under the file menu, choose open... and browse for the directory where you unziped the firmware
2. Select the file named "Makefile" in that directory and open it

7. Customize the makefile for your environment

1. Scroll down through the makefile to find the section that begins with the line "#---------------- Programming Options (avrdude serial bootloader) ----------------"
2. Update the line that starts "SERIAL_AVRDUDE" to match where you installed (extracted) Arduino in step 2 above (in my case, this was "SERIAL_AVRDUDE = C:\Arduino\0018\hardware\tools\avr\bin\avrdude")
3. Update the line that starts "SERIAL_AVRDUDE_CONFIG" to match where you installed Arduino in step 2 above (mine was "SERIAL_AVRDUDE_CONFIG = C:\Arduino\0018\hardware\tools\avr\etc\avrdude.conf")
4. Update the line that starts "SERIAL_AVRDUDE_PORT" to match the COM port on your system (mine was "SERIAL_AVRDUDE_PORT = COM3")
5. Save the updated makefile (file menu -> save)

8. Build and program the new OpenLog firmware

1. Under the tools menu, select the new shortcut you created in step 3 above ("Program Serial")
2. After compiling the firmware, the AVRDude tool should start programming the module with the new firmware
3. There will be two progress bars as the module is first programed and then verified 
4. Make sure the output window ends with "avrdude.exe done.  Thank you." and then "> Process Exit Code: 0" (see screen shot) 

0.      If it doesn't the process is either not complete or had some issue

1.      If you need help, copy and paste the complete contents of the output window into an email and we can try to help out

[Riccardo Kuebler]

Hi Adam,

thanks for your answer.

I read all what I found on Openlog. I tried and retraied to program it but my sunday ended before I could have any success.

I played a lot with all the commands you mention. I was able to write, to change baud rate, to navigate in the menu, create folder, but I never got <12< . It always was <12>. I don't get it anymore.

I tried to program it with Programmers Notepad and with cmd.exe inserting the programming string.

I tried to reset baud rate shorting rx to ground (but this never was a problem, seen that Hyperterminal communicates).

Now I'm stuck at :

avrdude.exe: stk500_getsync(): not in sync: resp=0x00

avrdude.exe: stk500_disable(): protocol error, expect=0x14, resp=0xe0

I have RTS on close selected.

Best regards,

Ric

2010/5/17 Adam Barrow <adam....@gmail.com>

[Murali- VU3MUV]

Ric,
Just in case, Have you tried with different SD card/mem ( smaller say 1 GB) just for the sake of diagnosis? It could be problem with card too, one of my card didn't do as expected with  Geocrone GPSlogger. When I changed it , it started working. Good luck

Best  regards
Morli

[Adam Barrow]

Sid,

 The newest firmware (v1.6) supports setting up the OpenLog from a file on the SD card, so no serial link would be required, which I think is a really amazing feature and I plan to test it as soon as I can. The earlier version (v1.5) had several improvements (automatic buffer flushing, new log file creation, built-in support for 19200 baud, and more) which benefit the UDB users and I would strongly encourage everyone to use at least that version of firmware on the OpenLog. To that end, I've started on an update for the wiki page to detail how to upgrade the firmware (it's a lot easier now -- you can checkout the OpenLog home page). 

A date and time stamp on the files is not likely to be supported by the OpenLog, since that would require some sort of real time clock (RTC) which I don't think can be supported by the current hardware.

As it stands today the OpenLog does support getting information about the SD card as well as manipulating files. If someone were interested, it should be possible to modify the UDB firmware to look at the SD card through the OpenLog, determine the card is almost full, delete the log file with the smallest number (the automatically generated log files are numbered sequentially up to 65,533). That would be a lot of work, however, considering that a one hour flight only generated about 234k of logs (a typical 1GB card can hold over 4,000 hours of flight logs and a small 256MB card can still hold over 1,000 hours of logs).

Regards,

Adam Barrow

[Adam Barrow]

Ric,

 the avrdude error sounds like an issue when trying to program the firmware onto the OpenLog module. I'm not very familiar with it, since the OpenLog is the only AVR module I have flashed recently. Perhaps someone on here has more experience with the AVR tool chain and can offer some suggestions.

When you just connect the OpenLog to your PC, do you still get output, and if so, what output is it? The 1 and 2 represent the initialization of the OpenLog module (1 is serial and 2 is SD card, IIRC) and then the < or > represent the mode the module is in. In < mode the module is writing to the SD card and you won't see any output until you close the file (CTRL-Z three times in a row by default). At that point you should get a > prompt which indicates the module is in 'command' (interactive) mode. What you type should show up in your terminal program and various commands will generate output. Start by typing a ? to see the list of commands supported.

Please let me know what you're seeing and I'll try to figure out from the code what is going on in the module. It would also help if you know what firmware the module is running.

Regards,

Adam Barrow

[Peter Hollands]

Adam and all,

I note on the OpenLog web site that it said that they strongly recommend not filling up your the memory cards, but running the system with just a few files inside. Apparently the cpu work required to store files increases dramatically when there is a large amount of data already stored on the card.

Pete

[Riccardo Kuebler]

Adam,

now I just receive a set of strange characters. I guess I corrupted the firmware somewhere and I'm no more able to reflash it. Still stuck on avrdude sync problem.

[Adam Barrow]

Ric,

 the first thing I would try if you are getting strange characters is to try different baud rates. In my experience, that has been the cause when I've seen strange characters from the OpenLog. 

Remember that when you reflash it, the settings are also changed back to the defaults. Also, if you still have the DTR pin connected, it will reset the OpenLog (for the bootloader) which will be communicating at 56,700 BAUD for the first 500ms.

From what I'm reading online, the AVRDude supports an interactive terminal mode, which might be helpful in troubleshooting. I'll play with it some on my setup and see if I can come up with commands for you to try.

Regards,

Adam Barrow

[Riccardo Kuebler]

Adam,

I already tried to change baud rate, but in this case I get nothing.

[Riccardo Kuebler]

Hi Adam,

I finally flashed it !

It was a very stupid procedure: while flashing Openlog, you have to write the string, connect it and then press enter within 500mSec. I hate to waste time this way.

Now I am on 1.61 and have a config file on the card.

Just to let you know.

Best regards,

Ric

2010/5/17 Riccardo Kuebler <kue...@ticino.com>

[SIDDHARTH]

Cognates.. RIC.. Things like this happens with me as well. I also hate but yes I accept my limited knowledge in programming so I do it the hard way but never give up.. I like your spirit.. Keep it up. This way the whole community is benefited and we as well.  

 

Regards

SID

 

---

From: uavde...@googlegroups.com [mailto:uavde...@googlegroups.com] On Behalf Of Riccardo Kuebler
Sent: Tuesday, May 18, 2010 9:34 AM
To: uavde...@googlegroups.com
Subject: Re: NEW OPEN LOG FROM SPARKFUN (VER 1.1)

 

Hi Adam,

Ric

 

Ric

 

2010/5/17 Adam Barrow <adam....@gmail.com>

Adam Barrow

 

 

2010/5/17 Adam Barrow <adam....@gmail.com>

Adam Barrow

 

Ric

2010/3/29 Adam Barrow <adam....@gmail.com>

3.      Hit CTRL-Z (control and Z) to close the log file and go to command mode

4.      You should now have a > prompt (> indicates the OpenLog is in 'command' mode)

5.      Type ? and ENTER to get a list of commands and confirm the firmware version (which should match the screenshot below)

6.      Type "baud" (no quotes) and ENTER to set the baud rate

7.      Type 3 and then ENTER to set the baud rate to 56700, and your screen should look like the following

8.      Restart HyperTerm at 56700 baud and reset your OpenLog module (I disconnect and reconnect the GND) to confirm that communications are working

9.      Close HyperTerm

5. Download and unzip the OLFWforUDBv1 file from the wiki (this is Adam Bellchambers' custom firmware)
6. From progammer's notepad, open the Makefile in that directory (where you unziped OLFWforUDBv1)

1. Under the file menu, choose open... and browse for the directory where you unziped the firmware
2. Select the file named "Makefile" in that directory and open it

7. Customize the makefile for your environment

1. Scroll down through the makefile to find the section that begins with the line "#---------------- Programming Options (avrdude serial bootloader) ----------------"
2. Update the line that starts "SERIAL_AVRDUDE" to match where you installed (extracted) Arduino in step 2 above (in my case, this was "SERIAL_AVRDUDE = C:\Arduino\0018\hardware\tools\avr\bin\avrdude")
3. Update the line that starts "SERIAL_AVRDUDE_CONFIG" to match where you installed Arduino in step 2 above (mine was "SERIAL_AVRDUDE_CONFIG = C:\Arduino\0018\hardware\tools\avr\etc\avrdude.conf")
4. Update the line that starts "SERIAL_AVRDUDE_PORT" to match the COM port on your system (mine was "SERIAL_AVRDUDE_PORT = COM3")
5. Save the updated makefile (file menu -> save)

8. Build and program the new OpenLog firmware

1. Under the tools menu, select the new shortcut you created in step 3 above ("Program Serial")
2. After compiling the firmware, the AVRDude tool should start programming the module with the new firmware
3. There will be two progress bars as the module is first programed and then verified 
4. Make sure the output window ends with "avrdude.exe done.  Thank you." and then "> Process Exit Code: 0" (see screen shot) 

0.      If it doesn't the process is either not complete or had some issue

1.      If you need help, copy and paste the complete contents of the output window into an email and we can try to help out

[Daniel Gmail]

Welldone all. 

Great spirit to get all way down till it's done. 

I will be going thru the same soon I believe. 

Cheers. 

[Adam Barrow]

Ric,

 glad to hear you finally got it flashed. Did you create the config file manually and it worked, or was it created once you connected to the OpenLog? Can you confirm that the line I'd sent you last week did work in the config file, or send over a copy of the config file you are using? I haven't actually flashed my OpenLog to 1.61 (busy lately :( ).

The 500msec rule should only apply if you do not have DTR connected, or if using a version of AVRdude that doesn't have the "DTR trick". Can you please confirm that you had the OpenLog connected like this and that you were using the version of AVRdude that comes from the OpenLog website?

The OpenLog, like the Arduino, is wired so that a toggle on the DTR pin will reset the module. The AVRdude that comes with Arduino is then modified to toggle the DTR pin before starting any operation, which effectively resets  the module automatically and means you shouldn't have to worry about the timing. Since you had to reset the module and start programming while the bootloader was still running, I'm guessing the automatic DTR waggle didn't work for some reason.

Regards,

Adam Barrow

[Riccardo Kuebler]

Adam,

I writed this line in Windows command prompt (cmd):

avrdude.exe -p atmega328p -P COM4 -c stk500v1 -b 57600 -Cavrdude.conf -U flash:w:main.hex

To program it I used an FTDI cable, with a connector cable to revert tx and rx.

I used all the files from Openlog site.

When I flashed it I found on the card a config file and a log1 file. Baud rate change is easily done in the config file. I played a little with the Openlog menu, tried to reset file number, append function etc. A very nice device (once it works ).

Best regards,

Ric

2010/5/18 Adam Barrow <adam....@gmail.com>

[DT]

Adam and all,
I am going to try using the serial cable that comes with Remzibi (Oti)
with Oit6858 driver. this cable only have grand and RX/TX line so i
assume i will have to feed the openlog with +5V.

Two main question:
- Anyone tried using this or you know that it is a sure NOT working? I
assume that the update of firmware is a simple serial communication
just like the Remzibi OSD.

- And for the 500ms, does it means I have to press the enter key for
the command and power up the openlog at the same time??

Thanks and wish me luck as will try it in next 5 hours.

Dan

On May 18, 5:37 pm, Riccardo Kuebler <kueb...@ticino.com> wrote:
> Adam,
>
> I writed this line in Windows command prompt (cmd):
>
> avrdude.exe -p atmega328p -P COM4 -c stk500v1 -b 57600 -Cavrdude.conf -U
> flash:w:main.hex
>
> To program it I used an FTDI

> cable<http://store.diydrones.com/product_p/ttl-232r-3v3.htm>,

> with a connector cable to revert tx and rx.
>
> I used all the files from Openlog site.
>
> When I flashed it I found on the card a config file and a log1 file. Baud
> rate change is easily done in the config file. I played a little with the
> Openlog menu, tried to reset file number, append function etc. A very nice

> device (once it works [?]).
>
> Best regards,
>
> Ric
>
> 2010/5/18 Adam Barrow <adam.bar...@gmail.com>

>
>
>
> > Ric,
> >  glad to hear you finally got it flashed. Did you create the config file
> > manually and it worked, or was it created once you connected to the OpenLog?
> > Can you confirm that the line I'd sent you last week did work in the config
> > file, or send over a copy of the config file you are using? I haven't
> > actually flashed my OpenLog to 1.61 (busy lately :( ).
>
> > The 500msec rule should only apply if you do not have DTR connected, or if
> > using a version of AVRdude that doesn't have the "DTR trick". Can you please
> > confirm that you had the OpenLog connected like this and that you were using
> > the version of AVRdude that comes from the OpenLog website?[image:
> > FTDI-Connections.jpg]
>
> > The OpenLog, like the Arduino, is wired so that a toggle on the DTR pin
> > will reset the module. The AVRdude that comes with Arduino is then modified
> > to toggle the DTR pin before starting any operation, which effectively
> > resets  the module automatically and means you shouldn't have to worry about
> > the timing. Since you had to reset the module and start programming while
> > the bootloader was still running, I'm guessing the automatic DTR waggle
> > didn't work for some reason.
>
> > Regards,
> > Adam Barrow
>
> > On May 17, 2010, at 11:03 PM, Riccardo Kuebler wrote:
>
> > Hi Adam,
>
> > I finally flashed it !
>
> > It was a very stupid procedure: while flashing Openlog, you have to write

> > the string, connect it *and then* press enter within 500mSec. I hate to

> > waste time this way.
>
> > Now I am on 1.61 and have a config file on the card.
>
> > Just to let you know.
>
> > Best regards,
>
> > Ric
>

> > 2010/5/17 Riccardo Kuebler <kueb...@ticino.com>

>
> >> Adam,
>
> >> I already tried to change baud rate, but in this case I get nothing.
>
> >> Ric
>

> >> 2010/5/17 Adam Barrow <adam.bar...@gmail.com>

>
> >>> Ric,
> >>>  the first thing I would try if you are getting strange characters is to
> >>> try different baud rates. In my experience, that has been the cause when
> >>> I've seen strange characters from the OpenLog.
>
> >>> Remember that when you reflash it, the settings are also changed back to
> >>> the defaults. Also, if you still have the DTR pin connected, it will reset
> >>> the OpenLog (for the bootloader) which will be communicating at 56,700 BAUD
> >>> for the first 500ms.
>
> >>> From what I'm reading online, the AVRDude supports an interactive
> >>> terminal mode, which might be helpful in troubleshooting. I'll play with it
> >>> some on my setup and see if I can come up with commands for you to try.
>
> >>> Regards,
> >>> Adam Barrow
>
> >>> On May 17, 2010, at 11:08 AM, Riccardo Kuebler wrote:
>
> >>> Adam,
>
> >>> now I just receive a set of strange characters. I guess I corrupted the
> >>> firmware somewhere and I'm no more able to reflash it. Still stuck on
> >>> avrdude sync problem.
>
> >>> Ric
>

> >>> 2010/5/17 Adam Barrow <adam.bar...@gmail.com>

> >>>> 2010/5/17 Adam Barrow <adam.bar...@gmail.com>

>
> >>>>> Ric,
> >>>>>  Sorry for not replying sooner, I'd missed this email earlier.
>
> >>>>> Since I wrote the first post, Nathan has updated the project page with

> >>>>> a much simpler firmware upgrade process. You can find it here<http://wiki.github.com/nseidle/OpenLog/flashing-firmware>.

> >>>>> Besides being a lot simpler to program the firmware, it has a download of

> >>>>> the compiled firmware HEX file (main.hex<http://github.com/nseidle/OpenLog/blob/master/Code/main.hex>
> >>>>> ).

>
> >>>>> I'm a little interested about what is going on with the OpenLog module,
> >>>>> however. If you are interested, here are the steps I'd use to troubleshoot:
> >>>>> 1) Connect the OpenLog to your PC using the FTDI cable. Using HyperTerm
> >>>>> (or a similar Terminal program) I would try to connect. For use with the
> >>>>> UDB, it should be set to 19200 baud, but I would also try 9600 baud to be
> >>>>> sure. What you want to see is the "12<" output from the OpenLog. The module
> >>>>> must have an SD card installed or it won't go past the 1. If you can't get
> >>>>> the output to come up, I would check that the module is connected properly.
> >>>>> I would then also check that the SD card was installed properly and probably
> >>>>> reseat it.
> >>>>> 2) Assuming the output shows up correctly above, I would then try and
> >>>>> type in something (bang keys). After at least a few keys, hit ctrl-z a
> >>>>> couple of times (3 by default) to get to the 'command' prompt (>). Try
> >>>>> typing a ? to get the list of commands supported by the module. Then try
> >>>>> doing an LS to see the files on the SD card. There should be at least one
> >>>>> file with the text you typed in earlier. You can examine the files using the
> >>>>> cat command (cat myfile.txt).
> >>>>> 3) If both of the above worked, I'd put the card into my PC and confirm
> >>>>> that I can see the same file(s) as the OpenLog module did. If that doesn't
> >>>>> work, then I would check on the PC.
> >>>>> 4) Once you get this far, check the UDB connections. You want to
> >>>>> connect the RX to the TX and vis-versa, as described on the wiki (

> >>>>>http://picasaweb.google.com.au/lh/photo/IvdY89ZTeGSe0rW_UGt1kn09kvwp_...).

> >>>>> If the connections are good, then I would connect the FTDI cable to the UDB
> >>>>> and verify that the UDB is outputting the serial data correctly.
>
> >>>>> If all of the above steps don't help to get this figured out, please
> >>>>> let me know and we can keep trying to get to the bottom of this.
>
> >>>>> Good luck,
> >>>>> Adam Barrow
>

> >>>>> On Sat, May 15, 2010 at 2:49 PM, Riccardo Kuebler <kueb...@ticino.com>wrote:
>
> >>>>>> Hi Adam,
>
> >>>>>> I reprogrammed the Openlog following your instructions of this post
> >>>>>> (the second of this thread).
>
> >>>>>> I searched for info on github and found that Openlog seems to work
> >>>>>> only with FAT card (not FAT 32). I formatted then the card to FAT, but it
> >>>>>> still does not record anything. I know that it needs some time to write from
> >>>>>> the buffer. When I tried yesterday I rebooted UDB to be sure it was all
> >>>>>> written.
>
> >>>>>> Do you have the full firmware, so I can reflash it, please ?
>
> >>>>>> Thanks,
>
> >>>>>> Ric
>

> >>>>>> 2010/3/29 Adam Barrow <adam.bar...@gmail.com>

>
> >>>>>>> SID,
> >>>>>>>  your analysis is spot on! We have two choices at the moment, to
> >>>>>>> either update the UDB to run the 'telemetry' serial port @ 9600 or update
> >>>>>>> the OpenLog firmware to run at 19200 (I and I think Adam Bellchambers have
> >>>>>>> been running our OpenLog modules with the later option).
>
> >>>>>>> We have seen some dropped telemetry even at 19200 but I'm not sure
> >>>>>>> yet of the actual cause. If you'd like to run with 9600 baud on your UDB,
> >>>>>>> the worst case would be that some of the telemetry lines are incomplete
> >>>>>>> (dropped) and perhaps some
>

> ...
>
> read more »
>
>  FTDI-Connections.jpeg
> 74KViewDownload
>
>  320.gif
> 1KViewDownload- Hide quoted text -
>
> - Show quoted text -

[DT]

Team,
Good news, I managed to connect the Openlog with the OTI cable from
Remzibi. Running with Win7 using the Vista driver for OTI cable.

However, I only can communicate using 9600 baud rate.

This Cable only have Rx/Tx and Ground so I have to use the external 5V
power to power up the openlog.

With the 500ms window method, after almost 20 tries, I finally see the
screen showing ########... Bingo.. the flashing routine started! Else
all the failed attemp will tell you out of sync.

So it is proven that OTI serial cable is working and able to flash the
openlog. the current version I saw is 1.61.

and after recycle the power, terminal screen show 12> as expected. I
will be going to do some data capture soon.

Now I have one question, what should I set in option.h? Serial_UDB?

what will each of the serial option will output the data?

Dan

> ...
>
> read more »- Hide quoted text -