FF Temperature Mux Configuration & Commssioning Procedure1 Iacc

FF devices Installation Manual
ABC
AB PLANT
EMEA
Invensys Ref: AB 1234

Client Ref: 1234
Author: IPS
Invensys Process Systems
Revision: 0.1
Revision Date: 28-08-06
Revision Status: Initial revision
ISSUE 0.1
Purpose Initial
revision
Date 28-08-06
INVENSYS
By
Checked
Approved
CLIENT
User
Manager
Systems
Manager
Validation
Coordinator
1. Introduction ..........................................................................................................................................................3
2. FOUNDATION fieldbus ECBs............................................................................................................................3
3. Installing new device ............................................................................................................................................4
3.1. Check Device type parameters ......................................................................................................................4

3.2. Creating New Device type.............................................................................................................................5
3.3. Modifying the device type.............................................................................................................................6
3.4. Add ECB for FF Device ................................................................................................................................9
3.5. Commissioning with IACC Commission Wizard........................................................................................11
3.6. Selectively download the configuration. .....................................................................................................16
4. Create FF function blocks...................................................................................................................................19
4.1. Create FF Function block in simple CSD....................................................................................................19

4.2. Create FF Function block in CSD template.................................................................................................20
5. Managing Change...............................................................................................................................................21
5.1. Modifying Function Blocks.........................................................................................................................21

5.2. Modifying Resource and Transducer Blocks...............................................................................................24
5.3. Downloading Resource and Transducer Blocks ..........................................................................................25
5.4. Comparing the Device with the Database....................................................................................................27
5.5. Upgrading a Device to a New DD ...............................................................................................................29
5.6. Changing Device Types...............................................................................................................................30
5.7. Removing a Device .....................................................................................................................................31
6. Device Maintenance ...........................................................................................................................................33
6.1. Troubleshooting FBMs................................................................................................................................33

6.2. Troubleshooting an H1 Segment .................................................................................................................34
6.3. Troubleshooting Devices .............................................................................................................................36
6.4. Troubleshooting with Field Device Manager ..............................................................................................36
6.5. Troubleshooting with the Vendor’s DTM ...................................................................................................38
7. System Management Displays............................................................................................................................39
7.1. FBM228 Equipment Change Screen ...........................................................................................................41

7.2. FBM Equipment Information ......................................................................................................................43
7.3. H1 Device Displays .....................................................................................................................................46
7.4. Block Error Display.....................................................................................................................................51
8. Backup of Databases ..........................................................................................................................................52
8.1. Periodic Backup of Databases .....................................................................................................................52

8.2. Backing Up a Database................................................................................................................................52
8.3. Restoring a Database ...................................................................................................................................54
8.3. Exporting Databases ....................................................................................................................................57
8.4. Importing Databases ....................................................................................................................................57
Appendix A: Recommended Settings for Resource Blocks ...................................................................................59
Appendix B: Selected Engineering Units Codes ....................................................................................................60
Invensys Proj.NoAB 1234 ABC Cust Proj.No: 1234

Issue: 0.1 AB PLANT
Revision Date: 28-08-06 Invensys Process Systems
Revision Status: Initial revision Page 2 of 2
FF devices installation manual_rev 1.doc

1. Introduction
This document is intended to be a guide for installation of new device types, devices, replacing
existing devices, changing configuration and diagnostic of the devices.
Beginning with Version 8.0, the I/A Series system offers the optionally redundant FBM228 to
connect FOUNDATION fieldbus devices with the advanced FCP270 Field Control Processor operating
on The I/A Series Mesh Network™, a 100-megabit switched network. The FBMs and the FCP270s are
installed in the same baseplate or adjacent baseplates. The baseplates and connecting cables form a
redundant 2-Mbit module fieldbus.
2. FOUNDATION fieldbus ECBs
In the I/A Series system, equipment control blocks (ECBs) are created for each FBM to
provide a holding place for the software data associated with that FBM. An ECB200 is created for an
FBM228 that is configured as a single unit. An ECB202 is created for FBM228s that are configured as
a redundant pair.
With FOUNDATION fieldbus, an ECB201 is created to represent each H1 device connected

by the FBM. The ECB201 links the device to Device Descriptors (DDs) imported by DD Explorer. The
device ECB201s are child ECBs to the parent ECB200 or ECB202.The linked device-specific
information is used by IACC to create configuration choices in the connected FF Function blocks. The
choices reflect the configurable parameters in the device function block.

Issue: 0.1 AB PLANT

3. Installing new device
3.1. Check Device type parameters
IACC creates the device type by extracting information from the device DD. To identify the
correct DD, you need the following information about the device:
- Manufacturer ID
- Device Type (Type ID)
- Device Revision
- Minimum DD Revision
After attaching the device to the FF segment all these parameters will be seen in live list tab of
FBM.
1. Start IACC, click the Network tab, and expand Configuration at the top of the Project
Navigator to display the host FBM228, its software package, and its ECB200/202.
2. Right-click the ECB200/202 and choose Field Device Manager > FBM228 Manager from the
pop-up menu to access the connected devices via the communications DTM
3. Choose the correct segment from selection box upper left
4. See the live list of FF devices with required information (Figure 3-1)
Figure 3-1 Live List of Segment
Check if you have installed required device type. Click the System tab, and expand System > Library
>Field Devices > FF Devices. Right click to particular Device type, select properties (Figure 3-2).

Issue: 0.1 AB PLANT

Figure 3-2 Device ECB properties
Each manufacturer has his own Manufacturer ID (parameter Manftr) and each device from
manufacturer has different Type ID (parameter Dvtype). Device revision is from first two numbers of
Vernum (03 in example), DD revision third and forth number of this parameter (01 in example). Four
parameters in Live list of FF devices (Figure 3-1) have to correspond with parameters in device type
(Figure 3-2). If your device type is not defined you have to do it according to next chapter.
3.2. Creating New Device type
To define a device type:

1. Click the System tab in the Project Navigator and expand System > Library >Field Devices
> FF Devices to display the existing definitions (Figure 3-3).
2. Right-click FF Devices and choose New Definition from the pop-up menu to open the Import
DD dialog box.
3. Use the dialog box to browse for and select the capability file (*.cff) for the device. IACC
accesses all the necessary files based on selection of the capability file. The Device Type Tag
dialog box (Figure 3-3) displays Manufacturer and Device fields for naming the device type.
4. Use pull-down lists for each field to enter names from the DD files (or enter names manually),
view the resulting name in the Preview Tag field, and click OK.

Issue: 0.1 AB PLANT

Figure 3-3 Import of dd file
5. The device definition is added to the IACC library with the configuration information from the
DD file stored in a device ECB201. The definition is now ready for use in creating instances of
the device type. A dialog box prompts you to edit the definition using the FDT Editor. Click No
in the dialog box to end the session.
6. The new definition is listed under System > Library > Field Devices > FF Devices in the
Project Navigator.
3.3. Modifying the device type
Use Field Device Manager to set device and block parameter values in the device template,
lock selected parameters so they cannot be changed at the device level, and specify which parameters
are to be downloaded to individual instances of the device. With these steps, you define the footprint of
each instance of the device type, that is, define the values that must be set in the physical device.
Field Device Manager displays a padlock icon to right of the value field for every configurable
parameter. The padlock enables you to specify the parameter’s locked status. Table 5-2 describes
how the icon indicates whether the parameter is locked in the current definition and the objects derived
from it, and when changes in the parent definition are propagated to the derived definitions and
instances.

Issue: 0.1 AB PLANT

