![Brodersen RTU32M Series User Manual Download Page 45](http://html1.mh-extra.com/html/brodersen/rtu32m-series/rtu32m-series_user-manual_2817532045.webp)
RTU32M Series User Guide
Brodersen A/S, Islevdalvej 187, DK-2610 Roedovre, Denmark, Tel: +45 45 35 26 27, Fax: +45 45 35 26 29, Email: [email protected]
August 2018
45
6.12
Data Logging
WorkSuite provides functions for logging data into one or more file(s) in the RTU32M. In general 2 functions are available:
1.
LOGCSV Function - a dedicated RTU32 Series logging function. You can find an example of this being used in the WorkSuite
Demo examples installed together with your WorkSuite Package. This data log function handles the read/write functions in a
background scan and does not interfere with the general PLC cycle. You will find details of the LOGCSV file function below.
2.
LogFileCSV
–
simple function for logging data into a CSV-file. It uses a standard file write function and it is not recommended
to use for data logging as a standalone Function.
LOGCSV Function
The LOGCSV Function is found in the Brodersen Function library folder.
The LogCSV function block generates a log file in CSV format for a list of variables. Each log operation is saved in a FIFO buffer and the
file access is done in a separate thread to ensure that the file access will not block the PLC runtime cycle. The depth of the FIFO is 10
log operation entries. LOG and RST operations are ignored if the FIFO is full and Q is then set to FALSE. This can happen if log
operations are entered faster to the FIFO than it can be written to the file.
Note: File access over network can be time consuming, especially if the file server is not available.