1 FUNCTIONS
1.12 Logging Function
79
1
Saving to a CSV file
The logging data stored in the buffer memory areas can be saved to a CSV file by using function blocks (FBs). The save data
is sorted in a time series, where the logging data can be easily checked.
However, function blocks (FBs) can be executed only when the logging operation is stopped. During the logging operation, the
execution of function blocks (FBs) is disabled.
Saving a CSV file
To save a CSV file, an SD memory card is required.
CSV files are saved in an SD memory card installed in the CPU module. CSV files cannot be saved in the built-in memory of
the CPU module.
Saving procedure
1. Check that ON (1) is stored in 'CH1 Logging hold flag' (Un\G409).
2. Execute the function block (FB).
If the execution state of the function block (FB) is maintained, logging data can be saved in the CSV file every
time logging stops.
Data to be saved in a CSV file
The logging data stored in the buffer memory areas is saved.
For how to check the logging data, refer to the following.
Page 66 Checking data when a hold trigger has occurred
CSV file name
CSV files saved with the function block (FB) are named as follows.
*1 The maximum number of the consecutive numbers can be set with the input label i_Max_Number (maximum number of saving files) of
the function block (FB).
The file name under the following condition is AD4516006.CSV.
• Start I/O number of the A/D converter module: 0450H
• Target channel: 16
• Saving to a CSV file: 6th time.
AD©©.CSV
Object CH
First two digits of the start I/O
number of the A/D converter module
(expressed in four hexadecimal digits)
Consecutive numbers
*1
To Next Page
Loading...
