IEC PAS 62453-5:2006

PUBLICLY
IEC
AVAILABLE
PAS 62453-5
SPECIFICATION
First edition
Pre-Standard
2006-05
Field Device Tool (FDT) interface specification –

Part 5:
FOUNDATION FIELDBUS communication

Reference number
IEC/PAS 62453-5:2006(E)
Publication numbering
As from 1 January 1997 all IEC publications are issued with a designation in the
60000 series. For example, IEC 34-1 is now referred to as IEC 60034-1.

Consolidated editions
The IEC is now publishing consolidated versions of its publications. For example,
edition numbers 1.0, 1.1 and 1.2 refer, respectively, to the base publication, the
base publication incorporating amendment 1 and the base publication incorporating
amendments 1 and 2.
Further information on IEC publications
The technical content of IEC publications is kept under constant review by the IEC,
thus ensuring that the content reflects current technology. Information relating to
this publication, including its validity, is available in the IEC Catalogue of
publications (see below) in addition to new editions, amendments and corrigenda.
Information on the subjects under consideration and work in progress undertaken
by the technical committee which has prepared this publication, as well as the list
of publications issued, is also available from the following:
• IEC Web Site (www.iec.ch)
• Catalogue of IEC publications
The on-line catalogue on the IEC web site (www.iec.ch/searchpub) enables you to
search by a variety of criteria including text searches, technical committees
and date of publication. On-line information is also available on recently issued
publications, withdrawn and replaced publications, as well as corrigenda.
• IEC Just Published
This summary of recently issued publications (www.iec.ch/online_news/ justpub)
is also available by email. Please contact the Customer Service Centre (see
below) for further information.
• Customer Service Centre
If you have any questions regarding this publication or need further assistance,
please contact the Customer Service Centre:

Email: custserv@iec.ch
Tel: +41 22 919 02 11
Fax: +41 22 919 03 00
PUBLICLY
IEC
AVAILABLE
PAS 62453-5
SPECIFICATION
First edition
Pre-Standard
2006-05
Field Device Tool (FDT) interface specification –

Part 5:
FOUNDATION FIELDBUS communication

 IEC 2006  Copyright - all rights reserved
No part of this publication may be reproduced or utilized in any form or by any means, electronic or
mechanical, including photocopying and microfilm, without permission in writing from the publisher.
International Electrotechnical Commission, 3, rue de Varembé, PO Box 131, CH-1211 Geneva 20, Switzerland
Telephone: +41 22 919 02 11 Telefax: +41 22 919 03 00 E-mail: inmail@iec.ch Web: www.iec.ch
PRICE CODE
Commission Electrotechnique Internationale
XC
International Electrotechnical Commission
Международная Электротехническая Комиссия
For price, see current catalogue

– 2 – PAS 62453-5  IEC:2006
CONTENTS
FOREWORD.4

INTRODUCTION.6

1 Scope .7

2 Normative references .7

3 Solution concept.7

3.1 Overview .7

3.2 Unique identifier .11

3.2.1 Component categories .11
3.2.2 Bus category.12
4 FF communication .13
4.1 Connection management .13
4.1.1 FMS connection .13
4.1.2 HSE connection .14
4.2 Abort .14
4.2.1 OnAbort indication .14
4.2.2 Abort request .15
4.3 Relation of FMS requests and FMS responses .15
4.4 Levels of support .16
5 Provided data .17
5.1 Interface IDtmParameter.17
5.2 SingleDataAccess interfaces.17
5.2.1 DTM .17
5.2.2 BTM .17
6 Protocol specific usage of XML attributes.18
7 XML schemas and definitions.19
7.1 DTM.19
7.1.1 Topology scan schema.19
7.1.2 DTM FF schema .19
7.2 BTM .19
7.2.1 Parameter access - FF specific definitions.19
7.3 Communication.31
7.3.1 ChannelParameter Schema.31

7.3.2 FF data type .32
7.3.3 FF FMS data types.33
7.3.4 H1 communication schema.36
7.3.5 HSE communication schema .37
7.3.6 BTM – DTM communication schema.39
7.4 Fieldbus management.40
7.5 H1 management schema .40
7.5.1 HSE management schema .55
7.6 Fieldbus Foundation device identification .69
7.6.1 FDTFieldbusIdentSchema.xml.69

BIBLIOGRAPHY .77

PAS 62453-5  IEC:2006 – 3 –
Figure 1 ─ Example of System Architecture and Components .8

Figure 2 ─ Object relations for H1 DeviceDTM.8

Figure 3 ─ Object relations for HSE DTMs.10

Figure 4 ─ Creation of an FMS connection .13

Figure 5 ─ Termination of an FMS connection .14

Table 1 ─ Explanation of object relations for H1 DeviceDTM.9

