<< 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 the 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 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 o 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 classes of 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 by 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, 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 the driver to ignore Assign class requests that may be received. que forem recebidos. The "Assign Class" is a DNP function which allows a dynamic association between an object and an event class 1, 2 or 3. |
Allow Multi App Fragment Class 2,3 - No Confirm |
Tells the driver to send class 2 or 3 pending events in multiple application fragments without confirmation in a response for Class 2 or 3 request, if the response buffer does not contain any Class 1 event. If Class 1 events are already present, then the response is limited to a single application fragment with confirmation. |
Add new timestamped event on First Connection |
When a master connects for the first time, this option makes this driver to generate new timestamped events based on current values. This gives an opportunity for the master to receive values with timestamp before a class 0 (integrity) request. According to DNP specification, class 0 shall return current static values without timestamp information, which may cause wrong timestamp information if the master receives value changes from class 0 response. With this option, if the master asks for events before class 0, or if unsolicited messages are enabled, it can receive current values with timestamp, if the points are configured accordingly.
This is valid only for tags configured with SOETYPE option with timestamp (Defined at N1 parameter). |
Add new timestamped event on Reconnection |
The same as above, but for reconnections (2nd connection and beyond). |