ifak system is Pro DP/PA Link DTM User manual

TECHNOLOGIEN MIT
VORSPRUNG
is Pro DP/PA Link DTM
User Manual

Copyright © ifak system GmbH 2004, all rights reserved.
No part of this work may be reproduced in any form or by any means -
graphic, electronic, or mechanical, including photocopying, recording,
taping or storage in an information retrieval system - without prior
written permission of the ifak system GmbH.
Information in this manual is subject to change without notice and does
not represent a commitment of the ifak system GmbH.
ifak system GmbH
Oststrasse 18
D-39114 Magdeburg (Germany)
www.ifak-system.com
Tel.: +49 - 391 - 544 563 - 0
Fax: +49 - 391 - 544 563 - 99
Email: [e-mail]

is Pro DP/PA Link DTM Contents
ifak system GmbH I
Contents
Chapter 1: Introduction
Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Our Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Chapter 2: FDT – A Brief Introduction
FDT-Specification Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Object Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Component interaction . . . . . . . . . . . . . . . . . . . . . . . . . 7
Summary: Objects in the FDT concept . . . . . . . . . . . . . . . . 9
DeviceDTM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
ActiveX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
CommDTM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
CommChannel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Chapter 3: Gateway DTM is Pro DP/PA Link DTM
Configuration in Offline Mode . . . . . . . . . . . . . . . . . . . . . . . . 12
Change DeviceDTM Address . . . . . . . . . . . . . . . . . . . 12
Configuration in Online Mode . . . . . . . . . . . . . . . . . . . . . . . . 13
Device List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Slave Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Change Slave Address . . . . . . . . . . . . . . . . . . . . . . . . 16

is Pro DP/PA Link DTM
II ifak system GmbH

is Pro DP/PA Link DTM SoftwareInstallation
ifak system GmbH 1
CHAPTER 1:
INTRODUCTION
The GatewayDTM is Pro DP/PA Link DTM allows the integration
of a Siemens Profibus DP/PA Link device into any FDT Engi-
neering and Configuration Tool (PACTware, FieldCare or other
FDT Containers). So the engineering and commissioning task for
a remote device can be handled from one central workplace.
The GatewayDTM can be used together with the Communica-
tionDTM is Pro FDT and a Profibus interface (USB and PCI) of
ifak system or with a communication interface and FDT software
of any manufacturer.
Software Installation
The operation of the GatewayDTM requires the correct installa-
tion of a Profibus Master interface and its CommunicationDTM.
The delivered software is Pro DP/PA Link DTM supports the
operating systems Windows 9x, ME, NT 4.0, 2000 and XP. It is
placed on the enclosed CD. The installation follows the steps
mentioned below:
• Insert the installation CD into your CD drive.
• Start
setup.exe and proceed according to the instructions
displayed on the screen.
• The software is installed in the default program directory of
your computer under the subdirectory
"C:\Program Files\ifak system\is Pro FDT".

Introduction is Pro DP/PA Link DTM
2 ifak system GmbH
Documentation
This documentation contains important information for the cor-
rect operation of the is Pro DP/PA Link DTM. Please read this
documentation carefully before installing the software.
Throughout the manual different fonts are used to indicate differ-
ent meanings.
Our Service
In case you have any questions concerning the is Pro DP/PA Link
DTM which can’t be solved by this manual, please contact our
service by phone, fax or e-mail.
ifak system GmbH
Oststrasse 18
D-39114 Magdeburg (Germany)
www.ifak-system.com
Tel.: +49 - 391 - 544 563 - 0
Fax: +49 - 391 - 544 563 - 99
e-mail: [e-mail]
Courier New: file names, code sequences
Arial: names, commands, remarks

FDT Tools FDT-SpecificationBasics
ifak system GmbH 3
CHAPTER 2:
FDT – A BRIEF INTRODUCTION
FDT-Specification Basics
The widespread technologies COM (Common Object Model),
XML (eXtensible Mark-up Language) and ActiveX (a COM
based technology for GUI elements) form the basis platform of
FDT.
COM integrates the different software components and facilitates
the interaction between them. Another example for the use of
COM as underlying concept of an automation standard can be
found in the area of online data exchange. There, the specifica-
tion OPC (DA) defines the interfaces and mechanisms for the
interaction between independent software components employ-
ing COM functionality.
Compared to OPC the aims of FDT are quite more challenging.
The COM functions transfer XML documents, which contain the
data to be communicated between different components. The
data which may be of different levels of complexity convey
information about the various aspects of the software component
(general information like manufacturer and device type; sup-
ported functions, communication data).
The ActiveX technology was chosen in order to integrate device
specific dialog elements in the HMI of the engineering system.
FDT adds new functions to the already existing ActiveX function
set, to adapt the standard to the special needs of FDT. For a
seamless integration of all components FDT specifies (with more
or less depth) the object model, interfaces and XML schemas, as
well as a session and data management.