Table 2 ─ Explanation of object relations for HSE DTMs.10

Table 3 ─ Relation of FMS requests and FMS responses.15
Table 4 ─ Levels of support .16
Table 5 ─ FF specific use of XML attributes.18
Table 6 ─ List of the standard block parameter mnemonic .20
Table 7 ─ Datatype definitions and mapping (structured types) .27
Table 8 ─ Datatype definitions and mapping (simple types) .30
Table 9 ─ FoundationFieldbusChannelParameterSchema – attributes and elements .31
Table 10 ─ FdtFFDataTypesSchema – attributes.32
Table 11 ─ FdtFFDataTypesSchema – elements .33
Table 12 ─ FdtFFFMSDataTypesSchema – attributes .33
Table 13 ─ FdtFFFMSDataTypesSchema – elements .34
Table 14 ─ FdtFFH1CommunicationSchema – attributes .36
Table 15 ─ FdtFFH1CommunicationSchema –elements .37
Table 16 ─ FdtFFHSECommunicationSchema – attributes .38
Table 17 ─ FdtFFHSECommunicationSchema –elements .38
Table 18 ─ BtmFFCommunicationSchema – attributes and elements .39
Table 19 ─ FDTFoundationFieldbusH1ManagementSchema – attributes .40
Table 20 ─ FDTFoundationFieldbusH1ManagementSchema –elements .46
Table 21 ─ FDTFoundationFieldbusHSEManagementSchema – attributes .55
Table 22 ─ FDTFoundationFieldbusHSEManagementSchema – elements.60
Table 23 ─ FDTFieldbusIdentSchema - attributes for Foundation Fieldbus H1.70
Table 24 ─ FDTFieldbusIdentSchema - attributes for Foundation Fieldbus HSE .71

Table 25 ─ FDTFieldbusIdentSchema - attributes for Foundation Fieldbus Blocks .72
Table 26 ─ FDTFieldbusIdentSchema - protocol independent attributes and elements.75
Table 27 ─ FieldbusScanTypeIdentSchema – attributes and elements .75
Table 28 ─ FieldbusDeviceTypeIdentSchema – attributes and elements .76

– 4 – PAS 62453-5  IEC:2006
INTERNATIONAL ELECTROTECHNICAL COMMISSION

____________
Field Device Tool (FDT) interface specification –

Part 5: FOUNDATION FIELBUS communication

FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote
international co-operation on all questions concerning standardization in the electrical and electronic fields. To
this end and in addition to other activities, IEC publishes International Standards, Technical Specifications,
Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC
Publication(s)”). Their preparation is entrusted to technical committees; any IEC National Committee interested
in the subject dealt with may participate in this preparatory work. International, governmental and non-
governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely
with the International Organization for Standardization (ISO) in accordance with conditions determined by
agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence
between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in
the latter.
5) IEC provides no marking procedure to indicate its approval and cannot be rendered responsible for any
equipment declared to be in conformity with an IEC Publication.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of
patent rights. IEC shall not be held responsible for identifying any or all such patent rights.

A PAS is a technical specification not fulfilling the requirements for a standard but made
available to the public .
IEC-PAS 62453-5 has been processed by subcommittee 65C: Digital communications, of IEC
technical committee 65: Industrial-process measurement and control.
The text of this PAS is based on the This PAS was approved for
following document: publication by the P-members of the
committee concerned as indicated in
the following document
Draft PAS Report on voting
65C/398A/NP 65C/411/RVN
Following publication of this PAS, which is a pre-standard, the technical committee or
subcommittee concerned will transform it into an International Standard.

PAS 62453-5  IEC:2006 – 5 –
This PAS shall remain valid for an initial maximum period of three years starting from

2006-05. The validity may be extended for a single three-year period, following which it shall

be revised to become another type of normative document or shall be withdrawn.

IEC 62453 consists of the following parts under the general title Field Device Tool (FDT)

interface specification:
Part 1: Concepts and detailed description

Part 2: INTERBUS communication

Part 3: PROFIBUS communication

Part 4: HART communication
Part 5: FOUNDATION FIELDBUS communication

– 6 – PAS 62453-5  IEC:2006
INTRODUCTION
This PAS is an interface specification for developers of FDT components for Function Control

and Data Access within a Client Server architecture. The specification is a result of an

analysis and design process to develop standard interfaces to facilitate the development of

servers and clients by multiple vendors that shall inter-operate seamlessly.

With the integration of fieldbusses into control systems, there are a few other tasks which

must be performed. This applies to fieldbusses in general. Although there are fieldbus- and

device-specific tools, there is no unified way to integrate those tools into higher level system-

wide planning or engineering tools. In particular, for use in extensive and heterogeneous

