ISO 15745-3:2003

INTERNATIONAL ISO
STANDARD 15745-3
First edition
2003-11-15
Industrial automation systems and
integration — Open systems application
integration framework —
Part 3:
Reference description for
IEC 61158-based control systems
Systèmes d'automatisation industrielle et intégration — Cadres
d'intégration d'application pour les systèmes ouverts —
Partie 3: Description de référence pour les systèmes de contrôle fondés
sur la CEI 61158
Reference number
©
ISO 2003
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.

©  ISO 2003
All rights reserved. Unless otherwise specified, 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 either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO 2003 — All rights reserved

Contents Page
Foreword.v
Introduction .vi
1 Scope.1
2 Normative references.1
3 Terms and definitions.2
4 Abbreviated terms.3
5 Technology specific elements and rules.4
5.1 Integration models and IAS interfaces .4
5.2 Profile templates.4
5.2.1 General.4
5.2.2 Contents and syntax.4
5.2.3 Header.5
5.3 Technology specific profiles .5
6 Device and communication network profiles for IEC61158-based control systems .6
6.1 ControlNet.6
6.1.1 Device profile.6
6.1.2 Communication network profile.8
6.2 PROFIBUS.10
6.2.1 Device profile.10
6.2.2 Communication network profile.10
6.3 P-NET.12
6.3.1 Device profile.12
6.3.2 Communication network profile.13
6.4 WorldFIP.15
6.4.1 Device profile.15
6.4.2 Communication network profile.18
6.5 INTERBUS.25
6.5.1 Device profile.25
6.5.2 Communication network profile.32
Annex A (normative) ControlNet profile templates .36
A.1 General.36
A.2 Device profile template description .37
A.2.1 Device profile template description – XML based.37
A.2.2 Device profile template description – XML encapsulation of EDS files .55
A.3 Communication network profile template description.57
A.3.1 Communication network profile template description – XML based .57
A.3.2 Communication network profile template description – XML encapsulation of EDS files .75
A.4 Electronic Data Sheet (EDS) .76
A.4.1 Common CIP EDS requirements .76
A.4.2 ControlNet specific EDS requirements.116
Annex B (normative)  PROFIBUS profile templates .121
B.1 General.121
B.2 Device profile template description .121
B.2.1 General.121
B.2.2 XML schema: GSD_Device_Profile_wrapper.xsd or EDD_Device_Profile_wrapper.xsd .122
B.3 Communication network profile template description.124
B.3.1 General.124
B.3.2 XML schema: GSD_CommNet_Profile_wrapper.xsd .124
B.4 Generic Station Description (GSD) .125
B.4.1 General. 125
B.4.2 Syntax and format of the GSD files. 126
B.5 Semantic of GSD . 127
B.5.1 Conventions. 127
B.5.2 General specifications. 128
B.5.3 Master-related specifications. 135
B.5.4 Slave-related specifications. 142
B.6 Formal description of GSD. 165
Annex C (normative) P-NET profile templates . 179
C.1 Device profile template description . 179
C.2 Communication network profile template description. 181
Annex D (normative) WorldFIP profile templates . 184
D.1 Device profile template description . 184
D.1.1 Overview. 184
D.1.2 DeviceConformityClass. 184
D.1.3 Device profile template XML schema. 187
D.2 Communication network profile template description. 190
D.2.1 Overview. 190
D.2.2 Application layers. 190
D.2.3 Transport layers; DLConformityClass . 193
D.2.4 Network Management. 194
D.2.5 Communication network profile template XML schema . 196
Annex E (normative) INTERBUS profile templates. 205
E.1 Device profile template description . 205
E.1.1 Overview. 205
E.1.2 Basics. 205
E.1.3 DeviceIdentity object - deviceType object. 207
E.1.4 DeviceManager object. 209
E.1.5 Supplementary element descriptions. 214
E.1.6 Device profile template XML schemas. 217
E.2 Communication network profile template description. 264
Bibliography . 269

