Data Logging SECTION 20 Best Practices
269
• Keep scripts short
Although the script editor can manage hundreds of lines this would
suggest a serious design problem. Consider 30 lines as a practical
maximum.
20-6 Data Logging
This section covers some data logging related good practices.
• Utilise Data Logging performance
Always use the inbuilt Data Logging in preference to trend graphs or file I/
O functions, as the performance is far superior.
• Always use ‘On Change’
Always log data ‘On Change’. There is no sampling error and CPU, disk
activity and storage required are almost certainly reduced.
• Use deadband option
Consider using the deadband option, especially for noisy analogue
signals to reduce the actual logging and storage requirements.
• Don’t ‘Keep all files’
The Dataset ‘Keep all files’ checkbox defaults 'On' for complete data
retention but this should be cleared to stop the Hard Disk filling up.