32
ICC
Timeout
For master/client protocols, enter the request timeout in milliseconds. This setting
is the maximum amount of time that the gateway will wait for a response from a
remote device after sending a request.
For slave/server protocols, this value is the maximum amount of time the protocol
driver will wait in between received packets before triggering a timeout event (for
network loss detection). For further timeout processing details, refer to section
8.3.
Scan Rate / Response Delay
For master/client protocols, the scan rate is the number of milliseconds the
device will wait between sending requests. This is a useful feature for certain
devices or infrastructure components (such as radio modems) that may not be
capable of sustaining the maximum packet rates that the gateway is capable of
producing. The start time for this delay is taken with respect to the moment at
which the gateway is capable of sending the next packet (due to either reception
or timeout of the previous request). The default setting of 0 means that the
gateway will send its next request packet as soon as possible.
For slave/server protocols, the response delay is the number of milliseconds the
device will wait before responding to a request. This is a useful feature for
certain master devices or infrastructure components (such as radio modems) that
may require a given amount of time to place themselves into a “receiving mode”
where they are capable of listening for slave responses. The default setting of 0
means that the gateway will send its responses as soon as possible.
8.5
Service Object Configuration
A service object is used by the gateway to make requests on a network when a
master/client protocol is enabled. Each service object defines the services (read
or write) that should be performed on a range of network objects of a common
type. The data from read requests is mirrored in the database starting at a user-
defined address (if a read function is enabled). When a value within that address
range in the database changes, a write request is generated on the network (if a
write function is enabled). Depending on the protocol selected, service objects
will vary slightly. Refer to section 8.7 for specific examples.
8.5.1
Description of Common Fields
This section contains general descriptions of the common service object fields,
regardless of which protocol is selected. Each protocol has its own additional
fields, as well as a more specific implementation of the common fields. These are
discussed in section 8.7.