control systems, typically in the area of the process industry, the unambiguous definition of
engineering interfaces that are easy to use for all those involved, is of great importance.
A device-specific software component, called DTM (Device Type Manager), is supplied by the
field device manufacturer with its device. The DTM is integrated into engineering tools via the
FDT interfaces defined in this specification. The approach to integration is in general open for
all kind of fieldbusses and thus meets the requirements for integrating different kinds of
devices into heterogeneous control systems.

PAS 62453-5  IEC:2006 – 7 –
Field Device Tool (FDT) interface specification –

Part 5: FOUNDATION FIELDBUS communication

1 Scope
This part of IEC 62435 provides information for integrating the FOUNDATION FIELDBUS (FF)

protocol into the FDT interface specification (IEC 62453-1).

This PAS describes communication schemas, protocol-specific extensions and the means for
block (e.g. transducer, resource or function blocks) representation.
The new protocol-specific XML schemas are based on FF specifications for H1 and HSE
protocols. Furthermore, the schemas contain information about the device that is needed by
systems to configure FF Devices.
The focus of this part is Foundation Fieldbus device configuration.
2 Normative references
The following referenced documents are indispensable for the application of this document.
For dated references, only the edition cited applies. For undated references, the latest edition
of the referenced document (including any amendments) applies
IEC 62453-1: Field Device Tool (FDT) interface specification – Part 1: Concepts and detailed
description
IEC 61158 (all parts), Digital data communications for measurement and control – Fieldbus for
use in industrial control systems
3 Solution concept
3.1 Overview
For the solution, this part provides communication schemas, protocol-specific extensions and
means for block (e.g. resource, transducer or function blocks) configuration.

The communication schemas are created to support System Management (SM), Network
Management (NM) and Fieldbus Message Specification (FMS).
Separate schemas are designed to support the different management structures for H1 and
HSE devices.
Protocol-specific schemas, as required by the FDT Specification, can be used to identify
Foundation Fieldbus devices and their internal structure.
A Foundation Fieldbus device is represented by a Device Type Manager (DTM) together with
a group of Block Type Manager (BTM). The BTMs represent the function block functionality in
an FF device.
The internal device structure is represented by the following topology, see Figure 1.

– 8 – PAS 62453-5  IEC:2006
Figure 1 ─ Example of System Architecture and Components

The following Figure 2 shows all possible object relations for an H1 DeviceDTM.

H1
H1-1
Communication
DTM
H1-2 H1 H1-2.3
Channel
Frame
H1-3 H1 Device
Application
DTM
H1-4 H1-4.5
Channel
H1-5
BTM for Block
Figure 2 ─ Object relations for H1 DeviceDTM
For an explanation of the figure components see the following Table 1.

PAS 62453-5  IEC:2006 – 9 –
Table 1 ─ Explanation of object relations for H1 DeviceDTM

Relation Type of information Used schemas Example

H1-1 Management FdtFFH1ManagementSchema FDTFoundationFieldbusH1ManagementSchema
Parameter Access
FdtFFDataTypesSchema
H1-2 Network Topology DtmFFSchema DTMFoundationFieldbusDeviceSchema

FdtFFDataTypesSchema
FdtFFHseCommunicationSchema
Channel Parameter FDTBasicChannelParameterSchema FDTFoundationFieldbusChannelParameterSchema
Access
H1-3 Management FdtFFH1ManagementSchema FDTFoundationFieldbusH1ManagementSchema
Parameter Access
FdtFFDataTypesSchema
H1-4 List of instantiated DtmFFSchema BTMTopologyScanSchema
blocks
BtmDataTypesSchema
FdtFFBlockSchema
Channel Parameter FDTBasicChannelParameterSchema FDTFoundationFieldbusChannelParameterSchema
Access
H1-5 Block Information BtmInformationSchema BTMInformationSchema
BtmDataTypesSchema
Initialization of BTM BtmInitSchema BTMInitSchema
BtmDataTypesSchema
Parameter Access BtmParameterSchema BTMParameterSchema
BtmDataTypesSchema
H1-2.3 Communication FdtFFFmsSchema FDTFoundationFieldbusFMSSchema
FdtFFH1CommunicationSchema FDTFoundationFieldbusH1Schema
FdtFFDataTypesSchema
H1-4.5 DTM-BTM FdtFFFmsSchema FDTFoundationFieldbusFMSSchema
Communication
BTMFFCommunicationSchema BtmCommunicationInstanceConnReq.xml
BtmDataTypesSchema BtmCommunicationInstanceConnResp.xml
FdtFFDataTypesSchema BtmCommunicationInstanceFmsReadReq.xml
BtmCommunicationInstanceFmsReadResp.xml

