The datalogging service allows application data archiving (events, alarms, process data, devices status, measures, etc.) in the internal memory of the BMXNOR0200H module. This service allows you to log data into CSV files in the ASCII format. CSV files are stored locally in the SD memory card of the BMXNOR0200H module.
Datalogging can be performed either periodically or when a specific event (configured by the user) occurs. CSV files are directly usable by an MS Excel spreadsheet or a database management system (DBMS). The CSV files can also be sent through FTP or attached to an email (using the email service) that is automatically sent to specified users. CSV files can also be accessed by an FTP client.
Any FTP client can access the module's file system. You can specify a URL to automatically send information to a remote FTP server.
NOTE: The datalogging service is configured using Web Designer software.
Datalogging is performed in the RAM memory of the BMXNOR0200H module to backup the SD card memory.
The datalogging service can manage up to 10 groups of datalogging files (tables). This allows for the archiving of several different tables of data, each associated with a different logging period.
Datalogging files can be backed up, periodically or on event, from the RAM memory to non-volatile memory of the module (on the SD memory card) into history files in the CSV format. For example, Table_n.csv represents the last backup file, and history files are renamed as Table_n.cs0, Table_n.cs1, etc.
CSV files can be purged on the SD memory card by an event trigger.
Remember:
-
To prolong the life of the SD card, Schneider-Electric recommends you not to backup datalogging files more frequently than every 30 minutes.
-
The time that each data logging instance occurs is not precise.
-
Back up any log files that are stored in the module's volatile memory to enable the restoration of lost data.
-
When power is lost during datalogging, the file that is being backed up is lost.
Datalogging Service Codes
|
Value
|
Comment
|
|
0
|
OK
|
|
2
|
The current file ‘.csv’ is renamed ‘.cs0’.
|
|
10
|
The module cannot reach a variable that should be logged because:
-
the variable does not appear in the namespace.
-
the variable is not write enabled.
-
the preceding value has not been updated yet.
|
|
11
|
FTP transfer interruption.
|
|
12
|
The URL specified for FTP cannot be accessed.
|
|
13
|
The internal flash is full.
|
|
14
|
The internal RAM is full.
|
|
15
|
The module cannot write on the media specified.
|
|
16
|
The module cannot access the namespace.
|
|
17
|
The maximum number of tables has been reached (10 maximum) in your .xml file.
|
|
18
|
The maximum number of variables has been reached in a table.
|
|
19
|
The service is empty, no table defined.
|
NOTE:
-
The datalogging service code 2 should be considered as a status.
-
The highest values have the priority. The datalogging service code 17 has priority over the datalogging service code 12. When the datalogging service code17 has been corrected, the datalogging service code 12 can then be sent to the variable declared for the status of the database service
-
The values of the table status variable are identical to the values of the datalogging service status variable.