iv © ISO 2003 — All rights reserved

Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO
member bodies). The work of preparing International Standards is normally carried out through ISO technical
committees. Each member body interested in a subject for which a technical committee has been established has
the right to be represented on that committee. International organizations, governmental and non-governmental, in
liaison with ISO, also take part in the work. ISO collaborates closely with the International Electrotechnical
Commission (IEC) on all matters of electrotechnical standardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International Standards adopted
by the technical committees are circulated to the member bodies for voting. Publication as an International
Standard requires approval by at least 75 % of the member bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights.
ISO shall not be held responsible for identifying any or all such patent rights.
ISO 15745-3 was prepared by Technical Committee ISO/TC 184, Industrial automation systems and integration,
Subcommittee SC 5, Architecture, communications and integration frameworks.
ISO 15745 consists of the following parts, under the general title Industrial automation systems and integration —
Open systems application integration framework:
— Part 1: Generic reference description
— Part 2: Reference description for ISO 11898-based control systems
— Part 3: Reference description for IEC 61158-based control systems
— Part 4: Reference description for Ethernet-based control systems
Introduction
The application integration framework (AIF) described in ISO 15745 defines elements and rules that facilitate:
 the systematic organization and representation of the application integration requirements using integration

models;
 the development of interface specifications in the form of application interoperability profiles (AIPs) that enable
both the selection of suitable resources and the documentation of the "as built" application.
ISO 15745-1 defines the generic elements and rules for describing integration models and AIPs, together with their
component profiles - process profiles, information exchange profiles, and resource profiles. The context of
ISO 15745 and a structural overview of the constituents of an AIP are given in Figure 1 of ISO 15745-1:2003.
This part of ISO 15745 extends the generic AIF described in ISO 15745-1 by defining the technology specific
elements and rules for describing both communication network profiles and the communication related aspects of
® ® TM
1 2 3 4
device profiles specific to control systems based on IEC 61158 (P-NET , PROFIBUS , WorldFIP , ControlNet , ®
and INTERBUS ). These technologies use profiles of IEC 61158 which are specified in IEC 61784-1. Profiles for
ISO/IEC 8802-3-based control systems are outside the scope of this part of ISO 15745 and are specified in
ISO 15745-4.
In particular, this part of ISO 15745 describes technology specific profile templates for the device profile and the
communication network profile. Within an AIP, a device profile instance or a communication network profile
instance is part of the resource profile defined in ISO 15745-1. The device profile and the communication network
profile XML instance files are included in a resource profile XML instance using the ProfileHandle_DataType as
specified in ISO 15745-1:2003, 7.2.5.
AIFs specified using the elements and rules of ISO 15745-1 can be easily integrated with the component profiles
defined using the elements and rules specified in this part.

P-NET is the registered trademark of the International P-NET User Organisation Aps (IPUO). Control of trademark use is
given to the non profit organisation IPUO. This information is given for the convenience of users of this International Standard
and does not constitute an endorsement by ISO of the trademark holder or any of its products. Compliance to this standard
does not require use of the trademark P-NET. Use of the trademark P-NET requires permission of the IPUO.
PROFIBUS is the trade name of the PROFIBUS Nutzerorganisation e.V. (PNO), control of trade name use is given to the non
profit organisation PNO. This information is given for the convenience of users of this International Standard and does not
constitute an endorsement by ISO of the trademark holder or any of its products. Compliance to this standard does not require
use of the trade name PROFIBUS. Use of the trade name PROFIBUS requires permission of the PNO. ®
WorldFIP is a registered trademark of the WorldFIP Association. Control of trademark use is given to the non profit
organisation WorldFIP Association. This information is given for the convenience of users of this International Standard and
does not constitute an endorsement by ISO of the trademark holder or any of its products. Compliance to this standard does not
require use of the trademark WorldFip. Use of the trademark WorldFIP requires permission of the WorldFIP Association.
ControlNet™ is a trade name of ControlNet International, Ltd. This information is given for the convenience of users of ISO
15745 and does not constitute an endorsement by ISO of the trademark holder or any of its products. Compliance to this
standard does not require use of the trade name ControlNet™. Use of the trade name ControlNet™ requires permission of
ControlNet International, Ltd.
INTERBUS is a trade name of Phoenix Contact GmbH & Co. KG, control of trade name use is given to the non profit
organisation INTERBUS Club. This information is given for the convenience of users of this International Standard and does not
constitute an endorsement by ISO of the trademark holder or any of its products. Compliance to this standard does not require
use of the trade name INTERBUS. Use of the trade name INTERBUS requires permission of the INTERBUS Club.
vi © ISO 2003 — All rights reserved