Icon Description
Locked By Me
The parameter value can be set at this level, but
the value cannot be changed in objects derived
from this device type. The parameter value is
inherited by any device or device type derived
from this type when the child object is created.
Subsequent changes to the parameter value are
propagated to the child objects. The parameter
can be changed to unlocked, in which case, the
unlocked status is propagated to the child objects.
Subsequent changes to the parameter value are
propagated to the child types and devices only if
the parameter has not been modified in the child
object.
Locked By Parent
The double padlock icon is displayed next to a
parameter value in a derived device type or a
device instance when the parameter is locked in a
parent object. No changes can be made to the
parameter value or locked status at this level.
Uploads from the device do not modify the
parameter in the IACC database.
Unlocked
The parameter value is not locked by a parent
object or by the object itself. The parameter value
can be set at this level. The change is propagated
to the derived objects if the value in the derived
object has not been edited and saved. The
change does not override a value that has been
saved in a derived device type
or device instance. However, the lock status can
be changed to Locked By Me to prevent
modification to the parameter in the derived
objects and to propagate changes to the next
level.
Table 3-1 Locking status
When a device type is created, most of the parameters are Locked By Me. You can unlock
and lock parameters individually as you set their values in the template. Or, you can lock and unlock all
parameters for each block or tab display.
Recommended approach is to unlock everything at the beginning of a project to facilitate
finding the best fit for each device type, and then set and lock key parameters at the device-type level
to standardize the configuration across all devices derived from the type.
1. Right click on the device type name, select Field Device Manager > Field Device Manager
(Universal).
2. Click on selection box in up-left corner and select the first block in the list – Resource block.

Issue: 0.1 AB PLANT

3. Select Configuration tab, click on Customize button. Click on lock button next to Tab :
Configuration to unlock it. Click on Lock/Unlock button (down-left), select Unlock All
Configurable Parameters then press OK.
Figure 3-4 Unlocking all parameters
4. The same actions do for all Transducer blocks (usually TB in the name or when selected see
Identification Tab, parameter type has to be Transducer Block …).

Issue: 0.1 AB PLANT

3.4. Add ECB for FF Device
1. Select the FBM228 in the Project Navigator and expand the object to display the FBM’s ECB200 or
ECB202 (Figure 3-5).
2. Right-click the ECB and choose New Child Device from the pop-up menu to list the device types in
the Create Device dialog box. The dialog box lists the device types defined in the database.
3. Select a type by clicking its check box. A 1 appears in the quantity column on the right. At this point
you can increase the count as well as select other device types. However, it is recommended that you
add only one device at a time.
4. Specify in the Port field the H1 segment to which the device is to be attached, and click OK.
Figure 3-5 Addition of new Device ECB
The specified device is listed under the parent ECB (both under the FBM software and in the control
station’s ECB compound) with default names such as ECB001, ECB002, and so on.

Issue: 0.1 AB PLANT

When the host FBM is assigned to a control station, IACC assigns the newly created device
ECB to the control station ECB compound, F27003_ECB in Figure 3-5 for example. The device can
later be assigned to the control compound in which it is to be used.
The last ECB to be created is highlighted indicating that you can rename the object. The name
should be changed to the PD_Tag of the connected device.
Figure 3-6 Renaming of Device ECB
Type the PD_Tag over the default ECB name and press Enter.
The name can be any string of up to 12 characters, which can be letters, numbers and underscores.
The tag should be unique among all devices attached to the FBM (although the name need only be
unique among devices on the same segment).
Dev_id - The parameter of device ECB is default set to the ECB name. But in System
management and detail display are used only first 6 characters and they have to be unique. Therefore
in ABC projects we will use 6 numbers for identification of device in the network:
ABCDEF
A - section no. 1-9
B - CP sequential no. 1,2,3...
C - baseplate sequential no. 1,2,3...
D - module position on the baseplate 1-8,A-D (redundant)
E - port no. 1-4
F - device sequential no. 1,2,3...
Last step is download ECB to CP – right click on device ECB, select Validate/Download > Download.
Downloading ECB to CP does not change Device parameters, only establish communication to device.

Issue: 0.1 AB PLANT

3.5. Commissioning with IACC Commission Wizard
All steps required to correctly commission device can be done with the IACC Commission
Wizard.
The IACC Commission Wizard applies a device tag from the database to a connected device,
downloads selected device and block parameters to the device, uploads the entire device configuration
to the IACC database, and marks the device configuration in the database as committed to a physical
device.
The wizard downloads only those Resource and Transducer block parameters that are included in the
Download List in the block templates. Device itself, Resource block and each Transducer block has in
tab Customize button Download setting (Figure 3-7). Function blocks are not downloaded; the device
function blocks are configured when the linked FF Function blocks are downloaded to the control
station.
Figure 3-7 Setup downloads
The Commission Wizard can be run from the instrument shop system as part of device preparation or
from the control room system as part of site commissioning.

Issue: 0.1 AB PLANT

To commission a device from an IACC control room system:

1. Expand Configuration in the Network tab to display the host FBM228, its software package
and ECB200/220.
2. Expand the ECB200/202 to display the devices configured for the FBM.
3. Right-click added device in the Project Navigator and choose FDT > Commission Device
from the pop-up menu.
4. The wizard lists the physical devices that are potential matches to the device selected in the
Project Navigator. If the device has not been commissioned yet, the wizard displays a live list
of physical devices with the same manufacturer ID, device type, and device revision as the
selected device in the IACC database.
Figure 3-8 List of Unassigned Devices

Issue: 0.1 AB PLANT

5. Select a physical device and click Next.

6. The Download Confirmation dialog box (Figure 3-9) lists the steps in the download, starting
with applying the PD Tag if the device has not yet been commissioned or setting the device
address if the device has already been tagged. The wizard then puts the device on-line and
sets the resource block to OOS.
Figure 3-9 Commissioning window
7. Check the left checkbox in POST-COMMISSIONING ACTIONS to set the target mode in the
device after the download. If the box is not checked, the target mode is left at OOS.
8. Check the right checkbox in POST-COMMISSIONING ACTIONS to upload the parameters
from the device to IACC and mark the device in the IACC database as committed to a physical
device. If the box is not checked, you must manually upload and save the configuration.
9. Click Next to proceed with the download.

Issue: 0.1 AB PLANT

10. The wizard displays a warning dialog box (Figure 3-10) so you can confirm your choices, or
return to the previous display and revise the selections.
Figure 3-10 Warning before doownload
11. Click OK to continue (or Back to change your selections or cancel the download). The wizard
displays the status of each step (PASS or FAIL) as the commissioning progresses.

Issue: 0.1 AB PLANT

Figure 3-11 Commission progress
12. If any step fails, you can either run the Commission Wizard again or selectively download the
configuration.
NOTE
Do not interrupt the download. Allow the wizard to complete all of the actions.

Issue: 0.1 AB PLANT

3.6. Selectively download the configuration.
Check if the Device name in Open Live list tab for FBM (see chapter 3.1) is the same as
device ECB name. If you click on device in Open Live list tab then two buttons below the table – “Set
PD Tag” and “Set PD Address” become active and you can change the PD tag or PD address.
To align the IACC database with the configuration of an online device:

1. Right-click the device in the Project Navigator and choose FDT > FDT Editor (Universal) from
the pop-up menu.
2. Select the Resource block in left-up selection field and click the Compare tab in the block
display. The editor displays the database values for all parameters in the block and the device
values as the editor reads them from the device database, replacing the cyan * in the device
value column. If the values do not match for a specific parameter, the editor displays in the
column between the two values and change the color for this line.
3. Right click on left-up selection field with RB name, select Rename. Change the name to
PD_tag & “RB”. For Transducer blocks PD_tag & “TB{1,2,…,n}”
4. Select parameter FF_BLOCK.BLOCK_TAG, press Download Sel to change block name in
device.
5. Use the filtering options at the bottom of the page to select parameters of interest:
- Use the pull down menu to select parameters that appear on a specific tab:
- Configuration for parameters shown on the Configuration tab for this block
- Diagnostics for parameters shown on the Diagnostics tab for this block
- Tuning for parameters shown on the Tuning tab for this block
- All for all resource block parameters.
- Check Differences Only to display only parameters for which the values do not agree.
- Check Selections Only to show only parameters you have selected.
6. Click the row header (the left-most button in the row) to select the first parameter.
7. Press Ctrl while clicking the row headers for additional parameters.
8. Click the left-most column header to select all parameters; click the column header a second
time to deselect all parameters.

Issue: 0.1 AB PLANT

