The citect.ini file
contains the following trend parameters:
[Trend]AbortStartupOnError- If
set and the history file properties of any Trend tag have been
modified, restart of the Trend Server will not occur because the
history files can not be reloaded.
[Trend]AcquisitionTimeout -
stops a trend server from infinitely acquiring a valid data sample
from a disconnected I/O device
[Trend]AllFiles - Indicates whether trend
history files should be created at startup or created when
needed.
[Trend]BlockByIODevice - Obsolete
in version 7.0.
[Trend]BytesReadBeforeSleep -
Controls the amount of data read from the trend archive before the
trend server has to sleep.
[Trend]BytesWrittenBeforeSleep
- Specifies how many bytes of trend data are written to file by the
TrendWriteTask before it sleeps.
[Trend]CacheSize0 - Determines the
number of samples that can be stored in the cache of a trend with
sample period < 50ms.
[Trend]CacheSize1 - Determines the
number of samples that can be stored in the cache of a trend with
sample period >= 50ms and < 250ms.
[Trend]CacheSize2 - Determines the
number of samples that can be stored in the cache of a trend with
sample period >= 250ms and < 1 second.
[Trend]CacheSize3 - Determines the
number of samples that can be stored in the cache of a trend with
sample period >= 1 second and < 5 seconds.
[Trend]CacheSize4 - Determines the
number of samples that can be stored in the cache of a trend with
sample period >= 5 seconds and < 10 seconds.
[Trend]CacheSize5 - Determines the
number of samples that can be stored in the cache of a trend with
sample period >= 10 seconds and < 20 seconds.
[Trend]CacheSize6 - Determines the
number of samples that can be stored in the cache of a trend with
sample period >= 20 seconds and < 50 seconds.
[Trend]CacheSize7 - Determines the
number of samples that can be stored in the cache of a trend with
sample period >= 50 seconds < 100 seconds.
[Trend]CacheSize8 - Determines the
number of samples that can be stored in the cache of a trend with
sample period >= 100 seconds.
[Trend]ClientRequestTime - The
delay (in milliseconds) after real-time trend data is requested
from the Trends Server before the next data is requested.
[Trend]CopyFilesMessage -
Determines whether the redundant Trends Server displays an alert
message if it cannot find any trend files.
[Trend]FileCreationWriteSize
- Controls the rate at which trend files are initialised (whether
created at startup or runtime).
[Trend]FileNameType - Specifies
whether your trend file names will be long or short.
[Trend]FilterViewByPrivilege
- Default is True which preserves the original behaviour. If
privilege is not checked a user with no privilege (0) can browse
and view trends that require privilege 1.
[Trend]GapFillMode - Determines which
method is used to fill gaps in a trend file and graph caused by
missing trend samples.
[Trend]GapFillSamples - Determines
whether gaps in a trend graph caused by missing samples are filled
(determined by the number of samples missed).
[Trend]GapFillTime - Determines whether
gaps in a trend graph caused by missing samples are filled
(determined by the duration of the gap).
[Trend]ReadWatchTime - Determines how
long the trend server will wait (in milliseconds) between each file
read of trend samples.
[Trend]Redundancy - Obsolete in
version 7.0.
[Trend]ReloadBackOffTime -
Back-off time configured to control the pace of the reload on an
Trend server.
[Trend]Server - Obsolete in
version 7.0.
[Trend]ShowCacheSizes - Determines
whether the currently set values and sample period ranges for
parameters [Trend]CacheSize0. . .[Trend]CacheSize8 are displayed in
the CitectSCADA
Kernel.
[Trend]StaggerRequestSubgroups -
Obsolete in version 7.0.
[Trend]TrendDebug - Used to debug the
trend system during commissioning.
[Trend]WatchTime - The delay (in
milliseconds) after data is returned from the I/O device before
data is requested for the next trend acquisition cycle.
[Trend]WriteWatchTime - The trend
write task writes out trend data to disk, and then sleeps for the
time specified in this parameter (before writing the next trend
file).