Critical issues

As for the use of the system feature DataLog, it’s required to consider some aspects related to overall efficiency of the system.Big data size stored with DataLog feature may degrade the general functionality of the system, both in the starting phase which during runtime.Whereas the operating characteristics of the DataLog are strictly related to the characteristics of the controlled machine (ex. PLC program execution times) it is advisable to evaluate in advance the number of DataLog and the related individual parameters (sampling time, number of samples).Information about the configured DataLog size, are available in the configuration table with Kb details for each archived data. Also it is suggested to monitor, during application development, the system loading information (running time, memory occupation, etc.). This type of information are available with the SID (System Information and Diagnostic) feature on GF_Project VX.If it’s required to store a big number of data for a long time, it is suggested to configure the Datalogs size smaller than those required by the application and to export a series of intermediate files (.cop). Using the PC tool DataLog Utility provided with GF_Project VX, you can recover data from a single stored file (.cop) and display the data in a graphical trend chart or a tabular spreadsheet format. Furthermore it’s possible to export the data to CSV or PDF file command. In order not to degrade the system performance it’s highly recommended to configure the DataLog Utility to get files and “delete” them (without leaving a copy on target).Following a situation of full disk, reported from the “System Error Popup” – Section Hardware – “D” Red Flag, please delete the * .bin files, on the datalog folder, because they would have been corrupted as a result of poor available space.