FDT – A Brief Introduction FDT Tools
4 ifak system GmbH
Object Model
The object model contains the following four elements:
• Frame Application
• Device Type Manager (DTM)
•Channel
• ActiveX
An engineering system or a configuration software forms a
Frame Application, which defines the run-time environment,
administers the project data and stores the persistent data. In most
cases also the access to the underlying fieldbus communication is
provided.
A DTM as device data server handles the tasks of management
and configuration of a device class, as defined by the manufac-
turer. This device class might be one device type or a group of
devices. A typical DTM contains no graphical HMI. In most
cases a DTM is invoked for every device.
The parameter of the device as well as the HMI elements can be
influenced or activated by the user of the DTM. Most HMI ele-
ments are implement as ActiveX components, although the
inclusion of external programs is also allowed. The ActiveX fits
seamlessly into the Frame Application. The user is not able to
determine where the called HMI came from. It appears as a natu-
ral part of the engineering system.

FDT Tools FDT-SpecificationBasics
ifak system GmbH 5
Figure 1: FDT Object Model
At this point two new terms are introduced, which are not con-
tained in the FDT specification but seem to be helpful for an eas-
ier understanding of the specification.
A DTM for a device class without any direct access to the com-
munication (the use of the FDT communication functions not-
withstanding) is named DeviceDTM. In order to configure a
field device (sensor, actuator) within a FDT compliant engineer-
ing system one Device DTM must exist for every device. The
DeviceDTM will be provided by the device manufacturer.
A DTM for a device class with direct access to a communication
device (e.g. a Profibus interface) is named CommDTM. The
CommDTM encapsulates all communication specific aspects. It
is responsible for the management and configuration of the com-
munication interface. Other applications (DTMs) call its Com-
mChannels for field communication access. The CommChannel
can be provided by an additional CommDTM or by the Frame
Application.
DeviceDTM and CommDTM differ mainly in the type of chan-
nels a DTM supports. A Channel represents either a communica-
tion (CommChannel) or data channel (DataChannel). A

FDT – A Brief Introduction FDT Tools
6 ifak system GmbH
CommChannel allows other DTMs an access to the fieldbus
communication. It supports the interface “IFdtCommunication“,
which groups the communication access function. A DataChan-
nel allows other DTMs an access to the data values and is pro-
vided by the device DTM. The values could be the process values
of a field device, which were communicated by cyclic data
exchange.
A device in FDT is managed by its dedicated DeviceDTM. Its
ActiveX based HMI allows the user the access to its parameters
and functions. The DeviceDTM communicates with its device
through a CommChannel and the underlying fieldbus interface.
Lets draw a comparison between the FDT terms DeviceDTM,
CommDTM, CommChannel and the terms in use within the
domain of automation software. A DeviceDTM (and its ActiveX
components) replaces the manufacturer specific field device con-
figuration software and the CommDTM (and its ActiveX compo-
nents) replaces the manufacturer specific fieldbus interface
configuration software. A CommChannel equals the driver
library of a communication interface.
If a DeviceDTM is called and attached to a certain device, this
DeviceDTM instance is associated with a CommChannel. The
device can establish a connection to the device through this Com-
mChannel. Contrary to today’s practice the DeviceDTM can
expect an interface with a manufacturer independent behaviour.

FDT Tools FDT-SpecificationBasics
ifak system GmbH 7
Figure 2: Frame Access
The definition of interfaces and XML schemas allows the con-
nection and interaction of the pictured software components.
About 30 data interfaces support the flow of information: A
frame application accesses the DTMs through the interfaces
“IDtm“ and “IDtmInformation“ in order to manage the DTM and
inquire about the DTMs capabilities. The DTM itself accesses
the frame through another set of interfaces which allow the DTM
to acquire information from and transmit data to the frame.
Component interaction
Before going into more detail a short example about the interac-
tion of the different components mentioned so far might help to
deepen the understanding of the matter. Let us picture a FDT
based system. The run-time environment (the frame application)
was started already.
In the next step we add a CommDTM to the system topology of
the frame application. The frame is now able to inquire the
CommDTM about the supported CommChannels.

FDT – A Brief Introduction FDT Tools
8 ifak system GmbH
Figure 3: Interaction of the Comm-Objects
If the check was successful, what means that the channel and the
DeviceDTM speak in the same "language" (HART, Profibus DP/
V1 etc.), the communication between channel and DTM can be
established. To achieve this the channel supports the interface
IFdtCommunication. The interface contains the fieldbus access
functionality (connection establishment, termination, data trans-
fer). The communication between both components is now estab-
lished.
If the DeviceDTM invokes a communication request via IFdt-
Communication the channel is responsible for the handling of the
request. The response of the device is transmitted to the DTM
through its IFdtCommunicationEvents interface.

