Introduction
The data logging service allows application data archiving (events, alarms, process data, devices status, measures, etc.) in the internal memory of the module. This service allows you to log data in .csv files in the ASCII format. These files are stored locally in the SD memory card of the module.
A configured interval (period) elapses.
The CPU or the user triggers an event.
File Format
Port the file directly to a Microsoft Excel spreadsheet or a database management system (DBMS) for analysis.
These files can be accessed by HTTPS clients.
Data Logging Tables
A data logging table occupies a chunk of the module’s memory (RAM).
The value of logged variables is stored in this table. A new record appears in the table for each logged event. The record can contain a timestamp or value for all selected variables. You can configure the number of records that the table can hold.
When the data logging backup event occurs, the table in RAM is saved as a backup file in the SD card and all table records are cleared.
Memory Usage
The data logging service can manage up to 10 tables that are independent of each other. That means each table can have a unique size and a different triggering mechanism. The service can also manage up to 10 groups of data logging files (backups). This mean you can create several different data tables, each of which can be associated with different logging periods.
For example, the folder Table_n represents the backup that corresponds to table_n. The table backup files on the SD memory card can be purged (or deleted) as configured (event n triggered by the CPU). When the module experiences a loss of power during data logging, the records in the RAM table that have not been backed up are lost while the backup files are retained.
The data logging tables in RAM are cleared and expelled.
The table's corresponding backup files on the SD card are archived if the table's configuration is changed.