ISO 15745-4 AMD 2-2007 Industrial automation systems and integration - Open systems application integration framework - Part 4 Reference description for Etherne.pdf

1、 Reference number ISO 15745-4:2003/Amd.2:2007(E) ISO 2007INTERNATIONAL STANDARD ISO 15745-4 First edition 2003-11-15 AMENDMENT 2 2007-02-01 Industrial automation systems and integration Open systems application integration framework Part 4: Reference description for Ethernet-based control systems AM

2、ENDMENT 2: Profiles for Modbus TCP, EtherCAT and ETHERNET Powerlink Systmes dautomatisation industrielle et intgration Cadres dintgration dapplication pour les systmes ouverts Partie 4: Description de rfrence pour les systmes de contrle fonds sur Ethernet AMENDEMENT 2: Profils pour Modbus TCP, Ether

3、CAT et ETHERNET Powerlink ISO 15745-4:2003/Amd.2:2007(E) PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on the co

4、mputer performing the editing. In downloading this file, parties accept therein the responsibility of not infringing Adobes licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the software products used to cr

5、eate this PDF file can be found in the General Info relative to the file; the PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event that a problem relating to it is found, please inform t

6、he Central Secretariat at the address given below. ISO 2007 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 eithe

7、r ISO at the address below or ISOs member body in the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org Published in Switzerland ii ISO 2007 All rights reservediiiForeword ISO (the Int

8、ernational Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing International Standards is normally carried out through ISO technical committees. Each member body interested in a subject for which a technical committee ha

9、s been established has the right to be represented on that committee. International organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of electrotechnical

10、standardization. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. Draft International Standards adopted by the technical committees are circulated to the member bodies for voting. Publication as an International Standard requires approval by a

11、t least 75 % of the member bodies casting a vote. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Amendment 2 to ISO 15745-4:2003 was prepared by Tec

12、hnical Committee ISO/TC 184, Industrial automation systems and integration, Subcommittee SC 5, Architecture, communications and integration frameworks. Amendment 2 to ISO 15745-4:2003 specifies profiles for Modbus TCP 1) , EtherCAT 2) , and ETHERNET Powerlink 3) , and, as such, adds to the number of

13、 technology-specific elements and rules in ISO 15745-4 for describing both communication network profiles and communication-related aspects of device profiles, thus further extending the Application Integration Framework in ISO 15745-1. 1) Modbus and Modbus TCP are the registered trademarks of Schne

14、ider Automation Inc. This information is given for the convenience of users of ISO15745 and does not constitute an endorsement by ISO of the trademark holder or any of its products. Compliance to ISO15745 does not require use of the trade name Modbus TCP or Modbus. Use of the trademark Modbus TCP or

15、 Modbus requires permission of the trade name holder. 2) EtherCAT is the registered trademark of Beckhoff, Verl. This information is given for the convenience of users of ISO15745 and does not constitute an endorsement by ISO/IEC of the trademark holder or any of its products. Compliance to ISO15745

16、 does not require use of the trade name EtherCAT. Use of the trademark EtherCAT requires permission of the trade name holder. 3) ETHERNET Powerlink is the registered trademark of ETHERNET Powerlink Standardization Group. This information is given for the convenience of users of ISO15745 and does not

17、 constitute an endorsement by ISO/IEC of the trademark holder or any of its products. Compliance to ISO15745 does not require use of the trade name ETHERNET Powerlink. Use of the trademark ETHERNET Powerlink requires permission of the trade name holder. ISO 15745-4:2003/Amd.2:2007(E) ISO 2007 All ri

18、ghts reserved 1Page 1, Clause 2 Add the following normative references: “ISO 1000, SI units and recommendations for the use of their multiples and of certain other units ISO 3166-1, Codes for the representation of names of countries and their subdivisions Part 1: Country IEC/PAS 62030, Digital data

19、communications for measurement and control - Fieldbus for use in industrial control systems - Section 1: MODBUS Application Protocol Specification V1.1a - Section 2: Real-Time Publish-Subscribe (RTPS) Wire Protocol Specification Version 1.0 IEC/PAS 62407, Real-time Ethernet control automation techno

20、logy (EtherCATTM) IEC/PAS 62408, Real-time Ethernet Powerlink (EPL) RFC 1157 SNMP, Simple Network Management Protocol (SNMP) Management Frameworks“ Page 2, Clause 4 Add the following abbreviated terms: “DDXML Device Description eXtensible Markup Language EPL ETHERNET Powerlink FMMU Fieldbus Memory M

