FIM VERSION 2.

ABB Ability™
Field Information Manager
User Guide
FIM VERSION 2.2

ABB Ability™
Field Information Manager
User Guide

Document Number: 2PAA117322V22

Document Revision: A
Release: January 2021

Trace back information Main Publication:

Tool version: 5.2.025
Build date: 2021-01-13 at 10:57:56
Domain: ABBPA
Workspace, version, checked in: Field Information Manager, a62, 2021-01-13
Master: ix-476693-Field Information Manager Manual.xml
Recipe: ix-476703-Field Information Manager PrintOnly.rcp
PDF stylesheet: ix-470537-PDF-Stylesheet.xml
Customer stylesheet: ix-470536-CustomerStylesheet.xml
Notice
This document contains information about one or more ABB products and may include a description of or a reference
to one or more standards that may be generally relevant to the ABB products. The presence of any such description of
a standard or reference to a standard is not a representation that all of the ABB products referenced in this document
support all of the features of the described or referenced standard. In order to determine the specific features supported
by a particular ABB product, the reader should consult the product specifications for the particular ABB product.

ABB may have one or more patents or pending patent applications protecting the intellectual property in the ABB
products described in this document.

The information in this document is subject to change without notice and should not be construed as a commitment
by ABB. ABB assumes no responsibility for any errors that may appear in this document.

Products described or referenced in this document are designed to be connected, and to communicate information and
data via a secure network. It is the sole responsibility of the system/product owner to provide and continuously ensure
a secure connection between the product and the system network and/or any other networks that may be connected.

The system/product owners must establish and maintain appropriate measures, including, but not limited to, the
installation of firewalls, application of authentication measures, encryption of data, installation of antivirus programs,
and so on, to protect the system, its products and networks, against security breaches, unauthorized access, interference,
intrusion, leakage, and/or theft of data or information.

ABB Ltd and its affiliates are not liable for damages and/or losses related to such security breaches, any unauthorized
access, interference, intrusion, leakage and/or theft of data or information.

ABB verifies the function of released products and updates. However system/product owners are ultimately responsible
to ensure that any system update (including but not limited to code changes, configuration file changes, third-party
software updates or patches, hardware change out, and so on) is compatible with the security measures implemented.
The system/product owners must verify that the system and associated products function as expected in the environment
they are deployed.

In no event shall ABB be liable for direct, indirect, special, incidental or consequential damages of any nature or kind
arising from the use of this document, nor shall ABB be liable for incidental or consequential damages arising from use
of any software or hardware described in this document.

This document and parts thereof must not be reproduced or copied without written permission from ABB, and the
contents thereof must not be imparted to a third party nor used for any unauthorized purpose.

The software or hardware described in this document is furnished under a license and may be used, copied, or disclosed
only in accordance with the terms of such license. This product meets the requirements specified in EMC Directive
2014/30/EU and in Low Voltage Directive 2014/35/EU.

Trademarks
All rights to copyrights, registered trademarks, and trademarks reside with their respective owners.

Copyright © 2021 by ABB. All rights reserved.

Table of Contents

Table of Contents

1 Introduction
2 Installation and Software Configuration
2.1 Operating System Requirements ...................................................................... 11
2.2 Installation and Upgrade ................................................................................... 11
2.3 User Management ............................................................................................. 12

3 Connectivities
3.1 Local Connectivities .......................................................................................... 13
3.1.1 HART isHRT FDI Communication Server ............................................ 13
3.1.2 PROFIBUS isPro FDI Communication Server ..................................... 14
3.1.3 UMC USB Serial Communication Server ............................................ 14
3.2 Remote Connectivities ...................................................................................... 14
3.2.1 ABB FIM Bridge 800xA ........................................................................ 14
3.2.2 ABB FIM Bridge PROFINET ................................................................ 14
3.2.3 ABB FIM Bridge OPC-UA .................................................................... 15
3.2.4 Thorsis isNet Pro FDI Communication Server ..................................... 15
3.2.5 Thorsis isNet HART FDI Communication Server ................................. 15
3.2.6 Thorsis HART-IP FDI Communication Server ..................................... 15
3.3 ABB Ability™ Support ....................................................................................... 15

4 Basic Concept
4.1 Overview ........................................................................................................... 17
4.2 Device representation – Device Tile ................................................................. 18
4.3 Add and remove a Communication Server ....................................................... 19
4.4 Communication Server Settings ........................................................................ 20
4.5 Tag Mapping ...................................................................................................... 20
4.6 Bulk Operations ................................................................................................. 21

2PAA117322V22 A 5
Table of Contents

4.7 Managing Projects ............................................................................................ 21

4.8 Info Center ........................................................................................................ 22
4.9 License Handling ............................................................................................... 22
4.10 Language Support and Language Packs .......................................................... 22
4.11 Easy Access Wizard ......................................................................................... 23
4.12 Optimized Touch Handling ................................................................................ 24
4.13 Tooltips and Tooltip-Picker ................................................................................ 24

5 Device Management
5.1 Topology View ................................................................................................... 25
5.2 Configurations View .......................................................................................... 25
5.3 Device Identification and Scanning ................................................................... 25
5.3.1 Local Communication Servers ............................................................. 25
5.3.2 Remote Communication Servers ......................................................... 26
5.4 Device Views ..................................................................................................... 26
5.5 Device Bar ......................................................................................................... 26
5.6 Multiple Device Views ....................................................................................... 27
5.7 Device Configuration ......................................................................................... 27
5.8 Offline Configuration ......................................................................................... 28
5.9 Upload / Download Configurations .................................................................... 28
5.10 Templates .......................................................................................................... 28
5.11 Compare Datasets ............................................................................................ 28
5.12 Import of Device Engineering Data ................................................................... 29
5.12.1 File Format ........................................................................................... 29
5.12.2 Comparison with parameters of connected field devices .................... 30
5.12.3 Loop Check based on imported Device Engineering Data .................. 31

6 Device Package Handling

6.1 Device Catalog .................................................................................................. 33
6.2 Device Package and Package Assignment ...................................................... 33
6.3 HART Generic Device Package ........................................................................ 34
6.4 Device Integration by GSDML ........................................................................... 34
6.5 ABB Repository ................................................................................................. 35

2PAA117322V22 A 6
Table of Contents

