Licensed Copy: athen reading, Reading University Library, 23/01/2010 05:47, Uncontrolled Copy, (c) BSI BS EN 62453-303-2:2009 BSI Standards Publication Field device tool (FDT) interface specification — Part 303-2: Communication profile integration — IEC 61784 CP 3/4, CP 3/5 and CP 3/6 NO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAW raising standards worldwide™ BRITISH STANDARD Licensed Copy: athen reading, Reading University Library, 23/01/2010 05:47, Uncontrolled Copy, (c) BSI BS EN 62453-303-2:2009 National foreword This British Standard is the UK implementation of EN 62453-303-2:2009 It is identical to IEC 62453-303-2:2009 The UK participation in its preparation was entrusted to Technical Committee AMT/7, Industrial communications: process measurement and control, including fieldbus A list of organizations represented on this committee can be obtained on request to its secretary This publication does not purport to include all the necessary provisions of a contract Users are responsible for its correct application © BSI 2010 ISBN 978 580 62563 ICS 25.040.40; 35.100.05; 35.110 Compliance with a British Standard cannot confer immunity from legal obligations This British Standard was published under the authority of the Standards Policy and Strategy Committee on 31 January 2010 Amendments issued since publication Amd No Date 标准分享网 www.bzfxw.com 免费下载 Text affected Licensed Copy: athen reading, Reading University Library, 23/01/2010 05:47, Uncontrolled Copy, (c) BSI BS EN 62453-303-2:2009 EUROPEAN STANDARD EN 62453-303-2 NORME EUROPÉENNE October 2009 EUROPÄISCHE NORM ICS 25.040.40; 35.100.05; 35.110 English version Field device tool (FDT) interface specification Part 303-2: Communication profile integration IEC 61784 CP 3/4, CP 3/5 and CP 3/6 (IEC 62453-303-2:2009) Spécification des interfaces des outils des dispositifs de terrain (FDT) Partie 303-2: Intégration des profils de communication CEI 61784 CP 3/4, CP 3/5 et CP 3/6 (CEI 62453-303-2:2009) Field Device Tool (FDT)Schnittstellenspezifikation Teil 303-2: Integration von Kommunikationsprofilen Kommunikationsprofile (CP) 3/4, 3/5 und 3/6 nach IEC 61784 (IEC 62453-303-2:2009) ｗｗｗ．ｂｚｆｘｗ．ｃｏｍ This European Standard was approved by CENELEC on 2009-08-01 CENELEC members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the Central Secretariat or to any CENELEC member This European Standard exists in three official versions (English, French, German) A version in any other language made by translation under the responsibility of a CENELEC member into its own language and notified to the Central Secretariat has the same status as the official versions CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Cyprus, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and the United Kingdom CENELEC European Committee for Electrotechnical Standardization Comité Européen de Normalisation Electrotechnique Europäisches Komitee für Elektrotechnische Normung Central Secretariat: Avenue Marnix 17, B - 1000 Brussels © 2009 CENELEC - All rights of exploitation in any form and by any means reserved worldwide for CENELEC members Ref No EN 62453-303-2:2009 E Licensed Copy: athen reading, Reading University Library, 23/01/2010 05:47, Uncontrolled Copy, (c) BSI BS EN 62453-303-2:2009 EN 62453-303-2:2009 -2- Foreword The text of document 65E/128/FDIS, future edition of IEC 62453-303-2, prepared by SC 65E, Devices and integration in enterprise systems, of IEC TC 65, Industrial-process measurement, control and automation, was submitted to the IEC-CENELEC parallel vote and was approved by CENELEC as EN 62453-303-2 on 2009-08-01 Each part of the EN 62453-3xy series is intended to be read in conjunction with EN 62453-2 The following dates were fixed: – latest date by which the EN has to be implemented at national level by publication of an identical national standard or by endorsement (dop) 2010-05-01 – latest date by which the national standards conflicting with the EN have to be withdrawn (dow) 2012-08-01 Annex ZA has been added by CENELEC Endorsement notice The text of the International Standard IEC 62453-303-2:2009 was approved by CENELEC as a European Standard without any modification In the official version, for Bibliography, the following note has to be added for the standard indicated: IEC 61158 ｗｗｗ．ｂｚｆｘｗ．ｃｏｍ NOTE Harmonized in EN 61158 series (not modified) 标准分享网 www.bzfxw.com 免费下载 Licensed Copy: athen reading, Reading University Library, 23/01/2010 05:47, Uncontrolled Copy, (c) BSI -3- BS EN 62453-303-2:2009 EN 62453-303-2:2009 Annex ZA (normative) Normative references to international publications with their corresponding European publications 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 NOTE When an international publication has been modified by common modifications, indicated by (mod), the relevant EN/HD applies Publication Year Title EN/HD Year IEC 61158-5-10 – 1) IEC 61158-6-10 – 1) Industrial communication networks Fieldbus specifications Part 6-10: Application layer protocol specification - Type 10 elements IEC 61784-2 – 1) EN 61784-2 Industrial communication networks Profiles Part 2: Additional fieldbus profiles for real-time networks based on ISO/IEC 8802-3 2008 IEC 62453-1 2009 Field device tool (FDT) interface specification - EN 62453-1 Part 1: Overview and guidance 2009 2009 Field device tool (FDT) interface specification - EN 62453-2 Part 2: Concepts and detailed description 2009 IEC 62453-2 EN 61158-5-10 Industrial communication networks Fieldbus specifications Part 5-10: Application layer service definition Type 10 elements 2008 2) 2008 2) 2) EN 61158-6-10 ｗｗｗ．ｂｚｆｘｗ．ｃｏｍ 1) Undated reference 2) Valid edition at date of issue Licensed Copy: athen reading, Reading University Library, 23/01/2010 05:47, Uncontrolled Copy, (c) BSI BS EN 62453-303-2:2009 –2– 62453-303-2 © IEC:2009(E) CONTENTS INTRODUCTION Scope .7 Normative references .7 Terms, definitions, symbols, abbreviated terms and conventions 3.1 3.2 3.3 Terms and definitions Abbreviated terms Conventions 3.3.1 Data type names and references to data types 3.3.2 Vocabulary for requirements 3.3.3 Use of UML Bus category Access instance and device data 5.1 Process Channel objects provided by DTM 5.2 DTM services to access instance and device data Protocol specific behavior .9 Protocol specific usage of general data types Protocol specific common data types 11 Network management data types 11 ｗｗｗ．ｂｚｆｘｗ．ｃｏｍ 9.1 General 11 9.2 Parameter access data types 11 10 Communication data types 17 11 Channel parameter data types 20 12 Device identification 23 12.1 Protocol specific handling of data type STRING 23 12.2 Device type identification data types 23 12.3 Topology scan data types 26 12.4 Scan identification data types 27 12.5 Device type identification data types 29 Bibliography 32 Figure – Part 303-2 of the IEC 62453 series Table – Protocol identifier Table – Physical layer identifier Table – Protocol specific usage of general data types Table – Simple parameter access data types 11 Table – Structured parameter access data types 14 Table – Simple communication data types 17 Table – Structured communication data types 18 Table – Simple channel parameter data types 21 Table – Structured channel parameter data types 22 Table 10 – Identification data types for PROFINET with pure DCP 24 标准分享网 www.bzfxw.com 免费下载 Licensed Copy: athen reading, Reading University Library, 23/01/2010 05:47, Uncontrolled Copy, (c) BSI BS EN 62453-303-2:2009 62453-303-2 © IEC:2009(E) –3– Table 11 – Identification data types for PROFINET with I&M 25 Table 12 – Simple identification data types with protocol independent semantics 26 Table 13 – Structured identification data types with protocol independent semantics 26 Table 14 – Simple device type identification data types 26 Table 15 – Structured device type identification data type 27 Table 16 – Simple scan identification data types 27 Table 17 – Structured scan identification data types 28 Table 18 – Structured device type identification data types 29 ｗｗｗ．ｂｚｆｘｗ．ｃｏｍ Licensed Copy: athen reading, Reading University Library, 23/01/2010 05:47, Uncontrolled Copy, (c) BSI BS EN 62453-303-2:2009 –6– 62453-303-2 © IEC:2009(E) INTRODUCTION This part of IEC 62453 is an interface specification for developers of FDT (Field Device Tool) 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 need to interoperate seamlessly With the integration of fieldbusses into control systems, there are a few other tasks which need to be performed In addition to fieldbus- and device-specific tools, there is a need to integrate these 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 kinds of fieldbusses and thus meets the requirements for integrating different kinds of devices into heterogeneous control systems Figure shows how IEC 62453-303-2 is aligned in the structure of the IEC 62453 series ｗｗｗ．ｂｚｆｘｗ．ｃｏｍ Part 303-2 Communication profile integration – IEC 61784 CP 3/4, CP 3/5 and CP 3/6 IEC 1132/09 Figure – Part 303-2 of the IEC 62453 series 标准分享网 www.bzfxw.com 免费下载 Licensed Copy: athen reading, Reading University Library, 23/01/2010 05:47, Uncontrolled Copy, (c) BSI BS EN 62453-303-2:2009 62453-303-2 © IEC:2009(E) –7– FIELD DEVICE TOOL (FDT) INTERFACE SPECIFICATION – Part 303-2: Communication profile integration – IEC 61784 CP 3/4, CP 3/5 and CP 3/6 Scope Communication Profile 3/4, Communication Profile 3/5 and Communication Profile 3/6 (commonly known as PROFINET® IO) define communication profiles based on IEC 61158-5-10 and IEC 61158-6-10 The basic profiles CP 3/4, CP 3/5, and CP 3/6 are defined in IEC 61784-2 This part of IEC 62453 provides information for integrating the PROFINET® technology into the FDT interface (IEC 62453-2) This part of the IEC 62453 specifies communication and other services This specification neither contains the FDT specification nor modifies it Normative references ｗｗｗ．ｂｚｆｘｗ．ｃｏｍ The following referenced documents are indispensable for the application of this specification For dated references, only the edition cited applies For undated references, the latest edition of the referenced document (including any amendments) applies IEC 61158-5-10, Industrial communication networks – Fieldbus specifications – Part 5-10: Application layer service definition – Type 10 elements IEC 61158-6-10, Industrial communication networks – Fieldbus specifications – Part 6-10: Application layer protocol specification – Type 10 elements IEC 61784-2 Industrial communication networks - Profiles - Part 2: Additional fieldbus profiles for real-time networks based on ISO/IEC 8802-3 IEC 62453-1:2009, guidance Field Device Tool (FDT) interface specification – Part 1: Overview and IEC 62453-2:2009, Field Device Tool (FDT) interface specification – Part 2: Concepts and detailed description 3.1 Terms, definitions, symbols, abbreviated terms and conventions Terms and definitions For the purposes of this document, the terms and definitions given in IEC 62453-1 and IEC 62453-2 apply ————————— PROFINET ® is the trademark of PROFIBUS Nutzerorganisation e.V (PNO) PNO is a non-profit trade organization to support the fieldbus PROFIBUS This information is given for the convenience of users of this International Standard and does not constitute an endorsement by IEC of the trademark holder or any of its products Compliance to this profile does not require use of the registered trademark Use of the trademark PROFIBUS and PROFINET requires permission of the trade name holder Licensed Copy: athen reading, Reading University Library, 23/01/2010 05:47, Uncontrolled Copy, (c) BSI BS EN 62453-303-2:2009 62453-303-2 © IEC:2009(E) –8– 3.2 Abbreviated terms For the purposes of this document, the abbreviations given in IEC 62453-1 and IEC 62453-2 and the following apply AR Application Relation DCP Discovery and basic Configuration Protocol GSDML Generic Station Description Markup Language IOCS IO Consumer Status IOPS IO Provider Status UML Unified Modeling Language 3.3 Conventions 3.3.1 Data type names and references to data types The conventions for naming and referencing of data types are explained in IEC 62453-2, Clause A.1 3.3.2 Vocabulary for requirements The following expressions are used when specifying requirements Usage of “shall” or “mandatory” No exceptions allowed Usage of “should” or “recommended” Strong recommendation It may make sense in special exceptional cases to differ from the described behaviour Usage of “can’ or “optional’ Function or behaviour may be provided, depending on defined conditions 3.3.3 ｗｗｗ．ｂｚｆｘｗ．ｃｏｍ Use of UML Figures in this document are using UML notation as defined in Annex A of IEC 62453-1 Bus category IEC 61784 CP 3/4, CP 3/5 and CP 3/6 protocols are identified in the protocolId element of the structured data type 'fdt:BusCategory' by the following unique identifier as defined in Table 1: Table – Protocol identifier Identifier value ProtocolId name DFC98364-DAB8-493B-BB92-23B3F92FEBCD Description ‘Profinet IO’ Support of IEC 61784 CP 3/4, CP 3/5 and CP 3/6 protocols IEC 61784 CP 3/4, CP 3/5 and CP 3/6 use the following unique identifier for its physical layers Table – Physical layer identifier PhysicalLayer element Description 99C36176-E59A-11DA-9023-0002B3ECDCBE 10BASET 99C36177-E59A-11DA-9023-0002B3ECDCBE 10BASETXHD 99C36178-E59A-11DA-9023-0002B3ECDCBE 10BASETXFD 99C36179-E59A-11DA-9023-0002B3ECDCBE 100BASETXHD 99C3617A-E59A-11DA-9023-0002B3ECDCBE 100BASETXFD 标准分享网 www.bzfxw.com 免费下载 Licensed Copy: athen reading, Reading University Library, 23/01/2010 05:47, Uncontrolled Copy, (c) BSI BS EN 62453-303-2:2009 62453-303-2 © IEC:2009(E) – 20 – Data type Definition Elementary data types WriteResponse SequenceBegin SequenceEnd U s a g e Multiplicity subSlot M [1 1] index M [1 1] fdt:CommunicationData M [1 1] STRUCT Describes the communication response for a write request according to the PROFINET specification communicationReference M [1 1] addData1 O [0 1] addData2 O [0 1] ResponseError O [0 1] sequenceTime O [0 1] delayTime O [0 1] communicationReference M [1 1] STRUCT Describes the sequence begin STRUCT Describes the sequence end communicationReference SequenceStart Description M [1 1] STRUCT Describes the sequence start ｗｗｗ．ｂｚｆｘｗ．ｃｏｍ communicationReference M [1 1] Handling of errors during connect and disconnect If an errors occurs during a PROFINET connect or disconnect request, the Communication Channel shall return a fdt:CommunicationError The error coding shall be done in the fdt:errorCode attribute The fdt:errorCode shall contain the PROFINET error information “ErrorDecode”, “ErrorCode1”, “ErrorCode2” in exactly this sequence 11 Channel parameter data types It is up to a DTM whether it provides any channels If a DTM allows a Frame Application, other DTMs, or a controller the direct access to its process values via PROFINET protocol, it should provide channel objects as described in this clause Only the complete description of all channels belonging to an PROFINET process value allows proper access for external applications The description of channels, especially of the process values, allows the Frame Application to support the device in a more efficient way A DTM shall provide all channels including IOPS and IOCS channels The channel collection exposed by the DTM describes the complete IO data structure The channel schema supports cyclic and acyclic data exchange The difference is made by using the data types IODataAddress or RecordDataAddress The data types are used at GetChannelParameters service and SetChannelParameters services The information returned by the GetChannelParameters service describes how to access an I/O value via PROFINET protocol (see Table and Table 9) 标准分享网 www.bzfxw.com 免费下载 Licensed Copy: athen reading, Reading University Library, 23/01/2010 05:47, Uncontrolled Copy, (c) BSI BS EN 62453-303-2:2009 62453-303-2 © IEC:2009(E) – 21 – The data types described in this clause are defined for the following namespace Namespace: pniochannel Table – Simple channel parameter data types Data type Definition Description api UDINT This data type belongs to the channel address data types according to the PROFINET specification for channels accessible via PROFINET The api value is set by the PROFINET controller during channel assignment bitLength UDINT This data type specifies the number of bits used for a specific IO signal that might be a “bitArea bitOffset UDINT Address information allows accessing single IO signal values inside a “DataItem” inside cyclic communicated data The data type can also specify the address of an acyclically exchanged parameter (ParameterRecord-DataItem/ Ref) according to the GSDML specification byteOffset UDINT The data type specifies the address of an acyclically exchanged parameter (ParameterRecordDataItem/ Ref) according to the GSDML specification frameApplicationTag STRING Frame Application specific tag used for identification and navigation The DTM should display this tag at channel specific user interfaces gatewayBusCategory UUID Unique identifier for a supported bus type like PROFINET according to the FDT specific CATID index UINT Address information according to the PROFINET specification for parameter access via acyclic read / write communication service number ｗｗｗ．ｂｚｆｘｗ．ｃｏｍ UDINT The data type represents the channel number according to PROFINET specification The address information is used for IO data access and for diagnosis according to the Profinet specification for channels accessible via Profinet alarm message The attribute is set by the DTM during device configuration protectedByChannelAssignment BOOL TRUE if the channel is set to read only by the Frame Application Usually set to TRUE if a channel assignment exists statusChannelType enumeration ( IOCS | IOPS ) Allowed values IOCS and IOPS slotNumber UINT Address information according to the PROFINET specification for channels accessible via cyclic and acyclic communication service subSlotNumber UINT Address information according to the PROFINET specification for channels accessible via cyclic and acyclic communication service Licensed Copy: athen reading, Reading University Library, 23/01/2010 05:47, Uncontrolled Copy, (c) BSI BS EN 62453-303-2:2009 62453-303-2 © IEC:2009(E) – 22 – Table – Structured channel parameter data types Data type Definition Elementary data types IODataAddress U s a g e Multiplicity STRUCT The address for IO data access bitOffset RecordDataAddress FDTChannel Description M [1 1] STRUCT The address information that allows accessing parameter data index M [1 1] bitOffset M [1 1] byteOffset M [1 1] STRUCT Description of the channel fdt:tag M [1 1] fdt:id M [1 1] fdt:descriptor O [0 1] protectedByChannelAssignment M [1 1] number M [1 1] api M [1 1] slotNumber M [1 1] subSlotNumber M [1 1] fdt:dataType M [1 1] bitLength M [1 1] fdt:signalType M [1 1] frameApplicationTag O [0 1] appId:applicationId O [0 1] fdt:SemanticInformation O [0 1] fdt:BitEnumeratorEntries O [0 1] fdt:EnumeratorEntries O [0 1] fdt:Unit O [0 1] IODataAddress O [0 1] RecordDataAddress O [0 1] fdt:Alarms O [0 1] fdt:Ranges O [0 1] fdt:SubstituteValue O [0 1] fdt:Deadband O [0 1] ｗｗｗ．ｂｚｆｘｗ．ｃｏｍ FDTChannelType STRUCT Description of the channel component in case of channels with gateway functionality fdt:VersionInformation M [1 1] gatewayBusCategory O [0 1] statusChannelType O [0 1] 标准分享网 www.bzfxw.com 免费下载 Licensed Copy: athen reading, Reading University Library, 23/01/2010 05:47, Uncontrolled Copy, (c) BSI BS EN 62453-303-2:2009 62453-303-2 © IEC:2009(E) – 23 – 12 Device identification There are different PROFINET specific identification elements An PROFINET scan may detect different device types: PROFINET devices supporting PROFINET I&M record data and devices supporting only pure DCP identification The following rule shall be applied for PROFINET Communication Channels: • if I&M record data is available, create an I&M identification element; • otherwise create a DCP identification element 12.1 Protocol specific handling of data type STRING PROFINET char array rules • In all strings based on char ranges defined in the field bus protocol specification, the leading spaces are left trimmed The char array is to be filled with 0x20h (blank) • In VisibleStrings, invisible characters provided by a device have to be replaced by ‘?’ Characters within VisibleStrings, which are not defined in the bit ASCII/ANSI character set, are considered to be invisible 12.2 Device type identification data types The PROFINET device type identification data types provide general data types with a protocol specific semantic (see Table 10 and Table 11) as well as data types without such a mapping (see Table 12) ｗｗｗ．ｂｚｆｘｗ．ｃｏｍ The data types described in this clause are defined for the following namespace Namespace: pnioident IdAddress nameOfStation IdManufacturer IdDeviceRole ManufacturerSpecificExtension manufacturerId deviceRole manufacturer SpecificExtension 标准分享网 www.bzfxw.com 免费下载 DCP Get, Device Properties/ Manufacturer specific DCP Get, Device Properties/Device-role DCP Get DCP Get, Device Properties/Device-ID DCP Get IP Option, Device Properties Option For all DCP devices: “protocol_DCP” Data request in physical device ｗｗｗ．ｂｚｆｘｗ．ｃｏｍ Manufacturer SpecificString DeviceRoleDe tails DeviceVendor Value DeviceIdentNumber enumeration ( ProfinetIO_Controller | ProfinetIO_Device | ProfinetIO_MultiDevice | ProfinetIO_Supervisor ) UINT UINT OctetString[ STRING Size according to DCPBlockLe ngth] Unsigned8 Unsigned16 Unsigned16 Octets Visible String Octets Visible String Octets Visible String Octets Visible String STRING [263] 240 Octets Visible String NameOfStatio n, IPparameter, Subnet Mask, Standard Gateway, MAC address FDT data type (display Format) enumeration ( protocol_DCP | protocol_IM ) PROFINET Data Format Protocol Protocol specific name Specification reference The semantic element “IdAddress” (string data type) consists after the XSL transformation of several PROFINET attributes These attributes shall be separated by a semicolon “;” within the string and ordered in the following sequence: IdTypeId deviceTypeId macAddress ipDefaultGateway ipSubnetMask ipAddress IdBusProtocol Semantic element name busProtocol PROFINET Attribute Table 10 – Identification data types for PROFINET with pure DCP Licensed Copy: athen reading, Reading University Library, 23/01/2010 05:47, Uncontrolled Copy, (c) BSI – 24 – 62453-303-2 © IEC:2009(E) BS EN 62453-303-2:2009 Semantic element name Data request in physical device Protocol specific name ｗｗｗ．ｂｚｆｘｗ．ｃｏｍ IdSoftwareRevision IdHardwareRevision softwareRevision hardwareRevision I&M Element I&M Element profileID profileSpecificType I&M Element I&M Element I&M Element IdSerialNumber serialNumber For all I&M devices: “protocol_IM” I&M Element IdBusProtocol orderId busProtocol IM_Profile_Specific_Type IM_Profile_ID IM_Hardware_Revision IM_Software_Revision IM_Serial_Number OrderID IdAdress, IdManufacturer, IdTypeID, IdDeviceRole, ManufacturerSpecificExtension as defined in Table 10 PROFINET Attribute Unsigned16 Unsigned16 Unsigned16 Octets – Char + Unsigned8 e.g V1.3.0 16 Octets Visible String 20 Octets Visible String PROFINET Data Format Table 11 – Identification data types for PROFINET with I&M Example: IdAddress=“theName;192.16.16.37;255.255.255.0;192.16.16.1;02:00:4C:4F:4F:50” “nameOfStation;ipAddress;ipSubnetMask;ipDefaultGateway;macAddress” UINT UINT UINT STRING STRING[16] STRING[20] enumeration ( protocol_DCP | protocol_IM ) FDT data type (display format) Specification reference Licensed Copy: athen reading, Reading University Library, 23/01/2010 05:47, Uncontrolled Copy, (c) BSI 62453-303-2 © IEC:2009(E) BS EN 62453-303-2:2009 – 25 – Licensed Copy: athen reading, Reading University Library, 23/01/2010 05:47, Uncontrolled Copy, (c) BSI BS EN 62453-303-2:2009 62453-303-2 © IEC:2009(E) – 26 – Table 12 – Simple identification data types with protocol independent semantics Data type Definition Description idDTMSupportLevel enumeration ( genericSupport | profileSupport | blockspecificProfileSupport | specificSupport | identSupport ) enumeration genericSupport profileSupport blockspecificProfileSupport specificSupport match STRING Used by Device DTM to define a regular expression which shall match to scanned physical define identification information nomatch STRING Used by Device DTM to define a regular expression which shall not match to scanned physical define identification information Used by Device DTM to indicate if identification information may not match Table 13 – Structured identification data types with protocol independent semantics Elements Definition Elementary data types RegExpr Usage Description Multiplicity STRUCT Includes regular expression string – either for match or for nomatch ｗｗｗ．ｂｚｆｘｗ．ｃｏｍ 12.3 match O [0 1] nomatch O [0 1] Topology scan data types This data type is used at scan service response The data types describe one entry in the list of scanned devices (see Table 14 and Table 15) The data types described in this subclause are defined for the following namespace Namespace: fdtpniodevice Table 14 – Simple device type identification data types Data type Definition Description deviceRole enumeration (IO_Controller | IO_Device | IO_MultiDevice | IO_Supervisor ) Indicates if the entry belongs to a PROFINET controller, a PROFINET device, PROFINET Multidevice or PROFINET Supervisor ipAddress STRING The data type contains the IP address that is assigned to the device The IP address is a secondary address The default value is “0.0.0.0” ipDefaultGateway STRING The data type contains the default gateway address The default value is an empty string ipSubNetmask STRING The data type contains the subnet mask The default value is “255.255.255.255” macAddress STRING The data type contains the MAC address of the device The MAC address is a secondary address The macAddress data type is of type string and shall be used with format shown in the example: Example: 00:A0:45:01:02:03 标准分享网 www.bzfxw.com 免费下载 Licensed Copy: athen reading, Reading University Library, 23/01/2010 05:47, Uncontrolled Copy, (c) BSI BS EN 62453-303-2:2009 62453-303-2 © IEC:2009(E) Data type – 27 – Definition nameOfStation Description STRING The station name is the primary address The default value is an empty string Table 15 – Structured device type identification data type Data type Definition Elementary data types Usage Description Multiplicity ProfinetIODevice STRUCT Definiton of PROFINET device concerning the scan response nameOfStation M [1 1] ipAddress M [1 1] ipSubnetNask M [1 1] ipDefaultGateway M [1 1] macAddress M [1 1] deviceRole M [1 1] fdt:deviceTypeId M [1 1] fdt:manufacturerId M [1 1] fdt:VersionInformation O [0 1] The vendor and device name information of a DCP Identify Response shall be mapped in the fdt:VersionInformation data type as described below: ｗｗｗ．ｂｚｆｘｗ．ｃｏｍ FDT Version Information vendor Vendor name as text (is optional in DCP Identify response) name 12.4 DCP Identify Response Device name as text (is optional in DCP Identify response) Scan identification data types This clause defines data types that are used to provide protocol specific scanning (see Table 16 and Table 17) The data types described in this clause are defined for the following namespace Namespace: pnioscan Table 16 – Simple scan identification data types Data type Definition Description resultState enumeration ( provisional | final | error ) Identifies if the result is one of the provisional results or the final result of the split scan results configuredState enumeration ( configuredAndPhysicall yAvailable | | configuredAndNotPhysi callyAvailable | availableButNotConfigur ed | notApplicable ) A communication master shall indicate in this attribute, if the scan response is related to a detected physical device which is configured or unconfigured Licensed Copy: athen reading, Reading University Library, 23/01/2010 05:47, Uncontrolled Copy, (c) BSI BS EN 62453-303-2:2009 62453-303-2 © IEC:2009(E) – 28 – Table 17 – Structured scan identification data types Tag Definition Elementary data types IdAddress Multiplicity pnioident:nameOfStation M [1 1] pnioident:ipAddress O [0 1] pnioident:macAddress M [1 1] pnioident:ipSubnetMask O [0 1] pnioident:ipDefaultGateway O [0 1] M [1 1] M [1 1] M [1 1] M [1 1] M [1 1] All elements contain exactly one attribute each including the value of the scanned physical device All elements with semantic meaning have a prefix “Id” for better identification STRUCT pnioident:busProtocol IdManufacturer STRUCT fdt:manufacturerId IdTypeID STRUCT fdt:deviceTypeId IdSoftwareRevision STRUCT pnioident:softwareRevision IdHardwareRevision STRUCT pnioident:hardwareRevision ｗｗｗ．ｂｚｆｘｗ．ｃｏｍ STRUCT pnioident:deviceRole IdOrder Usage STRUCT IdBusProtocol IdDeviceRole Description M [1 1] M [1 1] M [1 1] M [1 1] STRUCT pnioident:profileID ProfileSpecificType [1 1] STRUCT pnioident:orderId ProfileID M These data types contain corresponding data types defined in FDTProfinetIOIdentS chema.xml They are transformed to name value pairs without semantic meaning for Frame Application STRUCT pnioident:profileSpecificType ManufacturerSpecificExtension STRUCT ScanIdentification_DCP STRUCT pnioident:manufacturerSpecificExtension configuredState O [0 1] fdt:CommunicationError O [0 1] IdBusProtocol M [1 1] IdAddress M [1 1] IdManufacturer M [1 1] IdTypeID M [1 1] IdDeviceRole M [1 1] ManufacturerSpecificExtension O [0 1] 标准分享网 www.bzfxw.com 免费下载 These data types contain all elements for the appropriate protocol variant Licensed Copy: athen reading, Reading University Library, 23/01/2010 05:47, Uncontrolled Copy, (c) BSI BS EN 62453-303-2:2009 62453-303-2 © IEC:2009(E) – 29 – Tag Definition Elementary data types ScanIdentification_IM ScanIdentifications Description Usage Multiplicity STRUCT configuredState O [0 1] fdt:CommunicationError O [0 1] IdBusProtocol M [1 1] IdAddress M [1 1] IdManufacturer M [1 1] IdTypeID M [1 1] IdDeviceRole M [1 1] ManufacturerSpecificExtension O [0 1] IdOrder M [1 1] IdSerialNumber M [1 1] IdSoftwareRevision M [1 1] IdHardwareRevision M [1 1] ProfileID M [1 1] ProfileSpecificType M [1 1] STRUCT Collection of ScanIdentification elements fdt:protocolId M [1 1] resultState M [1 1] choice of M [1 *] ScanIdentification_DCP S [0 *] ScanIdentification_IM S [0 *] ｗｗｗ．ｂｚｆｘｗ．ｃｏｍ 12.5 Device type identification data types The schema provides attributes and elements for providing protocol specific information for device types (see Table 18) The data types described in this clause are defined for the following namespace Namespace: pniodevtype Table 18 – Structured device type identification data types Tag Definition Elementary data types IdBusProtocol IdManufacturer IdTypeID IdSoftwareRevision Description Usage Multiplicity STRUCT pnioident:busProtocol O [0 1] pnioident:RegExpr O [0 1] fdt:manufacturerId O [0 1] pnioident:RegExpr O [0 1] fdt:deviceTypeId O [0 1] pnioident:RegExpr O [0 1] STRUCT STRUCT STRUCT All data types contain exactly one data type each including the value of the scanned physical device All data types with semantic meaning have a prefix “Id” for better identification Licensed Copy: athen reading, Reading University Library, 23/01/2010 05:47, Uncontrolled Copy, (c) BSI BS EN 62453-303-2:2009 62453-303-2 © IEC:2009(E) – 30 – Tag Definition Elementary data types IdHardwareRevision Description Usage Multiplicity pnioident:softwareRevision O [0 1] pnioident:RegExpr O [0 1] pnioident:hardwareRevision O [0 1] pnioident:RegExpr O [0 1] STRUCT IdDeviceRole STRUCT IdOrder pnioident:deviceRole O [0 1] pnioident:RegExpr O [0 1] pnioident:orderId M [1 1] pnioident:RegExpr O [0 1] pnioident:profileID O [0 1] pnioident:RegExpr O [0 1] pnioident:profileSpecificType O [0 1] pnioident:RegExpr O [0 1] STRUCT ProfileID STRUCT ProfileSpecificType STRUCT ManufacturerSpecificExtension STRUCT DeviceIdentification_DCP STRUCT ｗｗｗ．ｂｚｆｘｗ．ｃｏｍ DeviceIdentification_IM DeviceIdentifications These data types contain corresponding data types defined in FDTProfinetIOIdent Schema.xml They are transformed to name value pairs without semantic meaning for Frame Application pnioident:manufacturerSpecificExtension M [1 1] pnioident:idDTMSupportLeve M [1 1] IdBusProtocol M [1 1] IdManufacturer M [1 1] IdTypeID M [1 1] IdDeviceRole M [1 1] ManufacturerSpecificExtension O [0 1] pnioident:idDTMSupportLevel" M [1 1] IdBusProtocol M [1 1] IdManufacturer M [1 1] IdTypeID M [1 1] IdDeviceRole M [1 1] ManufacturerSpecificExtension O [0 1] IdOrder M [1 1] IdSoftwareRevision M [1 1] IdHardwareRevision M [1 1] ProfileID M [1 1] ProfileSpecificType M [1 1] These elements contain all elements for the appropriate protocol variant STRUCT STRUCT Collection of DeviceIdentificatio n elements fdt:protocolId M [1 1] choice of M [1 *] 标准分享网 www.bzfxw.com 免费下载 Licensed Copy: athen reading, Reading University Library, 23/01/2010 05:47, Uncontrolled Copy, (c) BSI BS EN 62453-303-2:2009 62453-303-2 © IEC:2009(E) – 31 – Tag Definition Elementary data types Description Usage Multiplicity DeviceIdentification_DCP S [0 *] DeviceIdentification_IM S [0 *] ｗｗｗ．ｂｚｆｘｗ．ｃｏｍ Licensed Copy: athen reading, Reading University Library, 23/01/2010 05:47, Uncontrolled Copy, (c) BSI BS EN 62453-303-2:2009 – 32 – 62453-303-2 © IEC:2009(E) Bibliography IEC 61158 (all parts), Industrial communication networks – Fieldbus specifications Application Layer protocol for decentralized periphery and distributed automation Version 2.1 June 2006, PNO Order No: 2.722 Application Layer services for decentralized periphery and distributed automation Version 2.1 June 2006, PNO Order No: 2.712 ISO/IEC 19501:2005, Information technology – Open Distributed Processing – Unified Modeling Language (UML) Version 1.4.2 _ ｗｗｗ．ｂｚｆｘｗ．ｃｏｍ 标准分享网 www.bzfxw.com 免费下载 Licensed Copy: athen reading, Reading University Library, 23/01/2010 05:47, Uncontrolled Copy, (c) BSI ｗｗｗ．ｂｚｆｘｗ．ｃｏｍ This page deliberately left blank Licensed Copy: athen reading, Reading University Library, 23/01/2010 05:47, Uncontrolled Copy, (c) BSI British Standards Institution (BSI) BSI is the independent national body responsible for preparing British Standards and other standards-related publications, information and services It presents the UK view on standards in Europe and at the international level It is incorporated by Royal Charter Revisions Information on standards British Standards are updated by amendment or revision Users of British Standards should make sure that they possess the latest amendments or editions It is the constant aim of BSI to improve the quality of our products and services We would be grateful if anyone finding an inaccuracy or ambiguity while using this British Standard would inform the Secretary of the technical committee responsible, the identity of which can be found on the inside front cover Tel: +44 (0)20 8996 9001 Fax: +44 (0)20 8996 7001 BSI provides a wide range of information on national, European and international standards through its Knowledge Centre BSI offers Members an individual updating service called PLUS which ensures that subscribers automatically receive the latest editions of standards Tel: +44 (0)20 8996 7004 Fax: +44 (0)20 8996 7005 Email: knowledgecentre@bsigroup.com Various BSI electronic information services are also available which give details on all its products and services Tel: +44 (0)20 8996 7111 Fax: +44 (0)20 8996 7048 Email: info@bsigroup.com BSI Subscribing Members are kept up to date with standards developments and receive substantial discounts on the purchase price of standards For details of these and other benefits contact Membership Administration ｗｗｗ．ｂｚｆｘｗ．ｃｏｍ Tel: +44 (0)20 8996 7669 Fax: +44 (0)20 8996 7001 Email: plus@bsigroup.com Buying standards You may buy PDF and hard copy versions of standards directly using a credit card from the BSI Shop on the website www.bsigroup.com/shop In addition all orders for BSI, international and foreign standards publications can be addressed to BSI Customer Services Tel: +44 (0)20 8996 9001 Fax: +44 (0)20 8996 7001 Email: orders@bsigroup.com In response to orders for international standards, it is BSI policy to supply the BSI implementation of those that have been published as British Standards, unless otherwise requested Tel: +44 (0)20 8996 7002 Fax: +44 (0)20 8996 7001 Email: membership@bsigroup.com Information regarding online access to British Standards via British Standards Online can be found at www.bsigroup.com/BSOL Further information about BSI is available on the BSI website at www.bsigroup.com/standards Copyright Copyright subsists in all BSI publications BSI also holds the copyright, in the UK, of the publications of the international standardization bodies Except as permitted under the Copyright, Designs and Patents Act 1988 no extract may be reproduced, stored in a retrieval system or transmitted in any form or by any means – electronic, photocopying, recording or otherwise – without prior written permission from BSI This does not preclude the free use, in the course of implementing the standard of necessary details such as symbols, and size, type or grade designations If these details are to be used for any other purpose than implementation then the prior written permission of BSI must be obtained Details and advice can be obtained from the Copyright & Licensing Manager Tel: +44 (0)20 8996 7070 Email: copyright@bsigroup.com BSI Group Headquarters 389 Chiswick High Road London W4 4AL UK Tel +44 (0)20 8996 9001 Fax +44 (0)20 8996 7001 www.bsigroup.com/standards raising standards worldwide™ 标准分享网 www.bzfxw.com 免费下载