21、anagement Unit MIB Management Information Base SNMP Simple Network Management Protocol (RFC 1157)“ Page 4, Table 1 Add a row with the entries “DDXML“ under the “ProfileTechnology name“ column and “Modbus TCP“ under the “Technology“ column. Industrial automation systems and integration Open systems a

22、pplication integration framework Part 4: Reference description for Ethernet-based control systems AMENDMENT 2: Profiles for Modbus TCP, EtherCAT and ETHERNET Powerlink codes ISO 15745-4:2003/Amd.2:2007(E) ISO 2007 All rights reserved 2 Add a row with the entries “EtherCAT“ under the “ProfileTechnolo

23、gy name“ column and “EtherCAT“ under the “Technology“ column. Add a row with the entries “EPL“ under the “ProfileTechnology name“ column and “ETHERNET Powerlink“ under the “Technology“ column. Page 4, Subclause 5.3 Add the following items to the list in the first paragraph: “ Modbus TCP (see 6.5) Et

24、herCAT (see 6.6) ETHERNET Powerlink (see 6.7)“. Page 18 Insert the following new subclauses 6.5, 6.6 and 6.7 after subclause 6.4 inserted from Amendment 1 to ISO 15745-4:2003, and before Annex A. 6.5 Modbus TCP 6.5.1 Device profile 6.5.1.1 General Figure 20 shows the class structure of a Modbus TCP

25、device profile. DeviceProfile DeviceIdentity 01 DeviceManager 01 DeviceFunction 1* ApplicationProcess 0*Figure 20 Modbus TCP device profile class diagram NOTE The Modbus TCP device profile class diagram shown in Figure 20 defines the main classes. These classes are further decomposed and detailed in

26、 Annex E. The XML schemas representing the Modbus TCP device profile template are defined in E.4.6. The template is based on two parts: the DDXML profile header defined in E.3, and the DDXML device profile defined in E.4. 6.5.1.2 Device identity The DeviceIdentity class contains attributes that are

27、independent of the network, of the process and uniquely identify the device. ISO 15745-4:2003/Amd.2:2007(E) ISO 2007 All rights reserved 3Figure 21 shows the structure of the Modbus TCP DeviceIdentity class. DeviceIdentity vendorName 1 vendorID 01 vendorText 01 deviceFamily 01 productFamily 01 produ

28、ctName 1 productID 01 productText 01 orderNumber 0* version 0* buildDate 01 specificationRevision 01 instanceName 01Figure 21 Modbus TCP DeviceIdentity class diagram Further details are given in E.4.2. 6.5.1.3 Device manager The DeviceManager class contains attributes and supports services that enab

29、le the monitoring of the device. Communication specific configuration data and mapping information is defined in the communication network specific part structured according to the schema specified in E.5. Figure 22 shows the structure of the Modbus TCP DeviceManager class. DeviceManager indicatorLi

30、st LEDList 01 01Figure 22 Modbus TCP DeviceManager class diagram ISO 15745-4:2003/Amd.2:2007(E) ISO 2007 All rights reserved 4 Further details are given in E.4.3. 6.5.1.4 Device function The DeviceFunction class describes the intrinsic function of a device in terms of its technology. It contains net

31、work independent descriptions/definitions of the technological device functionality. Figure 23 shows the structure of the Modbus TCP DeviceFunction class. DeviceFunction capabilities picturesList dictionaryList characteristicsList characteristic characteristicName characteristicContent 01 01 01 1* 1

32、* 1 picture 01 dictionary standardComplianceList compliantWith 01 1* 1* 01 category 01 file 1* g_labels 1 1 1 1 1Figure 23 Modbus TCP DeviceFunction class diagram Further details are given in E.4.4. 6.5.1.5 Application process The ApplicationProcess class represents the set of services and parameter

33、s, which constitute the behaviour, and the interfaces of the device in terms of the application, independent of the device technology and the underlying communication networks and communication protocols. Figure 24 shows the structure of the Modbus TCP ApplicationProcess class. ISO 15745-4:2003/Amd.

34、2:2007(E) ISO 2007 All rights reserved 5ApplicationProcess dataTypeList 01 functionTypeList 1 functionInstanceList 1 parameterList 1 parameterGroupList 01Figure 24 Modbus TCP ApplicationProcess class diagram Further details are given in E.4.5. 6.5.2 Communication network profile 6.5.2.1 General Figu

