Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Plant SCADA

Event Processing Parameters

  • Last UpdatedAug 04, 2025
  • 2 minute read

warning2

UNINTENDED EQUIPMENT OPERATION

Do not change these protocol parameters, except on the advice of Technical Support for this product.

Failure to follow these instructions can result in death, serious injury, or equipment damage.

These parameters are used to manipulate the handling of events.

Parameter

Allowable Values

Default Values

Description

[DNPR]
EventProcessingEnable

0 – Disable the digital/analog events to be pushed to the alarm/trend server.

1 – Enable the digital/analog events to be pushed to the alarm/trend server.

1

Enables/disables event processing.

May be useful during testing.

[DNPR]
EventAtStartupDisable

0 – Events are generated on the initial integrity poll.

1 – Stop the initial integrity poll from generating events.

0

Help prevent an event that is not initialized from cache coming through summary system.

[DNPR]
PushIntegrityStaticsAsEvents

0 - Do not enable generation of alarm/trend events from static data.

1 - Enable generation of alarm/trend events from static data.

1

Enables generation of alarm/trend events from static data (with the timestamp set to the current time on the SCADA machine).

It is recommended that this parameter is turned off (set to 0) when the DNP slave should be solely responsible for event generation. This may be desired when there is a time disparity between when the RTU acquires data and when it is received by SCADA, in which case the event timestamps would be incorrect.

[DNPR]
UTCTimeSyncDefault

[<unit>]
UTCTimeSync

0 – Local time used

1 – UTC time used

0

Indicate if the stamp time of the events sent by the device is whether UTC or local time.

The default is local time.

[DNPR]
RefreshEventsOnStartup

0 – No events refresh

1 – Event refresh

0

This Citect.ini parameter should only be set on one server - not on both peer sides. When this server is restarted, it will set the refresh tag. If this server is the active server for a unit, it will regenerate events.

If another server is the active server for a unit, it asks the redundant server to regenerate events. So it is consistent that only active unit will generate events.

This may be needed in some systems to force fresh alarms or trends on all data points to help ensure that the system starts in the correct state. The events are generated when receiving a response to an integrity poll or static poll.

This parameter should not be set to 1 if the parameters [DNPR]IssueIntegrityPollOnUnitRecovery or [<unit>]IssueIntegrityPollOnUnitRecovery are set to 0. Otherwise, the events that were time-stamped before the timestamp of the events generated by the static poll will be ignored.

TitleResults for “How to create a CRG?”Also Available in