6.6 FieldComm Group Repository ........................................................................... 35

6.7 Offline Repository .............................................................................................. 36
6.8 Common Names ............................................................................................... 37

7 Dashboard
7.1 Diagrams ........................................................................................................... 39
7.2 Details Dashboard ............................................................................................. 40

8 Loop Check
8.1 Loop Check Settings ......................................................................................... 41
8.2 Loop Check Types ............................................................................................ 42
8.2.1 Automatic Loop Check ......................................................................... 42
8.2.2 Automatic Loop Check with Authorization ........................................... 42
8.2.3 Semi-Automatic Loop Check with Authorization .................................. 43
8.2.4 Manual Loop Check ............................................................................. 43
8.3 Loop Check Scope ............................................................................................ 43
8.3.1 Test Routine ......................................................................................... 43
8.3.2 Underrange and Overrange ................................................................. 43
8.3.3 Alarm Limits ......................................................................................... 44
8.4 Loop Check States ............................................................................................ 44
8.5 Additional Information ....................................................................................... 45

9 Troubleshooting
9.1 Contact ABB support for troubleshooting .......................................................... 47
9.2 Tool shutdown even when activities are ongoing .............................................. 47
9.3 Device is not identified by the Auto Scanning - HART modem ......................... 48
9.4 Installation or Un-installation fails ...................................................................... 48
9.5 License fails ...................................................................................................... 49

2PAA117322V22 A 7
2PAA117322V22 A 8
1 Introduction

1 Introduction

ABB Field Information Manager (FIM) is a field device configuration tool based on
FDI-Technology.
Get more information on
http://www.abb.com/fieldinfo

2PAA117322V22 A 9
2PAA117322V22 A 10
2 Installation and Software Configuration
2.1 Operating System Requirements

2 Installation and Software Configuration

2.1 Operating System Requirements

• Windows 8.1, Windows 10, 64 Bit.
• Connectivity services are installed normally on Windows Server OS.
Please find more information about the supported Windows Server versions referring
to the System Guide Summary document 3BSE078159
• 10 GB storage space, minimum of 1 Gigabyte RAM.

2.2 Installation and Upgrade

Please watch also the Frequently asked questions section for further information about
required Windows patches and troubleshooting.
http://new.abb.com/control-systems/fieldbus-solutions/fim/faq
• The installation of the Field Information Manager will automatically upgrade older
Field Information Manager versions.
• Please uninstall the Field Information Manager 1.0 version because this version
does not support any upgrade.
• The installation of the Field Information Manager software requires administrator
rights. Any other users can start the installation setup file, but during the installation
procedure the system will ask for an administrator user and password.
• Normally, the installation will complete in less than 3 minutes, but might be delayed
if the .NET Framework has to be installed or updated.
• The setup will install the Microsoft .NET Framework automatically if required and
reboot if necessary. After the reboot please start the setup file again.
• On nodes where the ABB Asset Vision Basic software is already installed, it is
required to uninstall the "is HRT CommDTM v2" Thorsis (ifak system) communication
driver.

2PAA117322V22 A 11
2 Installation and Software Configuration
2.3 User Management

2.3 User Management

User Management allows the configuration of access rights for specific users in order
to only allow certain actions in Field Information Manager.
When starting Field Information Manager for the first time after a fresh installation,
it is mandatory to have full access in order to import the FIM license. After successful
import of FIM license, other user roles can be used.
By default, user roles are defined in the following file: "C:\Program Files (x86)\Common
Files\ABB\Field Information Manager\ABB.DM.Application.exe.config". The configuration
file can be opened with any text editor, but administrator rights are required for saving
changes.
At the end of the configuration file, there is a section providing instructions how to define
user roles with examples to follow.
A user is identified by the combination of the domain/workgroup/node name and the user
name and can have one of the following user roles:
• Basic Access: No functionality within FIM besides basic options.
• Read-Only Access: All Read-Only operations within FIM are allowed, but it is not
possible to change information in field devices or settings.
• Write Access: All Write operations within FIM are allowed, but it is not possible to
work on global administrative settings.
• Full Access: All operations within FIM are possible.
In addition, the user role "App Access" can be granted to allow execution of Apps in FIM.
A combination of the user roles listed above with App Access is possible. Full Access
includes App Access automatically.
Without a configured User Management, all users are considered as Full Access
automatically.
In case of configured User Management, not defined users are considered as Basic
Access automatically to avoid unintentional access.

2PAA117322V22 A 12
3 Connectivities
3.1 Local Connectivities

3 Connectivities

Field Information Manager supports various connectivities.

Please refer to
http://new.abb.com/control-systems/fieldbus-solutions/fim/connectivities
and find an instructions how to install and setup connections.

3.1 Local Connectivities

Local Communication Servers allow connections to devices by using a supported local
modem.

3.1.1 HART isHRT FDI Communication Server

The HART isHRT FDI Communication Server allows connections to HART field devices
by using a supported local HART modem.

Supported HART modems

Field Information Manager (FIM) contains the Thorsis HART modem driver and is already
prepared to support ABB / Thorsis HART modems listed below:
• ABB NDA121-NX USB (Ex ia)
• ABB NHA121-NO USB
• Thorsis isHRT USB
• Thorsis isHRT USBeX
• Thorsis H@RT BluePack
• Thorsis isNet H@RT - HART Ethernet Gateway with Thorsis isNet Lite - Ethernet
Communication Module
Other modems require a manual modem driver installation. The supported baud rates
are: 1200, 9600, 19200, 38400, 115200.

2PAA117322V22 A 13
3 Connectivities
3.2 Remote Connectivities

3.1.2 PROFIBUS isPro FDI Communication Server

The PROFIBUS isPro FDI Communication Server allows connections to PROFIBUS
devices by using a supported local PROFIBUS modem.
For connectivity to I/O system components, the required Device Packages are
mandatory. For more information, please refer to 2PAA113895 Field Information
Manager Release Notes.

Supported PROFIBUS modems

Field Information Manager (FIM) contains modem drivers and is already prepared to
support PROFIBUS modems listed below:
• Thorsis isPro USBx12
• Thorsis isPro USBv4
• Thorsis isNet DP - PROFIBUS DP Ethernet Gateway with Thorsis isNet Lite -
Ethernet Communication Module

3.1.3 UMC USB Serial Communication Server