FDT Tools FDT-SpecificationBasics
ifak system GmbH 9
Summary: Objects in the FDT concept
DeviceDTM
A DeviceDTM is a DTM for fieldbus devices. It provides all nec-
essary functionality of the devices in software. To achieve this, it
employs the communication interfaces of the CommDTM.
Within the FDT concept the DeviceDTMs form the lowest level
in the system topology. They use the services of other Comm-
DTMs to access its field device. The parameters of the device are
made available to the user by a number of ActiveX dialog HMIs
which can be called from the DTM.
ActiveX
The ActiveX are the "visible" components of a FDT application
(as far as device functionality is concerned). DTM and channel
objects provide interfaces for the configuration, diagnosis, docu-
mentation and parameter manipulation, while the ActiveX pro-
vide an easy way of data presentation and user interaction.
CommDTM
A CommDTM is a DTM which offers communication function-
ality to other DTMs. These DTMs may have been developed for
a hardware (e.g. is HART USB device) or a software (e.g.
is HART OPC Server) communication interface. The Comm-
DTM itself can employ the services of another CommDTM
(gateway functionality). To allow communication with its under-
lying hardware or software the CommDTM offers a number of
communication (Comm) channels.

FDT – A Brief Introduction FDT Tools
10 ifak system GmbH
CommChannel
The CommChannel is responsible for the connection to its man-
aged hard- or software and provides the communication interface
to the DeviceDTMs. Communication requests and responses are
sent, received and manged by the CommChannel.
A pointer to the main interface of the channel
(IFdtCommunication) is passed to the DeviceDTM. The channel
provides the interface IFdtChannelSubTopology, which supports
the inclusion of a DeviceDTM into the topology of the Com-
mChannel. It also contains functions, which allow the Device-
DTM to check whether it is able to communicate with this
channel (e.g. information about the supported fieldbus protocol).

is Pro DP/PA Link DTM
ifak system GmbH 11
CHAPTER 3:
GATEWAY DTM IS PRO DP/PA LINK
DTM
Following is a description of the configuration of the Gateway
DTM is Pro DP/PA Link DTM. The Gateway DTM can be inte-
grated into any frame application e. g. Pactware. First one has to
install the software (see chapter 1). Start your frame application.
Then the device catalog has to be updated.
Now, the is Pro DP/PA Link DTM is registered and ready for
work. The DTM is listed in the device catalog of the FDT con-
tainer as Siemens DP/PA Link.
Figure 4: Gateway DTM in the FDT container PACTware

Gateway DTM is Pro DP/PA Link DTM is Pro DP/PA Link DTM
12 ifak system GmbH
Configuration in Offline Mode
Change DeviceDTM Address
This ActiveX allows to change tag and address of connected
DeviceDTMs. This is possible only in the offline mode, because
otherwise existing connections could be disconnected.
Figure 5: Change of DeviceDTM Addresses
The list on the left side shows connected DeviceDTMs. The but-
ton "Refresh List" updates the list with the currently connected
DTMs.
The data (tag and address) of a DTM are displayed in the upper
right part when the DTM is selected in the list. The new informa-
tion can be inserted below and the button "Apply" sends the new
information to the selected DeviceDTM.

is Pro DP/PA Link DTM Configuration in Online Mode
ifak system GmbH 13
Configuration in Online Mode
The FDT specification defines the function ScanRequest() for
CommDTMs. This function makes it possible to receive a list of
devices that are connected to the bus (also called "live list").
The is Pro DP/PA Link DTM implements this function according
to the FDT specification. It is necessary that the applied FDT
Container supports this function. You can use the ActiveX
"Device List" (see section below), too.
The specification allows a ScanRequest only for the DTM states
ONLINE, COMMUNICATIONSET and GOINGONLINE. The Gate-
way DTM follows the specification and allows only querying for
devices on the bus when the Gateway DTM is connected.
The list of devices found is transmitted to the frame application
with the help of an XML document und should be displayed to
the user.
Device List
This ActiveX lists all devices found during a Profibus scan. The
list shows the address of the device, its Profibus identification
number (Ident), and whether the device is currently in use by a
connection of a DeviceDTM. A scan triggered by the frame
application or pressing the button "Update List" will update the
list with the devices found on the Profibus segment.

Gateway DTM is Pro DP/PA Link DTM is Pro DP/PA Link DTM
14 ifak system GmbH
Figure 6: Device List (online)
An ActiveX with additional information about a device can be
opened by selecting the button "Extended Information..." for a
chosen slave device.
The button "Change Address..." opens another ActiveX for
changing the address of the Profibus device. This function is
available only when the slave is not in use by a DeviceDTM con-
nection.

is Pro DP/PA Link DTM Configuration in Online Mode
ifak system GmbH 15
Slave Information
The information in this ActiveX are obtained from the diagnosis
data of the selected Profibus slave device. Their meaning is
explained in the Profibus literature.
The device and vendor names are extracted from tables that con-
tain such information for a number of devices identified by the
identification number (Ident).
Figure 7: Slave Information

Gateway DTM is Pro DP/PA Link DTM is Pro DP/PA Link DTM
16 ifak system GmbH
Change Slave Address
This ActiveX offers an interface to change the address of a Profi-
bus slave device. The current address is set automatically when
the ActiveX is opened. The new address is not allowed to be in
use at the same Profibus segment. The DTM checks the existence
of the target address before actually performing the change. The
status line will indicate success or failure of the address change
operation.
Figure 8: Change of Slave Address