6. Operation
6.3. Monitoring Fieldbus Functions Through Monitoring Tab
R400 Experion PKS Series A Fieldbus Interface Module User's Guide 267
July 2010 Honeywell
Step Action Result
TIP
It may be a good idea to record the device's Tag name and Device ID for future
reference.
5
If a block type does exist, go to the
previous configuration procedures to
create, assign, configure, match, and
load the device.
If a block type does not exist, create
one using the vendor's DD files as
described in Creating a Fieldbus
device type from vendor DD in the
previous Configuration section.
A block type must exist before a device
can be integrated with the system. The
illustration is for example purposes only.
TIP
It is possible that the uncommissioned device may have an earlier version of the
vendor's software (Device Rev). In this case, the device would appear to have no
matching block type even if one exists for the same device but it is for a different
software version. If the vendor supports flash upgrade of its device's firmware, you can
upgrade the device's firmware through this tab. Please see Upgrading Firmware in
Uncommissioned Device the next Section Maintenance, Checkout and Calibration for
more information.
A new Link Schedule must be loaded to the FIM and other LinkMaster devices anytime
there is a change that invalidates the current Link Schedule, such as adding a device,
removing a device, or making a configuration change.
6
Click the OK button to close the form.
7
This completes the check for
uncommissioned devices.
Viewing and optimizing Link schedule configuration
Th
e following table summarizes how to call up a Link schedule configuration for
viewing in the control chart area of the Control Builder application. You can also interact
with the natural schedule to optimize it using the considerations listed below. Or, you can
configure the Link for the system to provide automatic schedule optimization as noted in
the following procedure.
To Next Page
Loading...
