# Log File Size Considerations

The setting for the Log File size allocation is accessed under Configurations | Devices | Log File | Advanced. Refer to Remote Data Logging for additional information on the use of log files.

This setting determines how much flash memory is to be reserved for storage of Log File data. This allocation is then subtracted from the memory otherwise available for user recorded voice messages.

Factors to consider in setting this parameter are:

- The number and type of channels being sampled (if any)
- The corresponding Data Sampling Interval
- How frequently the sampled data is to be delivered to another location.
- How much concern there is regarding available speech recording time

Typically, Data Sampling (if configured by selection in the Destinations dialog box in Alarmware) will require far more File storage than will other selectable categories of data logging such as Alarms, or Configuration Changes.

The RTU can automatically call the destinations when the file files to the configured "high water" mark percentage of fullness. RACO recommends that log file delivery be scheduled in each appropriate destination configuration. Use the high-water delivery capability only as a fail-safe against unexpected increases in the log file size.

Any fully delivered log file segment can be automatically deleted at any time. These log file segments are preserved as long as possible. The treatment of undelivered segments is determined by the "when reserved storage is completely full" parameter. When no destinations exist for log file downloads, or when overwrites of undelivered data are enabled, every segment is considered as fully delivered.

It is illegal to set the log file reserve to a value that will leave less than 1K of memory available for speech and database files. Operator must manually free up memory space.

The maximum size for logfile reserve depends on NVRAM usage at the time.

See Also

Catalyst Memory Allocation Tool