The UMC USB Serial Communication Servers allows connections to UMC field devices
using a supported local UMC modem.

3.2 Remote Connectivities

Remote Communication Servers allow connections to decentralized network architectures.

3.2.1 ABB FIM Bridge 800xA

The Field Information Manager supports a connection to ABB Ability™ System 800xA
by using the FIM Bridge 800xA.
For connectivity to I/O system components, the required Device Packages are
mandatory. For more information, please refer to 2PAA113895 Field Information
Manager Release Notes.

3.2.2 ABB FIM Bridge PROFINET

Field Information Manager supports connections to PROFINET devices by using the
FIM Bridge PROFINET.

2PAA117322V22 A 14
3 Connectivities
3.3 ABB Ability™ Support

Multiple communication paths to a PROFINET network

Field Information Manager supports topologies with several alternatives to access a
single PROFINET Network. For example, a topology can contain a FIM Bridge 800xA
with multiple AC800M controllers, each connected to the same PROFINET network via
the CI871 communication interface. Furthermore, the topology can contain a FIM Bridge
PROFINET with access to the same PROFINET network.
In this case, the devices found in the PROFINET network can appear multiple times in
the topology tree. The Address & Details dialog for the devices in the network and all
child devices will show all alternative communication paths.
For communication, FIM will choose the communication path with the smallest number
of nodes.

3.2.3 ABB FIM Bridge OPC-UA

Field Information Manager supports connections to OPC-UA devices by using the FIM
Bridge OPC-UA.
FIM Bridge OPC-UA requires configuration before being able to detect connected devices.

3.2.4 Thorsis isNet Pro FDI Communication Server

Field Information Manager supports connections to PROFIBUS devices by using the
Thorsis isNet Pro FDI Communication Server.

3.2.5 Thorsis isNet HART FDI Communication Server

Field Information Manager supports connections to HART field devices by using the
Thorsis isNet HART FDI Communication Server.

3.2.6 Thorsis HART-IP FDI Communication Server

Field Information Manager supports connections to HART-IP servers by using the generic
Thorsis isNet HART-IP FDI Communication Server. The HART-IP servers then allow
connections to (wireless) HART field devices.

3.3 ABB Ability™ Support

The Field Information Manager contains a OPC-UA server that is supporting ABB Ability™.
Please get in contact with your local ABB service partner for more information.

2PAA117322V22 A 15
2PAA117322V22 A 16
4 Basic Concept
4.1 Overview

4 Basic Concept

4.1 Overview

1. Tools Menu button

2. Top menu, consisting of links to add a new Communication Server and
maximize/minimize the Topology Tree
3. Communication Server Tile
4. Context Menu, available with a click on [...] icon of the Device Tile
5. Easy Access Wizard
6. Device Tile representing a field device

2PAA117322V22 A 17
4 Basic Concept
4.2 Device representation – Device Tile

7. Info Center
8. User settings information

4.2 Device representation – Device Tile

A physical field device is represented as a graphical object called Device Tile. The most
left side of the Device Tile shows the parent information, like the COM port that is used
by the HART modem or the channel number if connected to an IO board.

Right beside the channel information the device status is shown indicating how the
connection to the device behaves.

Status Ok: The device is connected and accessible.

Status Bad: The device is not reachable.

Not assigned: This is an Offline Dataset without a physical device.

This icon is used to indicate a Template.

This icon is used to indicate a Device Package that is based on an FDI Device
Package

This icon is used to indicate a Device Package that is based on a fm8 EDD file

2PAA117322V22 A 18
4 Basic Concept
4.3 Add and remove a Communication Server

The device views and device functions are available on a Context Menu which will appear
after a click on the Device Tile menu button.

The Device Tile object contains a preview functionality that provides access to the current
open views which are belonging to the Device Tile. As soon as a view is open, the Device
Tile object contains an icon to the right showing that open views exist. The user can click
on that icon and gets access to the preview area.

4.3 Add and remove a Communication Server

To establish a connection, a new Communication Server must be added.
Click the "Add Server" button within the top menu (see Overview) to open the "Add
Communication Server" dialog. Within this dialog, the available Communication Servers
are listed, grouped in local and remote types. Each of them has the following properties:
• Name: By default the same as the Communication Server type, but can be changed
by the user. The name is used as the Communication Server's identifier within FIM.
• IP Address (remote only): IP address of the network node running the Connectivity
Service, must be entered by the user.
• Port (remote only): By default the port number of the Connectivity Service running
on the network node, can be changed by the user.
Select the required Communication Server type(s), change the properties if required and
click the "Add" button.
Each new Communication Server appears as a Device Tile (see Device representation
– Device Tile) within the Topology Tree. The Hardware Scan functionality is available
as an option in the Device Tile Context Menu.
To remove an existing Communication Server, open the Context Menu of the
Communication Server via the Device Tile and select "DELETE".

2PAA117322V22 A 19
4 Basic Concept
4.4 Communication Server Settings

4.4 Communication Server Settings

The contains Communication Servers which are used for the communication between
the FIM software and other software or hardware, like a HART modem. The
Communication Server settings are available via the Context Menu of the corresponding
Device Tile.
Example for the HART Communication Server: Use the [...] icon and get access to the
server settings.

4.5 Tag Mapping

FIM contains a functionality that automatically synchronizes the names that are usually
required to identify a field device. This functionality is part of the Synchronizations options
which are available in Projects Tools Menu.
The following names are available in FIM:
• Device Tag: The identifier name that exists in the parameter set of the physical
device
• Device Name: The name of the Device Tile object in FIM
• Offline Dataset Tag: The identifier name that exists in the parameter set of the offline
database
HART 5 standardization supports TAG parameter names limited to 8 characters, but
usually the TAG concept of the projects requires more than 8 characters. HART 7
standardization contains a LONG TAG parameter that is limited to 32 characters, but at
the moment the penetration of HART 7 devices in projects is very rare. Due to that some
projects are using as well the MESSAGE parameter of HART 5 devices as the identifier.
This parameter is limited to 32 characters.
FIM is supporting the use of as well the TAG, LONG TAG, or MESSAGE parameter as
the tag identifier. In the FIM Project options (accessible via the Tools Menu) the
Synchronization area specifies which device parameter should be used for the tag
identifier. As soon as enabled any change on the Device Name in FIM (the name of the
Device Tile object) will automatically sync the tag identifier of the physical device and
corresponding offline dataset in FIM.

