Forward Compatibility Rules For Saving And Sending Configurations To Ams Trex; Automatically Detect A Device - Emerson AMS Trex User Manual

Hide thumbs Also See for AMS Trex:
Table of Contents

Advertisement

3.3
Forward Compatibility rules for saving and
sending configurations to AMS Trex
Note
Do not edit configurations on the AMS Trex unit while connected to Configuration Management.
You can edit offline configurations on the Trex unit according to forward compatibility
rules:
3.4

Automatically detect a device

The Field Communicator application can automatically detect a device, without requiring
any input from you. When you open the Field Communicator application or when the
Connect - Select screen is displayed, the Trex unit checks for the most common
connection scenarios and, if possible, detects the connected device and displays the
Device List. You can then select a device and display its device menu. The auto-detect
feature lets you skip the device connection wizard in the Field Communicator application,
which allows for faster connections to devices.
The Field Communicator application can automatically detect:
While the Trex unit is connecting to the device, the Auto-Detect screen is displayed to
show the status. If you tap Cancel, the Connect - Select screen is displayed and the Trex unit
stops the connection process.
User Guide
To edit a configuration with Trex, you must have the proper device description
installed on Trex. The installed device description must match the device type and
device revision of the configuration. If the configuration does not exactly match the
device description on the Trex unit, you cannot save the configuration.
To send a configuration to a device, you must have the proper device description
installed on Trex. The installed device description must be for the same device type,
and equal to or greater than the device rev of the configuration.
You cannot save or send configurations when using the generic device description.
A HART device that is on an externally-powered compliant HART loop, and the
device is communicating at address zero.
A 4-wire HART device that is communicating at address zero. (This may require a
resistor across the HART terminals. Check the device documentation for the proper
connection.)
A WirelessHART device that is powered by its battery, and the device is
communicating at address zero.
A powered FOUNDATION fieldbus segment that is actively communicating. The
fieldbus segment must have a host system or a FOUNDATION fieldbus device that is
the Link Active Scheduler (LAS).
Field Communicator application
47

Advertisement

Table of Contents
loading

Table of Contents