– 10 – PAS 62453-5  IEC:2006
High Speed
HSE-1 Ethernet
Communication
DTM
HSE-2 HSE HSE-2.1
Channel
HSE-2.1
HSE-1 HSE Device
DTM
HSE-4
HSE-4.5
Channel
HSE-5 BTM for
Block
HSE-1 Linking
Frame
Device DTM
Application
HSE-7
HSE-7.10
H1 Channel
HSE-4 HSE-4.5
Channel
HSE-5 BTM for
Block
HSE-10 H1 Device
DTM
HSE-4
HSE-4.5
Channel
HSE-5 BTM for
Block
Figure 3 ─ Object relations for HSE DTMs
In this Figure 3, blue lines show the object hierarchy as it is managed in the FDT Frame
Application. The relations are explained in following Table 2.
Table 2 ─ Explanation of object relations for HSE DTMs
Relation Type of information Used schemas Examples
HSE-1 Management Parameter FdtFFHSEManagementSchema FDTFoundationFieldbusHSEManagement
Access Schema
HSE-2 Network Topology DtmFFSchema DTMFoundationFieldbusDeviceSchema

Channel Parameter Access FdtFFChannelParameterSchema FDTFoundationFieldbusChannelParameter
Schema
HSE-2.1 Communication FdtFFFmsSchema FDTFoundationFieldbusFMSSchema
FdtFFHseCommunicationSchema FDTFoundationFieldbusHSESchema
FdtFFDataTypesSchema
HSE-4.5 DTM-BTM Communication FdtFFFmsSchema FDTFoundationFieldbusFMSSchema
BTMFFCommunicationSchema BtmCommunicationInstanceConnReq.xml
FdtFFDataTypesSchema BtmCommunicationInstanceConnResp.xml
BtmDataTypesSchema BtmCommunicationInstanceFmsReadReq.
xml
BtmCommunicationInstanceFmsReadResp.
xml
PAS 62453-5  IEC:2006 – 11 –
Relation Type of information Used schemas Examples

HSE-4 List of instantiated blocks DtmFFSchema BTMTopologyScanSchema

FdtFFBlockSchema
BtmDataTypesSchema
Channel Parameter Access FDTBasicChannelParameterSchema FDTFoundationFieldbusChannelParameter
Schema
HSE-5 Block Information BtmInformationSchema BTMInformationSchema

BtmDataTypesSchema
Initialization of BTM BtmInitSchema BTMInitSchema
BtmDataTypesSchema
Parameter Access BtmParameterSchema BTMParameterSchema
BtmDataTypesSchema
HSE-7 Network Topology DtmFFSchema DTMFoundationFieldbusDeviceSchema
FdtFFDataTypesSchema
FdtFFHseCommunicationSchema
FdtFFBlockSchema
Channel Parameter Access FdtFFChannelParameterSchema FDTFoundationFieldbusChannelParameter
Schema
FdtFFH1ManagementSchema
Parameter Access BtmParameterSchema BTMParameterSchema
HSE-10 Management Parameter FdtFFH1ManagementSchema FDTFoundationFieldbusH1Management
Access Schema
FdtFFDataTypesSchema
HSE-7.10 Communication FdtFFFMSSchema FDTFoundationFieldbusFMSSchema
FdtFFH1CommunicationSchema FDTFoundationFieldbusH1Schema
FdtFFDataTypesSchema
3.2 Unique identifier
3.2.1 Component categories
For device-specific BTMs, a bus category (CATID) must be defined for the protocol between

DTM and BTM.
The bus category is used by the Frame Application to identify the device-specific blocks. The
Frame Application can prevent a device-specific block from Device A being assigned to a
Device B that does not support the block.
Different protocols defined by different CATIDs can use the same communication schemas.
CATID Symbolic name UUID of the CATID Description
of the CATID
description in the
registry
“FDT FF CATID_FDT_FF {036D1693-387B-11D4- For FDT FF standard block protocol
STANDARD _STD_ 86E1-00E0987270B9}
BLOCK”
BLOCK
– 12 – PAS 62453-5  IEC:2006
The following table shows the valid combination of category ids.

Symbolic name of the CATID
CATID_FDT_BTM
√
CATID_FDT_STD_BLOCK  √
3.2.2 Bus category
FF protocol is identified by the following unique identifier in busCategory attributes within XML
BusCategory elements.
BusCategory Element Description
036D1691-387B-11D4-86E1-00E0987270B9 Object supports FF H1 protocol
036D1692-387B-11D4-86E1-00E0987270B9 Object supports FF HSE protocol
036D1693-387B-11D4-86E1-00E0987270B9 For FDT FF standard block protocol

CATID_FDT_DTM
CATID_FDT_DEVICE
CATID_FDT_MODULE
CATID_FDT_BTM
CATID_FDT_STD_BLOCK
PAS 62453-5  IEC:2006 – 13 –
4 FF communication
4.1 Connection management
FDT Connect request service establishes an FDT Connection. The FDT Connection acts as a

