Joseph Ellsworth / data_log

Proivdes data log data structure for FRAM, EPROM chip with functions to read chip and send back on serial data string.

Dependencies:   W25Q80BV multi-serial-command-listener

Dependents:   xj-data-log-test-and-example

You are viewing an older revision! See the latest version

Homepage

Table of Contents

  1. Data Logging Data structure
  2. Other Chips
  3. Motivation
  4. Design Notes
  5. Sample Use and Basic Test
  6. Journaling to micro-sd

Data Logging Data structure

This is currently WIP please do not use until this page is changed to indicate it is ready.

Other Chips

For legacy reasons I am using the library for "W25Q80BV.h" simply because I started with it. The actual FRAM chip I am using is 2 MBit FRAM MB85RS2MTPH-G-JNE I also tested it with SRAM 23LCV1024-I/P

Simplifying Design Decision

I made a simplifying assumption that everytime we generate a log entry I record the offset of the next write at a specific location in the chip. This works and is fast but it causes lots of updates against a single location. I prefer FRAM because this would rapidly fatigue FLASH chips like the W25Q80BV. Storing this pointer data in the CPU has the same fatigue problem.

Another other option would be to store this offset and our other critical configuration data in the clock chip but it is suseptible to loosing power and loosing this critical data.

One reason I don't log directly to the micro-sd is for the same fatique problem but it is mostly for power managment.

The FRAM chip provides adequate durability and data retention through power outage. The power outage retention is critical because the A2WH systems can be burried under feet of snow in the winter and solar panels do not provide much recharge under that condition.

One design option I have considered but not yet implemented is using a much smaller FRAM chip critical configuration data and rapid update data and then log directly to a larger and less expensive FLASHchip .

Motivation

I am working on A2WH which is a electronic controller for a sophisticated product that balances many sensors, battery charging from photo voltaic panels, controlling speed of many different fans, humidity and enviornmental data. Our challenge is we never have enough battery power to run everything so we have to make decisions about what to run in an effort to produce the maximum amount of water from the available solar power resource.

I found it challenging to track everything needed to do after the fact analysis to see where we need to improve our state machine. In addition what I wanted to measure changed with time and I needed a robust way to log this data so we could analyze it latter. A self describing data format like JSON or XML would work but FRAM is expensive so I wanted something flexible but still concise.

Design Notes

See: data-log-read.me.txt in the same project

Sample Use and Basic Test

Journaling to micro-sd

I latter decided to add features to allow after the fact copying of the data to micro-sd cards to obtain larger log storage without soldering in more chips. I found the micro-sd consume quite a lot of power so I still want to log direct to the FRAM then copy to the micro-sd when I have surplus power available. Still thinking about consolidation tactics to allow re-use of FRAM after the data has been copied ot micro-sd.

All wikipages