INTERNATIONAL STANDARD ISO 15745-3:2003(E)

Industrial automation systems and integration — Open systems
application integration framework —
Part 3:
Reference description for IEC 61158-based control systems
1 Scope
This part of ISO 15745 defines the technology specific elements and rules for describing both communication
network profiles and the communication related aspects of device profiles specific to IEC 61158-based control
systems. Profiles for ISO/IEC 8802-3-based control systems are outside the scope of this part of ISO 15745.
NOTE Generic elements and rules for describing integration models and application interoperability profiles, together with
their component profiles (process profiles, information exchange profiles, and resource profiles) are specified in
ISO 15745-1.
This part of ISO 15745 is to be used in conjunction with ISO 15745-1 to describe an application integration
framework.
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.
ISO 639-1:2002, Codes for the representation of names of languages – Part 1: Alpha-2 code
ISO 639-2:1998, Codes for the representation of names of languages – Part 2: Alpha-3 code
ISO 3166-1:1997, Codes for the representation of names of countries and their subdivisions – Part 1: Country
codes
ISO 9506-1:2000, Industrial automation systems – Manufacturing Message Specification – Part 1: Service
definition
ISO 15745-1:2003, Industrial automation and systems integration – Open systems application integration
framework – Part 1: Generic reference description
ISO/IEC 10646-1:2000, Information technology – Universal Multiple-Octet Coded Character Set (UCS) – Part 1:
Architecture and Basic Multilingual Plane
IEC 61131-3:2003, Programmable controllers – Part 3: Programming languages
IEC 61158 (all parts), Digital data communications for measurement and control – Fieldbus for use in industrial
control systems
IEC 61784-1:2003, Digital data communications for measurement and control - Part 1: Profile sets for continuous
and discrete manufacturing relative to fieldbus use in industrial control systems
IEC 61804-2, Function blocks (FB) for process control – Part 2: Specification of FB concept and electronic device
description language (EDDL)
ANSI TIA/EIA-232-F:1997, Interface Between Data Terminal Equipment and Data Circuit-Terminating Equipment
Employing Serial Binary Data Interchange
ANSI TIA/EIA-485-A:1998, Electrical Characteristics of Generators and Receivers for Use in Balanced Digital
Multipoint Systems
EN 50170:1996 Volume 3 Part 7-3, General purpose field communication system – WorldFIP – Network
Management
IEEE Std 754-1985 (R1990), IEEE Standard for Binary Floating Point Arithmetic
REC-xml-20001006, Extensible Markup Language (XML) 1.0 Second Edition – W3C Recommendation 6 October
REC-xmlschema-1-20010502, XML Schema Part 1: Structures – W3C Recommendation 02 May 2001
REC-xmlschema-2-20010502, XML Schema Part 2: Datatypes – W3C Recommendation 02 May 2001
RFC 1738:1994, Uniform Resource Locators (URL) – Internet Engineering Task Force (IETF), Request for
Comments (RFC)
RFC 1759:1995, Printer MIB – Internet Engineering Task Force (IETF), Request for Comments (RFC)
UML V1.4, OMG - Unified Modeling Language Specification (Version 1.4, September 2001)
3 Terms and definitions
NOTE The UML terminology and notation used in this document is described in Annex A of ISO 15745-1:2003.
For the purposes of this document, the terms and definitions given in ISO 15745-1 apply.

Edition 1 to be published
2 © ISO 2003 – All rights reserved

4 Abbreviated terms
AIF Application Integration Framework
AIP Application Interoperability Profile
AL Application Layer
ASCII American Standard Code for Information Interchange (see ISO/IEC 10646)
ASE Application Service Element (see IEC 61158-5)
CIP™  Common Industrial Protocol
CP Communication Profile
CRC Cyclic Redundancy Check
DL Data Link Layer
DP PROFIBUS DP services and protocol
EDD Electronic Device Description
EDDL Electronic Device Description Language
EDS Electronic Data Sheet
FDCML Field Device Configuration Markup Language
FIP Field Industrial Protocol
GSD Generic Station Description
HMI Human Machine Interface
I/O Input and Output
IAS Industrial Automation Systems
ID Identifier
kbit/s 1024 bit/s
LSB Least Significant Bit
MAU Medium Attachment Unit
Mbit/s 1024*1024 bits/s
MCS Messaging Common Services
MMS Manufacturing Messages Specifications (see ISO 9506-1)
MPS Manufacturing Periodic/aperiodic Services
MS1 Master class 1 (see IEC 61784-1:2003)
MS2 Master class 2 (see IEC 61784-1:2003)

