Timeout Configuration Tab - ICC XLTR-1000 Instruction Manual

ICC
Loading a Configuration from an XML File
To load a configuration from an XML file stored on the PC, click File→Load
Configuration... (or click the Load Configuration button on the toolbar).
Saving a Configuration to an XML File
To save the configuration to an XML file on the PC, click File→Save
Configuration... (or click the Save Configuration button on the toolbar).
Downloading a Configuration to a Device
To download the configuration to the gateway, click Device→Download
Configuration To Device (or click the Download Configuration To Device
button on the toolbar).
Note that because there is a different driver firmware for each protocol, the
correct firmware may not be installed on the device corresponding to your
configuration. The utility may need to update the firmware on the device before
the configuration can be loaded.
Updating Firmware
To update firmware on the gateway, click Device→Update Firmware (or click
the Update Firmware button on the toolbar).
Note that if a newer version exists for the firmware installed on the device, a
message will be displayed in the Status box indicating an update is available.
Resetting the Device
To reset the gateway, click Device→Reset Device (or click the Reset Device
button on the toolbar).
Monitoring the Database
To monitor the gateway's database in real time, select the Monitor tab. Data is
updated automatically to reflect the actual values in the database. Values can be
edited by double clicking the data in the database. The status of service objects
can also be added and viewed in this tab in the Status list. Section 8.4.2
describes how to view the status of a service object. For more information, refer
to the ICC Gateway Configuration Utility User's Manual.

8.2 Timeout Configuration Tab

The gateway can be configured to perform a specific set of actions when network
communications are lost. This allows each address in the database to have its
own unique "fail-safe" condition in the event of network interruption. Support for
this feature varies depending on the protocol: refer to the protocol-specific
section of this manual for further information.
23