2PAA117322V22 A 20
4 Basic Concept
4.6 Bulk Operations

4.6 Bulk Operations

The FIM supports several kind of bulk operations, like uploading the device configurations
from several devices in bulk, or removing several Device Packages in bulk.
The Configurations Tool and the Device Catalog are supporting bulk operations. First
please check mark one or several Device Tiles via the checkbox of the first column in
the view. Then please call up the Context Menu of any of the check marked Device Tiles.
The upcoming menu is called Bulk Context Menu. From here any started operation will
run for all the check marked Device Tiles in bulk.

Each started bulk operation is documented in the FIM Info Center.

4.7 Managing Projects

By default, a project is created when you start the Field Information Manager for the first
time after a fresh installation. A Field Information Manager project saves all the contained
offline datasets, the offline templates and the content of the Topology View and tree.
The Device Catalog with Device Packages, Fimlets and EDD files, is used by all projects
which are available on the Field Information Manager client, but is also saved in the
project file (.fimprj) as soon as a project is exported.
With a Field Information Manager project you can:
• Continue work on a project at a later time
• Switch between projects if you are working on several systems with the same FIM
computer client
• Share the project with others and move it to another computer
• Create project templates with general settings, Device Packages and template
datasets, and share the templates with others
The Field Information Manager project management is available via Projects Tools Menu.

2PAA117322V22 A 21
4 Basic Concept
4.8 Info Center

4.8 Info Center

The FIM reports activities in the Info Center, like running bulk activities. The Info Center
is an area that is usually temporary on screen and disappears automatically. The Info
Center is available on the left bottom part of the tool frame. The user has the option to
pin the Info Center to be able to stay on the screen permanently.

4.9 License Handling

Usually the FIM is available as one setup file containing all the available functionalities
no matter which edition of FIM is used. But it might be that for the FIM connection to
other systems, like ABB Ability™ System 800xA, additional setup files are required.
The Device Window Edition of FIM enables a point-to-point connection with a HART
modem and a physical HART device. This edition is active after installing the FIM. The
edition is free of charge and mainly used to get started.
Any other edition of FIM requires a valid license file to enable. Please import the license
file via drag & drop into the FIM main frame.
Please find more information about the different license options on
http://www.abb.com/fieldinfo

4.10 Language Support and Language Packs

In the Language Options the user can change the language of the FIM tools texts and
device views. The device views are based on the Device Package information. If the
Device Package does not contain the selected language then the default language will
be used for the device views. The default language is English language.
A set of the most used languages is part of the FIM installation and the user can select
one of these languages. But the FIM installation contains only English and German
language completely. All the other selectable languages require a Language Pack to
ensure that all the tool texts are displayed in that language. The released Language
Packs are available via http://www.abb.com/fieldinfo.
A Language Pack can be installed via drag & drop of the Language Pack file into the
tool. An overview of the already installed Language Packs is available via FIM Options
- Info page.

2PAA117322V22 A 22
4 Basic Concept
4.11 Easy Access Wizard

4.11 Easy Access Wizard

The Easy Access Wizard is a navigation area in FIM appearing to the right. The user
can pin the Easy Access Wizard if required.

Click on the Easy Access Wizard icon to open up the wizard.

Favorites
The favorites in FIM are part of the Easy Access Wizard and provide an easy access to
device parameter and device functions.
Three kinds of favorite categories are available.

Favorite The user specifies a favorite on device views via the [...] button that is
positioned close to the parameter name
Frequently The FIM manages this list based on the usage of device parameter
Used
Last Used The FIM records the changes on device parameter and calculates a
list of parameter that have been used last

Each favorite shows an icon in front of the favorite name that specifies either if the favorite
is a device parameter or a device menu / function.

This icon defines a device parameter

This icon is used for several elements, like groups, tabs, etc.

Offline Vs Online Favorites

The FIM supports favorites for connected physical devices as well as for offline device
configurations. As soon as the user works with a Device View the FIM will automatically
switch to the favorites related to that view. However, the user also can select the Favorites
Online or Offline section manually if required.

2PAA117322V22 A 23
4 Basic Concept
4.12 Optimized Touch Handling

4.12 Optimized Touch Handling

The FIM supports the user when working with touchable devices, like touch pads or
touch monitors. Several controls will appear in an optimized design as soon as the FIM
enables optimized touch handling. The user can set the optimized touch handling via
the "hand" icon.

4.13 Tooltips and Tooltip-Picker

Tooltips are mostly required when working with Device Views, like Device Settings for
example. The general Tooltip is designed to show how to use the mouse pointer which
does not work on touch devices. The Tooltip-Picker is an element which will show the
Tooltip. The picker is available on the upper right area of the FIM main frame. The user
can move the picker control to an element in the tool and as soon as the picker hits the
element the FIM will show the associated Tooltip.

2PAA117322V22 A 24
5 Device Management
5.1 Topology View

5 Device Management

5.1 Topology View

The Topology View is part of the Tools Menu. Use the Topology View to navigate through
the physical/logical network structure and to access devices. The Topology View consists
of a tree navigation element to the left, and an area appearing to the right which shows
the content of the selected tree object. The handling of the Topology View is very much
similar to the handling of the Windows Explorer.

5.2 Configurations View

The Configurations View is part of the Tools Menu. Use the Configurations View to access
to all available configurations in a flat list, like Device Dataset configurations, Offline
Dataset configurations and Templates.

5.3 Device Identification and Scanning

The Topology Tree shows the general progress icon left beside a Tile object in the tree
as soon as the scanning runs. In addition the Tooltip of the Tile object contains the
scanning status information.

5.3.1 Local Communication Servers

Unless otherwise stated, Local Communication Servers support Auto Scanning for
modems. The Auto Scanning will identify the reachable physical devices automatically
without any user interaction.
As soon as the Auto Scanning has identified a field device the Topology View will show
the corresponding Device Tile. As soon as the concept of HART communication is slow
the Auto Scanning will pause as soon as the user has opened a device view. In that
case no further device is identified if just connected. After closing all views the Auto
Scanning will continue the scanning for new devices again.

2PAA117322V22 A 25
5 Device Management
5.4 Device Views