CIP™ is a trade name of ControlNet International, Ltd. and Open DeviceNet Vendor Association, Inc. This information is given
for the convenience of users of ISO 15745 and does not constitute an endorsement by ISO of the trademark holder or any of its
products. Compliance to this standard does not require use of the trade name CIP™. Use of the trade name CIP™ requires
permission of either ControlNet International, Ltd. or Open DeviceNet Vendor Association, Inc

NC Numerical Control
NM Network Management
OSI Open System Interconnection
PC Personal Computer
PID Proportional Integration Differentiation controller
PLC Programmable Logic Controller
RC Robot Control
SM_MPS System Management Manufacturing Periodic Specification
SMS System Management Specification
SubMMS Subset of MMS
SWNo Softwire Number
UML Unified Modelling Language (see UML V1.4)
VMD Virtual Managed Device
XML eXtensible Markup Language (see REC-xml-20001006)
5 Technology specific elements and rules
5.1 Integration models and IAS interfaces
The AIP developer shall develop the integration model using the rules described in ISO 15745-1, and shall ensure
that the IEC 61158-based device and communication network profiles (whether representing the interface
requirements or those derived from existing devices/communication networks) include the necessary IAS
interfaces. The IAS interfaces included in the profile shall be identified in the header section (see
ISO 15745-1:2003, 7.2.2).
NOTE IAS interfaces are described in ISO 15745-1:2003, Annex B.
5.2 Profile templates
5.2.1 General
The IEC 61158 technology specific profile templates are derived from the generic profile templates specified in
ISO 15745-1:2003, clause 7.
5.2.2 Contents and syntax
ISO 15745 specifies profile templates that are XML schemas (REC-xmlschema-1-20010502 and REC-xmlschema-
2-20010502) and use a common general structure. The device and communication network profiles based on these
templates typically contain :
 information needed to identify the connected device,
 a description of device data that can be accessed via the network,
 a description of the communication capabilities supported by the device,
 additional vendor-specific information.
4 © ISO 2003 – All rights reserved

However, some IEC 61158 technologies use specific legacy ASCII syntax. Hence, for backward compatibility,
template definitions of any technology (Annex A to Annex E) include all or a relevant subset of the following:
 communication network and device profile templates, as defined in ISO 15745-1,
 ISO 15745 template to encapsulate files with legacy ASCII syntax ("wrapper"),
 legacy ASCII syntax.
5.2.3 Header
The profile template header defined in ISO 15745-1:2003, 7.2.2, is used for IEC 61158 technology specific profile
templates. Each technology uses one or more names to identify the technology or its particular component(s) (see
Table 1). The selected name shall be stored in the ProfileTechnology attribute in the header section.
Table 1 — ProfileTechnology names
ProfileTechnology name Technology
ControlNet ControlNet
CIP ControlNet
EDS ControlNet
GSD PROFIBUS
EDDL PROFIBUS
P-NET P-NET
WorldFIP WorldFIP
INTERBUS INTERBUS
FDCML INTERBUS
5.3 Technology specific profiles
The technology specific communication network profile structure and communication related aspects of device
profile structure based on IEC 61158 fieldbus technologies are described in clause 6. The technologies included
are:
 ControlNet (see 6.1)
 PROFIBUS (see 6.2)
 P-NET (see 6.3)
 WorldFIP (see 6.4)
 INTERBUS (see 6.5).
