Hi,
Can someone post the original subject lined file? I received my Logomatic V2 yesterday. I put my own version on the SD card and the USB bootloader seemed to load it. The file gets removed after powering it up not by USB connection. Problem I’m having is it will not create the config file or work if I put a config file on it. The status lights remain on all the time even with the SD card out. I’m using a 1GB Kingston SD card.
You can download the original code from the product page:
http://www.sparkfun.com/commerce/produc … ts_id=8627
You’ll have to just open main.c in the Main folder and compile in WinARM to get the FW.SFE file.
On the config file, it’s the original firmware that creates the config file, and loads the settings in it. If you’ve overwritten that firmware, then the config file obviously wouldn’t be created. And if you’re new firmware doesn’t look for the firmware file, then it wouldn’t matter if you’ve already loaded the config file onto the SD card.
I’d say you might be better off just modifying the main.c file that’s included in the zip file on the product page. Just change the default code rather than starting from scratch to make it do what you need.
I tried compiling and loading the code from the site you indicated already with the bootloader. When I put a config file that works fine on a Logomatic V1 setup for logging the analog channels every second it does not generate a log file. I’ve used the same SD card on the Logomatic V1 also with no problems.
You’re going to have to create a new config file based on the logomatic v2. There are a couple differences in the config files of the two versions:
1.) New Name: The logomatic v2 uses LOGCON for the config filename, wheras the v1 uses LOGcon (may be vice versa).
2.) The logomatic v1 has a handful more parameters in the log file. If these are absent, it may be screwing up the parser.
The parameters have the same names, though, so you may be able to just copy your settings from your previous config file into this one. You’ll have to read the datasheet to find out for sure.
I’ved tried as you suggested but still no go. Can you please post the file or email it to me that has been verified to work? That should determine if there is a hardware or firmware problem. Thanks.
I just modified the tutorial blinky code to work with the Logomatic V2 in a completely new main.c file and that works fine. There seems to be some warnings when I compile the Logomatic V2 firmware but not when I compile the blinky firmware. This forum will not allow me to post the warning outputs. Any ideas about this?
ryowens84:
You’re going to have to create a new config file based on the logomatic v2. There are a couple differences in the config files of the two versions:1.) New Name: The logomatic v2 uses LOGCON for the config filename, wheras the v1 uses LOGcon (may be vice versa).
2.) The logomatic v1 has a handful more parameters in the log file. If these are absent, it may be screwing up the parser.
The parameters have the same names, though, so you may be able to just copy your settings from your previous config file into this one. You’ll have to read the datasheet to find out for sure.
The real question is why were two ADC channels deleted from the configuration file and firmware when the V2 hardware still breaks them out to the connector with the other channels. (If the published schematic is correct.)
The effect of using a configuration file from the V1 hardware with the V2 hardware/firmware is that ADC channel enables are scrambled and the line for AD1.7 will be used for the value of the “Safety” variable. It will work but not quite as expected. (The parser just counts lines and looks at the end of each line. The text at the beginning is just for human readability and is completely ignored by the parser.)
All fixed now after getting the file via email. I was then also told a new version of the source is available at the product page which does definately work correctly with no modifications needed to the makefile to generate the FW.SFE file. 
This comes up elsewhere too:
viewtopic.php?p=78876&sid=b647af8045b5f … 8d886dd926
And in my post here:
viewtopic.php?p=81524&sid=5a0de3b553679 … 227d#81524
Yes, the code is easily available, as are many tools, but this isn’t the point, not at the outset of a complex task taken on by beginners. If I had web space of my own I’d host a copy myself, it’s likely just 30 KB or so so it’s not going to hurt bandwidth even on a limited BT internet account, but right now I haven’t even got one, and can’t find it anywhere. What really matters is that we shouldn’t have to rely on helpful emails from people for this, it ought to either be hosted directly in FW.SFE format by Sparkfun themselves, or if people agree and accept the terms that this duty is done by the forum, then it ought to be done here by those most qualified to do it. Just loading this forum page puts more demands on a system than letting us freely grab that file at need, so why is it nowhere in sight? There is probably more than its own weight now in questions asking for it, and I’m doing my best to add to that so this gets fixed ASAP. 
Update: Jim (and Pete) at Sparkfun has sorted this, the original firmware now includes the file FW.SFE as explained to, and linked to, in the quoted bit of mail below:
I updated the firmware download
online to include FW.SFE, so that should be taken care of.
Links ADDED because it is apparently impossible to make UBB URLs work in that quoted text.