The Auto Scanning will remove a disconnected field device automatically from the
topology. Disconnected devices cannot be removed as long as a device view is open
and those devices will be marked with the Bad status icon in the Device Tile.

5.3.2 Remote Communication Servers

Unless otherwise stated, Remote Communication Servers require a manual scan to
identify new hardware like controllers, modules and field devices.
The Scan is supported via the Context Menu of the supporting objects, like Communication
Server or Gateway Tile object.

5.4 Device Views

Device Views are available for physically connected devices or for offline Device Datasets.
The Device View header contains the word –DEVICE– if the view connects to a physical
device, or the view header contains the work –OFFLINE– if the view connects to an
Offline Dataset.
Most of the device views provide status information in front of the input element. The
tooltip of these elements provides more details about the status. The following status
information is available:

LOADING: The value is loading.

MODIFIED: The value was modified but not transferred so far.

WARNING: Several warnings exist explained by the tool tip text.

ALARM: Several alarms exist explained by the tool tip text.

5.5 Device Bar

Any device containing open views will appear in the Device Bar. From the Device Bar
the user can quickly access the Device Tile and open other views. As soon as all views
are closed the corresponding device will disappear from the Device Bar.
The Device Bar location is on top of the FIM frame. Any blue selected Device Tile
appearing in the Device Bar indicates that a corresponding device view is currently
selected and owns the focus.

2PAA117322V22 A 26
5 Device Management
5.6 Multiple Device Views

5.6 Multiple Device Views

A Multiple Device View consists of several views and can easily shaped with a drag &
drop of a “normal” view into another view. This version of FIM support multiple views
that consist of 4 single views. The user can drag & drop open views from the preview
area into the currently visible view to create a multiple view. Inside a multiple view each
single view can be dragged & dropped to a different position in the view.

5.7 Device Configuration

The right menu items of the Context Menu offer the FDI defined views for device
configuration - DEVICE SETTINGS, device diagnostic - DIAGNOSTIC and device
operation - OPERATE. These menus are only available as long as a device is connected
and reachable.

2PAA117322V22 A 27
5 Device Management
5.8 Offline Configuration

5.8 Offline Configuration

The FIM contains a database that stores the device configurations in Offline Datasets.
The user can change the device settings of an Offline Dataset. Offline Datasets which
are not connected to a device are accessible via the Configuration Tool. The user can
access the offline configuration with the Context Menu item OFFLINE.

5.9 Upload / Download Configurations

The user can upload the device configuration from the physical device into the Offline
Dataset or download the offline configuration into the physical device via accessing the
UPLOAD DOWNLOAD item of the ContextMenu.

5.10 Templates
The FIM supports device configuration templates that are used to prepare other datasets
with the template content. Each template can be exported or imported as a file via the
Configuration Tool. The import of template files is also supported via drag & drop.

5.11 Compare Datasets

The Compare Datasets function offers the possibility to compare:
• The offline and online datasets of a field device.
• The online datasets of different field devices.
• The offline datasets of different field devices or templates.
The function can be started via the context menu – MORE – COMPARE. Bulk operations
are supported, too.

2PAA117322V22 A 28
5 Device Management
5.12 Import of Device Engineering Data

The comparison leads to the following results:

• Equal: All parameters that exist in both datasets are equal. If the datasets contain
different parameters, the subset of the parameters is equal. This is often the case
when online and offline datasets are compared.
• Mismatch: at least one compared parameter contains different values. The user can
take over parameter values from one dataset to the other by using the “<” and “>”
buttons.
• Not comparable: The datasets cannot be compared by FIM. Most likely the
parameters of the datasets does not match each other. This can happen if completely
different field devices will be compared.

5.12 Import of Device Engineering Data

Field Information Manager supports the import of Device Engineering Data for various
use cases. The Device Engineering Data can be imported via Tools Menu - PROJECTS
and contains values of dedicated parameters or settings for one or more field devices.

5.12.1 File Format

Device Engineering Data is defined as a comma separated list (CSV file format) and
supports two formats for different use cases.

2PAA117322V22 A 29
5 Device Management
5.12 Import of Device Engineering Data

It can be converted e.g. from an export file created by the ABB Ethernet I/O Wizard. For
the import, Field Information Manager uses the column separators and number formats
specified in the regional settings of Windows. Example files can be downloaded from
the FIM website.

Basic Format
The file to be imported shall contain a table with at least the following column headers:
• Tag
• Process variable Lower range value
• Process variable Upper range value
• Process variable Unit
Values in the column Process variable Unit must be one of the values defined by HART
EDD specification.

Extended Format
The file to be imported shall contain a table with at least the following column headers:
• Device Tag
• Scaling-Min
• Scaling-Max
• Signal Unit
• Alarm HH
• Alarm H
• Alarm L
• Alarm LL
• Underrange Level
• Overrange Level
Values in the column Signal Unit must be one of the values defined by HART EDD
specification.

5.12.2 Comparison with parameters of connected field devices

Parameters from imported Device Engineering Data in Basic or Extended Format can
be compared with the parameters of connected field devices.

2PAA117322V22 A 30
5 Device Management
5.12 Import of Device Engineering Data

Once imported, the compare dialog provides a powerful option to find differences between
the imported values and the actual configuration of the device with a matching tag.
To compare imported values with online values, choose the “Compare imported Device
Parameters” option which is available in Tools Menu - PROJECTS.
The button “Start comparison with field devices” will open a compare dialog (see chapter
5.11, Compare Datasets).
If the parameter names of Device Engineering Data and field device cannot be
mapped, a configuration of Common Names is required before starting the
comparison. For more information, please refer to chapter 6.8, Common Names.

5.12.3 Loop Check based on imported Device Engineering Data

Settings from imported Device Engineering Data in Extended Format can be used to
preconfigure channels of a new Loop Check View. Channels not specified in the imported
Device Engineering Data are configured according to Default Loop Check Settings.
Test of Alarm Limits is only possible with defined values in imported Device Engineering
Data. For more information, please refer to chapter 8, Loop Check.

2PAA117322V22 A 31
2PAA117322V22 A 32
6 Device Package Handling
6.1 Device Catalog

6 Device Package Handling

6.1 Device Catalog

