So, although 3.7 MB is adequate for many data logger applications, if you need to store high-frequency data, you may need to add external memory to your data logger. In other words, if you can afford to lose a month’s worth of data, that’s how often you should collect data. That’s over 4 years! Of course, that’s in a perfect world where batteries never die and natural disasters never occur.Ī general rule of thumb is that you should not store any more data than you can afford to lose before collecting it. If we assume that these three tables are auto-allocated (that is, programmed to fill up at approximately the same time), it would take 1,533 days for these three tables to fill up 3.7 MB of space. Now, 3.7 MB may not sound like a lot of storage room, but for many data logger applications, this is ample room to store more than a year of data! For example, consider a weather station that stores averages of 10 variables (for example, air temperature, soil temperature, barometric pressure, wind speed, wind direction, precipitation, etc.) into three tables on 15-minute, hourly, and daily intervals.
#Cards for memory note serial number
(*If you have a CR1000 datalogger with a serial number less than 11832, your data logger has only 2 MB of SRAM.) Hence, there is approximately 3.7 MB of internal memory available for final data storage. If you have a CR1000, CR3000, or CR6, your data logger has 4 MB* of static random-access memory (SRAM), where the currently compiled program is stored along with some data logger and communications settings. How do I know if I need external data storage?
#Cards for memory note how to
In a future article, I’ll discuss how to store your data to a memory card. But do you know what kind of card you need-or if you even need one? In this article, I’ll answer these and other memory card questions.
You may already know that you can add external data storage to your data logger with flash-memory cards.
0 kommentar(er)