Figure 3-12 Renaming Resource block
9. Check parameters of Resource Block in FF Device according to tables A-1 & A-2 in Appendix
A – in tab Compare. If necessary change them in tab Configuration, click Save and
download them from tab Compare - select the parameters to be set from the IACC database,
and click Download Sel. If you have additional parameters you know that must be set, set and
download them.
10. Select Differences Only check box, select all items and do Upload Sel.

Issue: 0.1 AB PLANT

Figure 3-13 Visualized differences of Configuration parameters
11. Select each transducer block in turn and repeat steps 3 to10.
12. Set Resource and Transducer blocks in AUTO mode – set parameter MODE_BLK.TARGET to
AUTO and download it. If MODE_BLK.ACTUAL is still not AUTO then check the System
Management for failures.
13. Choose Window > Close All to exit the FDM.

Issue: 0.1 AB PLANT

4. Create FF function blocks
4.1. Create FF Function block in simple CSD
In the Plant tab, use the pop-up menu for a Plant Area to create a simple CSD and a
Compound or use existing Plant Area and Compound.
1. If you want to use new Plant Area right click on Plant, select New Plant Area. Rename new
Plant Area 1.
2. If you want to use new Compound right click on used Plant Area, select New > Compound.
Rename new COMPND1. Right click on Compound, select Assign to Control Station … and
select one of the available Controllers.
3. Right click on used Plant Area (FF_TEST in our example), select New > CSD > Simple CSD
4. New Simple CSD appears in Plant Area, rename it to used CSD Name.
5. Right click on new CSD, select Assign Default Compound and choose one in the list.
6. Double click on new CSD and open CSD Editor.
7. Select DCI palette from selection box in Palette window (on right side). The list of DCI blocks
appears, FF Function blocks – AI, AO, DI and DO are among them.
8. Drag one of them and place on CSD Editor. In our example it is AI. Double click on it or click
right and select Properties, change the name.
9. Click the Network tab in the Project Navigator and expand the display to show the ECB201s
representing the H1 devices to be connected. The ECBs are located under the FBM object
and under the ECB compound (F27003_ECB in Figure 4-1).
10. Select the ECB for the device providing the input, drag the block into the CSD Editor, and
position it to the left of the AI block.
11. Connect the Input_1 parameter in the ECB to the From_Fld1 parameter in the AI block
(Figure 4-1). For DI it will be From_Fld1, for AO and DO To_Fld1.
12. Check if these most important parameters in DCI block are filled in correctly: channel, L_type,
XD_scale100 and 0, XD_eu, OUT_scale100 and 0, OUT_eu.
13. Download the CSD, in case of new Compound download whole compound. Right click on
CSD or Compound, select Validate/Download > Download.
-

Issue: 0.1 AB PLANT

Figure 4-1 Making simple CSD
4.2. Create FF Function block in CSD template
The CSDs with FF Function blocks created in CSD template are build from tag in taglist. How
to fill in Tag parameters is described in PFS document of each CSD Template. Three CSD Templates
in ABC Toolkit, rev 6 uses FF Function blocks:
AI_3
BI_3
AO_3

Issue: 0.1 AB PLANT

5. Managing Change
This chapter covers some of the tools available for aligning the IACC database with the control system
and with the field devices, and for safeguarding multiple databases as the system evolves.
5.1. Modifying Function Blocks
You can change all Function Block parameters in IACC Db and then download it to CP / Device.
Download of modified parameters can be initiated from either the Project Navigator or the block’s
Properties dialog box (Figure 5-1).
Figure 5-1 AI block parameters
To download a modified block:

1. Click the Download button in the Properties dialog box then click Next in the Hierarchy Validation
dialog box to start the validation.
2. Click Next to start the download after the blocks have been validated.
If the live update determines that one of the affected device function blocks is not in the required
mode, it displays the Foundation Fieldbus Download Advisory dialog box (Figure 5-2).

Issue: 0.1 AB PLANT

Figure 5-2 Download Advisory
The top of the box describes the discrepancy and provides instructions for either cancelling the
download or changing the blocks to their required mode. The Help button in the lower right opens a
dialog box with additional information about the parameters that require that the block be in either OOS
or Manual (Figure 5-3).
Figure 5-3 FF Advisory Help

Issue: 0.1 AB PLANT

3. Open the detail display of the affected block in FoxView. If IACC is running on an I/A Series
workstation, you can access the block detail display in FoxView by clicking on the pathname of the
parameter (Figure 5-2).
4. Change the block’s mode by clicking the OOS SWITCH (or Man SWITCH) button in the lower right
corner of the display (Figure 5-4).
Figure 5-4 Switching modes of FF Function block from Detail display
5. When the detail display indicates that the block is in the required mode, switch back to IACC
and click Next in the Download Advisory dialog box to display the Downloading dialog box
(Figure 5-5).
Figure 5-5 Downloading FF Function Block
6. Click Start to complete the download.

7. Switch back to FoxView and turn the block back to its mode prior to the download.

Issue: 0.1 AB PLANT

5.2. Modifying Resource and Transducer Blocks
This section describes how to use Field Device Manager to modify the resource and
transducer block parameters in an installed H1 device. The parameter values are changed in the IACC
database and then downloaded to the device. The following example involves changing the permitted
modes in a resource block. These parameters are unlocked. The device is online and functioning in
the process. The instructions also apply to transducer blocks.
To modify a resource block in a live device:
1. Start IACC and click the Network tab.
2. Expand the host FBM, its software, and its ECB200/202 to display the attached H1 devices.
3. Right-click the device and choose Field Device Manager > Field Device Manager (Universal)
4. Use the pull-down list in the upper left corner of the editor window to select the resource block, and
then click the Configuration tab.
The editor displays the parameter values as set in the IACC database. The page displays only those
parameters that are selected in the template for this device type. The Actual field in the upper left of
the editor window displays the current block mode in the device. Target displays the target mode as
set in the IACC database; when the target mode is displayed in bold type, the parameter value in the
device is the same as the IACC database value. The button to the right of the mode field indicates the
currently configured permitted modes (OOS and Auto in Figure 5-6).
5. Click +5 to expand the MODE_BLK parameter, and click inside the MODE_BLK.PERMITTED value
cell to display a check list of configurable values.
6. Click the check boxes for Manual, and click anywhere outside the cell. The cell background color
turns to yellow to indicate that the change has not been downloaded to the device (Figure 5-6).
Figure 5-6 Configuration Tab of Resource block

Issue: 0.1 AB PLANT

7. Make other changes to the resource block.

At this point, the parameter change can be saved in the IACC database, or downloaded to the live
device, in which case the change is also saved to IACC database.
5.3. Downloading Resource and Transducer Blocks
Resource and transducer blocks configurations are downloaded from the IACC database as
part of the commissioning process, run either from an instrument shop or from IACC on an I/A Series
workstation. The blocks can also be downloaded individually using commands on the blocks’
Configuration page in Field Device Manager. The download can be performed at any time from either
an instrument shop system or a control room system, as described in this section.
The parameters that are included in the download and the order in which they are sent to the
device are configured in the device definition. The Download configuration (Figure 5-7) consists of two
lists: Writable Parameters and Download. To download a parameter change that parameter must be
on the Writable parameter list. This list can be edited at the device level if the configuration is not
locked at the device type level.
Figure 5-7 Download behavior setting
To download a resource block to a live device:

1. Use the pull-down list in the upper left corner of the editor window to select the resource block, and
then click the Configuration tab (Figure 5-6).
2. Click OOS above the resource block tabs to set the target block mode to OOS if the block mode is
not already out of service.

Issue: 0.1 AB PLANT

In the example in Figure 5-6, the resource block mode in the device is in its target mode (Auto) and
two parameters have been modified in the Configuration tab. The parameters are displayed in yellow
as the changes have not been downloaded. With the live connection to the device, the Upload All,
Download All, and Download buttons at the bottom of the tab are active.
3. Wait for the Actual mode to change to OOS.
4. Click one of the download commands:
Download to download only parameters that have been modified in the IACC database and that are
included in the Writable Parameters list (Figure 5-7).
Download All to download all the parameters on the Download List, and parameters that have been
modified in the IACC database and that are included in the Writable Parameters list. Both commands
also result in the configuration being saved to the IACC database.
5. Click Yes in the warning dialog box to confirm the action (Figure 5-8).
Figure 5-8 Warning before download
IACC displays progress messages in the Output window as it downloads to the device.
Choose View > Output Window from the IACC menu bar if the window is not open. The download of
certain parameters may have change other parameters in the device, and as result the device
configuration might not match the IACC database, especially if the download contained only selected
parameters.
6. Do one of the following to ensure that the IACC database is aligned with the actual device
configuration:
Click Upload All to upload all resource block parameters to IACC.
All resource block parameters with a locked status of or are updated by the upload.
Parameters with a locked status of are not updated by the upload.

