Iec tr 62453 52 150 2017

I E C TR 62 453 -52 -1 50 ® 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 -1 50 : C om m u n i cati on i m pl e m e n tati on for com m on l an g u ag e IEC TR 62453-52-1 50:201 7-06(en) i n fras tru ctu re – I E C 61 84 C P F 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 -1 50 ® 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 -1 50 : C om m u n i cati on i m pl e m e n 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 F INTERNATIONAL ELECTROTECHNICAL COMMISSION ICS 25.040.40; 35.1 00.05; 35.1 ISBN 978-2-8322-4336-7 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-1 50: 201 © I EC 201 CONTENTS FOREWORD I NTRODUCTI ON 1 Scope 1 Norm ative references 1 Terms, definitions, symbols, abbreviated term s and conventions Terms and definitions Sym bols and abbreviated terms 3 Conventions 3 Datatype names and references to datatypes 3 Vocabulary for requirem ents 3 Use of U ML Bus category Access to instance and device data General I O signals provided by DTM Data interfaces Common data set Mapping of Modbus datatypes to FDT datatypes 3 SemanticI nfo Protocol specific behaviour Modbus data and addressing model Modbus-related inform ation of a Device DTM Broadcasting Unconfirm ed private Modbus request Protocol specific usage of general datatypes Protocol specific common datatype: ModbusDeviceAddress Network managem ent datatypes General Configuration 9 Process Data I tem s 9 Parameterization Comm unication datatypes 1 General ModbusConnectRequest ModbusConnectResponse 20 ModbusDisconnectRequest 20 ModbusDisconnectResponse 21 ModbusAbortM essage 21 ModbusReadCoilsRequest 22 ModbusReadCoilsResponse 23 ModbusReadDiscreteI nputsRequest 24 1 ModbusReadDiscreteI nputsResponse 24 1 ModbusReadHoldingRegistersRequest 25 1 ModbusReadHoldingRegistersResponse 26 1 ModbusReadI nputRegistersRequest 27 1 ModbusReadI nputRegistersResponse 28 I EC TR 62453-52-1 50: 201 © I EC 201 –3– 1 ModbusWriteSingleCoilRequest 29 1 ModbusWriteSingleCoilResponse 30 1 ModbusWriteSingleRegisterRequest 30 1 ModbusWriteSingleRegisterResponse 31 1 ModbusReadExceptionStatusRequest 32 20 ModbusReadExceptionStatusResponse 32 21 ModbusDiagnosticsRequest 33 22 ModbusDiagnosticsResponse 34 23 ModbusGetCom mEventCounterRequest 35 24 ModbusGetCom mEventCounterResponse 35 25 ModbusGetCom mEventLogRequest 36 26 ModbusGetCom mEventLogResponse 37 27 lModbusWriteMultipleCoilsRequest 38 28 ModbusWriteM ultipleCoilsResponse 39 29 ModbusWriteM ultipleRegistersRequest 39 30 ModbusWriteM ultipleRegistersResponse 40 31 ModbusReportSlaveI DRequest 41 32 ModbusReportSlaveI DResponse 41 33 ModbusReadFileRecordRequest 42 34 ModbusReadFileSubRequest 43 35 ModbusReadFileRecordResponse 44 36 ModbusReadFileSubResponse 45 37 ModbusWriteFileRecordRequest 45 38 ModbusWriteFileSubRequest 46 39 ModbusWriteFileRecordResponse 47 40 ModbusMaskWriteRegisterRequest 47 41 ModbusMaskWriteRegisterResponse 48 42 ModbusReadWriteRegistersRequest 49 43 ModbusReadWriteRegistersResponse 50 44 ModbusReadFiFoQueueRequest 51 45 ModbusReadFiFoQueueResponse 52 46 ModbusEncapsulatedI nterfaceTransportRequest 53 47 ModbusEncapsulatedI nterfaceTransportResponse 53 48 ModbusReadDeviceI dentificationRequest 54 49 ModbusReadDeviceI dentificationResponse 55 50 ModbusPrivateRequest 58 51 ModbusPrivateResponse 58 52 ModbusU nconfirm edPrivateRequest 59 53 ModbusU nconfirm edPrivateResponse 60 54 ModbusExceptionResponse 61 1 Datatypes for process data inform ation 62 1 General 62 1 ModbusI OSignalI nfo 62 1 Mapping of Modbus datatypes to FDT datatypes 63 Device identification 63 General 63 2 ModbusDeviceScanI nfo datatype 63 ModbusDeviceI dentI nfo datatype 64 Mapping of I nformation Source 66 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– I EC TR 62453-52-1 50: 201 © I EC 201 Bibliograph y 68 Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure 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-1 50 of the I EC 62453 series – Modbus data and addressing m odel – ModbusDeviceAddress – ModbusN etworkData – ModbusConnectRequest – ModbusConnectResponse 20 – ModbusDisconnectRequest 21 – ModbusDisconnectResponse 21 – ModbusAbortMessage 22 – ModbusReadCoilsRequest 22 1 – ModbusReadCoilsResponse 23 – ModbusReadDiscreteI nputsRequest 24 – ModbusReadDiscreteI nputsResponse 25 – ModbusReadHoldingRegistersRequest 26 – ModbusReadHoldingRegistersResponse 27 – ModbusReadI nputRegistersRequest 28 – ModbusReadI nputRegistersResponse 28 – ModbusWriteSingleCoilRequest 29 – ModbusWriteSingleCoilResponse 30 20 – ModbusWriteSingleRegisterRequest 31 21 – ModbusWriteSingleRegisterResponse 31 22 – ModbusReadExceptionStatusRequest 32 23 – ModbusReadExceptionStatusResponse 33 24 – ModbusDiagnosticsRequest 34 25 – ModbusDiagnosticsResponse 34 26 – ModbusGetComm EventCounterRequest 35 27 – ModbusGetComm EventCounterResponse 36 28 – ModbusGetComm EventLogRequest 37 29 – ModbusGetComm EventLogResponse 37 30 – ModbusWriteMultipleCoilsRequest 38 31 – ModbusWriteMultipleCoilsResponse 39 32 – ModbusWriteMultipleRegistersRequest 40 33 – ModbusWriteMultipleRegistersResponse 40 34 – ModbusReportSlaveI DRequest 41 35 – ModbusReportSlaveI DResponse 42 36 – ModbusReadFileRecordRequest 43 37 – ModbusReadFileSubRequest 43 38 – ModbusReadFileRecordResponse 44 39 – ModbusReadFileSubResponse 45 40 – ModbusWriteFileRecordRequest 46 41 – ModbusWriteFileSubRequest 46 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-1 50: 201 © I EC 201 Figure Figure Figure Figure 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 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 –5– – ModbusWriteFileRecordResponse 47 – ModbusMaskWriteRegisterRequest 48 – ModbusMaskWriteRegisterResponse 49 – ModbusReadWriteRegistersRequest 50 – ModbusReadWriteRegistersResponse 51 – ModbusReadFiFoQueueRequest 52 – ModbusReadFiFoQueueResponse 52 – ModbusEncapsulatedI nterfaceTransportRequest 53 – ModbusEncapsulatedI nterfaceTransportResponse 54 – ModbusReadDeviceI dentificationRequest 55 – ModbusReadDeviceI dentificationResponse 56 – ModbusI dentificationObject 56 – ModbusPrivateRequest 58 – ModbusPrivateResponse 59 – ModbusUnconfirm edPrivateRequest 60 – ModbusUnconfirm edPrivateResponse 60 – ModbusExceptionResponse 61 – ModbusI OSignalI nfo 62 – ModbusDeviceScanI nfo 64 – ModbusDeviceI dentI nfo 65 – Mapping of datatypes – Usage of general datatypes – Usage of broadcasts in transaction requests – Protocol specific usage of general datatypes – ModbusDeviceAddress – ModbusDeviceSerialAddress – ModbusDeviceTcpAddress 8 – Modbus N etwork Data 9 – ModbusConnectRequest datatype 20 – ModbusConnectResponse datatype 20 1 – ModbusDisconnectRequest datatype 21 – ModbusDisconnectResponse datatype 21 – ModbusAbortMessage datatype 22 – ModbusReadCoilsRequest datatype 23 – ModbusReadCoilsResponse datatype 23 – ModbusReadDiscreteI nputsRequest datatype 24 – ModbusReadDiscreteI nputsResponse datatype 25 – ModbusReadHoldingRegistersRequest datatype 26 – ModbusReadHoldingRegistersResponse datatype 27 20 – ModbusReadI nputRegistersRequest datatype 28 21 – ModbusReadI nputRegistersResponse datatype 29 22 – ModbusWriteSingleCoilRequest datatype 29 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– 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 Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 I EC TR 62453-52-1 50: 201 © I EC 201 – M odbusWriteSingleCoilResponse datatype 30 – ModbusWriteSingleRegisterRequest datatype 31 – ModbusWriteSingleRegisterResponse datatype 32 – ModbusReadExceptionStatusRequest datatype 32 – ModbusReadExceptionStatusResponse datatype 33 – ModbusDiagnosticsRequest datatype 34 – ModbusDiagnosticsResponse datatype 35 – ModbusGetComm EventCounterRequest datatype 35 – ModbusGetComm EventCounterResponsedatatype 36 – ModbusGetComm EventLogRequest datatype 37 – ModbusGetComm EventLogResponse datatype 38 – ModbusWriteMultipleCoilsRequest datatype 39 – ModbusWriteMultipleCoilsResponse datatype 39 – ModbusWriteMultipleRegistersRequest datatype 40 – ModbusWriteMultipleRegistersResponse 41 – ModbusReportSlaveI DRequest datatype 41 – ModbusReportSlaveI DResponse 42 – ModbusReadFileRecordRequest datatype 43 – ModbusReadFileSubRequest datatype 44 – ModbusReadFileRecordResponse 45 – ModbusReadFileSubResponse 45 – ModbusWriteFileRecordRequest datatype 46 – ModbusWriteFileSubRequest datatype 47 – ModbusWriteFileRecordResponse 47 – ModbusM askWriteRegisterRequest datatype 48 – ModbusMaskWriteRegisterResponse 49 – ModbusReadWriteRegistersRequest datatype 50 – ModbusReadWriteRegistersResponse 51 – ModbusReadFiFoQueueRequest datatype 52 – ModbusReadFiFoQueueResponse 53 – ModbusEncapsulatedI nterfaceTransportRequest datatype 53 – ModbusEncapsulatedI nterfaceTransportResponse 54 – ModbusReadDeviceI dentificationRequest datatype 55 – ModbusReadDeviceI dentificationResponse 57 – ModbusI dentificationObj ect 58 – ModbusPrivateRequest datatype 58 – ModbusPrivateResponse 59 – ModbusUnconfirmedPrivateRequest datatype 60 – ModbusUnconfirm edPrivateResponse 61 – ModbusExceptionResponse 62 – ModbusI OSignalI nfo datatype 63 – ModbusDeviceScanI nfo datatype 64 – ModbusDeviceI dentI nfo datatype 65 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-1 50: 201 © I EC 201 –7– Table 66 – Protocol specific m apping of scan inform ation 66 Table 67 – Profile specific m apping of identification information 67 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-1 50: 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 -1 : C o m m u n i c a ti o n i m p l e m e n ta 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 EC 61 784 CP F FOREWORD ) The I nternati on al Electrotechni cal Comm ission (I EC) is a worl d wid e organization for stan dardization com prisin g all n ation al el ectrotechnical comm ittees (I EC National Comm ittees) The object of I EC is to prom ote internati onal co-operation on all q uestions concerni ng stand ardi zati on in the el ectrical an d electronic fi elds To this en d and in additi on to other acti vities, I EC pu blish es I nternational Stan dards, Techn ical Specificati ons, Technical Reports, Publicl y Avail abl e Specificati ons (PAS) and Gu ides (h ereafter referred to as “I EC Publication(s)”) Th ei r preparation is entrusted to tech nical comm ittees; any I EC N ational Comm ittee interested in the subj ect dealt with m ay partici pate in this preparatory work I nternational, governm ental an d n on governm ental organ izations l iaising with th e I EC also participate i n this preparation I EC collaborates closel y with the I nternational Organi zation 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 n early as possible, an i nternati onal consensus of opi nion 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 Publications have the form of recom m endations for intern ational use an d are accepted by I EC National Com m ittees in that sense While all reasonable efforts are m ade to ensure that th e tech nical content of I EC Publications is accu rate, I EC cann ot be h eld responsi ble for th e way in which th ey are used or for an y m isinterpretation by an y en d u ser 4) I n order to prom ote intern ational u niform ity, I EC National Com m ittees und ertake to apply I EC Publications transparentl y to the m axim um extent possible i n their national an d regi on al publicati ons Any d ivergence between an y I EC Publication and the correspondi ng national or regi on al publicati on sh all be clearl y in dicated in the latter 5) I EC itself d oes n ot provi de an y attestation of conform ity I n depend ent certificati on bodies provi de conform ity assessm ent services and, 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 they 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 inclu din g in divi du al experts an d m em bers of its tech nical com m ittees and I EC Nati on al Com m ittees for any person al i nju ry, property d am age or other dam age of any n ature whatsoever, wheth er di rect or indirect, or for costs (includ i ng leg al fees) and expenses arisi ng out of the publ ication, use of, or relian ce upon, this I EC Publicati on or any other I EC Publications 8) Attention is drawn to th e N orm ative references cited in th is publ ication Use of the referenced publ ications is indispensable for the correct applicati on of this publication 9) Attention is drawn to the possibility that som e of the elem ents of this I EC Publication m ay be the su bject of patent rig hts I EC shall not be held responsibl e for identifyi ng any or all such patent ri ghts The m ain task of I EC technical com mittees is to prepare I nternational Standards H owever, a technical committee m ay propose the publication of a technical report when it has collected data of a different kind from that which is normally published as an I nternational Standard, for exam ple "state of the art" I EC TR 62453-52-1 50, which is a technical report, has been prepared by subcomm ittee 65E: Devices and integration in enterprise systems, of I EC technical comm ittee 65: I ndustrial process m easurem ent, 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 This docum ent corresponds to IEC 63453-31 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 – 56 – I EC TR 62453-52-1 50: 201 © I EC 201 TransactionResponse Commu nication Reference: Gu id ErrorIn formation: Commu nication Error I d: String ModbusTransactionResponse M od b u sR ea d De vi ce Id en t ific at io n Re sp on se Read Devi ceId Cod e: byte ConformityLevel: byte M oreFol lows: bool N extObjectI d: byte N umberOfObjects: byte Modbu sId entificationObjects …* M od b u sI d en ti fi ca ti on Ob je ct IEC U s ed in: I Communication EndComm unicationRequest() F i g u re – M o d b u s R e a d D e v i c e I d e n t i fi c a t i o n R e s p o n s e The properties of the M odbusReadDeviceI dentificationResponse datatype are described in Table 56 M od b u sI d en ti fi ca ti on Ob je ct ObjectId: byte ObjectValue: byte[] IEC F i g u re – M o d b u s I d e n t i fi c a t i o n O b j e c t The properties of the M odbusI dentificationObj ect datatype are described in Table 57 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-1 50: 201 © I EC 201 – 57 – T a b l e – M o d b u s Re a d D e v i c e I d e n t i fi c a t i o n R e s p o n s e P ro p e rt y D e s c ri p t i o n E q u i va l e n t I E C 1 -5 -1 s e r v i c e p a m e t e r Com m unicationReference I dentifi er for a com m unication l ink to a device Com m unicationReference Conform ityLevel I dentificati on conform ity level of the device and type of supported access 01 : basic id entificati on (stream access only) 02: regul ar i dentification (stream access only) 03: exten ded identification (stream access onl y) 81 : basic id entificati on (stream access and indi vidual access) 82: regul ar id entificati on (stream access and indi vidual access) 83: extend ed i dentificati on (stream access and indi vidual access) Conform ity level ErrorI nform ation [Option al] Descri ption of a field bus protocol independent error occu rred d uring comm unication Id [Option al] I dentifier for a singl e Transaction Req uest ModbusI dentificati onObject I dentificati on objects of the Read Device I dentificati on service response provi ded by th e Encapsulated I nterface defined in I EC 61 58-5-1 MoreFollows I n case of read DeviceI d Cod e 01 , 02 or 03 (stream access), if the identification data does not fit into a sin gle response and several req uest/response transactions m ay be requi red: “0”: no m ore objects are avail able; “1 ”: other identification objects are avail abl e and fu rther Modbus tran sactions are req uired More-avai labl e flag I n case of ReadDevI d cod e 04 (indivi du al access), this field shall be set to “0” NextObj ectid “0”, if n o m ore id entificati on objects are avai l able (m oreFol lows=”0”) Next obj ect I D I dentificati on of th e next object to be obtain ed, if m ore identification obj ects are available (m oreFol lows=”1 ”) Num berOfObjects Num ber of i dentification obj ects returned in this response (for an in dividu al access, num berOfObjects=”1 ”) Num ber of objects ReadDeviceI dCode The param eter " Read Device I D code " allows to defin e fou r access types: 01 : requ est to get the basic device identificati on (stream access); 02: requ est to get th e reg ular d evice identificati on (stream access); 03: req uest to get the exten ded d evice identificati on (stream access); 04: requ est to get one speci fic identification object (i ndi vi dual access) Read device I D code ModbusI dentificati onObject I dentificati on conform ity level of the device and type of supported access 01 : basic id entificati on (stream access only) 02: regul ar i dentification (stream access only) 03: exten ded identification (stream access onl y) Conform ity level 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 – 58 – P ro p e rt y I EC TR 62453-52-1 50: 201 © I EC 201 D e s c ri p t i o n E q u i va l e n t I E C 1 -5 -1 s e r v i c e p a m e t e r 81 : basic id entificati on (stream access and indi vid ual access) 82: regul ar id entificati on (stream access and indi vid ual access) 83: extend ed i dentificati on (stream access and indi vidual access) T a b l e – M o d b u s I d e n t i fi c a t i o n O b j e c t P ro p e rt y D e s c ri p t i o n E q u i va l e n t I E C 1 -5 -1 s e r v i c e p a m e t e r ObjectI d I dentificati on of th e returned object Retu rn ed object I D ObjectValu e Object valu e Object valu e 50 M o d b u s P ri v a t e R e q u e s t This subclause describes the request for a private Modbus service (see Figure 54) Id: string TransactionRequest ModbusTransactionRequest M od b u sP ri va te Re q u es t Pri vateReq uest: byte[] IEC U sed in: I Comm unication BeginCommunicationRequest() F i g u re – M o d b u s P ri v a t e R e q u e s t The properties of the M odbusPrivateRequest datatype are described in Table 58 T a b l e – M o d b u s P ri v a t e R e q u e s t d a t a t y p e P ro p e rt y D e s c ri p t i o n E q u i va l e n t I E C 1 -5 -1 s e r v i c e p a m e t e r Id [Option al] I dentifier for a singl e Transacti on Req uest PrivateReq uest Sequence of h exad ecim al digits representin g the pri vate M odbu s request 51 M o d b u s P ri v a t e R e s p o n s e This subclause describes the response for a private Modbus service (see Figure 55) 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-1 50: 201 © I EC 201 – 59 – TransactionResponse Commu nication Reference: Gu id ErrorIn formation: Commu nication Error Id: String ModbusTransactionResponse M od b u sP ri va te Re spon s e Pri vateRes pon s e: byte[] IEC U sed in: I Comm unication EndComm unicationRequest() F i g u re 5 – M o d b u s P ri v a t e R e s p o n s e The properties of the ModbusPrivateResponse datatype are described in Table 59 T a b l e – M o d b u s P ri v a t e R e s p o n s e P ro p e rt y D e s c ri p t i o n E q u i val e n t I E C 1 - - s e rv i c e p a m e t e r Com m unicationReference I dentifi er for a com m unication l ink to a device ErrorI nform ation [Option al] Descri ption of a field bus protocol in dependent error occurred during com m unication Id [Option al] I dentifier for a singl e Transacti on Req uest PrivateResponse Sequence of h exad ecim al digits representin g the pri vate Modbu s response 52 Com m unicationReference M o d b u s U n c o n fi rm e d P ri v a t e R e q u e s t This subclause describes the request for an unconfirmed private M odbus service (see Figure 56) 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 – 60 – Id: string I EC TR 62453-52-1 50: 201 © I EC 201 TransactionRequest ModbusTransactionRequest M od b u sU n fi rm ed P ri v ate Re q u e st Pri vateReq uest: byte[] IEC U s ed in: I Communication BeginCommunicationRequest() F i g u re – M o d b u s U n c o n fi rm e d P ri v a t e R e q u e s t The properties of the ModbusUnconfirm edPrivateRequest datatype are described in Table 60 T a b l e – M o d b u s U n c o n fi rm e d P ri v a t e R e q u e s t d a t a t y p e P ro p e rt y D e s c ri p t i o n E q u i va l e n t I E C 1 -5 -1 s e r v i c e p a m e t e r Id [Option al] I dentifier for a singl e Transacti on Req uest PrivateReq uest Sequence of h exad ecim al digits representin g the pri vate M odbu s request 53 M o d b u s U n c o n fi rm e d P ri v a t e R e s p o n s e This subclause describes the response for an unconfirm ed private Modbus service (see Figure 57) TransactionResponse Commu nication Reference: Gu id ErrorIn formation: Commu nication Error I d: String ModbusTransactionResponse M od b u sU n fi rm ed P ri v ate Re sp o n se IEC U s ed in: I Comm unication EndComm unicationRequest() F i g u re – M o d b u s U n c o n fi rm e d P ri v a t e R e s p o n s e 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-1 50: 201 © I EC 201 – 61 – The properties of the ModbusU nconfirmedPrivateResponse datatype are described in Table 61 Tabl e 61 – M o d b u s U n c o n fi rm e d P ri v a t e R e s p o n s e P ro p e rt y D e s c ri p t i o n E q u i val e n t I E C 1 - - s e rv i c e p a m e t e r Com m unicationReference I dentifi er for a com m unication l ink to a device ErrorI nform ation [Option al] Descri ption of a field bus protocol in dependent error occurred during com m unication Id [Option al] I dentifier for a singl e Transacti on Req uest 54 Com m unicationReference M o d b u s E xce p ti o n Re s p o n s e This subclause describes the Modbus Exception Response (see Figure 58) TransactionResponse Commu nication Reference: Gu id ErrorIn formation: Commu nication Error Id: String ModbusTransactionResponse M od b u sE xc ep t i on Re sp o n se M od bu s Servi ce: Modbu sServiceEnu m M od bu s Exception Cod e: byte IEC U sed in: I Comm unication EndCom municationRequest() F i g u re – M o d b u s E x c e p t i o n R e s p o n s e The properties of the ModbusExceptionResponse datatype are described in Table 62 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 – 62 – I EC TR 62453-52-1 50: 201 © I EC 201 T a b l e – M o d b u s E x c e p t i o n Re s p o n s e P ro p e rt y D e s c ri p t i o n E q u i val e n t I E C 1 -5 -1 s e rv i c e p a m e t e r Com m unicationReference I dentifi er for a com m unication l ink to a device ErrorI nform ation [Option al] Descri ption of a field bus protocol independent error occu rred d uring comm unication Id [Option al] I dentifier for a singl e Transaction Req uest ModbusService Enum eration of Mod bus service nam es, used to identify th e M odbus service on which the exception occurred ModbusExcepti onCod e Modbus Exception Code 1 Com m unicationReference Exception cod e 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 The process data information of a DTM represents the “Device Variables”, available on that device A Process Control System (i e som e external system which m onitors values on a device) can query the DTM's process data inform ation via the I ProcessData interface The process data describes the process values such that an external system can use the inform ation to access and interpret the values from the device during normal device runtim e The external system m ight not use FDT to access the values 1 M o d b u s I O S i g n a l I n fo This is the Modbus specific im plementation of the abstract class ProtocolI OSignalI nfo (see Figure 59) Pro c es sD at aI te m Pro t o co lI OSig n a lIn fo IOS ig n alI n fo M od busI OSign alIn fo IOS ig n alI n fo ProtocolS pecif icI nfo M o db u s IOSi g na In fo Ad dress : int Qu an tity : int BitP osition : int BitLen gth : int ReadAccess : bool WriteAccess : bool DatatypeIn fo M o db u s Da t at yp eI n fo Datatype : M od busDatatype ByteLeng th : uin t IEC U s ed in: IProcessData () IProcessData SetI OSignalI nfo() F i g u re – M o d b u s I O S i g n a l I n fo 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-1 50: 201 © I EC 201 – 63 – The properties of the ModbusI OSignalI nfo datatype are described in Table 63 T a b l e – M o d b u s I O S i g n a l 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 Address of the discrete input, coil or register which sh all be accessed I n case of a rang e of these Mod bus d ata item s shall be accessed, the add ress datatype contains the add ress of the fi rst Modbus d ata item withi n this rang e BitLength Num ber of bits BitPosition I f the access to single bits or som e collections of bits is need ed, it can be defi ned the BitPosition an d BitLength property ModbusDatatypeI nfo The d atatype of the I O sign al Quantity Num ber of discrete i nputs, coil s or registers which represent the channel obj ect in the device ReadAccess Defin es wh ether the I OSi gnal can be read or n ot WriteAccess Defin es wh ether the I OSi gnal can be written or n ot The Modbus data model defines four prim ary datatypes: • • • • Discrete I nputs; Coils; I nput Registers; Holding Registers The bit access is defined for Discrete I nputs and Coils N evertheless, most devices use Holding Register for input and output data, also with bit access If the access to single bits or som e collections of bits is needed, it can be defined inside the ModbusI OSignalI nfo datatype with the BitPosition and BitLength properties I t is also feasible to define the bits of a H olding Register and additionall y the whole word of the sam e Holding Register as an I O signal I n other words, it is possible to define process data objects for a single holding register On the other hand it is not mandatory to describe all bits of a register word 1 M appi n g o f M o d b u s d a t a typ e s to F D T d a t a typ e s The datatype mapping defines how Modbus I O Signals are m apped to PLC applications using datatypes defined in I EC 61 31 -3 See Table for a mapping of datatypes 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 This subclause defines identification relevant protocol specific datatypes 2.2 M o d b u s D e v i c e S c a n I n fo d a t a t y p e This is the Modbus specific implem entation of the abstract class ProtocolDeviceScanI nfo (see Figure 60) 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 – 64 – I EC TR 62453-52-1 50: 201 © I EC 201 Pro t o co lD e vic eS can I nfo D ev ice Sc an In fo ProtocolI d : Gu id M od busDeviceScanIn fo M o db u s De vi ceS ca n In fo D ev ice Sc an In fo ProtocolS pecif icS can Info Bu sProtocolId : Gu id Vend orName : string Prod uctCode : string MajorMin orRevision : string Vend orUrl : string Prod uctName : string M od elName : string UserApplicationName : string Pro t o co lD e vic eAd d res s M o db u s De vi ceAd d re ss Ad dress IEC U s ed in: I DtmScanning EndScanRequest() F i g u re – M o d b u s D e v i c e S c a n I n fo The properties of the ModbusDeviceScanI nfo datatype are described in Table 64 T a b l e – M o d 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 Address D e s c ri p t i o n The bus add ress of the device BusProtocolI d Can be set to either M od bus Seri al or M odbus TCP This inform ation is provi ded by the Com m unication Chan nel (based on the ScanRequest) Maj orMi norRevisi on I nform ation of th e Mod bus protocol specific identification obj ect MajorMin orRevision Model Nam e I nform ation of th e Mod bus protocol specific identification obj ect ModelN am e Prod uctCod e I nform ation of th e Mod bus protocol specific identification obj ect ProductCode Prod uctNam e I nform ation of th e Mod bus protocol specific identification obj ect ProductNam e UserApplicati onN am e I nform ation of th e Mod bus protocol specific identification obj ect UserApplicati on Nam e VendorN am e I nform ation of th e Mod bus protocol specific identification obj ect VendorNam e VendorU rl I nform ation of th e Mod bus protocol specific identification obj ect VendorUrl 2.3 M o d 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 Modbus DTMs that may connect to a Modbus Communication Channel (e g Device DTMs and Gateway DTMs) shall provide inform ation, which m ay be used to identify the corresponding devices on the fieldbus This subclause describes the offline information (see Figure 61 ) For DTM assigned after Fieldbus-scanning, the fram e application can check in a protocol independent way if the identification of a scanned device type (DeviceScanI nfo) matches the supported DeviceI 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 I EC TR 62453-52-1 50: 201 © I EC 201 – 65 – Pro t o co lD e vic eId e n tI nfo D ev ice Id en t In fo ProtocolI d : Gu id Mod busDeviceId entInfo M o db u s De vi ceI d en t In fo D ev ice Id en t In fo ProtocolS pecif icI den tIn fo Bu sProtocol : Gu id Man ufacturerId : string DeviceTypeCod e : string SoftwareRevision : string Prod uctName : string Mod elName : string Vend orUrl : string UserApplicationName : string IEC U sed in: I DtmI nformation.GetDeviceI dentI nfo() F i g u re – M o d b u s D e v i c e I d e n t I n fo The properties of the ModbusDeviceI dentI nfo datatype are described in Table 65 T a b l e – M o d 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 u niq ue id entifi er of either Modbus Serial or Modbus TCP DeviceTypeCode Modbus product cod e ManufacturerI d Modbus vendor n am e Model Name Modbus m odel nam e Prod uctNam e Modbus product nam e SoftwareRevisi on Modbus Maj or Mi nor Version UserApplicati onN am e Modbus user application nam e VendorU rl Modbus Vendor U RL The information described here will be used to m atch the information retrieved from Com munication Channels via the method I Com munication This match is executed by device independent software That is wh y it is im portant to provide in ModbusDeviceI dentI nfo inform ation that can be m atched with the ModbusDeviceScanI nfo inform ation Developers of DTMs need to consider which inform ation the devices will provide (see 4) 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 2.4 M appi n g o f I n fo rm a t i o n S o u rc e Table 66 defines the sem antics of ModbusDeviceScanI nfo properties and how this inform ation is mapped to predefined properties of DeviceScanI nfo The Comm unication channel will read these values from the device and write them into the properties of ModbusDeviceScanI nfo T a b l e 6 – P ro t o c o l M o d b u s D e v i c e S c a n I n fo p ro p e r t y n a m e M apped 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 D a ta Req u e s t i n of s can p h ys i c a l i n fo rm a t i o n d evi ce P ro t o c o l p ro p e rt y n a m e s p e c i fi c M o d b u s d a ta n am e S p e c i fi c r e fe re n c e fo rm a t ProtocolI dentificati onProfil e - - - Address Address BusAddress Modbus device ad dress - - - BusProtocolI d ProtocolI d Set by Com m unicationCh annel - - - - PhysicalLayer - - - - VendorN am e Manufactu rerI d Function code 43 /1 4, Object I d 0x00 VendorN am e String [2] 21 ProductCod e DeviceTypeI d Function code 43 /1 4, Object I d 0x01 ProductCod e String [2] 21 Maj orMi norRevisi on SoftwareRevisi on Function code 43 /1 4, Object I d 0x02 Maj orMi norRevisi on String [2] 21 VendorU rl ProtocolSpecificProperty Function code 43 /1 4, Object I d 0x03 VendorU rl String [2] 21 ProductNam e ProtocolSpecificProperty Function code 43 /1 4, Object I d 0x04 Prod uctNam e String [2] 21 Model Nam e ProtocolSpecificProperty Function code 43 /1 4, Object I d 0x05 Model Nam e String [2] 21 UserApplicati onN am e ProtocolSpecificProperty Function code 43 /1 4, Object I d 0x06 UserApplicati onN am e String [2] 21 Table 67 defines the semantics of M odbusDeviceI dentI nfo properties and how this inform ation is m apped 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 I EC TR 62453-52-1 50: 201 © I EC 201 P ro t o c o l S p e c i fi c P r o p e r t i e s : – 66 – - 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 M o d b u s D e v i c e I d e n t I n fo p ro p e r t y n a m e M apped D e v i c e I d e n t I n fo D a ta Req u e s t i n o f i d e n t i fi c a t i o n p h ys i c a l i n fo rm a t i o n d evi ce P ro t o c o l p ro p e rt y n a m e s p e c i fi c n am e M od bu s S p e c i fi c r e fe re n c e d a t a fo rm a t BusProtocol ProtocolI d Set by Com m unicationCh annel - - - ProtocolI dentificati onProfil e - - - - Manufactu rerI d Manufactu rerI d Function code 43 /1 4, Object I d 0x00 VendorN am e String [2] 21 DeviceTypeCode DeviceTypeI d Function code 43 /1 4, Object I d 0x01 Prod uctCode String [2] 21 SoftwareRevisi on SoftwareRevisi on Function code 43 /1 4, Object I d 0x02 Maj orMi norRevisi on String [2] 21 VendorU rl ProtocolSpecificProperty Function code 43 /1 4, Object I d 0x03 VendorU rl String [2] 21 ProductNam e ProtocolSpecificProperty Function code 43 /1 4, Object I d 0x04 ProdcutNam e String [2] 21 Model Nam e ProtocolSpecificProperty Function code 43 /1 4, Object I d 0x05 Model Nam e String [2] 21 UserApplicati onN am e ProtocolSpecificProperty Function code 43 /1 4, Object I d 0x06 UserApplicati onN am e String [2] 21 P ro t o c o l S p e c i fi c P r o p e r t i 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 – 67 – The M odbusDeviceI dentI nfo properties may 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 I EC TR 62453-52-1 50: 201 © I EC 201 T a b l e – P ro fi l e 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 – 68 – I EC TR 62453-52-1 50: 201 © I EC 201 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-06] [2] MODBU S Application Protocol Specification V1 a, M odbus I DA, J une 4, 2004 _ 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