The related profile template definitions are specified in Annex A to Annex E.
6 Device and communication network profiles for IEC 61158-based control systems
6.1 ControlNet
6.1.1 Device profile
6.1.1.1 General
Figure 1 shows the class structure of the ControlNet device profile.
DeviceProfile
DeviceIdentity
ApplicationProcess
0.*
DeviceManager
0.1
Assembly
0.*
Parameter
DeviceFunction
1.* 0.*
ParameterGroup
0.*
Figure 1 — ControlNet device profile class diagram
The available formats for ControlNet device profiles are described in A.2.
The XML schema representing the ControlNet device profile template is defined in A.2.1.3.3. The file name of this
XML schema shall be “CIP_Device_Profile.xsd”.
NOTE The ControlNet device profile class diagram shown in Figure 1 defines the main classes. These classes are further
decomposed ; details are defined in Annex A.
The XML schema representing the encapsulation of a legacy ControlNet EDS into the ISO 15745 device profile
template is defined in A.2.2.2. The file name of this XML schema shall be “EDS_Device_Profile_wrapper.xsd”. The
legacy EDS ASCII syntax itself is described in A.4.
6.1.1.2 Device identity
The DeviceIdentity class contains attributes which uniquely identify the device, and supports services which allow
the retrieval of this information from the device.
These attributes provide in particular:
 manufacturer's identification (name and identification code);
 device identification (device type, product name, revision, serial number);
 device classification;
 location of storage of additional information (e.g. icons).
6 © ISO 2003 – All rights reserved

6.1.1.3 Device manager
The DeviceManager class contains attributes and supports services used to monitor and configure the device.
These attributes provide in particular:
 revision of the ControlNet identity object;
 information on device structure (for devices integrated in a modular system).
Services allow:
 device reset;
 retrieval of DeviceManager attributes.
6.1.1.4 Device function
The DeviceFunction class contains attributes and supports services which enable the management (e.g.
configuration) of a function of the device.
EXAMPLE  Examples of DeviceFunction objects are Overload, Presence Sensing, Analogue Input, and Discrete Output
objects.
NOTE The DeviceFunction class is not defined in ISO 15745-3.
6.1.1.5 Application process
Figure 2 shows the class structure of the ApplicationProcess class.
ApplicationProcess
0.1
0.1 0.1
Assembly Parameter ParameterGroup
AssemblyClass ParameterClass Group
0.1 0.1 0.*
AssemblyInstance ParameterInstance
0.1 0.1
Assem Param
0.* 0.*
Figure 2 — ControlNet ApplicationProcess class diagram
The Assembly class assembles several application process data items into a single block for optimisation of
communications. The Parameter class provides a standardized interface for accessing individual application
process data items. The ParameterGroup class specifies groups of related parameters for a specific purpose (e.g.
configuration, monitoring).
The Assembly class and the Parameter class support attributes and services both at the class and instance levels.
The Assem, Param and Group classes specify individual instances of the main classes.
NOTE The Assembly class and the Parameter class correspond to the ControlNet Assembly object and Parameter object.
The Assembly object is fully specified in IEC 61158-5:2003 and IEC 61158-6:2003 (Type 2).
6.1.2 Communication network profile
6.1.2.1 General
Figure 3 shows the class structure of the ControlNet communication network profile.
CommNetworkProfile
1 0.1
ApplicationLayers TransportLayers NetworkManagement
0.1
NM-ControlNetObject
1 1
ConnectionManager CNPhysicalLayer
0.1
1 1 NM-ConnectionManager
MessageRouter CNLinkLayer
0.1
1 NM-MessageRouter
ControlNetObject
0.1
Keeper
0.1
Ports
0.1
ControlNetScheduling
Figure 3 — ControlNet communication network profile class diagram
The available formats for ControlNet communication network profiles are described in A.3.
The XML schema representing the ControlNet communication network profile template is defined in A.3.1.3. The
file name of this XML schema shall be “CNet_CommNet_Profile.xsd”.
The XML schema representing the encapsulation of a legacy ControlNet EDS into the ISO 15745 communication
network profile template is defined in A.3.2.2. The file name of this XML schema shall be
“EDS_CommNet_Profile_wrapper.xsd”. The legacy EDS ASCII syntax itself is described in A.4.
6.1.2.2 Application layers
The ControlNet ApplicationLayers class represents the combined profiles for the upper 3 OSI layers of the
ControlNet communication network integration model.
It is further divided into several classes, as shown in Figure 3:
 ConnectionManager defines the properties associated with connections and connection management;
 MessageRouter defines the properties associated with internal message routing in the device.