container for FMS Connections, as a container for SM connectionless services and as a

container for FDA sessions.
It is necessary to maintain the FMS Connection separate from the underlying FDT

Connection.
4.1.1 FMS connection
All FMS services are modelled in FDT as Transactions in the respective protocols. This
includes the services for the FMS connection management. FMSInitiate and FMSAbort
manage the lifetime of a FMS connection.
In order to open multiple FMS Connections on the same FDT Connection,
IFdtCommunication::TransactionRequest() is called with an FmsInitiateRequest element as
argument (see Figure 4).
The communication reference passed with the FmsInitiateRequest element identifies the FDT
Connection to be used. The FmsInitiateResponse element returned with
IFdtCommunicationEvents::OnTransactionResponse provides a communication reference
used for all further FMS services on that FMS Connection.
This allows multiple FMS connections on one FDT Connection.

Figure 4 ─ Creation of an FMS connection

– 14 – PAS 62453-5  IEC:2006
If the FDT connection is closed, the FMS connections for this connection are also closed

automatically (by the communication channel) before the FDT Disconnect is completed (see

Figure 5).
Any transactions requested after that will fail. No outstanding services will be processed.

Figure 5 ─ Termination of an FMS connection
FMSAbort service request closes a single FMS connection.

4.1.2 HSE connection
FDT Connection is using ConnectRequest:
• To establish an FDT connection intended for System Management services only. When
FDT connections for SM services only are established, the OpenSessionRequest element
is not part of the ConnectRequest. Any request to establish an FMS Connection on this
type of FDT Connection shall be rejected.
• To establish an FDT Connection that represents a session as described with the
specification FF-588 Field Device Access Agent. FMS Connections can be established by
using the FDT Communication reference returned as a result of FDT connection
establishment. Note that Multicast SM services are not allowed in this Connection.
If a HSE device needs both types of connections it needs to create System management and
FDT Session Connections.
When a Frame Application requests the DTM to disconnect all FMS, and FDT (SM and

Session), connections will be terminated.
4.2 Abort
4.2.1 OnAbort indication
At any moment during the lifetime of the (FDT or FMS) Connection an OnAbort event
indication can be received by the DTM/BTM from the Communication Channel. There can be
two reasons for OnAbort Event:
• FMS Connection Abort
• FDT Connection Abort.
The Communication reference uniquely identifies the Connection to be aborted. If a FDT
Connection Abort is indicated, all FMS connections of the corresponding FDT Connection
must be terminated. No Abort requests are issued to the Communication Channel. All
pending requests must be canceled.

PAS 62453-5  IEC:2006 – 15 –
If a FMS Connection Abort is indicated, only the FMS Connection identified by that

Communication Reference is terminated.

4.2.2 Abort request
At any moment during the lifetime of the (FDT or FMS) Connections a DTM/BTM can issue an

Abort request to the Communication Channel. There can be two types of Communication

References in the Abort request:

• FMS Communication Reference
• FDT Communication Reference
The Communication reference uniquely identifies the Connection to be aborted. If an FDT
Connection Abort is requested, all related FMS connections in the Communication channel
must be terminated.
No separate Abort requests are issued to the Communication Channel for the individual FMS
Connections. All pending requests must be canceled.
If an FMS Communication Reference is used in the Abort, only the FMS Connection identified
by that Communication Reference is terminated.
4.3 Relation of FMS requests and FMS responses
If a DeviceDTM (communication client) issues a certain FMS request, it has to expect a
response from a certain set (one or more) of possible responses. The following Table 3 shows
what responses can be expected in regard to different FMS requests.
Table 3 ─ Relation of FMS requests and FMS responses
Request Response (s)
FmsInitiateRequest FmsInitiateResponse
FmsInitiateError
FmsAbortRequest FmsStandardResponse
FmsReadRequest FmsReadResponse
FmsServiceError
FmsWriteRequest FmsStandardResponse
FmsServiceError
FmsStatusRequest FmsStatusResponse
FmsServiceError
FmsIdentifyRequest FmsIdentifyResponse
FmsServiceError
FmsDefineVariableListRequest FmsDefineVariableListResponse
FmsServiceError
FmsDeleteVariableListRequest FmsStandardResponse
FmsServiceError
FmsGetOdRequest FmsGetOdResponse FmsServiceError
FmsGenericInitiateDownloadSequenceRequest FmsStandardResponse
FmsServiceError
FmsGenericDownloadSegmentRequest FmsStandardResponse
FmsServiceError
FmsGenericTerminateDownloadSequence FmsGenericTerminateDownloadSequenceResponse
Request FmsServiceError
– 16 – PAS 62453-5  IEC:2006
A standard FDT CommunicationError response can be received instead of FMS Transaction

