|
<< Click to Display Table of Contents >>
Time / Event Settings Tab |

Time / Event Settings tab
The available options on this tab are described on the next table.
Available options on the Time / Event Settings tab
Option |
Description |
|---|---|
Informs whether this Driver accepts requests for clock syncing, which then sync Windows clock |
|
Enable Time Zone Offset on Sync |
Applies a local timezone to the clock to sync |
Report Events in GMT TIme |
Changes the timestamp of Tags, changing them to GMT (Greenwich Mean Time) based on Windows regional settings and daylight saving time |
Use Callbacks for Commands |
Notifies application Tags immediately when commands are received from a Master. If this option is not selected, that notification is based on the scan of each command Tag |
Generate Event on First Write |
Indicates whether the first writing of a Tag must generate an event or not. If this option is not selected, the first writing only creates a point on this Driver's internal database, and that value is used for comparison starting with the second writing, checking whether there was an event or change of value or quality. If this option is selected, the first writing creates a point on this Driver's internal database and generates an event |
Limit Event Class Msg Size - Single Datalink Fragment |
Limits event messages to a Data Link fragment at a time |
If there is a second Slave in the same application that is operating redundantly, that is, the Master side selects by which channel the communication is performed, this option instructs this Driver that for each received confirmation message of Class events, it generates a corresponding message to send to the redundant Driver |
|
Stop Analog events if not connected |
Stops accumulating analog events when the connection to a Master is interrupted. The current value of each analog Tag keeps being stored. This applies to Objects 32 and 33 |
One Analog Event per Index |
Sends only one event per index at each communication, so that communication become more compatible with implementations of Masters supporting a single event at a time |
Sort Analog Events by Index |
Instructs this Driver to sort analog events (Objects 3X with any Variation) by their Index and not by their timestamp, according to what is performed by default for all other events. This allows Sag/Swell-type events of a point to be reported together, so that the Master side understand this is an event of that type |
Ignore Assign Class Requests |
Instructs this Driver to ignore Assign Class requests received. An Assign Class request is a DNP function that allows linking certain Objects to a Class 1 (one), 2 (two), or 3 (three) event at run time |
Allow Multi App Fragment Class 2,3 - No Confirm |
Informs this Driver to send pending Class 2 (two) or 3 (three) events in multiple application fragments without a confirmation, in a response to a Class 2 (two) or 3 (three) request, if the response buffer does not contain any Class 1 (one) event. If it contains, then the response is limited to a single application fragment with confirmation |
Add new timestamped event on First Connection |
Informs, when the first connection of a Master occurs, whether this Slave Driver must generate new events with timestamp based on the current value of points. The goal is that the Master can receive values with timestamp before performing a Class 0 (zero), which by definition of DNP protocol, occurs with static values, or current, without a timestamp. This way, when connecting, if the Master requests events before a Class 0 (zero), or if unsolicited messages are enabled, then the Master receives the current values with a timestamp, if they are configured this way. This option is only used for Tags that are configured with SOETYPE with timestamp, that is, the N1 parameter |
Add new timestamped event on Reconnection |
The same as the previous option, but when there are no reconnections |