35、re 25 shows the class structure of the Modbus TCP communication network profile. These classes are further decomposed and detailed in Annex E. NetworkManagement 01 1 1 TransportLayers ApplicationLayers CommNetworkProfileFigure 25 Modbus TCP communication network profile class diagram The XML schemas

36、 representing the Modbus TCP communication network profile template are defined in E.5.5. Like for the device profile, the template is also based on two parts: the DDXML profile header defined in E.3, and the DDXML communication network profile defined in E.5. 6.5.2.2 Application layers The Modbus T

37、CP ApplicationLayers class represents the combined profiles for the upper 3 OSI layers of the Modbus TCP communication network integration model. Further details are given in E.5.2. 6.5.2.3 Transport layers The Modbus TCP TransportLayers class represents the combined profiles for the lower 4 OSI lay

38、ers of the Modbus TCP communication network integration model. Further details are given in E.5.3. ISO 15745-4:2003/Amd.2:2007(E) ISO 2007 All rights reserved 6 6.5.2.4 Network management The Modbus TCP NetworkManagement class represents the network configuration and performance adjustment capabilit

39、ies of the Modbus TCP communication network integration model. Further details are given in E.5.4. 6.6 EtherCAT 6.6.1 Device profile 6.6.1.1 General Figure 26 shows the class structure of an EtherCAT device profile. DeviceProfile DeviceIdentity 01 DeviceManager 01 DeviceFunction 1* ApplicationProces

40、s 0*Figure 26 EtherCAT device profile class diagram NOTE The EtherCAT device profile class diagram shown in Figure 26 defines the main classes. These classes are further decomposed and detailed in Annex F. The XML schema representing the EtherCAT device profile template is defined in F.4.6. The temp

41、late is based on two parts: the EtherCAT profile header defined in F.3, and the EtherCAT device profile defined in F.4. 6.6.1.2 Device identity The DeviceIdentity class contains attributes that are independent of the network, of the process and uniquely identify the device. Figure 27 shows the struc

42、ture of the EtherCAT DeviceIdentity class. ISO 15745-4:2003/Amd.2:2007(E) ISO 2007 All rights reserved 7DeviceIdentity vendorName 1 vendorID 01 vendorText 01 deviceFamily 01 productFamily 01 productName 1 productID 01 productText 01 orderNumber 0* version 0* buildDate 01 specificationRevision 01 ins

43、tanceName 01Figure 27 EtherCAT DeviceIdentity class diagram Further details are given in F.4.2. 6.6.1.3 Device manager The DeviceManager class contains attributes and supports services that enable the monitoring of the device. Communication specific configuration data and mapping information is defi

44、ned in the communication network specific part structured according to the schema specified in F.5. Figure 28 shows the structure of the EtherCAT DeviceManager class. DeviceManager indicatorList 01 LEDList 01Figure 28 EtherCAT DeviceManager class diagram Further details are given in F.4.3. ISO 15745

45、-4:2003/Amd.2:2007(E) ISO 2007 All rights reserved 8 6.6.1.4 Device function The DeviceFunction class describes the intrinsic function of a device in terms of its technology. It contains network independent descriptions/definitions of the technological device functionality. Figure 29 shows the struc

46、ture of the EtherCAT DeviceFunction class. DeviceFunction dictionaryList 01 picturesList 01 capabilities 1 dictionary 1* file 1* characteristicsList 1* standardComplianceList 01 category 01 characteristic 1* characteristicName 1 characteristicContent 1* compliantWith 1* picture 1* g_labels 1Figure 2

47、9 EtherCAT DeviceFunction class diagram Further details are given in F.4.4. 6.6.1.5 Application process The ApplicationProcess class represents the set of services and parameters, which constitute the behaviour, and the interfaces of the device in terms of the application, independent of the device

48、technology and the underlying communication networks and communication protocols. Figure 30 shows the structure of the EtherCAT ApplicationProcess class. ISO 15745-4:2003/Amd.2:2007(E) ISO 2007 All rights reserved 9ApplicationProcess dataTypeList 01 functionTypeList 1 functionInstanceList 1 paramete

49、rList 1 parameterGroupList 01Figure 30 EtherCAT ApplicationProcess class diagram Further details are given in F.4.5. 6.6.2 Communication network profile 6.6.2.1 General Figure 31 shows the class structure of the EtherCAT communication network profile. These classes are further decomposed and detailed in