The Device Catalog is part of the Tools Menu and this is the place where to handle the
Device Packages and fm8 EDD files. The user can import new Device Packages via
drag & drop of the Device Package file into the tool. Each Device Package is represented
as a Device Package Tile object. The Device Package information and functionality is
available on a Context Menu that will appear after a click on the Tile.
Please find the set of ABB Device Packages by using this link
http://new.abb.com/control-systems/fieldbus-solutions/fim/ABB-device-packages

6.2 Device Package and Package Assignment

The FIM requires FDI Device Packages or EDD files in fm8 format to establish a
connection to a device. The packages are stored in the Device Catalog which is available
via the Tools Menu. The user can import new packages or EDD files via drag & drop.
For new identified devices FIM will automatically use the best available package, but the
user can replace the package to another one if needed.
Please find the set of ABB Device Packages by using this link
http://new.abb.com/control-systems/fieldbus-solutions/fim/ABB-device-packages

2PAA117322V22 A 33
6 Device Package Handling
6.3 HART Generic Device Package

Used for Specific Device Package: The device vendor has designed this FDI
Package.
Used for Generic Device Package: An FDI Package usually designed by ABB.
The package supports a reduced set of functions and is not as good as a Specific
Device Package.
For HART: The Generic Device Package supports Universal Commands and
Common Practice Commands.
Used for EDD fm8 file.
Please note: The EDD fm8 format has been used for many years and was
typically designed by the device vendor. Compared to an FDI package the fm8
EDD is good to use for online communications to the device, but might be limited
in upload / download functionality and offline dataset handling. Very old EDDs
might end up in communications errors as well.

6.3 HART Generic Device Package

The Generic Device Package supports HART Universal- and Common Practice
Commands. The package is prepared to get used for each HART device which is available
on the market. However, when available, a Device Package supplied by the
instrumentation vendor should be used.
Please find the set of ABB Device Packages by using this link
http://new.abb.com/control-systems/fieldbus-solutions/fim/ABB-device-packages

6.4 Device Integration by GSDML

Field Information Manager supports the integration of devices by GSDML instead of
using an FDI package.
Due to the limited information available in GSDML, the device views are very generic
and provide information only in a flat structure. The device functionality in FIM is limited,
i.e. Device Views are only available in read-only mode and Offline Functionality is not
given.
The GSDML used to integrate devices can be replaced by a suitable FDI package
once it is available. When detecting a new device, an existing FDI package is always
preferred over the GSDML for extended device functionality.

2PAA117322V22 A 34
6 Device Package Handling
6.5 ABB Repository

6.5 ABB Repository

The ABB Repository is a cloud-based storage, which contains ABB FDI Device Packages,
EDDs and definition files for ABB communication hardware. If an internet connection is
available, then FIM checks the ABB Repository for updated contents when the application
starts.
All FDI Device Packages of the ABB Repository will be shown in the Device Catalog of
FIM. A special cloud package icon indicates that the FDI Device Package is available
in the ABB Repository, but currently not downloaded into FIM. In order to use the FDI
Device Packages from the ABB Repository the user has to download the Package via
the Context Menu – DOWNLOAD.
It is also possible to exchange the used FDI Device Package for each field device. Via
the Context Menu – MORE – REPLACE DEVICE PACKAGE also the FDI Device
Packages of the ABB Repository will be offered. If the user selects a FDI Device Package
of the cloud, then it will be downloaded and assigned automatically.

6.6 FieldComm Group Repository

The FieldComm Group Repository (FCG Repository) is a cloud-based storage, which
contains FDI Device Packages and other files for communication hardware of various
manufacturers.
The FCG Repository is a licensed feature and can be used like the ABB Repository.

2PAA117322V22 A 35
6 Device Package Handling
6.7 Offline Repository

6.7 Offline Repository

The Offline Repository can be used to create an offline collection of FDI Device Packages,
EDDs and definition files for communication hardware.
It is created via the "Offline Repository Handling" mode, that can be entered within the
top menu of Device Catalog. All cloud-based Repositories serve as input for selecting
the required Device Packages within this mode to then create an Offline Repository
following the instructions within FIM. After creation, the new Offline Repository is stored
in a local file for further use, e.g. to move it to another machine which has no connection
to the cloud-based Repositories.
The created Offline Repository can be added to FIM in Tools Menu – OPTIONS –
REPOSITORY SETTINGS by referencing the Offline Repository file. It is then included
automatically in the next update of the Device Catalog.

The Device Catalog only displays elements of included Offline Repositories for which
a suitable FIM license exists.

2PAA117322V22 A 36
 6 Device Package Handling
6.8 Common Names

n Manager FIM ABB FDI

Repository
FieldComm Group
FDI + EDD Repository

Case
Online Environment
with Internet Connection (DMZ)
FCG
FIM in Device Window „Free“ Edition FIM Client in
(no license required) Device Window
“Free” Edition
Create Offline Repository based on
data from Online Repositories
DMZ
Transfer Offline Repository File

Offline
Repository

Engineering Client FIM Client

Plant-Network

Offline Environment
without Internet Connection

FIM Production Environment

Control-Network
Import Offline Repository
created in Online Environment Controller
Level

PROFIBUS / PROFINET
I/O Level …
… …

6.8 CONFIDENTIAL
Common Names
Common Names are used to assign external generic names to internal Device Package
items with specific names. After successful assignment, the respective Device Package
items can also be accessed via their Common Names for further use.
The external generic names are based on the NAMUR Standard Namespace.
The assignment of a Common Name to a Device Package item is done in the respective
Device View, similar to favorite handling. Within the context menu of each Device Package
item, a Common Name can be assigned or removed. Common Names are displayed
and accessible with their assignment status in the Shortcuts menu.
The configuration of Common Names for a Device Package can be exported and imported
via the Device Catalog.

2PAA117322V22 A 37
2PAA117322V22 A 38
7 Dashboard
7.1 Diagrams

7 Dashboard

FIM provides an overview of field device information in the form of a Dashboard. The
Dashboard displays the following information:
• Modified device parameters through online EDD menus
• Modified device parameters using a download
• Change in device diagnosis information
• Change in device communication state
• Messages entered by the user
Information can be displayed for a dedicated device, a user-selected list of devices, or
all devices contained in a project.
The Dashboard can be opened through Tools Menu – DASHBOARD, or via MORE –
DASHBOARD within the Device Tile Context Menu.