Use the Compare tab to review differences between the two databases and then selectively upload or
download parameters that do not match.
7. Click Save on the Configuration tab.
If there is failure in the download, the Database Value cells for affected parameters and the
message icon in the upper right corner of the block display change to a dark red.
1. Click to open an Error Monitor dialog box describing the problems (Figure 5-9).

Issue: 0.1 AB PLANT

Figure 5-9 Error Monitor
2. Do the following to resolve the problem:

Check the actual resource block mode to ensure that it is appropriate for the parameters being
downloaded.
Verify that you have permissions to download the specific parameters. Repeat the download
procedure.
5.4. Comparing the Device with the Database
This section describes how to use the Compare tabs in Field Device Manager to align the
IACC database with the configuration of a device that has that has just been brought online. In the
following example, the device has been prepared off-line in the instrument shop, and all resource and
transducer block parameters have been set to the desired configuration except the block tags, which
are correct in the IACC database. The blocks tags are downloaded to the device and then the entire
device configuration is uploaded from the device to update the IACC database.
Note: While Field Device Manager provides a Compare tab for function blocks, the feature
should only be used with resource and transducer blocks. Function blocks are configured in the IACC
CSD Editor and the properties sheets for the corresponding FF Function blocks as part of control
configuration; function blocks are not configured or maintained in Field Device Manager. The Compare
tab should be used with function blocks only to view the values in the device. To align the IACC
database with the configuration of an online device:
1. Right-click the device in the Project Navigator and choose Field Device Manager > Field Device
Manager (Universal) from the pop-up menu.
2. Use the pull-down list en the top left corner of the editor window to select the resource block, and
the click the Compare tab in the block display. The editor displays the database values for all
parameters in the block and the device values as the editor reads them from the device database,

Issue: 0.1 AB PLANT

replacing the cyan * in the device value column (Figure 5-10). If the values do not match for a specific
parameter, the editor displays in the column between the two values.
Figure 5-10. Resource Block Compare Tab
3. Select parameters to be updated:

♦Click the row header (the left-most button in the row) to select the first parameter.
♦Press Ctrl while clicking the row headers for additional parameters.
♦Click the left-most column header to select all parameters; click the column header a second time to
de-select all parameters.
4. Use the filtering options at the bottom of the page to select parameters of interest:
♦Use the pull-down list to select parameters that appear on a specific tab:
♦Configuration for parameters shown on the Configuration tab for this block
♦Diagnostics for parameters shown on the Diagnostics tab for this block
♦All for all resource block parameters.
♦Check Differences Only to display only parameters for which the values do not agree.
♦Check Selections Only to show only parameters you have selected.
5. Select the parameters (BLOCK_TAG in Figure 15-10) to be set from the IACC database, and click
Download Sel.
6. Click Save.
7. Select each transducer block in turn and download parameters values from the IACC database
where appropriate.

Issue: 0.1 AB PLANT

8. Select the device tag in the Field Device Manager navigation pane and click Upload All.
9. Click Save and choose File > Close from the IACC menu bar to exit Field Device Manager.
5.5. Upgrading a Device to a New DD
This section describes how to update devices to a new DD, while maintaining the templates for the
devices including resource and transducer block parameter settings, download setup, access
permissions, and customization of the user interface. There are two distinct cases of a DD upgrade:
There is a revision to the DD files but not to the device version. In this case, the number of blocks and
the block parameter sets have not changed, but the new DD may include additional methods, and
modified descriptions and enumerations.
There is a new device version, in which case there is a higher likelihood that there are changes to the
parameter sets making the new DD incompatible with the old devices. Use the procedure described in
this section only if you are actually swapping out all the old devices to the new version.
In both cases, you will use a separate IACC database to merge information from the old device
templates with the new DD version. Refer to the “Managing IACC Databases” topic in IACC Help for
additional information on setting up the separate database.
Before upgrading to the new DD, take the following precautions:

Consult with the device manufacturer to determine the changes made in the DD revision.
Ensure that you have a current backup of the IACC database that contains the devices to be
upgraded.
Export the device type (or the entire database) in case the original templates need to be restored.
Merging Templates with the New DD

To upgrade a device type to a new DD revision:
1. Open the top-level device type in Field Device Manager, and do the following for each block in the
device:
a. Select the block, click the Customize tab, and click Save As at the bottom of the tab.
b. Use the Save As dialog box to specify a name and location of an XML file for the resource block
template.
2. Close the Field Device Manager and exit IACC.
3. Start IACC, selecting a database other than the one containing the old device type.
4. Create a new device type by importing the new DD version, but using the old device type name.
Refer to chapter 3.2. Creating New Device type.for detailed instructions on creating and naming
device types.
5. Open the new device type in Field Device Manager and for each block in the device do the
following:
a. Select the block and click the Customize tab.
b. Click the Load From button at the bottom of the tab, and use the Open dialog box to browse for and
load the XML file created in step 2.
6. Export the device type – select Device type end select Export to IACC format.
7. Start IACC selecting the database that contains the old device type and instances.
8. Import the new device type selecting the Replace Existing Objects, Copy Other Objects option in
the Import dialog box.
9. Open the device type in the Field Device Manager, select each block in turn and review any error
messages in the Output pane to identify incompatibilities between the between the device type and the
new DD version.

Issue: 0.1 AB PLANT

New DD, Same Device Version

It is anticipated that when the new DD is only a revision to the DD itself and not to the device version,
there will be a few minor incompatibilities between the DD and the device templates. The
inconsistencies will be noted when you open an individual device instance until the new configuration
is saved.
Review the error messages, if any.
Review all settings in each block.
Download the new configuration to each device as part of regular device maintenance.
The error messages for the device and for each block are removed only when the device or
block configuration has been saved.
New Device Version

Anticipate a greater number incompatibilities when the DD is for a new device version. As you import
the template for each block, there will a separate error message for each parameter that cannot be
imported and one for each parameter value that cannot imported.
Print or save the error listings in the Output pane.
An error listings file can be linked to the Identification page for the device or one of its blocks, and the
contents of the file can be cut and pasted to device or block Notes. The error messages for the device
and for each block are removed only when the device or block configuration has been saved.
Review all settings.
Click the Save button to accept the new template for each block.
Install the replacement devices.
Open each device and save the template for each block to clear the error messages, before
commissioning the replacement.
5.6. Changing Device Types
This section describes replacement of devices with a different device type from the same or
different manufacturer. The process involves creating a new device template in the IACC database as
the database for the new devices is not compatible with the existing templates. Before proceeding with
the replacement:
Refer to the manufacturers’ documentation to identify differences between the devices in addition to
those which led to the decision to replace the existing devices.
Ensure that you have a current backup of the IACC database that contains the devices to be
upgraded.
Export the original device type and device instances (or the entire database) in case they need to be
restored.
To start the device type replacement:
Create a new device type by importing the DD for the replacement device, configure the
device template and the template for each resource and transducer block. See chapter 3.2. Creating
New Device type for detailed instructions on creating device types and developing the templates. If
the old and new device types are similar, some of the settings for the previous device (particularly
resource block and function block parameters) may be reused as settings for the new device, using the
Save As and Load From functions described in the previous section. Importing the previous template
may be useful for standard device blocks such as the resource block. However, before experimenting
with importing - templates, you should export templates for the newly created device type so you can
revert to those templates if there are too many incompatibilities between the two device types.
WARNING

Issue: 0.1 AB PLANT