NOTE The corresponding Connection Manager object and Message Router object are fully specified in IEC 61158-5:2003
and IEC 61158-6:2003 (Type 2).
8 © ISO 2003 – All rights reserved

6.1.2.3 Transport layers
The ControlNet TransportLayers class represents the combined profiles for the lower 4 OSI layers of the
ControlNet communication network integration model.
It is further divided into several classes, as shown in Figure 3:
 CNPhysicalLayer identifies the physical layer characteristics (e.g. connectors, delays);
 CNLinkLayer and ControlNetObject define the properties associated with data link layer configuration and
monitoring;
 Ports identifies the device ports which are able to route messages from one link to another link.
NOTE The corresponding ControlNet object is fully specified in IEC 61158-4:2003 (Type 2).
6.1.2.4 Network management
The ControlNet NetworkManagement class represents the network configuration and performance adjustment
capabilities of the ControlNet communication network integration model.
It is further divided into several classes, as shown in Figure 3:
 Keeper defines the properties associated with network management;
 ControlNetScheduling defines the properties associated with allocation of scheduled transmission time;
 NM-ConnectionManager , NM-MessageRouter and NM-ControlNetObject define the properties associated with
class management of the corresponding objects.
NOTE The corresponding Keeper object and ControlNet Scheduling object are fully specified in IEC 61158-4:2003
(Type 2).
6.2 PROFIBUS
6.2.1 Device profile
Figure 4 shows the class structure of the PROFIBUS device profile.
DeviceProfile
DeviceIdentity
0.1
ApplicationProcess
0.*
DeviceManager
0.1
DeviceFunction
1.*
Figure 4 — PROFIBUS device profile class diagram
The class information for DeviceIdentity, DeviceManager, and ApplicationProcess is given by the legacy device
profile format EDD and GSD.
The DeviceFunction class contains attributes and supports services which enable the management (e.g.
configuration) of a function of the device.
EXAMPLE  Examples of DeviceFunction objects are Analogue Input, and Discrete Output objects.
NOTE The DeviceFunction class is not defined in ISO 15745-3.
The available formats for PROFIBUS device profiles are described in B.2.
The XML schema representing the encapsulation of a legacy EDD and GSD of a PROFIBUS device into the
ISO 15745 device profile template is defined in B.2. The file name of this XML schema shall be
“EDDL_Device_Profile_wrapper.xsd” or “GSD_Device_Profile_wrapper.xsd”. The legacy EDDL ASCII syntax itself
is described in IEC 61804-2, using the PROFIBUS profile of IEC 61804-2: Ed.1, F.2.
Simple devices, which do not have the need to have an EDD, shall reference the GSD.
Equivalences of the classes DeviceIdentity, DeviceManager, and ApplicationProcess are defined in IEC 61804-2 or
in the case of referencing an GSD in B.4.
6.2.2 Communication network profile
6.2.2.1 General
Figure 5 shows the class structure of the PROFIBUS communication network profile.
10 © ISO 2003 – All rights reserved

CommNetworkProfile
1 0.1
ApplicationLayers TransportLayers NetworkManagement

