Page 74 of 110
Rev. G
Request is an edge-sensitive trigger for an update, and Update
Acknowledgement is the response telling the system it triggered. This
group will not be processed again until the trigger is reset to zero and
then returns to non-zero once again.
c. Update Period: This is the time period of action taken on the group as
defined by the Update Mode above.
d. Update Request: If the Update Mode is set to Periodic Sync or Async, then
the Update Request is an “ENABLE” for this data group. I.e. If you only
wanted to check a group while an engine is running, you may create an
internal tag that says Is RPM>500. When you put this internal tag into the
Update Request, the group will only be processed if the Internal tag is true
and the update period is satisfied.
e. Update Acknowledgement: This sets the acknowledge that the group has
triggered and can be reset to rearm the triggered group for the next
triggered event.
f. Send on Connect: This setting controls whether to send data immediately
upon connection. Enable or Disable.
g. Update Policy: This sets the policy determining what values in a group are
sent when an exception is met:
i. Send Only Changes: This policy is most common and means that
upon each evaluation of the group, only parameters that have net
the exception will be time stamped and sent.
ii. Send All On Any Change: This policy that if any parameter meets
exception values, it will send all parameters in the group.
iii. Send All Each Time: This policy will cause all parameters to be sent at
each time period whether any exception is met or not. To be clear, all
parameters will be sent every time period.
h. Maximum Interval: This setting will cause the group to send each
parameter in a group at least this often. Note that this feature is
implemented on a per-parameter basis, such that it does not force the
entire group to be sent every so-many seconds, but rather forces additional
transmissions so that each parameter is sent at least that often. The timing
To Next Page
Loading...