If the parameter names, parameter types or some other parameter attributes are not matching
between manufacturers, the export/import may not be successful for all parameters.
If the replacement device type is reasonably similar to the existing type, import template for the
resource block, review errors to determine whether applying the previous templates is significantly less
work than developing new templates from scratch.
WARNING
Review all settings to ensure correct behavior.
1. Do the following to remove the original device from the I/A System:
a. Start I/A Series System Management, select the host control station in System Monitor Domains
screen, and click CONFIG to display control station’s PIO Bus display.
b. Select the FBM228 to which the device is connected, click NEXT LEVEL, and then choose the
appropriate H1 segment in the port selection dialog box.
c. Select the device in the segment I/O Display and click the EQUIP CHG button.
d. Select DISABLE COMMS in the Equipment Change Screen to take the device offline.
e. Disconnect the device from the fieldbus.
2. Do the following to remove the device from the IACC database:
a. Select the Network tab in IACC and expand the configuration to display the device instance.
b. Right-click the device, choose Where Used from the pop-up menu, and note the uses of the device
ECB listed in the Output pane Where Used tab. Use the Where Used tab’s context menu to print the
listing or save the tab contents to a file.
c. Right-click the device, choose Delete from the pop-up menu, and click OK in the Delete Request
dialog box.
3. Create an instance of the new device type using the name of the deleted device. See Chapter 6
“Defining the Fieldbus” for information on creating and naming device instances.
4. Set the device tag, block tags and other values in the newly created devices to match the settings of
the device it replaces.
5. Update each CSD that used the previous device ECB, as follows:
a. Insert the new ECB block into the control strategy diagram.
b. Restore the connection between the FF function blocks (AI, AO, DI and DO) and the device ECB. If
the CSDs were generated from a CSD template, modify the CSD template and taglist, and then
regenerate the CSDs.
6. Connect the replacement device to the fieldbus and run the Commission Wizard
7. Download the modified CSDs to the CP.
8. Use I/A Series System Management to bring the device on line, and verify the data provided from/to
the devices in the FF function blocks.
9. Delete the original device type when all instances have been replaced with the new device type.
5.7. Removing a Device

Removing an H1 device from the I/A Series system involves taking the device off line, physically
removing it from the segment, deleting the device ECB from the IACC database, and downloading the
changes to FBM. Of course, if the device provides process I/O for any control strategies, those
strategies must be modified also and then downloaded to the control station.
To remove a device from an H1 segment:
1. Make the appropriate changes in the IACC database to CSDs that reference the device and
download the changes to the control station.
Select the device in the Project Navigator and choose Edit > Where Used to display all current
configured references to the device in the IACC database.
See “Modifying Function Blocks” on page 307 for detailed instructions on modifying and downloading
blocks.

Issue: 0.1 AB PLANT

2. Switch to I/A Series System Management, select the device in the display of the segment, click
EQUIP CHG at the bottom of the screen, and make the following selections in the Equipment Change
screen:
♦ INHIBIT ALARMS to suppress system alarms when the device is removed
♦ DISABLE COMMS to take the device off line.
See “System Management Displays” on page 261 for detailed instructions on locating devices in
System Management and performing equipment change actions.
3. Disconnect the device from the H1 segment.
4. Access IACC and expand Configuration at the top of the Network tab to display the host control
station and the FBM228.
5. Expand the FBM228 to display its software, its ECB200/202, and the connected devices.
6. Right-click the device to be removed, choose Delete from the pop-up menu, and click OK in the
Delete Confirmation dialog box.
7. Right-click the host control station and choose Validate/Download > Download to update the
control database in the CP and FBM.

Issue: 0.1 AB PLANT

6. Device Maintenance
Diagnostics tabs in Field Device Manager provide convenient access to diagnostic information about
FBM228s, the H1 segments, and individual devices, and are used in conjunction with the I/A Series
System Management displays to resolve fieldbus problems. Field Device Manager can be invoked
from the FBM228 ECB or any of the devices listed below it
6.1. Troubleshooting FBMs
The FBM Diagnostics tab (Figure 6-1) displays counters for communications events and errors, and
provides tools for advanced troubleshooting. An Invensys service representative may ask for specific
counters from this page to resolve a problem.
Figure 6-1. FBM Diagnostic Tab
To access this display:

1. Right-click the FBM228’s ECB200/202 and choose Field Device Manager > FBM228 Manager
2. Click the Diagnostics tab.
NOTE

Issue: 0.1 AB PLANT

A high value for a counter in this tab or other diagnostic displays does not necessarily indicate a
problem.
6.2. Troubleshooting an H1 Segment
To display diagnostics information for an H1 segment:

1. Right-click the FBM228’s ECB200/202 and choose Field Device Manager > FBM228 Manager
2. Use the pull-down list in the upper left corner of the editor window to select the segment (Link1 in
Figure 6-2).
Figure 6-2. Live List for an H1 Segment
3. The editor displays the Live List tab for the link; the multi-colored cube icon on upper right corner of
the window rotates as the FBM queries the fieldbus and builds the live list table.
4. Wait for the editor to complete the table in the Live List tab and then click the Diagnostic tab in the
editor window to display activity counters for the link (Figure 6-3). The time stamp above the display
indicates when the counters were read from the FBM.

Issue: 0.1 AB PLANT

Figure 6-3. Segment Diagnostic Tab
5. Review the counters for diagnostic information.

6. Consider the following actions if a high number of client/server requests indicates segment overload:
♦ Adjust the minimum macrocylce period for the segment or the
♦ Increase the update period (UPDPER parameter) for FF blocks. This parameter specifies the scan
rate at which the block acquires View_1 information.
♦ Increase the update period (UPDPER parameter) for DCI blocks that access devices on the segment
for maintenance data.
♦ If practical, move selected devices to other segments.
In addition to changing the physical connections, this action requires updating the ECB201s of the
affected devices
7. Attach a bus analyzer to the segment if the number of receive errors, frame errors and overflow
errors indicate problems with the receive components, or if transmission component problems are
evidenced by a relatively high number of transmission errors and aborted transmissions.
Follow the instructions in the bus analyzer documentation to verify power on the bus, list active
instruments, isolate sources of noise, and collect other diagnostic information.
8. Click Reset Counters to restart the counters after making modifications to observe changes in the
link operation.
9. Select other segments for analysis.

Issue: 0.1 AB PLANT

6.3. Troubleshooting Devices
Use the I/A Series System Management displays to respond to system alarms involving H1 devices as
summarized below and described in detail in Chapter 7 System Management Display. Use the
System Management resources to begin troubleshooting and then, if necessary, open IACC and use
the Diagnostic tabs in Field Device Manager to view specific device and block error information.
To respond to a system alarm:
1. Click the red system alarm indicator in FoxView menu bar to access the System Management
displays.
2. Starting with System Domains page, use the yellow and red coding of logical names to navigate the
system hierarchy to the source of the alarm.
a. Select the marked CP in the System Domains screen and click CONFIG to display the connected
FBMs.
b. Select the FBM indicating the alarm condition and click NEXT LEVEL to display the port selection
dialog box.
c. Click the port number that is shown in either yellow or red to display the attached H1 devices.
d. Select the device that indicates either a warning or a failure.
e. Click BLOCK INFO to display the block errors reported by the device.
Note that the display does not identify which blocks in the device are reporting the error condition.
f. Click EQUIP INFO to display additional status and configuration information.
Note that Compound:Block gives the full pathname of the device ECB201.
3. If the System Management resources do not provide enough information to resolve the alarm,
display the Field Device Manager Diagnostic tabs for the device:
a. Expand Configuration in the Network tab to display the host CP and FBM.
b. Expand the FBM’s software and ECB200/202 to display the attached devices. You can also expand
the compound to which the ECB201 is assigned, usually <CP name>_ECB.
c. Right-click the device and choose Field Device Manager > Field Device Manager (Universal)
from the pop-up menu to open the device in Field Device Manager.
d. Select the device tag or one of the blocks in the Field Device Manager using the pull-down lit in the
upper left corner of the editor window, and click the Diagnostic tab in the editor window for specific
details on the device or block status.
6.4. Troubleshooting with Field Device Manager
This section describes the Diagnostic tabs for a device and its blocks. To troubleshoot a device using
Field Device Manager:
1. Right-click the device and choose Field Device Manager > Field Device Manager (Universal)
from the pop-up menu to open the device in Field Device Manager.
2. Click the Diagnostic tab in the editor window to view a status summary of each block in the device
(Figure 6-4).