Figure 5 — PROFIBUS communication network profile class diagram
The available formats for PROFIBUS communication network profiles are described in B.3.
The file name of this XML schema shall be “GSD_CommNet_Profile.xsd”.
The XML schema representing the encapsulation of a legacy GSD of PROFIBUS devices into the ISO 15745
communication network profile template is defined in B.3. The file name of this XML schema shall be
“GSD_CommNet_Profile_wrapper.xsd”. The legacy GSD ASCII syntax itself is described in B.4 and B.5.
6.2.2.2 Application layers
The PROFIBUS ApplicationLayers class represents the combined profiles for the upper 3 OSI layers of the
PROFIBUS communication network integration model, see IEC 61784-1:2003 CP3/1 and CP3/2, especially the
subclauses for AL protocol and AL service.
6.2.2.3 Transport layers
The PROFIBUS TransportLayers class represents the combined profiles for the lower 4 OSI layers of the
PROFIBUS communication network integration model, see IEC 61784-1:2003 CP3/1 and CP3/2, especially the
subclauses for DL protocol and DL service.
6.2.2.4 Network management profile
The NetworkManagement profile class represents the network configuration and performance adjustment
capabilities of the PROFIBUS communication network integration model.
6.3 P-NET
6.3.1 Device profile
Variables in P-NET devices are normally organised into Channels. A Channel is a collection of related variables
and functions for a single process signal. A Channel can hold up to 16 registers, each having its own SoftWire
number (SWNo). The contents of these registers can be of any data type, including complex structures, such as
multi-dimensional arrays and databases.
At least one Channel, the ServiceChannel, shall be present in every P-NET device. The ServiceChannel contains
information used for making easy service on the device, e.g. a Globally Unique Identifier (GUID), error information,
etc. Any other Channels that are included in a device depend on the device type. A device can consist of multiples
of the same Channel type and/or a mixture of different Channel types.
EXAMPLE 1  Examples of various standardised Channel types include: Digital Input, Digital Output, Analogue
measurement, PID, etc. Additional Channel types are user definable.
A P-NET device profile shall describe all network accessible variables and channels in the device in the
ApplicationProcess object. The device profile also includes objects for device management and identification (see
Figure 6).
DeviceProfile
1 1.*
DeviceManager ApplicationProcess
NumberOfSWNo
Revision
ChError
SWNoType
GUID SWNoType
0.*
1 1 1
Channel
ServiceChannel
Reset PrimaryValue
SWNoType SWNoType
Name
TypeName
1 1
WriteEnable ChConfig
SWNoType SWNoType
1 1
CHType Maintenance
SWNoType SWNoType
DeviceIdentity
1 1
CommandError ChType
DeviceNumber
ProgramVersion
SWNoType SWNoType
ManufacturerNo
Manufacturer
SWNo SWNo
0.9 0.11
SWNoType SWNoType
DeviceFunction
SWNo
0.*
SWNoType
Figure 6 — P-NET device profile class diagram
EXAMPLE 2 Examples of Device Function objects are Flowmeter, Controller, Analogue Input 4-20 mA, Digital I/O objects.
12 © ISO 2003 – All rights reserved

NOTE In P-NET, there are no special services for accessing properties of the DeviceFunction, DeviceManager and
DeviceIdentity objects. Instead, these properties can be mapped to the ApplicationProcess objects, and accessed
from the network by using the Application Protocol Data Unit (APDU) specified in the P-NET ApplicationLayers
class (see 6.3.2.2).
Attributes and sub-classes for the device profile classes are detailed in C.1, which specifies the XML schemas
required for device profiles. The file name of the XML schema shall be "P-NetDeviceProfile.XSD".
6.3.2 Communication network profile
6.3.2.1 General
Figure 7 shows the class structure of the P-NET communication network profile.
CommNetworkProfile
APDU
TransportLayers ApplicationLayers
APDU Header
APDU body
1.* 1
PhysicalLayer NetworkManagement
ElectricalStandard
Baudrate
PortNo
Name
DataLinkLayer
ErrorDetection
Figure 7 — P-NET communication network profile class diagram
The XML schema representing the P-NET communication network profile is defined in C.2. The file name of the
XML schema shall be "P-NetCommNetworkProfile.XSD".
6.3.2.2 Application layers
The application layer of a P-NET device shall always provide the services and protocol elements needed for
accessing the variables defined in the P-NET device profile. The services and protocol elements are represented in
an APDU.
6.3.2.3 Transport layers
6.3.2.3.1 General
The TransportLayers class shall represent the combined profiles for the lower 4 OSI layers of the communication
network integration model. The TransportLayers object is composed of one or more PhysicalLayer objects (one for
each physical port) and a DataLinkLayer object.
{At least 1}
6.3.2.3.2 PhysicalLayer
The PhysicalLayer object(s) shall specify the supported electrical standard and baud rate(s). Valid electrical
standards are RS485 and RS232. Valid baud rates for RS232 are 1200, 2400, 4800, 9600, 19200, and 38400
bits/sec. For RS485 the only valid baud rate is 76800 bits/sec.
6.3.2.3.3 DataLinkLayer
The Data-Link layer of a P-NET device shall always provide the protocol elements needed according to the device
class, specified by the NetworkManagement object. Valid device classes are Slave, Simple nod
...