response to indicate a general communication error. Communication clients must be prepared

to handle such response.
If the FMS connection is shared between several BTMs, all connections will receive OnAbort

event.
4.4 Levels of support
Similar to the levels of support for FF devices, this PAS defines levels of support for DTMs

(see Table 4).
Table 4 ─ Levels of support
Services
HSE H1
Level 0 Level 1 Level 2 Level 4 Level 0 Level 1 Level 2 Level 4
support support support support Support Support Support Support
SmSetPDTag N/A N/A N/A N/A O - M -
SmSetAddress N/A N/A N/A N/A O - M -
SmFindTag O - M - O - M -
SmIdentify M - M - M - M -
SmClearAddress O - M - O - M -
SmClearAssignmentInfo O - M - N/A N/A N/A N/A
SmSetAssignmentInfo O - M - N/A N/A N/A N/A
fms:FmsInitiate M M - - M M - -
fms:FmsAbort M M - - M M - -
fms:FmsStatus O M - - O M - -
fms:FmsIdentify O M - - O M - -
fms:FmsRead M M - - M M - -
fms:FmsWrite M M - - M M - -
fms:FmsGetOd O M - - O M - -
fms:FmsDefineVariableList O - - M O - - M
fms:FmsDeleteVariableList O - - M O - - M
fms:FmsGenericDownload O - - M O - - M
Legend:
M – Mandatory O – Optional N/A - Not Applicable
Level 0: Minimal Support
Level 1: FMS Mandatory services support
Level 2: SM Address assignment support
Level 4: Download (Domain and Variable List) Services support

FF H1 and HSE support levels for DTMs are a combination of the levels defined in Table 5.
The levels in the table are defined in a way that the sum of different levels always yields a
unique resulting level number.
Examples:
Mandatory Services on Level 0 will be always implemented.

PAS 62453-5  IEC:2006 – 17 –
A fully functional HSE DTM is level HSE-7, since it supports levels HSE-1, HSE-2, and

HSE-4 additional to the basic HSE level 0.

An H1 DTM, that supports all Mandatory FMS services and also allow Address and Tag

Assignment is of level H1-3, since it supports levels H1-1 and H1-2 additional to the

basic H1 level 0.
SM services SetPDTag and SetAddress are H1 specific and therefore not listed in the

HSE levels 0 and 2.
SM services ClearAssignmentInfo and SetAssignmentInfo are HSE specific and therefore

not listed in the H1 levels 0 and 2.

5 Provided data
5.1 Interface IDtmParameter
The minimum set of provided data should be
• for foundation fieldbus devices, System Management and Network Management
parameters should be provided by the DTM as specified in 4.4. "Fieldbus Management” of
the FF addendum,
• all standard block parameters should be provided by the corresponding BTM object as
specified in 4.2.3. "Parameter Access” of the FF addendum.

5.2 SingleDataAccess interfaces
5.2.1 DTM
All parameters exposed by the DTM to the Frame Application must be accessible by these
interfaces.
5.2.2 BTM
BTMs build according to the function block specification must expose all parameters for the
corresponding block. This means all parameters defined for a block in the FF specification
must be exposed. The manufacturer specific parameters can extend this list. User-defined
parameters must be exposed if they exist.

– 18 – PAS 62453-5  IEC:2006
6 Protocol specific usage of XML attributes

The following Table 5 describes the protocol specific use of XML attributes that are defined in

protocol independent schemas.
Table 5 ─ FF specific use of XML attributes

Attribute Description for use in Fieldbus Foundation

address The address attribute (defined in FDTDataTypesSchema.xml) is mandatory for

the exposed parameters in the DTMs and BTMs. The address attribute string

should be constructed according to the following model:
VFD:xx.INDEX:yyy[.SUBINDEX:zz],
where
xx is the VFD tag or index
yy is the parameter index from the beginning of the VFD
zz is the parameter subindex
The numbers are integers (some can be 32-bit) and are presented as decimal
digits. There should be no leading zeros for the numbers.
The subindex portion of the address is optional and for parameters without
subindex it can be skipped or the subindex can be set to 0.
busCategory See 3.2.2
semanticId The applicationDomain attribute is: FDT_FoundationFieldbus
applicationDomain
The semanticId for Foundation Fieldbus related parameter follows the following
rules:
The semanticId must be built based on the names defined in the FF
specification
Structured parameters must be combined with a ‘.’
Spaces within the profile definition must be exchanged with an underscore
Capital letters should be used
For detailed description please refer to “4.2.3 Parameter Access” of the FF
addendum.
Examples:
OUT.STATUS
OUT.VALUE
OUT
SemanticID for FF Fieldbus management parameter:
Fieldbus management parameter (well-defined with inline schemas within the
element ‘UserdefinedBus’ of the DTMParameterSchema) follow the following
rule:
‘FDT.UserDefinedBus’ followed by the structure of the XML document of the
inline schema. Each element must be divided by a ‘.’.
Example:
FDT.UserDefinedBus.ListOfH1NmaVfds.H1NmaVfd.SMIB.SmAgent.T1.t1