Issue: 0.1 AB PLANT

Figure 6-4. Device Diagnostic Tab
The page displays the target mode and actual mode for each block, value and status of the primary
and secondary values for transducer and function blocks, and any block errors.
3. Use the pull-down list in the upper left corner of the editor window to select a specific block, and
click the Diagnostic tab to display its diagnostics information.
For selected block parameters, the tab displays the value configured in IACC and the current value in
the device. The background for each Device Value field changes from blue to white when the value
has been read from the device (Figure 6-4). Once all the values have been read, the tab is updated
periodically.

Issue: 0.1 AB PLANT

Figure 6-5 Block Diagnostic Tab
4. Click + on a parameter index number to display the sub-indices; click the minus sign on an index
number to collapse the parameter display.
The parameters that are included in the tab and the rate at which they are read from the device are
defined in the block template. These settings can be modified if the tab configuration is not locked in
the parent device type definition. If the configuration is locked, an additional tab can be defined to
review other parameters or update diagnostic data at a different rate.
6.5. Troubleshooting with the Vendor’s DTM
Field Device Manager provides the option of using a DTM from the device manufacturer to run
additional diagnostics. The vendor’s DTM must be associated with the device in the IACC database.
This is usually done during definition of the device type.
If you save any diagnostic information when using the associated DTM, the information is saved in the
instance-related path of the DTM and not included in the data saved in an IACC database backup.
Therefore if you want to have up to date IACC database after change you have to upload changed
parameters.
Vendor’s DTM offer better visualization of diagnostic for device. On the other hand, existing DTMs
doesn’t support the communication via foundation fieldbus. Therefore is necessary to use connection
to devices via other interfaces (Serial link, Wireless link, NI Field bus Card)

Issue: 0.1 AB PLANT

7. System Management Displays
The System Management Display Handler (SMDH) obtains current and historical informationabout the
system and displays this information in System Management displays. For the FBM228 and the
associated H1 field devices, the SMDH provides the following displays:
♦ A Fieldbus level display (PIO Network), which shows the control station and connected Fieldbus
devices.
♦ For the ZCP270s, a module Fieldbus display showing the selected FCM and its FBMs.
♦ A module Fieldbus level display (PIO Sub-Network), which shows the selected FCP270 or FCM and
its associated FBMs and H1 field devices.
♦ H1 Segment display with device ECBs for the selected segment (port).
♦ Detailed equipment change (EQUIP CHG) and equipment information (EQUIP INFO) displays for
each FBM and associated H1 field devices.
For detailed information on the use of the System Management Displays, refer to System
Management Displays (B0193JC).
To access FBM228 System Management functions:
1. Click the System button in the upper left corner of the FoxView screen to display the
System Monitor Domains screen (Figure 7-1).
Figure 7-1. System Domains Screen in System Management

Issue: 0.1 AB PLANT

2. Select the control station and click the CONFIG button to display the field devices connected to the
control station (the PIO BUS display). Figure 7-2 shows the configuration of a redundant FCP270 pair
(CPFF01) with five FBM228s attached. The two white squares at the bottom of each FBM icon indicate
that devices are attached to the FBM and can be displayed on the next level.
Figure 7-2 FCP270 PIO Bus Display
The first row in each of these device icons gives the device ID (based on the DEV_ID parameter of the
ECB200/202); the second row displays the device hardware type. The colors used for the device ID
and type indicate the status of the ECB and the FBM:
♦ White indicates that there are no errors.
♦ Yellow is a caution, indicating there is at least one existing error warning with the FBM or one of the
H1 devices connected to the FBM.
♦ Red indicates a failure.
An asterisk next to the ECB name indicates that an error has been detected. When the ECB is
white, the error has been resolved.
Table 13-3 lists the command buttons that are active when an FBM icon is selected.

Issue: 0.1 AB PLANT

Button Description
Returns to the System Monitor level
Displays the Equipment Change Screen for the FBM with commands to:
♦Toggle the modules on and off-line
♦Inhibit alarm messages
♦Download database changes to the FBM
♦Update the EEProm.
For a redundant pair, the commands are applicable to one or both of the modules.
There is a command for switching the Master and Tracker roles.
For a redundant FBM pair, displays the first of four Equipment

Information pages (Figure 13-9).
For a non-redundant FBM, displays the first of two Equipment Information
pages.
Displays a dialog box for selecting one of the connected H1 segments
(Figure 13-13). When the port is selected, the ECBs for the connected
H1 devices are displayed.
Displays an overlay with four commands:

♦ENABLE PIO BUS CABLE A ALARMS
♦ENABLE PIO BUS CABLE B ALARMS
♦INHIBIT PIO BUS CABLE A ALARMS
♦INHIBIT PIO BUS CABLE B ALARMS
Table 7-1. PIO Bus Display Command Buttons
7.1. FBM228 Equipment Change Screen
The following commands can be available on the Equipment Change screen for an FBM228:
GO ON-LINE and GO OFF-LINE
Switches the communication between the module and the control station on or off. When a non-
redundant FBM is selected, Go ON-LINE and Go OFFLINE are mutually exclusive. The Go OFF-LINE
command is active only when the FBM is on-line, and the Go ON-LINE is active only when the
modules is off-line. For a redundant FBM228 pair, both commands are always active. When you click
one of the commands, System Management opens the Module Selection dialog box for specifying the
modules to go on-line or off-line (Figure 7-3). The dialog box shows the current state (on-line or off-
line) of the modules.

Issue: 0.1 AB PLANT

Figure 7-3. Module Selection Dialog Box
♦ Select one or both of the modules, or click Cancel to return to the Equipment Change screen without
applying the command.
ENABLE DEVICE ALARMING and INHIBIT DEVICE ALARMING
Enables/disables communication to the control station of alarms generated by the FBM and the
attached H1 devices. Note that the commands only deal with generation of the alarm messages and
not with the FBM’s ability to detect alarm conditions or with the alarm detection functions of the H1
devices.
EEPROM UPDATE
Updates the FBM software revision. For a non-redundant FBM, an EEPROM update causes the
module to restart, calculate the Link Active Schedule, and re-establish communications with the
connected devices. It will take several minutes to regain all the publisher/subscriber and client/servers
connections between the device function blocks and the control station. If a redundant FBM pair is
selected, System Management opens the Module Selection dialog box (Figure 7-3) allowing you to
update the FBMs without interrupting service.
NOTE
You can perform an online update for a revision within the same version (from 2.1 to 2.2, for example)
but not to implement a new version (from 2.1 to 3.0, for example). Version updates must be done
offline.
To perform an EEPROM update on a redundant pair:
♦ Select the Tracker module.
♦ When the EEPROM update is completed, the FBM returns to the Tracker role it had before the
update.
♦ Click EQUIP INFO and verify that the module is online, tracking and operating properly (Figure 7-5
through Figure 7-8 in the next section).
♦ Use the SWITCH ROLES command to make the updated FBM the Master.
♦ Click EEPROM Update and select the other FBM.
NOTE
Selecting select both modules for an EEPROM update at the same time interrupts communication with
the attached H1 devices.
SWITCH ROLES
Causes the FBMs to switch roles. The Tracker module assumes the role of Master, and the Master
becomes the Tracker. When you select this command, System Management opens a confirmation
dialog box (Figure 7-4). The dialog box shows the current state (on-line or off-line) of the modules.

Issue: 0.1 AB PLANT

Figure 7-4. Confirmation Dialog Box for Switch Roles
♦ Click Yes to proceed.

