Event Data Logging Buffering for Low-Wear Non-Volatile Memory
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data logging systems for vehicles face challenges in managing the limited number of program and erase cycles in non-volatile memory and high power requirements for data storage during trigger events, such as crashes, which can lead to increased costs or reduced data storage capacity.
Innovation Solution
A data logging system that stores input data in a volatile memory during normal operation and copies the data to a non-volatile memory only when a trigger event occurs, using a backup power supply specifically for the storage device during such events, allowing multiple copies of event data sets while preserving previously stored data and overwriting older data when capacity is reached.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is stored continuously in non-volatile memory, then data retention is ensured, but the number of program and erase cycles is exceeded
Solution Approach 1:
The system performs preliminary actions by continuously writing data to volatile memory during normal operation. When a trigger event occurs, the system then performs the critical action of copying data from volatile to non-volatile memory. This preliminary buffering in volatile memory prevents excessive write operations to non-volatile memory, resolving the contradiction between data retention and program/erase cycle limits.
Solution Approach 2:
Volatile memory acts as an intermediary between the data source and non-volatile memory. Instead of directly writing all data to non-volatile memory, the system uses volatile memory as a buffer, only transferring data to non-volatile memory when trigger events occur. This intermediary approach ensures data retention while significantly reducing the number of program and erase cycles on non-volatile memory.
2Reliability
If data is copied from volatile memory to non-volatile memory continuously, then data safety is improved, but power consumption increases
Solution Approach 1:
Instead of continuous copying operations, the system implements periodic action by copying data from volatile to non-volatile memory only at specific intervals - namely, when trigger events occur. This event-driven approach maintains data safety by ensuring critical data is preserved, while dramatically reducing power consumption by avoiding continuous transfer operations.
Solution Approach 2:
The system extracts the critical function of data preservation from continuous operation and isolates it to specific trigger events. By taking out only the necessary data copying action and performing it selectively rather than continuously, the system maintains data safety while minimizing energy consumption during normal operation.
3Quantity of substance
If memory size is increased to store more data, then data storage capacity is improved, but system cost increases
Solution Approach 1:
The system merges volatile and non-volatile memory resources to achieve effective data storage capacity without requiring a single large non-volatile memory. By combining the high-speed volatile memory for active data with non-volatile memory for preserved event data, the system achieves adequate storage capacity while using smaller, more cost-effective memory components.
Solution Approach 2:
The system implements dynamic memory management where the effective storage capacity adapts based on operational needs. Volatile memory provides fast access for active data, while non-volatile memory provides persistent storage for triggered events. This dynamic allocation allows the system to achieve necessary storage capacity without permanently allocating large amounts of expensive non-volatile memory.
Data Source
AI summary
The system has a processing unit that collects input data and a peripheral storage device, connected to the processing unit via an interface system, for recording event data in a non-volatile memory, wherein the event data are input data stored for a recording time period relative to a time zero representing a time when a trigger event occurs. The peripheral storage device has also a volatile memory, and the data logging system stores the input data in the volatile memory of the peripheral storage device, when input data are being collected, and, when a trigger event occurs, makes a copy of stored input data as a backup from the volatile memory of the peripheral storage device into the non-volatile memory of the peripheral storage device.