PAS 62453-5  IEC:2006 – 19 –
7 XML schemas and definitions
7.1 DTM
7.1.1 Topology scan schema
As a result of the scanning the DTM detects DTMs and objects that are covered by this

Addendum. As a result of topology scan a DTM can expose information about the FF linking

devices, about FF instruments and about the Blocks in the instruments.

If the DTM detects that the Frame Application supports the objects covered by this addendum

it can include directly the reference to the corresponding schemas. The following files have
examples demonstrating the reference to the FF schemas:
• DTMTopologyScanInstanceBlockList.xml
• DTMTopologyScanInstanceH1Device.xml
If the DTM detects that the Frame Application does not support the objects covered by this
addendum the required definitions have to be defined in an inline schema. The following
examples demonstrate the use of inline schemas:
• DTMTopologyScanInstanceBlockList (Inline).xml
• DTMTopologyScanInstanceH1Device (Inline).xml
The in-line schema elements must be the same as the corresponding elements from the
schemas defined in this addendum.
7.1.2 DTM FF schema
The DtmFFSchema.XML flie provides description information about the FF Devices.
Data types of this schema are referenced via the prefix fdtffdevice: within the other schemas.
Tag Description
BlockList Provides the list of blocks in the device
HSEDeviceInformation HSEDeviceInformation describes High Speed Eternet compatible devices
including device version, redundancy, etc.
FoundationFieldbusH1Device FoundationFieldbusH1Device includes information describing H1 compatible
devices
FoundationFieldbusHSEDevice Describes HSE compatible devices including the device address, VFD
information, etc.
7.2 BTM
In case of a BTM the following schemas are used instead of the DTM-specific schemas
defined within the FDT specification.
7.2.1 Parameter access - FF specific definitions
BTMs should use standard name attributes for standard Block parameters. The following
Table 6 provides the list of the standard block parameter Mnemonic (based on Foundation
Fieldbus specifications FF-890, FF-891, FF-892, FF-893, and FF-894) and their mapping to
the FDT data types. The parameter mnemonic should be used as name attribute value for
parameter definition.
– 20 – PAS 62453-5  IEC:2006
Table 6 ─ List of the standard block parameter mnemonic

Parameter Mnemonic Fieldbus Foundation FDT Datatype (Note 1)

Datatype/Structure
ACCEPT_ALM DS-72 StructuredVariable

ACCEPT_D Unsigned8 EnumeratorVariable

ACCEPT_PRI Unsigned8 NumberData

ACK_OPTION Bit String BitEnumeratorVariable

ALARM_HYS Float NumberData
ALARM_SUM DS-74 StructuredVariable

ALERT_KEY Unsigned8 NumberData
ALGORITHM_SEL Unsigned32 NumberData
ALM_RATE_DN Float NumberData
ALM_RATE_UP Float NumberData
ARITH_TYPE Unsigned8 NumberData
AUTO_CYCLE Unsigned8 EnumeratorVariable
BAL_TIME Float NumberData
BIAS Float NumberData
BIAS_IN_1 Float NumberData
BIAS_IN_2 Float NumberData
BIAS_IN_3 Float NumberData
BKCAL_HYS Float NumberData
BKCAL_IN DS-65 StructuredVariable
BKCAL_IN_1 DS-65 StructuredVariable
BKCAL_IN_2 DS-65 StructuredVariable
BKCAL_IN_D DS-66 StructuredVariable
BKCAL_OUT DS-65 StructuredVariable
BKCAL_OUT_D DS-66 StructuredVariable
BKCAL_SEL_1 DS-65 StructuredVariable
BKCAL_SEL_2 DS-65 StructuredVariable
BKCAL_SEL_3 DS-65 StructuredVariable
BLOCK_ALM DS-72 StructuredVariable
BLOCK_ERR Bit String BitEnumeratorVariable

BYPASS Unsigned8 EnumeratorVariable
CAS_IN DS-65 StructuredVariable
CAS_IN_D DS-66 StructuredVariable
CFM_ACT1_TIME Float NumberData
CFM_ACT2_TIME Float NumberData
CFM_PASS_TIME Float NumberData
CHANNEL Unsigned16 NumberData
CHARACTERISTICS (Note 2) DS-64 StructuredVariable
CLOCK_PER Float NumberData
CLR_FSTATE Unsigned8 EnumeratorVariable
COMB_TYPE Unsigned8 EnumeratorVariable
COMP_HI_LIM Float NumberData
COMP_LO_LIM Float NumberData
PAS 62453-5  IEC:2006 – 21 –
Parameter Mnemonic Fieldbus Foundation FDT Datatype (Note 1)