♦ Click No to cancel the command.
The command is not active for a non-redundant FBM.
DOWNLOAD
Causes the module to reload its image and any database configuration changes. The FBM
recalculates the Link Active Schedule and establishes connections with the devices. It may take
several minutes before all of the publisher/subscriber and client/server connections are re-established.
When the module is a redundant FBM, it is returned to its pre-download state. For a redundant
FBM228 pair, DOWNLOAD is always active. When you click DOWNLOAD, System Management
displays the Module Selection dialog box (Figure 7-3), which shows the current state (on-line or off-
line) of the modules.
♦ Select one or both of the modules, or click Cancel to return to the
Equipment Change screen without applying the command.
7.2. FBM Equipment Information
To display status and configuration information about an FBM228:

1. Select the FBM icon and click the EQUIP INFO button. SMDH displays the first Equipment
Information page (Figure 7-5). The pages are numbered in the bottom right corner of the screen.
2. Click the button to view additional pages (Figure 7-6, Figure 7-7, and Figure 7-8). In the
Equipment Information displays, redundant FBMs are labeled Main and Backup, or M and B. Main
refers to the module installed in the lower numbered slot, as described in “Identifying Modules in a
Redundant Pair” on page 256, and not to its role as either Master or Tracker.
After reviewing the FBM information, you can select the Equipment Change screen, return to the
System Monitor screen on the previous level, or access the PIO Bus Display.

Issue: 0.1 AB PLANT

Figure 7-5. First Equipment Information Page for Redundant FBM228s

Issue: 0.1 AB PLANT

Figure 7-6. Second Equipment Information Page for Redundant FBM22s
Figure 7-7. Third Equipment Information Page for Redundant FBM228s

Issue: 0.1 AB PLANT

Figure 7-8. Fourth Equipment Information Page for Redundant FBM228s
7.3. H1 Device Displays
From the PIO Bus Display, you can access information about specific H1 devices connected to the
FBM228.
To access the connected H1 devices:
1. Select the FBM and click the NEXT LEVEL button. SMDH prompts you to select the H1 segment by
port number (Figure 7-9). If there is no segment connected to a port, the port number is displayed in
red.
Figure 7-9. Selecting the H1 Segment
The color of the port number indicates the health of the devices on the segment:
White All devices are on this segment are healthy.
Issue: 0.1 AB PLANT

Yellow One or more devices are reporting a warning condition.

Red At least one device on the segment has a failure or its ECB is off-line.
Black There are no devices configured for this segment.
2. Click the port number for the segment to display the attached devices (Figure 7-10).
Figure 7-10. I/O Display for an H1 Segment
Each square at the top of the page represents an ECB201 that holds information about a device on the
segment. The first row in each of these device icons lists the device ID; the second row displays the
hardware type of the FBM. As with the FBM icons, the colors used for the name and type indicate the
status of the ECB and the H1 device:
♦ White indicates that there are no errors.
♦ Yellow is a caution, indicating there is at least one existing error warning with the H1 device.
♦ Red indicates a failure.
An asterisk next to the ECB name indicates that an error has been detected. When the device ID
lettering is white, the asterisk indicates that there has been an error or warning, but the device has
been returned to normal. Raise the Equipment Information display for the device to acknowledge the
error and clear the asterisk from the display.
Table 7-2 lists the command buttons that are active when a device icon is selected.

Issue: 0.1 AB PLANT

Button Description
Returns to the previous level, the PIO Bus Display, showing the FBMs.
Displays the Equipment Change Screen for the device ECB including the
following commands:
♦ ENABLE DEVICE ALARMING/INHIBIT DEVICE ALARMING
Enables/disables communication to the control station of system alarms
generated by the FBM and the attached H1.
♦ ENABLE COMMS/DISABLE COMMS
Enables/disables communications between the device and the control
station. Disabling communications disables all publisher/subscriber and
client/server connections to the device function blocks.
Displays the Equipment Information pages for the device

(Figure 7-11).
Displays a Block Error Information overlay with information on errors

in the device ECB (Figure 7-14).
To review status information for a connected H1 device:

1. Select the device icon and click EQUIP INFO to display the first Equipment
Information page (Figure 7-11).
The page number is displayed in the bottom right corner.
2. Click the button to view additional pages (Figure 13-12 and Figure 13-13).

Issue: 0.1 AB PLANT

Figure 7-11. First Equipment Information Page for an H1 Device
Figure 7-12. Second Equipment Information Page for an H1 Device

Issue: 0.1 AB PLANT

Figure 7-13. Last Equipment Information Screen for an H1 Device

Issue: 0.1 AB PLANT

7.4. Block Error Display
To access the Block Error display (Figure 7-14):

♦ Click the Block Info button.
The display is the logical OR of the multiple device block BLOCK_ERR parameters as read by the
FBM228. The bit-enumerated BLOCK_ERR parameter is common to all of the resource, transducer
and function blocks. If an error bit is set in any one of these device blocks, it is reported in the Block
Error Display. Otherwise, the condition is marked OK or No as shown in Figure 7-14.
Figure 7-14. Block Error Information Overlay for Selected Device ECB

Issue: 0.1 AB PLANT

8. Backup of Databases
8.1. Periodic Backup of Databases
The IACC Database Administrator is a separate utility for backing up, verifying, and restoring
IACC databases. All three functions are selected from the IACC Database Administration window
(Figure 8-1), which includes an Output window for monitoring the progress of the selected operation.
When the IACC Database Administrator is initiated from Explorer, three command buttons are active:
Backup, Restore, and Verify. When the IACC Database Administrator is initiated from the IACC
window, only the backup option is active, and the backup command is applied only to the currently
open database. Database restoration and verification can be executed only off-line; no user can be
logged into the target IACC database.
Figure 8-1. IACC Database Administration Window
8.2. Backing Up a Database
The backup procedure makes a copy of the complete IACC database, including DD files and
device data entered using third-party DTMs, and saves the database to a user-specified location. You
can save multiple backup copies and select from among them when you need to restore the files. All
changes made since the backup are eliminated. Backups are automatically made each time you
download.
You can also make backup copies of the IACC database using the copy and paste functions in
Windows Explorer. However, this approach requires separate backups for DTM data, which is not

Issue: 0.1 AB PLANT

saved in the IACC application path. The IACC Database Administrator utility is the recommended
method for a comprehensive backup and restoration of an IACC database.
To back up the currently open IACC database:
1. Choose Window > Close All to close all editors.
2. Choose Tools > Backup from the menu bar.
IACC opens the IACC Database Administrator dialog box, with only the Backup and Exit buttons
active.
3. Click Backup.
An Enter backup file dialog box (Figure 15-12) prompts you to specify the location and name of the backup file.
The default name for the backup file is the filename with the current date and time, for example:
IACC_mmddyyyy_hhmm.bdb
Figure 8-2. Enter Backup File Dialog Box
4. Click Save to accept the default name and location, or use the controls in the dialog box to enter a
different name or location, and then click Save.
The Output window in the dialog box displays the backup functions as they are
performed, and error messages if there are problems. When the process is complete,
the utility displays a message box (Figure 8-3).

Issue: 0.1 AB PLANT

Figure 8-3. Backup Complete
5. Click OK to close the information box and exit the utility.

NOTE
The Backup function is applied to only one database at time. When accessed from
within IACC, the Backup only applies to the currently opened database.
6. Restart IACC, selecting another database to be backed up, and repeat the steps in
described in this section until backups have been made of all the databases.
8.3. Restoring a Database
The Restore function overwrites the current database with a file that was created with the backup
function.
To restore a database:
1. Ensure that no one is logged into the target database. If there is an active client, work is overwritten
by the restore function.
If you are using multiple databases, make sure that you have the correct name and path for
the target database. The pathnames are displayed in the IACC Databases dialog box when you log
onto to IACC, and stored in the file \IACC\Database\ IACCSettings.txt.
2. Use Explorer to locate the utility in the executable folder:
…\IACC\bin\DbAdmin.exe
3. Double-click DbAdmin.exe to open the IACC Database Administrator window (Figure 8-1).
4. Click Restore.
The utility displays a dialog box in which you select the database to be restored (Figure 8-4). The
dialog box is similar to a standard.

Issue: 0.1 AB PLANT

Figure 8-4 Selecting the Backup File
6. Use the dialog box controls to select the database to be restored, and click Open. The
utility displays the target directory, that is, the directory in which the original IACC
database files were located (Figure 8-5). If you select another location, the Restore
function does not work.

