Closed pollockm closed 7 years ago
Log Rotation tab: Max file size: A new log will be created once the log file size exceeds this amount, and the previous log will be renamed and placed in the archive directory.
Maxmimum number of archived files to keep:
When more than this number of archive files exists in the archive directory, the oldest files are deleted until the maximum is no longer exceeded. Archived files get a sequential identifier appended to the name before the file extension (test.log archives to test.1.log, test.2.log, up to test.<
Archive old logs in original directory: By default, logs are archived in a different directory than the original location and have an archive sequence number appended to the file name. If this option is checked, archived files are renamed and kept in the same directory.
Archive Directory: Directory on the local disk to which archived files are moved.
Maximum age of files: Archive files older than this maximum age will be deleted, even if the number of archive files is less than the maximum.
Datalogger Configuration tab: File Name: Base file name to which data will be logged (Example: log.tdms). If log rotation is enabled, previous logs will be archived wih a sequential archive number (Example: log.1.tdms, log.2.tdms, etc).
Log Directory: Directory on the target disk to which the file will be saved.
Logging File Path: Path to the log file on target disk.
scans per write: Sets the number of sets of data that are buffered between writes, and therefore the block size written to disk at a time. Setting this value too low will cause excessive CPU usage, as disk accesses incur overhead. Increasing this value requires a larger memory buffer to hold the scanned data before it is pushed to disk.
Approximate memory usage: Calculated size of memory buffer required to hold the requested number of scans of the requested tags in memory between writes. This value ignores any tags that are dynamically mapped at runtime.
Queue size Size of the internal RT FIFO used to queue up scans to be added to the buffer. This setting usually does not require modification.
use enable channel If enabled, data is only logged to the file if the value of the enable channel is TRUE. Use this option to only log data if the system is in a particular state or a particular event has occurred, based on logic in another module. If disabled, data is always logged.
It would also be an appropriate time to fix the capitalization of the UI controls to be consistent, and to change the use enable channel option to just have a checkbox, and remove the OFF/ON, as this is inconsistent with current UI guidelines.
Tooltips would be nice also.