Iec tr 62453 52 31 2017

I E C TR 62 453 -52 -3 ® Edition 201 7-06 TE C H N I C AL RE P ORT colour i n sid e F i e l d d evi ce tool (F D T) i n te rface s pe ci fi cati on – P art 52 -3 : C om m u n i cati on i m pl em en tati on for com m on l an g u ag e IEC TR 62453-52-31 :201 7-06(en) i n fras tru ctu re – I E C 61 84 C P 3/1 an d C P 3/2 T H I S P U B L I C AT I O N I S C O P YRI G H T P RO T E C T E D C o p yri g h t © I E C , G e n e v a , S wi tz e rl a n d 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 IEC or IEC's member National Committee in the country of the requester If you have any questions about I EC copyright or have an enquiry about obtaining additional rights to this publication, please contact the address below or your local I EC member National Committee for further information IEC Central Office 3, rue de Varembé CH-1 21 Geneva 20 Switzerland Tel.: +41 22 91 02 1 Fax: +41 22 91 03 00 info@iec.ch www.iec.ch Ab ou t th e I E C The I nternational Electrotechnical Commission (I EC) is the leading global organization that prepares and publishes I nternational Standards for all electrical, electronic and related technologies Ab o u t I E C p u b l i ca ti o n s The technical content of IEC publications is kept under constant review by the IEC Please make sure that you have the latest edition, a corrigenda or an amendment might have been published I E C Catal og u e - webstore i ec ch /catal og u e The stand-alone application for consulting the entire bibliographical information on IEC International Standards, Technical Specifications, Technical Reports and other documents Available for PC, Mac OS, Android Tablets and iPad I E C pu bl i cati on s s earch - www i ec ch /search pu b The advanced search enables to find IEC publications by a variety of criteria (reference number, text, technical committee,…) It also gives information on projects, replaced and withdrawn publications E l ectroped i a - www el ectroped i a org The world's leading online dictionary of electronic and electrical terms containing 20 000 terms and definitions in English and French, with equivalent terms in additional languages Also known as the International Electrotechnical Vocabulary (IEV) online I E C G l os sary - s td i ec ch /g l oss ary 65 000 electrotechnical terminology entries in English and French extracted from the Terms and Definitions clause of IEC publications issued since 2002 Some entries have been collected from earlier publications of IEC TC 37, 77, 86 and CISPR I E C J u st Pu bl i s h ed - webstore i ec ch /j u stpu bl i sh ed Stay up to date on all new IEC publications Just Published details all new publications released Available online and also once a month by email I E C C u stom er S ervi ce C en tre - webstore i ec ch /csc If you wish to give us your feedback on this publication or need further assistance, please contact the Customer Service Centre: csc@iec.ch I E C TR 62 453 -52 -3 ® Edition 201 7-06 TE C H N I C AL RE P ORT colour i n sid e F i e l d d evi ce tool (F D T) i n terface s peci fi cati on – P art 52 -3 : C om m u n i cati on i m pl em en tati on for com m on l an g u ag e i n fras tru ctu re – I E C 61 84 C P 3/1 an d C P 3/2 INTERNATIONAL ELECTROTECHNICAL COMMISSION ICS 25.040.40; 35.1 00.05; 35.1 ISBN 978-2-8322-4335-0 Warn i n g ! M ake s u re th a t you ob tai n ed th i s p u b l i cati on from an au th ori zed d i stri b u tor ® Registered trademark of the International Electrotechnical Commission –2– I EC TR 62453-52-31 : 201 © I EC 201 CONTENTS FOREWORD I NTRODUCTI ON Scope Norm ative references Terms, definitions, sym bols, abbreviated terms and conventions Term s and definitions Symbols and abbreviated term s 3 Conventions 3 Datatype nam es and references to datatypes 3 Vocabulary for requirements 3 Use of U ML Bus category Access to instance and device data 1 General 1 I O signals provided by DTM 1 Data interfaces 1 General 1 Mapping of PROFI BU S datatypes to FDT datatypes 1 3 Sem anticI nfo Protocol specific behaviour PROFI BU S device m odel Configuration and param eterization of PROFI BU S devices General 2 Monolithic DTM for a m odular PROFI BU S device 6 Composite DTM for a m odular PROFI BU S device 6 Support for DP-V0 configuration PROFI BU S slaves operating without a class PROFI BU S master PROFI BU S-related information of a slave DTM General PROFI BU S Network Data (PND) GSD I nform ation 25 Process Data I tem s 26 Protocol specific usage of general datatypes 26 General datatypes 26 Protocol specific handling of the datatype STRI N G 27 Network management datatypes 27 General 27 Configuration 28 Process Data I tems 28 Parameterization 28 Com munication datatypes 29 General 29 ProfibusAbortMessage 29 DP-V0 Comm unication 29 General 29 Dpv0ConnectRequest 30 I EC TR 62453-52-31 : 201 © I EC 201 –3– 3 Dpv0ConnectResponse 31 Dpv0DisconnectRequest 32 Dpv0DisconnectResponse 32 Dpv0TransactionRequest 33 Dpv0TransactionResponse 37 DP-V1 Comm unication 42 Dpv1 ConnectRequest 42 Dpv1 ConnectResponse 43 Dpv1 DisconnectRequest 45 4 Dpv1 DisconnectResponse 45 Dpv1 TransactionRequest 46 Dpv1 TransactionResponse 47 Error inform ation provided by Comm unication Channel 49 Datatypes for process data information 49 1 General 49 ProfibusI OSignalI nfo 49 1 Device identification 50 1 General 50 1 ProfibusDeviceScanI nfo datatype 51 1 General 51 1 2 Datatypes derived from ProfibusBaseScanI nfo 52 1 ProfibusDeviceI dentI nfo datatype 54 1 General 54 1 Datatypes derived from ProfibusBaseI dentI nfo 55 1 Mapping of I nformation Source 57 Bibliograph y 63 Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure – Part 52-31 of the I EC 62453 series – FDT PROFI BUS Device Model – ProfibusN etworkData 27 – ProfibusAbortMessage 29 – Dpv0ConnectRequest 31 – Dpv0ConnectResponse 31 – Dpv0DisconnectRequest 32 – Dpv0DisconnectResponse 32 – Dpv0ReadConfigurationDataRequest 33 – Dpv0ReadDiagnosisDataRequest 34 1 – Dpv0ReadI nputDataRequest 34 – Dpv0ReadOutputDataRequest 35 – Dpv0ReadUserParam eterRequest 36 – Dpv0WriteOutputDataRequest 36 – Dpv0WriteUserParam eterRequest 37 – Dpv0ReadConfigurationDataResponse 38 – Dpv0ReadDiagnosisDataResponse 39 – Dpv0ReadI nputDataResponse 39 – Dpv0ReadOutputDataResponse 40 –4– Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 I EC TR 62453-52-31 : 201 © I EC 201 – Dpv0ReadUserParam eterResponse 41 – Dpv0WriteOutputDataResponse 41 – Dpv0WriteUserParam eterResponse 42 – Dpv1 ConnectRequest 43 – Dpv1 ConnectResponse 44 – Dpv1 DisconnectRequest 45 – Dpv1 DisconnectResponse 45 – Dpv1 ReadRequest 46 – Dpv1 WriteRequest 47 – Dpv1 ReadResponse 48 – Dpv1 WriteResponse 48 – ProfibusI OSignalI nfo 50 – ProfibusDeviceScanI nfo 51 – Datatypes derived from ProfibusBaseScanI nfo 52 – ProfibusDeviceI dentI nfo 54 – Datatypes derived from ProfibusBaseI dentI nfo 55 – Mapping of datatypes 1 – Usage of general datatypes – PROFI BU S Network I nformation – Protocol specific usage of general datatypes 27 – ProfibusAbortMessage datatype 29 – Availability of services for Master Class (C1 ) 30 – Availability of services for Master Class (C2) 30 – Dpv0ConnectRequest datatype 31 – Dpv0ConnectResponse datatype 32 – Dpv0DisconnectRequest datatype 32 1 – Dpv0DisconnectResponse datatype 33 – Dpv0ReadConfigurationDataRequest datatype 33 – Dpv0ReadDiagnosisDataRequest datatype 34 – Dpv0ReadI nputDataRequest datatype 35 – Dpv0ReadOutputDataRequest datatype 35 – Dpv0ReadUserParam eterRequest datatype 36 – Dpv0WriteOutputDataRequest datatype 37 – Dpv0WriteUserParameterRequest datatype 37 – Dpv0ReadConfigurationDataResponse datatype 38 20 – Dpv0ReadDiagnosisDataResponse datatype 39 21 – Dpv0ReadI nputDataResponse datatype 40 22 – Dpv0ReadOutputDataResponse datatype 40 23 – Dpv0ReadUserParam eterResponse datatype 41 24 – Dpv0WriteOutputDataResponse datatype 42 25 – Dpv0WriteUserParameterResponse datatype 42 26 – Dpv1 ConnectRequest datatype 43 I EC TR 62453-52-31 : 201 © I EC 201 Table Table Table Table Table Table Table Table Table Table Table Table Table 27 28 29 30 31 32 33 34 35 36 37 38 39 –5– – Dpv1 ConnectResponse datatype 44 – Dpv1 DisconnectRequest datatype 45 – Dpv1 DisconnectResponse datatype 45 – Dpv1 ReadRequest datatype 46 – Dpv1 WriteRequest datatype 47 – Dpv1 ReadResponse datatype 48 – Dpv1 WriteResponse datatype 49 – ProfibusI OSignalI nfo datatype 50 – ProfibusDeviceScanI nfo datatype 52 – Datatypes derived from ProfibusBaseScanI nfo 53 – ProfibusDeviceI dentI nfo datatype 55 – Datatypes derived from ProfibusBaseI dentI nfo 56 – Profile specific mapping of identity information 58 –6– I EC TR 62453-52-31 : 201 © I EC 201 INTERNATI ONAL ELECTROTECHNI CAL COMMISSI ON F I E L D D E VI C E T O O L ( F D T ) I N T E RF AC E S P E C I F I C AT I O N – P a rt -3 : C o m m u n i c a ti o n i m p l e m e n t a ti o n fo r c o m m o n l a n g u a g e i n fra s t ru c tu re – I E C C P /1 a n d C P /2 FOREWORD ) The I nternati on al Electrotech ni cal Comm ission (I EC) is a worl d wid e organization for stand ardization com prisin g all nati on al el ectrotechnical comm ittees (I EC Nation al Comm ittees) The object of I EC is to prom ote internati onal co-operation on all qu estions concerni ng standardi zati on in the electrical and electronic fields To this en d and in ad dition to other activities, I EC pu blish es I nternational Stan dards, Technical Specificati ons, Technical Reports, Publicly Avail abl e Specificati ons (PAS) an d Gui des (hereafter referred to as “I EC Publication(s)”) Th eir preparation is entrusted to technical comm ittees; any I EC N ation al Comm ittee interested in the subj ect dealt with m ay participate i n this preparatory work I nternational, governm ental and nongovernm ental org ani zations li aising with the I EC also partici pate i n this preparati on I EC col laborates cl osel y with the I ntern ational Organization for Stand ardization (I SO) in accordance with ditions determ ined by agreem ent between th e two organi zati ons 2) The form al decisions or ag reem ents of I EC on tech nical m atters express, as nearly as possi ble, an international consensus of opin ion on the rel evant subjects since each technical com m ittee has representati on from all interested I EC N ational Com m ittees 3) I EC Publicati ons have the form of recom m endations for i nternational use an d are accepted by I EC N ational Com m ittees in that sense While all reasonable efforts are m ade to ensure that the tech nical content of I EC Publications is accurate, I EC cann ot be held responsibl e for the way in which they are used or for an y m isinterpretation by an y en d u ser 4) I n ord er to prom ote internati onal u niform ity, I EC Nation al Com m ittees undertake to apply I EC Publ ications transparentl y to th e m axim um extent possibl e in thei r n ational an d regi onal pu blicati ons Any di vergence between an y I EC Publ ication and the correspondi ng n ational or regi on al pu blicati on shall be clearl y in dicated in the latter 5) I EC itself d oes n ot provid e an y attestati on of conform ity I ndepend ent certificati on bod ies provi de conform ity assessm ent services an d, in som e areas, access to I EC m arks of conform ity I EC is not responsi ble for an y services carri ed out by ind ependent certification bodi es 6) All users shou ld ensure that th ey h ave the l atest editi on of thi s publicati on 7) No liability shall attach to I EC or its directors, em ployees, servants or ag ents includ ing i n divi du al experts and m em bers of its tech nical com m ittees and I EC Nati onal Com m ittees for an y person al i nju ry, property dam ag e or other dam age of an y nature whatsoever, wheth er di rect or indirect, or for costs (includi ng leg al fees) and expenses arisi ng out of th e publ ication, use of, or rel ian ce upon, this I EC Pu blicati on or an y other I EC Publications 8) Attention is drawn to the Norm ative references cited i n this publ ication Use of the referenced publications is indispensable for the correct appl icati on of this publication 9) Attention is drawn to th e possibility that som e of the elem ents of this I EC Publication m ay be the subject of patent rig hts I EC shall not be held responsibl e for identifyi ng any or all such patent ri ghts The main task of I EC technical comm ittees is to prepare I nternational Standards H owever, a technical comm ittee may propose the publication of a technical report when it has collected data of a different kind from that which is norm ally published as an I nternational Standard, for example "state of the art" I EC TR 62453-52-31 , which is a technical report, has been prepared by subcomm ittee 65E: Devices and integration in enterprise system s, of I EC technicall comm ittee 65: I ndustrialprocess measurement, control and automation Each part of the I EC 62453-52-xy series is intended to be read in conj unction with its corresponding part in the I EC 62453-3xy series The corresponding part for this document is I EC 62453-303-1 I EC TR 62453-52-31 : 201 © I EC 201 –7– The text of this technical report is based on the following documents: Enqui ry draft Report on votin g 65E/440/DTR 65E/51 4/RVC Full inform ation on the voting for the approval of this technical report can be found in the report on voting indicated in the above table This docum ent has been drafted in accordance with the I SO/I EC Directives, Part The list of all parts of the I EC 62453 series, under the general title Field device tool (FDT) interface specification , can be found on the I EC website The comm ittee has decided that the contents of this document will remain unchanged until the stability date indicated on the I EC website under "http: //webstore iec.ch" in the data related to the specific docum ent At this date, the docum ent will be • • • • reconfirm ed, withdrawn, replaced by a revised edition, or amended A bilingual version of this publication may be issued at a later date I M P O R T AN T – T h e ' c o l o u r i n s i d e ' th at it tai n s u n d e rs t a n d i n g c o l o u r p ri n t e r of c o l o u rs i ts wh i c h c o n te n ts l og o a re U s e rs on th e co ve r p ag e o f th i s c o n s i d e re d s h ou l d to t h e re fo re be p ri n t p u b l i c ati o n u s e fu l th i s fo r i n d i c ate s th e d o cu m en t c o rre c t u sin g a –8– I EC TR 62453-52-31 : 201 © I EC 201 I NTRODUCTI ON This part of I EC 62453 is an interface specification for developers of Field Device Tool (FDT) com ponents for function control and data access within a client/server architecture The specification is a result of an anal ysis and design process to develop standard interfaces to facilitate the development of servers and clients by m ultiple vendors that need to interoperate seamlessl y With the integration of fieldbuses into control systems, there are a few other tasks which need to be perform ed I n addition to fieldbus- and device-specific tools, there is a need to integrate these tools into higher-level system -wide planning or engineering tools I n particular, for use in extensive and heterogeneous control system s, typicall y in the area of the process industry, the unam biguous definition of engineering interfaces that are easy to use for all those involved is of great importance A device-specific software com ponent, called Device Type Manager (DTM), 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 fieldbuses and thus m eets the requirements for integrating different kinds of devices into heterogeneous control system s Figure shows how this part of the I EC 62453-52-xy series is aligned in the structure of the I EC 62453 series Part 52-31 Com m unication im pl em entation for comm on lang uage infrastructure – I EC 61 784 CP 3/1 and CP 3/2 IEC F i g u re – P a rt - o f t h e I E C s e ri e s – 52 – I EC TR 62453-52-31 : 201 © I EC 201 T a b l e – P ro fi b u s D e v i c e S c a n I n fo d a t a t y p e P ro p e rt y D e s c ri p t i o n Address The bus add ress of the device BusProtocol Can be set to either DP-V0 or DP-V1 This inform ation is provi ded by the Com m unication Chan nel (based on th e ScanRequest) ProtocolI dentificati onProfil e I ndicates the i dentification type for the d evice ("DP", "PA", “I M -PA” or "I M") ScannedPhysical Layer I nform ation about the physical layer th at was scann ed This inform ation is provi ded by the Com m unication Chan nel (based on knowl edg e of the fi eld bus) Manufactu rerI d Manufactu rer id entificati on n u m ber Avail abl e for PA an d I &M onl y DeviceTypeI d The I DENT_N U MBER of the d evice Hard wareRevisi on The h ard ware version revision of the device Avail abl e for PA an d I &M onl y SoftwareRevisi on The software version revision of the device Avail abl e for PA an d I &M onl y Serial Num ber The serial n um ber of th e specific device Avail abl e for PA an d I &M onl y Tag I dentifyin g tag for a d evice Avail abl e for PA an d I &M onl y P ro t o c o l S p e c i fi c P r o p e r t i e s ProtocolI nform ation Profile specific inform ation (provi ded by derived datatypes) The inform ation of th is m em ber is m apped i nto DeviceScanI nfo ProtocolSpecificProperties D e v i c e S p e c i fi c P ro p e r t i e s Manufactu rerSpecificExtension 1 2 Can be used by DTM for vend or specific device id entificati on i nform ation, e g by com binin g a n um ber of d evi ce param eter val ues into one string val ue Th is can be used to identify a specific device variant D a t a t y p e s d e ri v e d fro m P ro fi b u s B a s e S c a n I n fo This is the profile specific im plementation of the abstract class ProfibusBaseScanI nfo (see Figure 33) P ro fi bu sB as eS can I n fo P rofi bu s Scan I n foD p P rofi bu s Scan I n foP a PA_HardwareRevision : string PA_SoftwareRevision : string DeviceId : string Profile : ushort ProfileRevision : ushort ProfileSpecificType : ushort DeviceRevision : ushort DeviceRevCompatibility : ushort Profi b u sS can I n fo PaI m OrderId : string ProfileId : ushort TagLocation : string ProfileSpecificType : ushort PA_HardwareRevision : string PA_SoftwareRevision : string DeviceId : string Profile : ushort ProfileRevision : ushort ProfileSpecificType : ushort DeviceRevision : ushort DeviceRevCompatibility : ushort P rofi bu s Scan I n foI m OrderId : string ProfileId : ushort TagLocation : string ProfileSpecificType : ushort IEC U s ed in: I Dtm Scanning EndScanRequest() F i g u re 3 – D a t a t y p e s d e ri v e d fro m P ro fi b u s B a s e S c a n I n fo I EC TR 62453-52-31 : 201 © I EC 201 – 53 – The properties of the datatypes derived from ProfibusBaseScanI nfo are described in Table 36 T a b l e – D a t a t y p e s d e ri v e d fro m P ro fi b u s B a s e S c a n I n fo P ro p e rt y D e s c ri p t i o n P ro fi b u s S c a n I n fo D P P ro fi b u s S c a n I n fo P a DeviceI d The PA specific device type id entification (Ph ysical Block – I ndex 1 ) DeviceRevisi on The revision of th e device (Ph ysical Block – I ndex 0, bytes starting at byte offset 4) DeviceRevCom patibi lity The d evice revision com patibil i ty for the device (Physical Bl ock – I ndex 0, bytes starti ng at byte offset 6) PA_Hard wareRevisi on The PA hard ware revisi on for the d evice (Ph ysical Block – I n dex 9) PA_SoftwareRevisi on The PA software revisi on for th e device (Ph ysical Block – I n d ex 8) Profile The profil e identification for th e device (Ph ysical Block – I n d ex 0, bytes starting at byte offset 0) ProfileRevision The profil e revisi on for the d evi ce (Physical Block – I n dex 0, bytes starting at byte offset 2) ProfileSpecificType Additional profi le id entificati on inform ation of the d evice (first Transd ucer Block – I ndex 0, byte at byte offset 2) P ro fi b u s S c a n I n fo P a I m Ord erI d The com plete order n um ber or at least the rel evant part that allows unam biguous id entificati on of the device withi n the m anufactu rer's web site (I &M El em ent 2) ProfileI d I &M defi ned Profil e identifier (I &M Elem ent 7) ProfileSpecificType Additional profi le id entificati on inform ation of the device (I &M Elem ent 8) TagLocation I &M defi ned l ocation specific of the device (I&M Element 2) DeviceI d The PA specific device type id entification (Ph ysical Block – I ndex 1 ) DeviceRevisi on The revision of th e device (Ph ysical Block – I ndex 0, bytes starting at byte offset 4) DeviceRevCom patibi lity The d evice revision com patibil i ty for the device (Physical Bl ock – I ndex 0, bytes starti ng at byte offset 6) PA_Hard wareRevisi on The PA hard ware revisi on for the d evice (Ph ysical Block – I n dex 9) PA_SoftwareRevisi on The PA software revisi on for th e device (Ph ysical Block – I n d ex 8) Profile The profil e identification for th e device (Ph ysical Block – I n d ex 0, bytes starting at byte offset 0) ProfileRevision The profil e revisi on for the d evi ce (Physical Block – I n dex 0, bytes starting at byte offset 2) ProfileSpecificType Additional profi le id entificati on inform ation of the d evice (first Transd ucer Block – I ndex 0, byte at byte offset 2) P ro fi b u s S c a n I n fo I m Ord erI d The com plete ord er n um ber or at least the rel evant part that allows unam biguous id entificati on of the device withi n the m anufactu rer's web site (I &M El em ent 2) ProfileI d I &M defi ned Profil e identifier (I &M Elem ent 7) ProfileSpecificType Additional profi le id entificati on inform ation of the d evice (I &M Elem ent 8) TagLocation I &M defi ned l ocation specific of the device (I&M Element 2) – 54 – 1 I EC TR 62453-52-31 : 201 © I EC 201 P ro fi b u s D e v i c e I d e n t I n fo d a t a t yp e 1 G e n e l PROFI BU S DTMs that m ay connect to a PROFI BU S Comm unication Channel (e.g Device DTMs and Gateway DTMs) shall provide information, which m ay be used to identify the corresponding devices on the fieldbus This subclause describes the offline information (see Figure 34) D evi ceI d en tI n fo Protocol D evi ceI d en tI n fo ProtocolId : Guid ProtocolId : Guid ProfibusDeviceIdentInfo D evi ceI d en tI n fo ProtocolSpecificIdentInfo P rofi bu s D evi ceI d en tI n fo BusProtocol : Guid ProtocolIdentificationProfile : string ManufacturerId : ushort DeviceTypeCode : ushort HardwareRevision : string SoftwareRevision : string ManufacturerSpecificExtension : string ProtocolInformation Profi bu sB as eI d en tI n fo IEC U s ed in: I Dtm I nform ation GetDeviceI dentI nfo() F i g u re – P ro fi b u s D e v i c e I d e n t I n fo The properties of the ProfibusDeviceI dentI nfo datatype are described in Table 37 Protocol specific properties will be stored as key-value pairs in the property DeviceI dentI nfo ProtocolSpecificProperties Device specific properties will be stored as keyvalue pairs in the property DeviceI dentI nfo DeviceSpecificProperties I EC TR 62453-52-31 : 201 © I EC 201 – 55 – T a b l e – P ro fi b u s D e v i c e I d e n t I n fo d a t a t y p e P ro p e rt y D e s c ri p t i o n BusProtocol The uniq ue identifi er of either DP-V0 or DP-V1 ProtocolI dentificati onProfil e I ndicates the i dentification type for the d evice ("DP", "PA", “I M -PA”, or "I M") Manufactu rerI d Manufactu rer id entificati on n u m ber DeviceTypeI d The I DENT_N U MBER of the d evice SoftwareRevisi on The software version revision of the device Hard wareRevisi on The hard ware version revision of the device P ro t o c o l S p e c i fi c P r o p e rt i e s ProtocolI nform ation Profile specific inform ation (provi ded by derived datatypes) The inform ation of th is m em ber is m apped i nto DeviceScanI nfo ProtocolSpecificProperties D e v i c e S p e c i fi c P ro p e r t i e s Manufactu rerSpecificExtension Can be used by DTM for vend or specific device id entificati on i nform ation, e g by com binin g a n um ber of devi ce param eter valu es into one string val ue Th is can be used to identify a specific device variant The inform ation described here will be used to m atch with the inform ation retrieved from Comm unication Channels via the method I Com munication This m atch is executed by device independent software That is wh y it is im portant to provide in ProfibusDeviceI dentI nfo information that can be m atched with the ProfibusDeviceScanI nfo information Developers of DTMs need to consider which information the devices will provide (see 1 4) 1 D a t a t y p e s d e ri v e d fro m P ro fi b u s B a s e I d e n t I n fo This is the profile specific im plementation of the abstract class ProfibusBaseI dentI nfo (see Figure 35) P rofi bu sB aseI d en tI n fo P rofi bu sI d en tI n foD p P rofi bu sI d en tI n foP a PA_HardwareRevision : string PA_SoftwareRevision : string DeviceId : string Profile : ushort ProfileRevision : ushort ProfileSpecificType : ushort DeviceRevision : ushort DeviceRevCompatibility : ushort P rofi bu s I d en tI n foP aI m OrderId : string ProfileId : ushort TagLocation : string ProfileSpecificType : ushort PA_HardwareRevision : string PA_SoftwareRevision : string DeviceId : string Profile : ushort ProfileRevision : ushort ProfileSpecificType : ushort DeviceRevision : ushort DeviceRevCompatibility : ushort P rofi b u s I d en tI n foI m OrderId : string ProfileId : ushort TagLocation : string ProfileSpecificType : ushort IEC U s ed in: I Dtm Scanning EndScanRequest() F i g u re – D a t a t y p e s d e ri v e d fro m P ro fi b u s B a s e I d e n t I n fo – 56 – I EC TR 62453-52-31 : 201 © I EC 201 The properties of the datatypes derived from ProfibusBaseI dentI nfo are described in Table 38 T a b l e – D a t a t y p e s d e ri v e d fro m P ro fi b u s B a s e I d e n t I n fo P ro p e rt y D e s c ri p t i o n P ro fi b u s I d e n t I n fo D P P ro fi b u s I d e n t I n fo P a DeviceI d The PA specific device type id entification (Ph ysical Block – I ndex 1 ) DeviceRevisi on The revision of th e device (Ph ysical Block – I ndex 0, bytes starting at byte offset 4) DeviceRevCom patibi lity The d evice revision com patibil i ty for the device (Physical Bl ock – I ndex 0, bytes starti ng at byte offset 6) PA_Hard wareRevisi on The PA hard ware revisi on for the d evice (Ph ysical Block – I n dex 9) PA_SoftwareRevisi on The PA software revisi on for th e device (Ph ysical Block – I n d ex 8) Profile The profil e identification for th e device (Ph ysical Block – I n d ex 0, bytes starting at byte offset 0) ProfileRevision The profil e revisi on for the d evi ce (Physical Block – I n dex 0, bytes starting at byte offset 2) ProfileSpecificType Additional profi le id entificati on inform ation of the d evice (first Transd ucer Block – I ndex 0, byte at byte offset 2) P ro fi b u s I d e n t I n fo P a I m Ord erI d The com plete order n um ber or at least the rel evant part that allows unam biguous id entificati on of the device withi n the m anufactu rer's web site (I &M El em ent 2) ProfileI d I &M defi ned Profil e identifier (I &M Elem ent 7) ProfileSpecificType Additional profi le id entificati on inform ation of the d evice (I &M Elem ent 8) TagLocation I &M defi ned l ocation specific of the device (I&M Element 2) DeviceI d The PA specific device type id entification (Ph ysical Block – I ndex 1 ) DeviceRevisi on The revision of th e device (Ph ysical Block – I ndex 0, bytes starting at byte offset 4) DeviceRevCom patibi lity The d evice revision com patibil i ty for the device (Physical Bl ock – I ndex 0, bytes starti ng at byte offset 6) PA_Hard wareRevisi on The PA hard ware revisi on for the d evice (Ph ysical Block – I n dex 9) PA_SoftwareRevisi on The PA software revisi on for th e device (Ph ysical Block – I n d ex 8) Profile The profil e identification for th e device (Ph ysical Block – I n d ex 0, bytes starting at byte offset 0) ProfileRevision The profil e revisi on for the d evi ce (Physical Block – I n dex 0, bytes starting at byte offset 2) ProfileSpecificType Additional profi le id entificati on inform ation of the d evice (first Transd ucer Block – I ndex 0, byte at byte offset 2) P ro fi b u s I d e n t I n fo I m Ord erI d The com plete order n um ber or at least the rel evant part that allows unam biguous id entificati on of the device withi n the m anufactu rer's web site (I &M El em ent 2) ProfileI d I &M defi ned Profil e identifier (I &M Elem ent 7) ProfileSpecificType Additional profi le id entificati on inform ation of the d evice (I &M Elem ent 8) TagLocation I &M defi ned l ocation specific of the device (I&M Element 2) I EC TR 62453-52-31 : 201 © I EC 201 1 M appi n g o f I n fo rm a t i o n – 57 – S o u rc e PROFI BU S Comm unication DTMs shall provide identification properties according to the supported device profile The following rule shall be applied by PROFI BU S Comm unication Channels: • • • • if the device supports I &M information as well as PA profi le inform ation (PROFI LE_I D has value 0x9700), then the Comm unication Channel shall create com bined I &M and PA identification (define ProtocolI dentificationProfile="I M-PA" and map the information corresponding to entry "For I M -PA: " in Table 39), otherwise if the device supports I &M information, then the Com munication Channel shall create I &M identification (define ProtocolI dentificationProfile=”I M” and m ap the information corresponding to entry "For I M: " in Table 39), otherwise if the device supports PA profile inform ation, then the Communication Channel shall create PA identification (define ProtocolI dentificationProfile=”PA” and map the information corresponding to entry "For PA:" in Table 39), otherwise the Com munication Channel shall create DP identification (define ProtocolI dentificationProfile=”DP” and m ap the inform ation corresponding to entry "For DP: " in Table 39) Table 39 shows the mapping of device properties to predefined ProfibusDeviceScanI nfo properties T a b l e – P ro fi l e s p e c i fi c m a p p i n g P ro fi b u s D e v i c e S c a n I n fo M apped P ro fi b u s D e v i c e I d e n t I n fo , D e v i c e S c a n I n fo P ro p e rt y N a m e P ro p e rt y N a m e D a ta Re q u e s t i n p h ys i c a l o f i d e n t i t y i n fo rm a t i o n d evi ce P ro t o c o l S p e c i fi c N a m e P RO F I B U S S p e c i fi c D a t a F o rm a t R e fe r e n c e ProtocolI dentificati onProfile "I M" or “I M-PA” or “PA” or “DP” - - - SlaveAdd ress Address BusAddress Bus add ress is provid ed as part of live list by a PROFI BUS m aster Service: FMA1 /2_LI VE_LI ST Slave Address - [6] Part 3, BusProtocol ProtocolI d Set by Com m unicationCh an nel - - - ScannedPhysical Layer PhysicalLayer Set by Com m unicationCh an nel - - - Manufactu rerI d Manufactu rerI d For “I M ”: I &M Elem ent MAN UFACTURER_I D Unsig ned [4] 2 For “I M -PA”: I &M El em ent MAN UFACTURER_I D Unsigned [4] 2 For “PA”: Physical Block – I nd ex DEVICE_MAN_ID Unsig ned [3] For “DP”: n ull (not available) - - - I DENT_NU MBER can be req uested by: DP Service DDLM _SLAVE_DI AG I DENT_NU MBER Unsig ned [6] Part 8, DeviceTypeI d DeviceTypeI d Displayed as hex num ber Hard wareRevisi on SoftwareRevisi on Hard wareRevisi on SoftwareRevisi on For “I M ”: I &M Elem ent int1 form atted as string HARDWARE_REVI SI ON Octets VisibleStrin g [4] For “I M -PA”: I &M El em ent int1 form atted as string HARDWARE_REVI SI ON Octets VisibleStrin g [4] For “PA”: Physical Block – I nd ex HARDWARE_REVI SI ON Octets VisibleStrin g [3] For “DP”: "N/A" (not available) - - - For “I M ”: I &M Elem ent int1 form atted as string SOFTWARE_REVI SI ON Octets VisibleString [4] For “I M -PA”: I &M El em ent int1 form atted as string SOFTWARE_REVI SI ON Octets VisibleStrin g [4] For “PA”: Physical Block – I nd ex SOFTWARE_REVI SI ON Octets VisibleStrin g [3] For “DP”: "N/A" (not available) - - - I EC TR 62453-52-31 : 201 © I EC 201 Allowed valu es are: Profil e I DENT_N U MBER: 0x9700 (0x9700 to 0x9742) or m anufacturer specific I DENT_N U MBER – 58 – - M apped D e v i c e S c a n I n fo P ro p e rt y N a m e P ro p e rt y N a m e Tag Serial Num ber Tag Serial Num ber D a ta Re q u e s t i n p h ys i c a l d evi ce P ro t o c o l S p e c i fi c N a m e P RO F I B U S S p e c i fi c D a t a F o rm a t R e fe r e n c e TAG_FUN CTI ON 32 Octets VisibleStrin g [4] 2 For “I M -PA”: I &M El em ent TAG_FUN CTI ON 32 Octets VisibleString [4] 2 For “PA”: Physical Block – I nd ex TAG_DESC 32 Octets VisibleStrin g [3] 1 For “DP”: "N/A" (not available) - - - For “I M ”: I &M Elem ent SERI AL_N UMBER Octets VisibleStrin g [4] For “I M -PA”: I &M El em ent SERI AL_N UMBER Octets VisibleStrin g [4] For “PA”: Physical Block – I nd ex DEVI CE_SER_NU M Octets VisibleStrin g [3] For “DP”: "N/A" (not available) - - - For “I M ”: not available - - - For “I M -PA”: Physical Bl ock – I ndex HARDWARE_REVI SI ON Octets VisibleStrin g [3] For “PA”: Physical Block – I nd ex HARDWARE_REVI SI ON Octets VisibleStrin g [3] For “DP”: n ot avail abl e - - - For “I M ”: not available - - - For “I M -PA”: Physical Bl ock – I ndex SOFTWARE_REVI SI ON Octets VisibleStrin g [3] For “PA”: Physical Block – I nd ex SOFTWARE_REVI SI ON Octets VisibleStrin g [3] For “DP”: n ot avail abl e - - - P ro t o c o l S p e c i fi c P ro p e r t i e s : PA_Hard wareRevisi on PA_SoftwareRevisi on – 59 – For “I M ”: I &M Elem ent I EC TR 62453-52-31 : 201 © I EC 201 P ro fi b u s D e v i c e S c a n I n fo P ro fi b u s D e v i c e I d e n t I n fo , P ro fi b u s D e v i c e S c a n I n fo M apped P ro fi b u s D e v i c e I d e n t I n fo , D e v i c e S c a n I n fo P ro p e rt y N a m e P ro p e rt y N a m e OrderI d DeviceI d d evi ce P ro t o c o l S p e c i fi c N a m e P RO F I B U S S p e c i fi c D a t a F o rm a t R e fe r e n c e For “I M ”: I &M Elem ent ORDER_I D 20 Octets VisibleStrin g [4] 3 For “I M -PA”: I &M El em ent ORDER_I D 20 Octets VisibleString [4] 3 For “PA”: not avai lable - - - For “DP”: n ot avail abl e - - - For “I M ”: not available - - - For “I M -PA”: Physical Bl ock – I ndex 1 DEVI CE_I D Octets VisibleStrin g [3] For “PA”: Physical Block – I nd ex 1 DEVI CE_I D Octets VisibleStrin g [3] For “DP”: n ot avail abl e - - - For “I M ”: I &M Elem ent PROFI LE_I D Unsig ned [4] For “I M -PA”: I &M El em ent PROFI LE_I D Unsig ned [4] For “PA”: not avai lable - - - For “DP”: n ot avail abl e - - - For “I M ”: not available - - - For “I M -PA”: Block structure of physical block – el em ent (Ph ysical Block – I n dex 0, bytes starting at byte offset 0) Profile Unsig ned [3] For “PA”: Block structure of ph ysical bl ock – el em ent (Ph ysical Block – I n dex 0, bytes starting at byte offset 0) Profile Unsig ned [3] For “DP”: n ot avail abl e - - - I EC TR 62453-52-31 : 201 © I EC 201 Profile p h ys i c a l – 60 – ProfileI d D a ta Re q u e s t i n M apped D e v i c e S c a n I n fo P ro p e rt y N a m e P ro p e rt y N a m e ProfileRevision ProfileSpecificType DeviceRevisi on - - p h ys i c a l d evi ce P ro t o c o l S p e c i fi c N a m e P RO F I B U S S p e c i fi c D a t a F o rm a t R e fe r e n c e For I &M: not avail abl e - - - For “I M -PA”: Block structure of physical block – el em ent (Ph ysical Block – I n dex 0, bytes starting at byte offset 2) Profile Revision Unsig ned [3] For “PA”: Block structure of ph ysical bl ock – el em ent (Ph ysical Block – I n dex 0, bytes starting at byte offset 2) Profile Revision Unsig ned [3] For “DP”: n ot avail abl e - - - For “I M ”: I &M Elem ent PROFI LE_SPECI FI C_TYP E Unsigned [4] For “I M -PA”: Block structure of first transducer block – elem ent (first Transducer Block – I nd ex 0, byte at byte offset 2) PROFI LE_SPECI FI C_TYP E Unsig ned [3] For “PA”: Block structure of fi rst transducer bl ock – elem ent (fi rst Transducer Block – I ndex 0, byte at byte offset 2) PROFI LE_SPECI FI C_TYP E Unsig ned [3] For “DP”: n ot avail abl e - - - For “I M ”: I&M Element TAG_LOCATION 22 Octets VisibleStrin g [4] 3.2.1 For “I M -PA”: I&M Element TAG_LOCATION 22 Octets VisibleStrin g [4] 3.2.1 For “PA”: not avai lable - - - For “DP”: n ot avail abl e - - - For “I M ”: not available - - - For “I M -PA”: Block structure of physical block – el em ent (Ph ysical Block – I n dex 0, bytes starting at byte offset 4) Dev_Rev Unsigned1 [3] [3] 5 For “PA”: Block structure of ph ysical bl ock – el em ent (Ph ysical Block – I n dex 0, bytes starting at byte offset 4) Dev_Rev Unsigned1 [3] [3] 5 For “DP”: n ot avail abl e - - - – 61 – TagLocation - D a ta Re q u e s t i n I EC TR 62453-52-31 : 201 © I EC 201 P ro fi b u s D e v i c e S c a n I n fo P ro fi b u s D e v i c e I d e n t I n fo , P ro fi b u s D e v i c e S c a n I n fo M apped P ro fi b u s D e v i c e I d e n t I n fo , D e v i c e S c a n I n fo P ro p e rt y N a m e P ro p e rt y N a m e DeviceRevCom patibi lity - D a ta Re q u e s t i n p h ys i c a l d evi ce P ro t o c o l S p e c i fi c N a m e P RO F I B U S S p e c i fi c D a t a F o rm a t R e fe r e n c e For “I M ”: not available - - - For “I M -PA”: Block structure of physical block – el em ent (Ph ysical Block – I n dex 0, bytes starting at byte offset 6) Dev_Rev_Com p Unsig ned [3] [3] 5 For “PA”: Block structure of ph ysical bl ock – el em ent (Ph ysical Block – I n dex 0, bytes starting at byte offset 6) Dev_Rev_Com p Unsig ned [3] [3] 5 For “DP”: n ot avail abl e - - - - - - D e v i c e S p e c i fi c P ro p e r t i e s depends on the DTM im plem entation – 62 – I EC TR 62453-52-31 : 201 © I EC 201 I EC TR 62453-52-31 : 201 © I EC 201 – 63 – Bibliography [1 ] FDT Specification v1 0, J ul y 201 2, Order No of FDT Group: 0001 -0008-000, available at http: //fdtgroup org/download/3823/ [viewed 201 7-03-28] [2] Specification for PROFI BU S Device Description and Device I ntegration, Volume : GSD (Order N o 22) Version , J ul y 2008 [3] PROFI BU S-PA Profile for Process Control Devices (Order N o 042) Version 02, April 2009 [4] PROFI BU S Profile Guidelines, Part , I dentification & Maintenance Functions, Version , May 2003 [5] Profile Drive Technolog y PROFI drive (Ord er N o 72), Version , May 2006 [6] PROFI BU S Specification Normative Parts of PROFI BU S -FMS, -DP, -PA according to the European Standard EN 50 70 Volume 2, Edition 0, March 998 _ INTERNATIONAL ELECTROTECHNICAL COMMISSI ON 3, rue de Varembé PO Box 31 CH-1 21 Geneva 20 Switzerland Tel: + 41 22 91 02 1 Fax: + 41 22 91 03 00 info@iec.ch www.iec.ch