Datatype/Structure
CONFIRM_TIME Unsigned32 NumberData

CONTENTS_REV Unsigned32 NumberData

CONTROL_OPTS Bit String BitEnumeratorVariable

CRACK_TIME Float NumberData
CRACK_TIMER Float NumberData
CURVE_X Float NumberData
CURVE_Y Float NumberData
CYCLE_SEL Bit String BitEnumeratorVariable
CYCLE_TYPE Bit String BitEnumeratorVariable
DC_STATE Unsigned8 NumberData
DD_RESOURCE Visible String StringData
DD_REV Unsigned8 NumberData
DEAD_TIME DS-65 StructuredVariable
DELAY_TIME Float NumberData
DELAY_TIMER Float NumberData
DEV_REV Unsigned8 NumberData
DEV_TYPE Unsigned16 NumberData
DEVICE_OPTS Bit string BitEnumeratorVariable
DISABLE_1 DS-66 StructuredVariable
DISABLE_2 DS-66 StructuredVariable
DISABLE_3 DS-66 StructuredVariable
DISABLE_4 DS-66 StructuredVariable
DISC_ALM DS-72 StructuredVariable
DISC_LIM Unsigned8 NumberData
DISC_PRI Unsigned8 NumberData
DURATION DURATION_TYPE (10 Floats) StructuredVariable
(Note 3)
DV_HI_ALM DS-71 StructuredVariable
DV_HI_LIM Float NumberData
DV_HI_PRI Unsigned8 NumberData
DV_LO_ALM DS-71 StructuredVariable

DV_LO_LIM Float NumberData
DV_LO_PRI Unsigned8 NumberData
EXPAND_DN Float NumberData
EXPAND_UP Float NumberData
FAIL Unsigned16 NumberData
FAIL_ALM DS-72 StructuredVariable
FAIL_PRI Unsigned8 NumberData
FAULT_STATE Unsigned8 EnumeratorVariable
FCF_LOCATOR LOCATOR (Unsigned32 Array) StructuredVariable
(Note 4)
FDD_LOCATOR LOCATOR (Unsigned32 Array) StructuredVariable
FEATURE_SEL Bit String BitEnumeratorVariable
FEATURES Bit String BitEnumeratorVariable

– 22 – PAS 62453-5  IEC:2006
Parameter Mnemonic Fieldbus Foundation FDT Datatype (Note 1)

Datatype/Structure
FF_GAIN Float NumberData
FF_SCALE DS-68 StructuredVariable

FF_VAL DS-65 StructuredVariable

FIELD_VAL DS-65 StructuredVariable

FIELD_VAL_D DS-66 StructuredVariable

FILE_LOCATOR LOCATOR (Unsigned32 Array) StructuredVariable

FILE_REV Unsigned32 NumberData

FOLLOW DS-66 StructuredVariable
FREE_SPACE Float NumberData
FREE_TIME Float NumberData
FSTATE_STATUS Unsigned8 NumberData
FSTATE_TIME Float NumberData
FSTATE_VAL Float NumberData
FSTATE_VAL_D Unsigned8 NumberData
FSTATE_VAL_D1 Unsigned8 NumberData
FSTATE_VAL_D2 Unsigned8 NumberData
FSTATE_VAL_D3 Unsigned8 NumberData
FSTATE_VAL_D4 Unsigned8 NumberData
FSTATE_VAL_D5 Unsigned8 NumberData
FSTATE_VAL_D6 Unsigned8 NumberData
FSTATE_VAL_D7 Unsigned8 NumberData
FSTATE_VAL_D8 Unsigned8 NumberData
FSTATE_VAL1 Float NumberData
FSTATE_VAL2 Float NumberData
FSTATE_VAL3 Float NumberData
FSTATE_VAL4 Float NumberData
FSTATE_VAL5 Float NumberData
FSTATE_VAL6 Float NumberData
FSTATE_VAL7 Float NumberData
FSTATE_VAL8 Float NumberData
GAIN Float NumberData
GAIN_IN_1 Float NumberData
GAIN_IN_2 Float NumberData
GAIN_IN_3 Float NumberData
GOOD_LIM Float NumberData
GRANT_DENY DS-70 StructuredVariable
HARD_TYPES Bit String BitEnumeratorVariable
HI_ALM DS-71 StructuredVariable
HI_BIAS Float NumberData
HI_GAIN Float NumberData
HI_HI_ALM DS-71 StructuredVariable
HI_HI_BIAS Float NumberData
HI_HI_LIM Float NumberData
...