7.1 Diagrams
Diagrams show data gathered from a device. Data can be filtered using Field Device
Tag, Field Device Type and Time Range. Elements to be displayed can be enabled or
disabled in the legends.
The events covered by the Audit Trail diagram are:
• Communication State
• Field Device Diagnosis
• Send to Field Device
• Read from Field Device
• Parameter Change
• User Message
• Loop Check

2PAA117322V22 A 39
7 Dashboard
7.2 Details Dashboard

• Warning
• Error
The Device Diagnosis diagram displays the number of devices with a specific NE107
state over time.
The Device Communication diagram displays the number of devices with a communication
state good or bad over time.

7.2 Details Dashboard

Dashboard diagrams can be opened in a detailed view within the same window, a new
window, or in a splitted window. The Details Dashboard contains a table with appropriate
events. Filter settings are initially inherited from the Overview Dashboard and can be
changed.

2PAA117322V22 A 40
8 Loop Check
8.1 Loop Check Settings

8 Loop Check

Field Information Manager supports Loop Check of channels and connected field devices
in conjunction with ABB Ability™ System 800xA.
It can be started for a dedicated channel, a user-selected list of channels, or all channels
contained in a project.
The Loop Check can be opened through Tools Menu – LOOP CHECK, or via MORE –
LOOP CHECK within the Device Tile Context Menu.
The Loop Check view provides an overview about the status of displayed channels, while
the detailed grid can be filtered and used to select and configure channels for Loop
Check.
After execution, details about the Loop Check can be displayed for each channel.
The results of the Loop Check can be exported to CSV and PDF file format for further
use.
The Audit Trail diagram of the Dashboard includes each executed Loop Check for a
channel with a connected field device.

8.1 Loop Check Settings

For configuration of Loop Check, the following settings are available for each channel
with a detected field device:
• Test Routine: Defines the test points to be checked during Loop Check.
• Tolerance: Defines the allowed relative difference (in percentage) between expected
and measured value of a test point, always in relation to the complete signal range.
• Underrange and Overrange: Test of Underrange and Overrange can be enabled or
disabled by default for input channels. If enabled, the defined default values are
used during Loop Check, if not overwritten by imported Device Engineering Data.

2PAA117322V22 A 41
8 Loop Check
8.2 Loop Check Types

• Loop Check Type: Choose between "Automatic with Authorization" and

"Semi-Automatic with Authorization" for output channels.
• Alarm Limits: Test of Alarm Limits can be enabled or disabled by default. If enabled,
the Alarm Limits defined in the imported Device Engineering Data are used during
Loop Check.
The default values of all of these settings can be defined in Tools Menu – PROJECTS
– LOOP CHECK SETTINGS. These default values are always applied to all channels
when opening a new Loop Check View.
If Device Engineering Data has been imported and contains setting definitions for
a specific channel, these settings are used for the channel instead of the default
settings.
Within an open Loop Check View, the Loop Check settings can be changed manually
per channel or for a bulk selection.

8.2 Loop Check Types

Depending on the characteristics of the respective channel, one of the following Loop
Check Types is used.

8.2.1 Automatic Loop Check

Automatic Loop Check is only applicable for channels with connected field device and
Signal Direction "In".
The Loop Check is performed automatically without any required user interaction, including
all test points for the configured test routine, Underrange and Overrange and Alarm
Limits. For each of the test points, the measured value is checked against the expected
value automatically, leading to a result for the respective test point.

8.2.2 Automatic Loop Check with Authorization

Automatic Loop Check with Authorization is only applicable for channels with connected
field device and Signal Direction "Out".
The Loop Check of such channels (and the connected field devices) can cause moving
parts within the system, therefore the user has to enter his credentials before each
execution in order to authorize it.
After successful authorization, the Loop Check is performed automatically without any
further required user interaction, including all test points for the configured test routine
and Alarm Limits. For each of the test points, the measured value is checked against
the expected value automatically, leading to a result for the respective test point.

2PAA117322V22 A 42
8 Loop Check
8.3 Loop Check Scope

8.2.3 Semi-Automatic Loop Check with Authorization

Semi-Automatic Loop Check with Authorization is only applicable for channels with
connected field device and Signal Direction "Out" and represents an alternative to
Automatic with Authorization.
The Loop Check is performed step by step, including all test points for the configured
test routine and Alarm Limits. For each of the test points, the user has to check the value
manually against the expected value and enter a result for the respective test point.

8.2.4 Manual Loop Check

Manual Loop Check is applicable for channels without a connected field device.
The Loop Check is performed manually with a documentation dialog, in which the user
can enter a result and a remark in text form.

8.3 Loop Check Scope

8.3.1 Test Routine
The Test Routine represents the basic Loop Check by validating a number of test points.
The number of test points depends on the selected Test Routine:
• 5-Point Test: Signal range is tested in one direction from lower range to upper range
value (4, 8, 12, 16, 20 mA).
• 9-Point Test: Signal range is tested in both directions from lower range to upper
range value and back (4, 8, 12, 16, 20, 16, 12, 8, 4 mA).
The measured channel value received from the system is compared against the expected
value. Only if the measured deviation is within the defined tolerance, the test point is
rated as "Passed". Otherwise, it is rated as "Failed".

8.3.2 Underrange and Overrange

The check of Underrange and Overrange represents the validation of correct status
indication within the system for values below and above the defined signal range.

The check of Underrange and Overrange is only applicable for channels with
connected field device and Signal Direction "In".

Underrange and Overrange test values can be specified in the imported Device
Engineering Data or in the Default Loop Check Settings.

2PAA117322V22 A 43
8 Loop Check
8.4 Loop Check States

If available, the channel status received from the system is checked for correct status
indication of Underrange and Overrange. If set correctly, the test point is rated as
"Passed". Otherwise, it is rated as "Failed". Only if no channel status is received from
the system, the measured channel value is compared against the expected value as in
the normal Test Routine.
To ensure that the channel status is set correctly, the Underrange value is tested
with 0.02 mA below and the Overrange value is tested with 0.02 mA above the
defined values.

8.3.3 Alarm Limits

The check of Alarm Limits represents the validation of correct alarm indication for defined
Alarm Limits within the system.

Alarm Limits have to be defined in the imported Device Engineering Data.

