Datalogging Solutions
Ok, this subject has been covered before, just not recently. Any
schematics, suggestions or documentation on how to utilize some of
the new nvram, flash, atmel, etc in a datalogger configuration.
I have seen a commercial product or two, but I would like to board it
myself in order to be flexible with the storage capacity of the
device, depending upon its intended usage.
For an idea of the size of the storage needed, I figure each data
entry will include day, date, time, and 1 or two other string
parameters. Overall I would store on the average of two weeks of data
with 6-8 entries per day. It would also be nice if the device was
transportable between the field and the shop.
Thanks in advance,
Tim
schematics, suggestions or documentation on how to utilize some of
the new nvram, flash, atmel, etc in a datalogger configuration.
I have seen a commercial product or two, but I would like to board it
myself in order to be flexible with the storage capacity of the
device, depending upon its intended usage.
For an idea of the size of the storage needed, I figure each data
entry will include day, date, time, and 1 or two other string
parameters. Overall I would store on the average of two weeks of data
with 6-8 entries per day. It would also be nice if the device was
transportable between the field and the shop.
Thanks in advance,
Tim
Comments
is a simple data logger that tracks changes in eight inputs. It logs the day
(offset from start date), time (hr, min, sec) and the new events; five bytes
per record. Data is stored in an external (I2C) EEPROM. Time comes from an
I2C real-time-clock.
The article will probably be helpful to you.
-- Jon Williams
-- Parallax
In a message dated 8/15/02 9:26:57 AM Central Daylight Time,
tweaver@i... writes:
> Ok, this subject has been covered before, just not recently. Any
> schematics, suggestions or documentation on how to utilize some of
> the new nvram, flash, atmel, etc in a datalogger configuration.
>
> I have seen a commercial product or two, but I would like to board it
> myself in order to be flexible with the storage capacity of the
> device, depending upon its intended usage.
>
> For an idea of the size of the storage needed, I figure each data
> entry will include day, date, time, and 1 or two other string
> parameters. Overall I would store on the average of two weeks of data
> with 6-8 entries per day. It would also be nice if the device was
> transportable between the field and the shop.
>
> Thanks in advance,
>
[noparse][[/noparse]Non-text portions of this message have been removed]
writes:
> Take a look at my Nuts & Volts article that is out this month -- the project
> is a simple data logger that tracks changes in eight inputs. It logs the
> day
> (offset from start date), time (hr, min, sec) and the new events; five
> bytes
> per record. Data is stored in an external (I2C) EEPROM. Time comes from
> an
> I2C real-time-clock.
>
> The article will probably be helpful to you.
>
Good morning, Jon
Wouldn't StampDAQ perform essentially the same task without requiring an
external real-time clock ? Plus the data could be printed out if desired.
Sid
[noparse][[/noparse]Non-text portions of this message have been removed]
impression he was looking for a portable device. StampDAQ could still be
used -- but not in real-time, just to accept data dumps for analysis and
printing.
There are many roads that lead to Rome.
-- Jon
In a message dated 8/15/02 10:11:28 AM Central Daylight Time, Newzed@a...
writes:
> In a message dated 08/15/2002 10:49:55 Eastern Daylight Time, jonwms@a...
> writes:
>
>
> > Take a look at my Nuts & Volts article that is out this month -- the
> project
> > is a simple data logger that tracks changes in eight inputs. It logs the
> > day
> > (offset from start date), time (hr, min, sec) and the new events; five
> > bytes
> > per record. Data is stored in an external (I2C) EEPROM. Time comes from
> > an
> > I2C real-time-clock.
> >
> > The article will probably be helpful to you.
> >
>
> Good morning, Jon
>
> Wouldn't StampDAQ perform essentially the same task without requiring an
> external real-time clock ? Plus the data could be printed out if desired.
>
> Sid
>
[noparse][[/noparse]Non-text portions of this message have been removed]
>schematics, suggestions or documentation on how to utilize some of
>the new nvram, flash, atmel, etc in a datalogger configuration.
>
>I have seen a commercial product or two, but I would like to board it
>myself in order to be flexible with the storage capacity of the
>device, depending upon its intended usage.
>
>For an idea of the size of the storage needed, I figure each data
>entry will include day, date, time, and 1 or two other string
>parameters. Overall I would store on the average of two weeks of data
>with 6-8 entries per day. It would also be nice if the device was
>transportable between the field and the shop.
>
>Thanks in advance,
>Tim
Hi Tim,
Two weeks of data at 6-8 records per day is not much. Say the time
plus the other stuff takes 8 bytes storage per record, you are only
talking about 14days*8 records*8 bytes = 896 bytes. I would just
store that in the Stamp's own eeprom. You could do that with a BS2.
If you get one of the multibank stamps, you get lots of additional
eeprom, 16k or I think the new BS2pe will have 32k (16k for program
and and an addional 16k for data storage).
There is information out there about the external memory, like the
fine tutorial article Jon Williams has in the recent Nuts and Volts.
For the atmel dataflash, I have an article at
<http://www.emesys.com/BS2flash.htm>. For an IDE interface to a
compact flash card check out way cool
<http://www.barrymichels.com/ide>.
For large storage capacity with the Stamp in a field setting, you are
wise to keep the storage device separate from the logger. Running
lots of data the data back through the Stamp to get it into you
computer via RS232 can be too slow; especially if you are standing
out in the middle of a corn field in the rain!
-- regards
Tracy Allen
electronically monitored ecosystems
http://www.emesystems.com
mailto:tracy@e...
What is the I2C RTC that you are using?
cheers,
Ben, Wellington, New Zealand.
--
http://www.lennard.net.nz/
Ben Lennard, NCEE, Dip EE
Web Hosting and Electronics R&D
Hm: +64 4 972 7567
Mb: +64 21 536 627
87 Spencer Street
Crofton Downs
Wellington
New Zealand
"To the optimist, the glass is half full. To the pessimist, the glass is
half empty. To the engineer, the glass is twice as big as it needs to be."
No animals were harmed in the transmission of this email, although the
Dog next door is living on borrowed time, let me tell you! Those of you
with an overwhelming fear of the unknown will be gratified to learn that
there is no hidden message revealed by reading this warning backwards.
> From: jonwms@a...
> Reply-To: basicstamps@yahoogroups.com
> Date: Thu, 15 Aug 2002 10:43:48 EDT
> To: basicstamps@yahoogroups.com
> Subject: Re: [noparse][[/noparse]basicstamps] Datalogging Solutions
>
> Take a look at my Nuts & Volts article that is out this month -- the project
> is a simple data logger that tracks changes in eight inputs. It logs the day
> (offset from start date), time (hr, min, sec) and the new events; five bytes
> per record. Data is stored in an external (I2C) EEPROM. Time comes from an
> I2C real-time-clock.
>
> The article will probably be helpful to you.
>
> -- Jon Williams
> -- Parallax
>
>
> In a message dated 8/15/02 9:26:57 AM Central Daylight Time,
> tweaver@i... writes:
>
>
>> Ok, this subject has been covered before, just not recently. Any
>> schematics, suggestions or documentation on how to utilize some of
>> the new nvram, flash, atmel, etc in a datalogger configuration.
>>
>> I have seen a commercial product or two, but I would like to board it
>> myself in order to be flexible with the storage capacity of the
>> device, depending upon its intended usage.
>>
>> For an idea of the size of the storage needed, I figure each data
>> entry will include day, date, time, and 1 or two other string
>> parameters. Overall I would store on the average of two weeks of data
>> with 6-8 entries per day. It would also be nice if the device was
>> transportable between the field and the shop.
>>
>> Thanks in advance,
>>
>
>
>
>
> [noparse][[/noparse]Non-text portions of this message have been removed]
>
>
> To UNSUBSCRIBE, just send mail to:
> basicstamps-unsubscribe@yahoogroups.com
> from the same email address that you subscribed. Text in the Subject and Body
> of the message will be ignored.
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
In a message dated 8/15/02 8:04:34 PM Central Daylight Time,
ben@l... writes:
> Hey Jon,
>
>
[noparse][[/noparse]Non-text portions of this message have been removed]