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-32:201 7-06(en) i n fras tru ctu re – I E C 61 84 C P 3/4, CP /5 an d C P /6 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/4, CP /5 an d C P /6 INTERNATIONAL ELECTROTECHNICAL COMMISSION ICS 25.040.40; 35.1 0.05; 35.1 ISBN 978-2-8322-4331 -2 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-32: 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 Abbreviations 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 General I O signals provided by DTM Data interfaces General Mapping PROFI N ET datatypes to FDT datatypes 3 Sem anticI nfo 1 Protocol specific behavior PROFI N ET device m odel Configuration and param eterization of PROFI N ET devices PROFI N ET – related inform ation of a Device DTM Rem arks on FDT / Com patibility Protocol specific usage of general FDT datatypes Protocol specific comm on datatype: PnDeviceAddress Network management General Configuration Process Data I tems 28 Parameterization 28 Com munication datatypes 28 1 General 28 ConnectRequest and ConnectResponse Services 28 PnConnectRequest Service 28 2 PnConnectResponse Service 29 DisconnectRequest and DisconnectResponse Services 30 PnDisconnectRequest Service 30 PnDisconnectResponse Service 31 TransactionRequest and TransactionResponse Services 32 PnReadRequest Service 32 PnReadResponse Service 33 PnWriteRequest Service 35 4 PnWriteResponse Service 36 PnCancelRequest Service 37 PnCancelResponse Service 38 C.vT.Bg.Jy.Lj.Tai lieu Luan vT.Bg.Jy.Lj van Luan an.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj Do an.Tai lieu Luan van Luan an Do an.Tai lieu Luan van Luan an Do an I EC TR 62453-52-32: 201 © I EC 201 –3– SubscribeRequest and SubscribeResponse Service 39 PnSubscribeRequest 39 PnSubscribeResponse 40 UnsubscribeRequest and U nsubscribeResponse Service 41 PnU nsubscribeRequest Service 41 PnU nsubscribeResponse Service 41 AbortMessage Service 42 PnResponseError 42 Comm unication error 42 Handling of errors during Connect and Disconnect 43 1 Datatypes for process data information 43 1 General 43 1 PnI OSignalI nfo 43 1 Mapping of PROFI N ET datatypes to FDT datatypes 45 Device identification 45 General 45 2 PnDeviceScanI nfo datatype 45 PnDeviceI dentI nfo datatype 49 Bibliograph y 51 Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure – Part 52-32 of the I EC 62453 series – PROFI N ET Device Model 3 – PROFI N ET Device Address – PROFI N ET N etwork Data – PnConnectRequest 29 – PnConnectResponse 30 – PnDisconnectRequest 31 – PnDisconnectResponse 32 – PnReadRequest 33 – PnReadResponse 34 1 – PnWriteRequest 36 – PnWriteResponse 37 – PnCancelRequest 38 – PnCancelResponse 39 – PnSubscribeRequest 40 – PnSubscribeResponse 40 – PnU nsubscribeRequest 41 – PnU nsubscribeResponse 41 – PnAbortMessage 42 20 – PnResponseError 43 21 – ProtocolI OSignalI nfo 44 22 – PnDeviceScanI nfo datatype 46 23 – PnDeviceI dentI nfo 49 Table – Mapping of datatypes 1 Stt.010.Mssv.BKD002ac.email.ninhd.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj.dtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn.Stt.010.Mssv.BKD002ac.email.ninhddtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn C.vT.Bg.Jy.Lj.Tai lieu Luan vT.Bg.Jy.Lj van Luan an.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj Do an.Tai lieu Luan van Luan an Do an.Tai lieu Luan van Luan an Do an –4– 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 I EC TR 62453-52-32: 201 © I EC 201 – Usage of Sem anticI nfo – Usage of general datatypes 4 – PnDeviceAddress 5 – PROFI N ET N etwork Data – PnConnectRequest datatype 29 – PnConnectResponse datatype 30 – PnDisonnectRequest datatype 31 – PnDisconnectResponse datatype 32 – PnReadRequest datatype 33 1 – PnReadResponse datatype 35 – PnWriteRequest datatype 36 – PnWriteResponse datatype 37 – PnCancelRequest datatype 38 – PnCancelResponse datatype 39 – PnSubscribeRequest datatype 40 – PnSubscribeResponse datatype 40 – PnUnsubscribeRequest datatype 41 – PnUnsubscribeResponse datatype 42 20 – PnAbortMessage datatype 42 21 – PnResponseError datatype 43 22 – PnDatatypeI nfo 44 23 – ProtocollI OSignalI nfo datatypes 45 24 – PnDeviceScanI nfo datatype 46 25 – PnDeviceScanI nfo specific m apping 47 26 – PnDeviceI dentI nfo datatypes 49 27 – PnDeviceI ndentI nfo specific mapping 50 Stt.010.Mssv.BKD002ac.email.ninhd.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj.dtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn.Stt.010.Mssv.BKD002ac.email.ninhddtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn C.vT.Bg.Jy.Lj.Tai lieu Luan vT.Bg.Jy.Lj van Luan an.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj Do an.Tai lieu Luan van Luan an Do an.Tai lieu Luan van Luan an Do an I EC TR 62453-52-32: 201 © I EC 201 –5– 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 /4 , C P /5 a n d C P /6 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 end and in ad dition to other activities, I EC pu blish es I nternational Stan dards, Techn ical 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 ntern ational, governm ental and nongovernm ental org ani zations li aising with th e I EC also partici pate i n this preparati on I EC collaborates closel y with the I ntern ational Organization for Stand ardization (I SO) in accordance with conditions 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 opinion 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 ntern ational 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 th e way in which they are used or for an y m isinterpretation by an y end u ser 4) I n ord er to prom ote internati onal u niform ity, I EC Nation al Com m ittees undertake to appl y 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 any 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 not provid e an y attestati on of conform ity I n depend 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 dual experts and m em bers of its tech nical com m ittees and I EC Nati on al Com m ittees for an y person al i nju ry, property dam age or other dam age of an y nature whatsoever, wheth er di rect or indirect, or for costs (incl udi 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 applicati 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-32, which is a technical report, has been prepared by subcomm ittee 65E: Devices and integration in enterprise system s, of I EC techn ical comm ittee 65: I ndustrialprocess measurement, control and autom ation 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 This document corresponds to I EC 62453-303-2 Stt.010.Mssv.BKD002ac.email.ninhd.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj.dtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn.Stt.010.Mssv.BKD002ac.email.ninhddtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn C.vT.Bg.Jy.Lj.Tai lieu Luan vT.Bg.Jy.Lj van Luan an.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj Do an.Tai lieu Luan van Luan an Do an.Tai lieu Luan van Luan an Do an –6– I EC TR 62453-52-32: 201 © I EC 201 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 document 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 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 c o l o u r p ri n t e r Stt.010.Mssv.BKD002ac.email.ninhd.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj.dtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn.Stt.010.Mssv.BKD002ac.email.ninhddtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn 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 C.vT.Bg.Jy.Lj.Tai lieu Luan vT.Bg.Jy.Lj van Luan an.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj Do an.Tai lieu Luan van Luan an Do an.Tai lieu Luan van Luan an Do an I EC TR 62453-52-32: 201 © I EC 201 –7– 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 system s, 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 systems, typically 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 component, 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 fieldbusses 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 IEC 62453 series Part 52-32 Com m unication im plem entation for comm on lang uage infrastructure – I EC 61 784 CP 3/4, CP 3/5 and CP 3/6 IEC F i g u re – P a rt - o f t h e I E C s e ri e s Stt.010.Mssv.BKD002ac.email.ninhd.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj.dtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn.Stt.010.Mssv.BKD002ac.email.ninhddtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn C.vT.Bg.Jy.Lj.Tai lieu Luan vT.Bg.Jy.Lj van Luan an.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj Do an.Tai lieu Luan van Luan an Do an.Tai lieu Luan van Luan an Do an –8– I EC TR 62453-52-32: 201 © I EC 201 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 /4 , C P /5 a n d C P /6 S cop e This part of the I EC 62453-52-xy series, which is a Technical Report, provides information for integrating the PROFI N ET® technolog y into the CLI -based implem entation of FDT interface specification (I EC TR 62453-42) This part of I EC 62453 specifies im plementation of comm unication and other services based on I EC 62453-303-2 This docum ent neither contains the FDT specification nor modifies it N o rm a t i ve re fe re n c e s The following docum ents are referred to in the text in such a way that som e or all of their content constitutes requirem ents of this docum ent For dated references, onl y the edition cited applies For undated references, the latest edition of the referenced document (including an y amendments) applies I EC 61 31 -3: 201 3, Programmable controllers – Part 3: Programming languages I EC 61 58-6-1 0, Industrial communication networks – Fieldbus specifications – Part 6-10: Application layer protocol specification – Type 10 elements IEC 61 58 (all parts), Industrial communication networks – Fieldbus specifications IEC 61 784-1 : 201 4, Industrial communication networks – Profiles – Part 1: Fieldbus profiles IEC 62453-1 : 201 6, Field device tool (FDT) interface specification – Part 1: Overview and guidance IEC 62453-2: 201 6, Field device tool (FDT) interface specification – Part 2: Concepts and detailed description IEC TR 62453-42: 201 6, Field device tool (FDT) interface specification – Part 42: Object model integration profile – Common language infrastructure IEC 62453-303-2: 2009, Field device tool (FDT) interface specification – Part 303-2: Communication profile integration – IEC 61784 CP 3/4, I EC 62453-303-2: 2009/AMD1 : 201 CP 3/5 and CP 3/6 _ PROFI NET ® is th e tradem ark of PROFI BUS N utzerorganisation e V (PNO) PNO is a non-profit trad e org ani zati on to support the fiel dbus PROFI BUS This inform ation is given for th e conveni en ce of users of this I ntern ational Standard and does not constitute an end orsem ent by I EC of the trad em ark hold er or any of its products Com pliance to th is profi le does not req uire use of the reg istered tradem ark Use of the tradem ark PROFI BUS an d PROFI NET requi res perm ission of the trade nam e hold er Stt.010.Mssv.BKD002ac.email.ninhd.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj.dtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn.Stt.010.Mssv.BKD002ac.email.ninhddtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn C.vT.Bg.Jy.Lj.Tai lieu Luan vT.Bg.Jy.Lj van Luan an.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj Do an.Tai lieu Luan van Luan an Do an.Tai lieu Luan van Luan an Do an – 40 – I EC TR 62453-52-32: 201 © I EC 201 FdtDatatype Communication::SubscribeRequest # SubscribeRequest() «property» + CommunicationReference() :Guid PnSubscribeRequest {leaf} + PnSubscribeRequest() + PnSubscribeRequest(Guid) IEC Figu re – Pn Su bscribeRequ est Table – PnSubscribeRequest datatype Property Com m unicationReference U sag e M ulti pli ci ty M Description [1 ] Mand atory id entifi er for a com m unication link to a device This id entifier is all ocated by the comm unication com ponent du ri ng the Connect The address inform ation shall be used for all foll owing com m unication calls PnSu bscribeResponse The class PnSubscribeResponse describes a response when subscribing to device-initiated data transfer This specification provides a generic definition (see Figure and Table 7) FdtDatatype Communication::SubscribeResponse # SubscribeResponse() «property» + CommunicationReference() :Guid PnSubscribeResponse {leaf} + PnSubscribeResponse() + PnSubscribeResponse(Guid) IEC Figu re – PnSu bscri beRespon se Table – PnSubscribeResponse datatype Property Com m unicationReference U sag e M M u ltipl icity [1 ] Description Mand atory id entifi er for a com m unication link to a device This identifier is all ocated by the comm unication com ponent du ri ng the Connect The add ress inform ation shall be u sed for al l foll owi ng comm unication calls Stt.010.Mssv.BKD002ac.email.ninhd.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj.dtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn.Stt.010.Mssv.BKD002ac.email.ninhddtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn C.vT.Bg.Jy.Lj.Tai lieu Luan vT.Bg.Jy.Lj van Luan an.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj Do an.Tai lieu Luan van Luan an Do an.Tai lieu Luan van Luan an Do an I EC TR 62453-52-32: 201 © I EC 201 – 41 – U nsubscribeRequ est and U nsubscribeRespon se Servi ce 6.1 Pn UnsubscribeRequ est Servi ce The class PnU nsubscribeRequest describes a requ est in order to unsubscribe from deviceinitiated data transfer This specification provides a generic definition (see Figure and Table 8) FdtDatatype Communication::UnsubscribeRequest # UnsubscribeRequest() «property» + CommunicationReference() :Guid PnUnsubscribeRequest {leaf} + PnUnsubscribeRequest() + PnUnsubscribeRequest(Guid) IEC Figu re – PnU nsubscribeRequ est Table – PnU nsubscribeReq uest datatype Property Com m unicationReference U sag e M ul tipl icity M [1 ] Descri pti on Mand atory id entifi er for a com m unication link to a device This identifier is allocated by the com m unication com ponent d uri ng th e Conn ect The ad dress inform ation shal l be used for all followin g comm unication calls PnU nsubscribeResponse Service The class PnU nsubscribeResponse describes a response when unsubscribing from deviceinitiated data transfer This specification provides a generic definition (see Figure and Table 9) FdtDatatype Communication:: UnsubscribeResponse # UnsubscribeResponse() «property» + CommunicationReference() :Guid PnUnsubscribeResponse {leaf} + PnUnsubscribeResponse() + PnUnsubscribeResponse(Guid) IEC Figu re – Pn Un subscribeResponse Stt.010.Mssv.BKD002ac.email.ninhd.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj.dtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn.Stt.010.Mssv.BKD002ac.email.ninhddtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn C.vT.Bg.Jy.Lj.Tai lieu Luan vT.Bg.Jy.Lj van Luan an.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj Do an.Tai lieu Luan van Luan an Do an.Tai lieu Luan van Luan an Do an – 42 – I EC TR 62453-52-32: 201 © I EC 201 Table – PnUnsubscribeResponse datatype Property Com m unicationReference Usag e M ultiplicity M [1 ] Description Mand atory id entifi er for a com m unication link to a device This identifier is allocated by the com m unication com ponent during th e Conn ect The add ress inform ation shall be used for all followin g comm unication calls 0.7 AbortM essage Service The class PnAbortMessage describes the abort This message shall be sent when the communication component recognizes the loss of the ph ysical connection (see Figure and Table 20) FdtDatatype Communication::AbortMessage + Details :FdtList # AbortMessage() «property» + CommunicationReference() :Guid PnAbortMessage {leaf} + PnAbortMessage() + PnAbortMessage(Guid, FdtList) IEC Figu re – Pn AbortM essage Table 20 – Pn AbortM essage datatype Property Com m unicationReference Usag e M ultiplicity M [1 ] Description Mand atory id entifi er for a com m unication link to a device This identifier is allocated by the com m unication com ponent during th e Conn ect The add ress inform ation shall be used for all followin g comm unication calls 0.8 PnResponseError 0.8.1 Communication error The class PnResponseError describes the I EC 61 784 CPF 3/3 specific communication error (see Figure 20 and Table 21 ) I f a transaction fails, the response object shall provide either the response error or error inform ation I f the failure is specific to PROFI NET, the response error shall be used I f the failure is related to nested comm unication, the error information shall be used Stt.010.Mssv.BKD002ac.email.ninhd.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj.dtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn.Stt.010.Mssv.BKD002ac.email.ninhddtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn C.vT.Bg.Jy.Lj.Tai lieu Luan vT.Bg.Jy.Lj van Luan an.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj Do an.Tai lieu Luan van Luan an Do an.Tai lieu Luan van Luan an Do an I EC TR 62453-52-32: 201 © I EC 201 – 43 – FdtDatatype P n Res pon s eE rror {leaf} «Property» + ErrorCode1 :byte + ErrorCode2 :byte + ErrorDecode :byte + PnResponseError() + PnResponseError(byte, byte, byte) IEC F i g u re – P n R e s p o n s e E rro r Tabl e 21 P ro p e rt y – P n R e s p o n s e E rro r d a t a t y p e U sag e M u l ti p l i ci ty ErrorDecod e M [1 ] Status inform ation accordi ng to the I EC 61 784 CPF 3/3 specification ErrorCod e1 M [1 ] Status inform ation accordi ng to the I EC 61 784 CPF 3/3 specification ErrorCod e2 M [1 ] Status inform ation accordi ng to the I EC 61 784 CPF 3/3 specification H an d l i n g D e s c ri p t i o n o f e rro rs d u ri n g C o n n e c t a n d D i s co n n e ct I f an error occurs during of an I EC 61 784 CPF 3/3 connect or disconnect request, the communication component shall return an obj ect of type Comm unicationError The error coding shall be done in the field ErrorCode The ErrorCode shall contain the I EC 61 784 CPF 3/3 error information “ErrorDecode”, “ErrorCode1 ”, “ErrorCode2” exactl y in this sequence 1 D a t a t yp e s fo r p ro c e s s d a t a i n fo rm a t i o n 1 G e n e l ProcessData in a DTM can be used to represent the “Process values” available on that device A Process Control System (i e som e external system which monitors values on a device) can query the DTM’s ProcessData for its properties The ProcessData describes the process values such that an external system can use the inform ation to access and interpret the values from the device during norm al device runtime The external system might not use FDT to access the values 1 P n I O S i g n a l I n fo This is the PROFI N ET specific implem entation of the abstract class ProtocolI OSignalI nfo (see Figure 21 ) Stt.010.Mssv.BKD002ac.email.ninhd.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj.dtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn.Stt.010.Mssv.BKD002ac.email.ninhddtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn C.vT.Bg.Jy.Lj.Tai lieu Luan vT.Bg.Jy.Lj van Luan an.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj Do an.Tai lieu Luan van Luan an Do an.Tai lieu Luan van Luan an Do an – 44 – I EC TR 62453-52-32: 201 © I EC 201 P roces s D ataI tem P rotocol I OS i g n al I n fo I OS i g n al I n fo P n I OS i g n al I n fo ProtocolSpecificInfo I OS i g n al I n fo + + + + + API :UInt32 BitOffset :Uint32 ChannelNumber :UInt32 SlotNumber :UInt1 SubSlotNumber :UInt1 PnSignalType DatatypeInfo 1 «enumeration» P n D atatypeI n fo P n S i g n al Types + BitLength :UInt32 + ByteLength :UInt1 Datatype «enumeration» P rofi n etD atatype IEC U s ed in: I ProcessData:: () I ProcessData:: SetI OSignalI nfo() F i g u re – P ro t o c o l I O S i g n a l I n fo The properties of the datatype are described in Table 22 and Table 23 T a b l e 2 – P n D a t a t y p e I n fo P ro p e rt y U sag M u l ti p l i ci t e y D e s c ri p t i o n ByteLength O [0 ] Shoul d onl y be used to descri be the ByteLength of the d atatypes Visibl e-String and OctetStrin g BitLength O [0 ] Shoul d onl y be used to descri be the BitLength of the d atatypes BitArea Profin etDatatype M [1 ] Protocol specific datatype Stt.010.Mssv.BKD002ac.email.ninhd.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj.dtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn.Stt.010.Mssv.BKD002ac.email.ninhddtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn C.vT.Bg.Jy.Lj.Tai lieu Luan vT.Bg.Jy.Lj van Luan an.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj Do an.Tai lieu Luan van Luan an Do an.Tai lieu Luan van Luan an Do an I EC TR 62453-52-32: 201 © I EC 201 – 45 – T a b l e – P ro t o c o l l I O S i g n a l I n fo d a t a t y p e s U sag e M u l ti p l i ci t y API P ro p e rt y M [1 ] API Chann elN um ber M [1 ] Chann el num ber SlotNum ber M [1 ] Slot num ber SubSlotN um ber M [1 ] SubSlotN um ber BitOffset M [1 ] BitOffset 1 M appi n g D e s c ri p t i o n o f P RO F I N E T d a t a t y p e s t o F D T d a t a t y p e s The datatype mapping shall fulfill two functions: – The datatype defines the string representation form atting rules for a certain value provided in protocol specific datatypes The related string form ats are defined by W3C standards The binary layout of datatypes for param eterization purpose is defined by the Microsoft datatypes – The datatype describes the binary form at of I O signals contained in cyclic communication The binary layout of all datatypes is defined in the I EC 61 58 series Therefore the FDT defined datatypes have to be compared to the Microsoft N ET datatypes See Table for a mapping of datatypes The form at of all datatypes is defined in the I EC 61 58 series D e vi c e i d e n t i fi c a t i o n 2.1 G e n e l A PROFI N ET scan may detect different device types: I &M devices or pure DCP devices Depending on the detected device type, not all properties of PnDeviceScanI nfo or PnDeviceI dentI nfo are available The BusProtocol property shall be set either to Profinet_BusProtocol protocol_DCP or Profinet_BusProtocol protocol_I M to indicate the identification type for the device There is a strong recomm endation for the developers of comm unication DTMs, to support PnDeviceScanI nfo in two steps: The first scan should be done via DCP The second scan should be done via I &M (0 and ) The scan result is a merged data structure containing both information (DCP and I &M) 2.2 P n D e v i c e S c a n I n fo d a t a t y p e This is the protocol-specific im plem entation of the DeviceScanI nfo (see Figure 22 and Table 25) Stt.010.Mssv.BKD002ac.email.ninhd.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj.dtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn.Stt.010.Mssv.BKD002ac.email.ninhddtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn C.vT.Bg.Jy.Lj.Tai lieu Luan vT.Bg.Jy.Lj van Luan an.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj Do an.Tai lieu Luan van Luan an Do an.Tai lieu Luan van Luan an Do an – 46 – I EC TR 62453-52-32: 201 © I EC 201 IEC F i g u re 2 – P n D e v i c e S c a n I n fo d a t a t y p e The properties of the datatypes are described in Table 24 T a b l e – P n D e v i c e S c a n I n fo d a t a t yp e P ro p e rt y D e s c ri p t i o n Confi gu redState PnDeviceAddress Address inform ation of scanned device BusProtocolI d ProtocolI d BusProtocol Protocol used for scan (DCP or I M) ScannedPhysical Layer Determ ines the ph ysical m ediu m for which the scan inform ati on is provided DCP PROFI NET DCP data I M0 PROFI NET I M data I M1 PROFI NET I M data Table 25 defines the sem antics of PnDeviceScanI nfo properties and how this information is m apped to predefined properties of DeviceScanI nfo The Comm unication Channel will read these values from the device and write them into the properties of PnDeviceScanI nfo Stt.010.Mssv.BKD002ac.email.ninhd.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj.dtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn.Stt.010.Mssv.BKD002ac.email.ninhddtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn C.vT.Bg.Jy.Lj.Tai lieu Luan vT.Bg.Jy.Lj van Luan an.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj Do an.Tai lieu Luan van Luan an Do an.Tai lieu Luan van Luan an Do an P n D e v i c e S c a n I n fo p ro p e r t y n a m e D a t a t yp e M apped t o p ro p e r t y D a t a re q u e s t i n n am e i n P h ys i c a l P ro t o c o l d e vi c e P n i o d a t a fo rm a t s p e c i fi c n am e S p e c i fi c re fe re n c e D e v i c e S c a n I n fo PnDeviceAd dress I PAdress - I P-param eter - - Address - Standard Gateway - - Address - Subnet Mask - - Address Address I &M Elem ent UNSI GNED1 - DCP DeviceVend orValu e uint Manufactu rerI d MAC add ress Nam eOfStation MAN UFACTURER_I D MAN UFACTURER_I D UNSI GNED1 - I M1 DeviceN am e I M0 I M_Ord er_I D DCP DeviceI dentNum ber I M0 I M_Serial_N um ber I M0 I M_Hardware_Revision string string uint string string Tag DeviceTypeI d DeviceTypeI d Serial Num ber Hard wareRevisi on Ord erI D Visible Strin g[20] - I &M Elem ent I &M Elem ent Visible Strin g[1 6] Unsig ned - I M0 I M_Software_Revision string SoftwareRevisi on I &M Elem ent Uniq ue serial num ber HARDWARE_ REVI SI ON SOFTWARE_ REVI SI ON - I M0 I M_Profil e_I D int? I &M Elem ent PROFI LE_I D I M0 I M_Profil e_Specific_Type I nt? I &M Elem ent - Profin et_DeviceRole PROFI LE_SPECI FI C _TYPE DeviceRoleDetails Unsig ned DCP DeviceRol eDetail ProtocolSpecificPropert y ProtocolSpecificPropert y ProtocolSpecificPropert y Octets -1 Ch ar +3 Unsig ned e g V1 Unsig ned Unsig ned - PnDeviceAd dress I PDefaultGateway PnDeviceAd dress I PSubnetMask ProtocolI d PhysicalLayer Manufactu rerI d DCP DeviceVen dorVal ue I &M Elem ent I &M Elem ent DCP DeviceRol eDetail Stt.010.Mssv.BKD002ac.email.ninhd.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj.dtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn.Stt.010.Mssv.BKD002ac.email.ninhddtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn - – 47 – Address PnDeviceAd dress MacAdd ress PnDeviceAd dress Nam eOfStation Confi gu redState BusProtocolI d BusProtocol ScannedPhysical Layer I M0 I M_Vend or_I D System Net I PAddres s System Net I PAddres s System Net I PAddres s byte[6] string int? GUI D Profin et_BusProtocol PhysicalLayer uint I EC TR 62453-52-32: 201 © I EC 201 T a b l e – P n D e v i c e S c a n I n fo s p e c i fi c m a p p i n g C.vT.Bg.Jy.Lj.Tai lieu Luan vT.Bg.Jy.Lj van Luan an.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj Do an.Tai lieu Luan van Luan an Do an.Tai lieu Luan van Luan an Do an P n D e v i c e S c a n I n fo p ro p e r t y n a m e D a t a t yp e M apped t o p ro p e r t y n am e i n D a t a re q u e s t i n P h ys i c a l d e vi c e P ro t o c o l s p e c i fi c P n i o d a t a fo rm a t n am e S p e c i fi c re fe re n c e D e v i c e S c a n I n fo DCP M an ufacturerSpecificStrin g string ProtocolSpecificPropert y DCP Manufactu rerSpecific String ManufacturerSpecific String OctetString[Si ze accordi ng to DCPBlockLength] - – 48 – I EC TR 62453-52-32: 201 © I EC 201 Stt.010.Mssv.BKD002ac.email.ninhd.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj.dtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn.Stt.010.Mssv.BKD002ac.email.ninhddtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn C.vT.Bg.Jy.Lj.Tai lieu Luan vT.Bg.Jy.Lj van Luan an.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj Do an.Tai lieu Luan van Luan an Do an.Tai lieu Luan van Luan an Do an I EC TR 62453-52-32: 201 © I EC 201 2.3 – 49 – P n D e v i c e I d e n t I n fo d a t a t yp e PnDeviceI dentI nfo provides PROFI N ET specific identifications of supported device types returned by GetDeviceI nfo() (see Figure 23 and Table 26) For DTM assigned after Fieldbusscanning, the frame application can check in a protocol independent way, if the identification of a scanned device type (DeviceScanI nfo) m atches to the supported DeviceI nfo P n D evi ceI d en tI n fo IEC F i g u re – P n D e v i c e I d e n t I n fo T a b l e – P n D e v i c e I d e n t I n fo d a t a t y p e s P ro p e rt y D e s c ri p t i o n BusProtocolI d ProtocolI d I dDtm SupportLevel Enum eration valu e of the su pport Level of the DTM: genericSupport, profi leSu pport, blockspecificSu pport, specificSupport DeviceVen dorVal ue Manufactu rer identificati on n u m ber DCP_DeviceI d entN um ber Device id ent n um ber DCP_DeviceRoleDetail Device role d etail DCP_ManufacturerSpecificString Manufactu rer specific strin g I M_Ord er_I D The com plete ord er n um ber or at least the rel evant part that allows unam bigu ous id entificati on of the d evice withi n the m anufactu rer’s website (I M data) I M_Software_Revision Revision of the d evice em bedd ed software (I M data) I M_Hard ware_Revision Hard ware revisi on of th e device (I M data) I M_Profile_I D The profil e identification for the device (I M d ata) I M_Profile_Specific_Type Additional profi le id entificati on inform ation of the d evice (I M d ata) Table 27 defines the semantics of PnDeviceI dentI nfo properties an d how this inform ation is mapped to predefined properties of DeviceI dentI nfo Stt.010.Mssv.BKD002ac.email.ninhd.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj.dtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn.Stt.010.Mssv.BKD002ac.email.ninhddtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn C.vT.Bg.Jy.Lj.Tai lieu Luan vT.Bg.Jy.Lj van Luan an.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj Do an.Tai lieu Luan van Luan an Do an.Tai lieu Luan van Luan an Do an T a b l e – P n D e v i c e I n d e n t I n fo s p e c i fi c m a p p i n g P n D e v i c e I d e n t I n fo D a t a t yp e M apped p ro p e r t y n a m e t o p ro p e r t y D a t a re q u e s t i n n am e i n p h ys i c a l P ro t o c o l d e vi c e s p e c i fi c P n i o d a t a fo rm a t n am e S p e c i fi c re fe re n c e D e v i c e I d e n t I n fo - - - - Profin et_DTMSu pportLevel - - - - - DeviceVen dorVal ue uint Manufactu rerI d I &M El em ent or DCP DeviceVend orValue MAN UFACTURER_I D UNSI GNED1 - DCP_DeviceI d entN um ber uint DeviceTypeI d DCP DeviceI dentNum ber DeviceI dentN um ber Unsig ned - DCP_DeviceRol eDetail Profinet_DeviceRole ProtocolSpecificProperty DCP DeviceRol eDetail DeviceRoleDetail Unsig ned - DCP_ManufacturerSpecifi cString string ProtocolSpecificProperty DCP Manufactu rerSpecificStri n g Manufactu rerSpecific String OctetString[Si ze accordi ng to DCPBlockLength] - I M_Ord er_I D string ProtocolSpecificProperty I &M El em ent Ord erI D Visible Strin g[20] - I M_Hard ware_Revision string Hard wareRevisi on I &M Elem ent HARDWARE_ REVI SI ON Unsig ned - I M_Software_Revision string SoftwareRevisi on I &M Elem ent SOFTWARE_ REVI SI ON Octedts -1 Char +3 Unsig ned e g V1 - I M_Profile_I D int? ProtocolSpecificProperty I &M Elem ent PROFI LE_I D Unsig ned - I M_Profile_Specific_Type I nt? ProtocolSpecificProperty I &M Elem ent PROFI LE_SPECI FI C _TYPE Unsig ned - The PnDeviceI dentI nfo properties m ay have either a single value which shall exactl y m atch the supported device, or a range of m atching values may be defined in regular expressions Stt.010.Mssv.BKD002ac.email.ninhd.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj.dtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn.Stt.010.Mssv.BKD002ac.email.ninhddtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn I EC TR 62453-52-32: 201 © I EC 201 GUI D I dDTMSupportLevel – 50 – BusProtocol C.vT.Bg.Jy.Lj.Tai lieu Luan vT.Bg.Jy.Lj van Luan an.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj Do an.Tai lieu Luan van Luan an Do an.Tai lieu Luan van Luan an Do an I EC TR 62453-52-32: 201 © I EC 201 – 51 – 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-04-04] [2] FDT Online Help, J uly 201 [3] FDT I nterface Specification V1 2, Order No of FDT Group: 0001 -0001 -001 , available at http: //fdtgroup org/download/3866/ [viewed 201 7-04-04] [4] FDT I nterface Specification V1 2.1 , Order N o of FDT Group: 0001 -0001 -002, available at http: //fdtgroup org/download/3840/ [viewed 201 7-04-04] [5] FDT Group Field Device Tool for PROFI N ET I O V1 , Order N o of FDT Group: 00020008-000, available at http: //fdtgroup org/download/3840/ [viewed 201 7-04-04] [6] GSDM L 2.3: Technical Specification for PROFI N ET I O, October 201 [7] I dentification & M aintenance Functions 2: Profile Guidelines Part Guideline for PROFI BU S and PROFI N ET, M ay 2003 _ Stt.010.Mssv.BKD002ac.email.ninhd.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj.dtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn.Stt.010.Mssv.BKD002ac.email.ninhddtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn C.vT.Bg.Jy.Lj.Tai lieu Luan vT.Bg.Jy.Lj van Luan an.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj Do an.Tai lieu Luan van Luan an Do an.Tai lieu Luan van Luan an Do an Stt.010.Mssv.BKD002ac.email.ninhd.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj.dtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn.Stt.010.Mssv.BKD002ac.email.ninhddtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn C.vT.Bg.Jy.Lj.Tai lieu Luan vT.Bg.Jy.Lj van Luan an.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj Do an.Tai lieu Luan van Luan an Do an.Tai lieu Luan van Luan an Do an Stt.010.Mssv.BKD002ac.email.ninhd.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj.dtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn.Stt.010.Mssv.BKD002ac.email.ninhddtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn C.vT.Bg.Jy.Lj.Tai lieu Luan vT.Bg.Jy.Lj van Luan an.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj Do an.Tai lieu Luan van Luan an Do an.Tai lieu Luan van Luan an Do an Stt.010.Mssv.BKD002ac.email.ninhd.vT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.LjvT.Bg.Jy.Lj.dtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn.Stt.010.Mssv.BKD002ac.email.ninhddtt@edu.gmail.com.vn.bkc19134.hmu.edu.vn