Field Information Manager supports the Alarm Limits High-High (HH), High (H), Low (L)
and Low-Low (LL). Each of them is tested in hysteresis, resulting in 3 test points for each
alarm (No Alarm, Coming Alarm and Going Alarm).
The hysteresis ensures a correct alarm behavior. The alarm flags received from the
system are checked for correct alarm indication, i.e. whether the respective alarm is set
in the system. If set correctly, the test point is rated as "Passed". Otherwise, it is rated
as "Failed".
The paths to the alarm flags are very specific to the used libraries within the system
application. If alarm flags cannot be detected by Loop Check, further configuration
is required. For more information, please refer to the Field Information Manager
website.

8.4 Loop Check States

The Loop Check Status of each channel is indicated by one of the following states:

Status Description
Passed All test points of the selected Loop Check Scope are passed.
Failed One or more test points of the selected Loop Check Scope
are failed.
Not available Channel or connected field device is not reachable or does
not support required functionality.

2PAA117322V22 A 44
8 Loop Check
8.5 Additional Information

Status Description
Not used Channel is not used (can only be documented in manual
Loop Check).
In Execution Loop Check is currently in execution.
In Queue Loop Check is currently in queue and will be executed soon.
Untested Channel is untested without any existing Loop Check result.

Results from previous Loop Check are indicated by a history icon.

8.5 Additional Information

Loop Check represents a functionality that is bound strongly to the used system
connectivity.
In order to pass Loop Check, the complete communication loop from the used system
to the field device and back needs to be configured correctly. If available, the imported
and used Device Engineering Data has to be taken into account as well.
A failing Loop Check indicates a mismatch between the configuration within the used
system, the field device and the Device Engineering Data.

Loop Check in Field Information Manager supports only positive linear signal curves.

For more information about configuration prerequisites to pass Loop Check, please refer
to the Field Information Manager website.

2PAA117322V22 A 45
2PAA117322V22 A 46
9 Troubleshooting
9.1 Contact ABB support for troubleshooting

9 Troubleshooting

In addition to the following topics please watch the FAQ area on

http://new.abb.com/control-systems/fieldbus-solutions/fim/faq

9.1 Contact ABB support for troubleshooting

Use this option if you request the support of an ABB expert. The FIM will automatically
generate a bunch of log files containing all information for troubleshooting.
1. Open the Options of the FIM Tools Menu.
2. Select the option TECHNICAL SUPPORT.
3. On the view appearing to the right please read the describing steps and select the
START button.

9.2 Tool shutdown even when activities are ongoing

The user can stop the FIM even when activities are ongoing, such as device modal dialog
requires a user input, or a bulk operation is running.
Usually the FIM is waiting until all activities have been ended before closing itself.
However, there might be situation that the user needs to stop the FIM right now.
Please note that a hard stop of FIM might cause device problems as soon as any ongoing
communication is interrupted and the device might remain in a status being inoperable.
1. Assume the user has tried to stop a User Interface Plugin with a click on the ABORT
button, but the User Interface Plugin remains open for a few minutes. Now the user
decides to interrupt FIM.
2. The user clicks the FIM close button to stop the tool.
3. FIM generates a message explaining that there are modal dialogs open which
prevent the tool from closing.
4. The user accepts that message and clicks the FIM close button a second time.

2PAA117322V22 A 47
9 Troubleshooting
9.3 Device is not identified by the Auto Scanning - HART modem

5. FIM generates another message explaining that the user can force the tool for
closing.
6. The user accepts that message and selects the YES button.
7. FIM has been stopped.

9.3 Device is not identified by the Auto Scanning - HART

modem
Please use the Context Menu item DIAGNOSTIC for the HART Communication Server
and start a diagnostic scan for the com port where the HART modem is connected to.
The scan will run in multi drop mode and will go through all possible channels and baud
rates, and the scan will report the identified field devices right now in the result list.
If the diagnostic scan is not able to identify the field device, then please validate that the
HART modem connects successfully to the computer node, and that the device connects
to the HART modem in a proper way. In most cases a wrong or defect hardware setup
between computer node, HART modem and device is the problem cause.
If the problem still persists, then please get in contact with ABB technical support.
In addition, the FAQ section "Communication" shows examples of the wirering between
HART modem and field device for sensors and actuators. The FAQ section is available
via this link:
http://new.abb.com/control-systems/fieldbus-solutions/fim/faq

9.4 Installation or Un-installation fails

Please refer the FAQ describing Installation Un-installation on
http://new.abb.com/control-systems/fieldbus-solutions/fim/faq

2PAA117322V22 A 48
9 Troubleshooting
9.5 License fails

9.5 License fails

The FIM license file is linked to a Machine ID. The Machine ID is a unique identification
representing the physical address of a network adapter in the Windows Operating System.
Depending on the computer hardware the number of network adapters are different. For
example, a laptop computer sitting in a docking station contains more network adapters
as a touch pad. It is important that the linked Machine ID of the license file and the
corresponding network adapter has to be enabled.
Some computer hardware disables the network adapters automatically if not used. This
is usually caused by the power options of that computer node. A disabled network adapter
is no longer visible in the Microsoft Operating System and therefore not visible for FIM
either. If a FIM license is linked to a Machine ID where the corresponding network adapter
has been disabled, then the FIM will signalize that the license fails.
If FIM reports a license error, or the license file might not get loaded because FIM is
saying that the file is not valid, then please compare the license file Machine ID with the
available Machine IDs of your computer. The FIM options page LICENSE HANDLING
provides such information.
For further information please watch the FAQ License Handling on
http://new.abb.com/control-systems/fieldbus-solutions/fim/faq

2PAA117322V22 A 49
2PAA117322V22 A 50
www.abb.com/800xA 800xA is a registered or pending trademark We reserve all rights to this document and
of ABB. All rights to other trademarks reside the items and images it contains. The
www.abb.com/controlsystems with their respective owners. reproduction, disclosure to third parties or
the use of the content of this document –
We reserve the right to make technical including parts thereof – are prohibited
changes to the products or modify the without ABB’s prior written permission.
2PAA117322V22 A

contents of this document without prior

notice. With regard to purchase orders, the Copyright © 2021 ABB.
agreed particulars shall prevail. ABB does All rights reserved.
not assume any responsibility for any errors
or incomplete information in this document.