HistorianConnector.Citect.Properties.Settings
- Last UpdatedMar 26, 2025
- 3 minute read
The following settings are found in the HistorianConnector.Citect.Properties.Settings section.
MaxBackfillRange
The maximum backfill range, as a number of days, for AVEVA Plant SCADA trend tags, alarms, and events. This setting only applies to the first startup of the AVEVA Historian Plant SCADA Connector, defining how far back from the current date the Connector will start requesting data. On subsequent startups, the Connector will resume requesting data from the point where it last stopped, ignoring the maximum backfill range.
The value is stored as a time range in the following format:
-
d.HH:mm:ss
where
-
d = The number of days
-
HH = The number of hours
-
mm = The number of minutes
-
ss = The number of seconds
Valid values include:
-
Minimum = 0 (0.00:00:00)
-
Default = 1 day (1.00:00:00)
Note: This setting only applies to the first startup, so if you want to change the setting after you have already started up the Connector, you should stop the Connector, remove the SQLite database found in C:\ProgramData\Wonderware\Citect SCADA Connector\Data, change the MaxBackfillRange setting, and then restart the Connector. If the Connector sends duplicate Trend history to the Historian, the duplicate data is ignored.
MaxRecordsToRead
The maximum number of records to retrieve in a single request from the AVEVA Plant SCADA alarm server.
Valid values include:
-
Minimum = 1
-
Default = 20000
LateAlarmToleranceDays
The number of days tolerance to apply to "late" alarms (that is, where eventTime is less than receiptTime).
Valid values include:
-
Minimum = 0
-
Maximum = 31 days
-
Default = 1 day
FutureAlarmToleranceHours
The number of hours tolerance to apply to "future" alarms (that is,clock drift).
Valid values include:
-
Minimum = 0 hrs
-
Maximum = 24 hours
-
Default = 1 hr
PriorityRangeToSeverityCritical
The range of priority values in AVEVA Plant SCADA that correspond to a critical severity (severity = 1) in AVEVA Historian.
The default range is priority values 1-250.
PriorityRangeToSeverityHigh
The range of priority values in AVEVA Plant SCADA that correspond to a high severity (severity = 2) in AVEVA Historian.
The default range is priority values 251-500.
PriorityRangeToSeverityMedium
The range of priority values in AVEVA Plant SCADA that correspond to a medium severity (severity = 3) in AVEVA Historian.
The default range is priority values 501-750.
PriorityRangeToSeverityLow
The range of priority values in AVEVA Plant SCADA that correspond to a low severity (severity = 4) in AVEVA Historian.
The default range is priority values 751-999.
Note: AVEVA Plant SCADA supports priority levels from 1 through 255, but in some situations you can set the priority to a value of 0. The AVEVA Historian Plant SCADA Connector maps priority value 0 in AVEVA Plant SCADA to severity level 4 (low) in AVEVA Historian.
IsClusterPartOfModel
Enables or disables cluster options. The default value is True.
Valid values include:
-
True - Cluster options are enabled.
-
False - Cluster options are disabled.
This affects the HierarchicalName and Location properties for item and equipment entities.
|
Equipment Defined? |
Item Defined? |
IsCluster PartOfModel |
Hierarchical Name |
Location |
|---|---|---|---|---|
|
No |
No |
True or False |
. |
/ |
|
Yes |
Yes |
True |
<Equipment Name End Part>.<Item Name> |
/<Cluster>/<Equipment Name Parent Part>/<Equipment Name End Part> |
|
Yes |
Yes |
False |
<Equipment Name End Part>.<Item Name> |
/<Equipment Name Parent Part>/<Equipment Name End Part> |
|
Yes |
No |
True |
<Equipment Name End Part>.<Tag Name> |
/<Cluster>/<Equipment Name Parent Part>/<Equipment Name End Part> |
|
Yes |
No |
False |
<Equipment Name End Part>.<Tag Name> |
/<Equipment Name Parent Part>/<Equipment Name End Part> |
Example 1
Given a trend tag Bottler_CapConveyor_PM800\MMXU1\TotPF with the equipment name Plant.Bottler.CapConveyor.PM800, the item defined as PowerFactorTotal, and with cluster Cluster1, the Hierarchical Name and Location are represented according to the following table:
|
Equipment Defined? |
Item Defined? |
IsCluster PartOfModel |
Hierarchical Name |
Location |
|---|---|---|---|---|
|
No |
No |
True or False |
. |
/ |
|
Yes |
Yes |
True |
PM800.PowerFactorTotal |
/Cluster1/Plant/Bottler/CapConveyor/PM800 |
|
Yes |
Yes |
False |
PM800.PowerFactorTotal |
/Plant/Bottler/CapConveyor/PM800 |
|
Yes |
No |
True |
PM800.Bottler_CapConveyor_PM800\MMXU1\TotPF |
/Cluster1/Plant/Bottler/CapConveyor/PM800 |
|
Yes |
No |
False |
PM800.Bottler_CapConveyor_PM800\MMXU1\TotPF |
/Plant/Bottler/CapConveyor/PM800 |
Example 2
If the equipment name is defined, but the equipment is at the root level of the hierarchy, the Hierarchical Name and Location are represented according to the following table. For example, if the equipment name is defined as Pump1, with cluster Cluster1:
|
IsCluster PartOfModel |
Item Defined? |
Hierarchical Name |
Location |
|---|---|---|---|
|
False |
No |
Pump1.<Tag Name> |
/Pump1 |
|
False |
Yes |
Pump1.<Item Name> |
/Pump1 |
|
True |
No |
Pump1.<Tag Name> |
Cluster1/Pump1 |
|
True |
Yes |
Pump1.<Item Name> |
Cluster1/Pump1 |