Issue: 0.1 AB PLANT

Figure 8-5 Select Destination Directory Dialog Box
6. Click Open.
If the target directory already contains a valid database, Restore overwrites it with the selected
database. To prevent data loss, the utility prompts you to back up the database in the target
directory (Figure 8-6).
Figure 8-6. Option to Back Up Files Currently in the Target Directory
7. Select Yes to back up the database using the default name and location, or click No to skip the
backup.
If you select Yes, the utility displays the Enter backup file dialog box (Figure 8-2) so you can specify a
filename and location.
The Output window displays the restore procedure, which includes both a verification of the database
to ensure that all pointers and references in that database are valid and a database integrity check
(Figure 8-7).

Issue: 0.1 AB PLANT

Figure 8-7. Restore Complete
8. Click Exit when the Output window indicates that the target database volume has
been closed.
8.3. Exporting Databases

Select the “Managing IACC Database” topic in IACC Help for additional information on exporting and
importing databases. To export an IACC database:
1. Select System at the top of the System tab.
2. Choose File > Export from the menu bar to open the Available Formats dialog box.
3. Select Export to IACC Format in the dialog box and click OK.
4. Specify a destination folder and an export file name (with the .ida extension) in the IACC Export File
Name dialog box, and click Next to display the specified export in the Verify dialog box.
5. Click Next to start the actual export, and then Finish when the Export dialog box displays the
following message:
The Export operation is done.
8.4. Importing Databases

To import from an IACC database:
1. Start IACC, selecting the database into which the data is to be imported, if there are multiple
databases available.
NOTE
Once IACC is opened, you cannot switch databases. Care should be exercised to ensure that the data
is imported to the correct database.

Issue: 0.1 AB PLANT

2. Select System at the top of the System tab in the Project Navigator
3. Choose File > Import from the menu bar to open the Available Formats dialog box.
4. Select Import from IACC Format in the dialog box and click OK.
5. Specify the source folder and the export file name in the IACC Import File Name dialog box, and
click Next to display contents of the file in the Import dialog box (Figure 8-8).
Figure 8-8. Import Dialog Box
6. Click the check boxes for the objects to be imported.

7. Select one of the Import options:
♦ Copy All Objects, if you do not want to overwrite any object in the IACC database that has the same
name as an imported object. After import, the duplicate names are displayed in red italic letters until
one of the names is changed.
♦ Replace Existing Object, Copy Others to update definitions that have matching names with the
imported definitions.
8. Click Next.
A warning dialog box identifies those objects that will replace objects already in the database.
9. Click Next to proceed or Back to change the object selection or the import option.
10. Click Next in the verify dialog box, and then click Finish when the Export dialog box displays the
following message:
The import operation is done
When all imported items are copied, duplicate object names are displayed in red italic letters, until you
rename or delete one of the objects.
Issue: 0.1 AB PLANT

Appendix A: Recommended Settings for Resource Blocks
Source: B0700ba_b
For Transmitters:
MODE_BLK.Permitted Select Auto and OOS. These are required
modes; other modes are optional.
MODE_BLK.Target Select Auto, the required target mode.
FEATURE_SEL Make sure the following features are NOT
selected:
Reports Option
Write Lock
Direct Write to Output Hardware
These features are not supported.
GRANT_DENY Make sure that none of the options are selected;
GRANT_DENY is not supported.
SHED_RCAS Set to 0. SHED_RCAS is not supported
SHED_ROUT Set to 0. SHED_ROUT is not supported
ALARM_SUM.Disabled Check each option in ALARM_SUM.Disabled.
All alarms should be disabled. Use the alarm
options in the I/A Series FF Function blocks.
Table A-1
For Positioners and Discrete Valve Controllers:
MODE_BLK.Permitted Select Auto and OOS. These are required

modes; other modes are optional.
MODE_BLK.Target Select Auto, the required target mode.
FEATURE_SEL Make sure the following features are NOT
selected:
Reports
Write Lock
These features are not supported.
FEATURE_SEL Select the following features:
Out Readback
FaultState
FaultState is partially supported:
♦The FBM228 supports FaultState actions at the
device level on loss of communications between
the CP and the FBM228.
♦The FBM228 does not support faultstate logic
using SET_FSTATE and CLR_FSTATE
parameters.
GRANT_DENY Make sure that none of the options are selected;
GRANT_DENY is not supported.
SHED_RCAS Set to 0. SHED_RCAS is not supported
SHED_ROUT Set to 0. SHED_ROUT is not supported
Table A-2

Issue: 0.1 AB PLANT

Appendix B: Selected Engineering Units Codes
Table B-1

Issue: 0.1 AB PLANT

FF Temperature Mux Configuration & Commssioning Procedure1 Iacc

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

FF Temperature Mux Configuration & Commssioning Procedure1 Iacc

Uploaded by

Copyright:

Available Formats

FF devices Installation Manual

FF devices Installation Manual

Invensys Ref: AB 1234

2. FOUNDATION fieldbus ECBs............................................................................................................................3

3. Installing new device ............................................................................................................................................4

3.1. Check Device type parameters ......................................................................................................................4

4.1. Create FF Function block in simple CSD....................................................................................................19

5.1. Modifying Function Blocks.........................................................................................................................21

6.1. Troubleshooting FBMs................................................................................................................................33

7.1. FBM228 Equipment Change Screen ...........................................................................................................41

8.1. Periodic Backup of Databases .....................................................................................................................52

Appendix B: Selected Engineering Units Codes ....................................................................................................60

Invensys Proj.NoAB 1234 ABC Cust Proj.No: 1234

FF devices installation manual_rev 1.doc

2. FOUNDATION fieldbus ECBs

With FOUNDATION fieldbus, an ECB201 is created to represent each H1 device connected

Invensys Proj.NoAB 1234 ABC Cust Proj.No: 1234

FF devices installation manual_rev 1.doc

3. Installing new device

3.1. Check Device type parameters

Figure 3-1 Live List of Segment

Invensys Proj.NoAB 1234 ABC Cust Proj.No: 1234

FF devices installation manual_rev 1.doc

Figure 3-2 Device ECB properties

3.2. Creating New Device type

To define a device type:

Invensys Proj.NoAB 1234 ABC Cust Proj.No: 1234

FF devices installation manual_rev 1.doc

Figure 3-3 Import of dd file

3.3. Modifying the device type

Invensys Proj.NoAB 1234 ABC Cust Proj.No: 1234

FF devices installation manual_rev 1.doc

Invensys Proj.NoAB 1234 ABC Cust Proj.No: 1234

FF devices installation manual_rev 1.doc

Figure 3-4 Unlocking all parameters

Invensys Proj.NoAB 1234 ABC Cust Proj.No: 1234

FF devices installation manual_rev 1.doc

3.4. Add ECB for FF Device

Figure 3-5 Addition of new Device ECB

Invensys Proj.NoAB 1234 ABC Cust Proj.No: 1234

FF devices installation manual_rev 1.doc

Figure 3-6 Renaming of Device ECB

Invensys Proj.NoAB 1234 ABC Cust Proj.No: 1234

FF devices installation manual_rev 1.doc

3.5. Commissioning with IACC Commission Wizard

Figure 3-7 Setup downloads

Invensys Proj.NoAB 1234 ABC Cust Proj.No: 1234

FF devices installation manual_rev 1.doc

To commission a device from an IACC control room system:

Figure 3-8 List of Unassigned Devices

Invensys Proj.NoAB 1234 ABC Cust Proj.No: 1234

FF devices installation manual_rev 1.doc

5. Select a physical device and click Next.

Figure 3-9 Commissioning window

Invensys Proj.NoAB 1234 ABC Cust Proj.No: 1234

FF devices installation manual_rev 1.doc

Figure 3-10 Warning before doownload

Invensys Proj.NoAB 1234 ABC Cust Proj.No: 1234

FF devices installation manual_rev 1.doc

Figure 3-11 Commission progress

Invensys Proj.NoAB 1234 ABC Cust Proj.No: 1234

FF devices installation manual_rev 1.doc

3.6. Selectively download the configuration.