BS EN 61131-5-2001 Programmable controllers Communications《可编程控制器 通信》.pdf

1、BRITISH STANDARD BS EN 61131-5:2001 IEC 61131-5: 2000 Programmable controllers Part 5: Communications The European Standard EN 61131-5:2001 has the status of a British Standard ICS 17.200.20; 25.040.40 NO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAWBS EN 61131-5:2001 This Brit

2、ish Standard, having been prepared under the direction of the Electrotechnical Sector Committee, was published under the authority of the Standards Committee and comes into effect on 15 June 2001 BSI 06-2001 ISBN 0 580 37338 X National foreword This British Standard is the official English language

3、version of EN 61131- 5:2001. It is identical with IEC 61131-5:2000. The UK participation in its preparation was entrusted by Technical Committee GEL/65, Measurement and control, to Subcommittee GEL/65/2, Elements of systems, which has the responsibility to: A list of organizations represented on thi

4、s subcommittee can be obtained on request to its secretary. From 1 January 1997, all IEC publications have the number 60000 added to the old number. For instance, IEC 27-1 has been renumbered as IEC 60027-1. For a period of time during the change over from one numbering system to the other, publicat

5、ions may contain identifiers from both systems. Cross-references Attention is drawn to the fact that CEN and CENELEC Standards normally include an annex which lists normative references to international publications with their corresponding European publications. The British Standards which implemen

6、t these international or European publications may be found in the BSI Standards Catalogue under the section entitled “International Standards Correspondence Index”, or by using the “Find” facility of the BSI Standards Electronic Catalogue. A British Standard does not purport to include all the nece

7、ssary provisions of a contract. Users of British Standards are responsible for their correct application. Compliance with a British Standard does not of itself confer immunity from legal obligations. aid enquirers to understand the text; present to the responsible international/European committee an

8、y enquiries on the interpretation, or proposals for change, and keep the UK interests informed; monitor related international and European developments and promulgate them in the UK. Summary of pages This document comprises a front cover, an inside front cover, the EN title page, pages 2 to 106, an

9、inside back cover and a back cover. The BSI copyright date displayed in this document indicates when the document was last issued. Amendments issued since publication Amd. No. Date CommentsEUROPEAN STANDARD EN 61131-5 NORME EUROPENNE EUROPISCHE NORM February 2001 CENELEC European Committee for Elect

10、rotechnical Standardization Comit Europen de Normalisation Electrotechnique Europisches Komitee fr Elektrotechnische Normung Central Secretariat: rue de Stassart 35, B - 1050 Brussels 2001 CENELEC - All rights of exploitation in any form and by any means reserved worldwide for CENELEC members. Ref.

11、No. EN 61131-5:2001 E ICS 25.040.40;25.240.50 English version Programmable controllers Part 5: Communications (IEC 61131-5:2000) Contrleurs programmables Partie 5: Communications (CEI 61131-5:2000) Speicherprogrammierbare Steuerungen Teil 5: Kommunikation (IEC 61131-5:2000) This European Standard wa

12、s approved by CENELEC on 2001-01-01. CENELEC members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references concerning suc

13、h national standards may be obtained on application to the Central Secretariat or to any CENELEC member. This European Standard exists in three official versions (English, French, German). A version in any other language made by translation under the responsibility of a CENELEC member into its own l

14、anguage and notified to the Central Secretariat has the same status as the official versions. CENELEC members are the national electrotechnical committees of Austria, Belgium, Czech Republic, Denmark, Finland, France, Germany, Greece, Iceland, Ireland, Italy, Luxembourg, Netherlands, Norway, Portuga

15、l, Spain, Sweden, Switzerland and United Kingdom.Foreword The text of document 65B/411/FDIS, future edition 1 of IEC 61131-5, prepared by SC 65B, Devices, of IEC TC 65, Industrial-process measurement and control, was submitted to the IEC-CENELEC parallel vote and was approved by CENELEC as EN 61131-

16、5 on 2001-01-01. The following dates were fixed: latest date by which the EN has to be implemented at national level by publication of an identical national standard or by endorsement (dop) 2001-10-01 latest date by which the national standards conflicting with the EN have to be withdrawn (dow) 2004

17、-01-01 This part is to be read in conjunction with the other parts of EN 61131. Annexes designated “normative“ are part of the body of the standard. In this standard, annexes A, B and ZA are normative. Annex ZA has been added by CENELEC. _ Endorsement notice The text of the International Standard IE

18、C 61131-5:2000 was approved by CENELEC as a European Standard without any modification. _ 2egaP EN611315:2000Page2 EN611315:2001 BSI 06-2001 CONTENTS Page 1 Scope 8 2 Normative references. 8 3 Definitions 9 4 Symbols and abbreviations11 5 Models11 5.1 PC network communication model11 5.2 PC function

19、al model.12 5.3 PC hardware model .14 5.4 Software model14 6 PC communication services 15 6.1 PC subsystems and their status .15 6.1.1 PC summary status16 6.1.2 I/O subsystem17 6.1.3 Processing unit 18 6.1.4 Power supply subsystem 19 6.1.5 Memory subsystem 19 6.1.6 Communication subsystem.20 6.1.7 I

20、mplementer specific subsystems .20 6.1.8 Presentation of status information 21 6.2 Application specific functions .23 6.2.1 Device verification24 6.2.2 Data acquisition .24 6.2.3 Control.25 6.2.4 Synchronization between user applications.25 6.2.5 Alarm reporting 26 6.2.6 Application program executio

21、n and I/O control26 6.2.7 Application program transfer 28 6.2.8 Connection management29 7 PC communication function blocks 29 7.1 Overview of the communication function blocks29 7.1.1 Device verification29 7.1.2 Data acquisition .30 7.1.3 Control.30 7.1.4 Alarm reporting 30 7.1.5 Connection manageme

22、nt30 7.2 Semantic of communication FB parameters30 7.3 Device verification35 7.4 Polled data acquisition .41 7.5 Programmed data acquisition.44 7.5.1 USEND/URCV function blocks44 7.5.2 BSEND / BRCV Function Blocks.49 7.6 Parametric control55 7.7 Interlocked control .58 7.8 Programmed alarm report 65

23、 3egaP EN611315:2000Page3 EN611315:2001 BSI 06-2001 7.9 Connection management .73 7.10 Example for the use of communication function blocks .77 7.10.1 Establishing a communication channel .77 7.10.2 Transferring data .78 7.10.3 Using a timer to supervise communication79 8 Compliance and implementer

24、specific features and parameters.80 8.1 Compliance80 8.2 Implementation specific features and parameters.81 Annex A (normative) Mapping to ISO/IEC 9506-582 A.1 General .82 A.2 Application specific functions .83 A.2.1 Device verification83 A.2.2 Data acquisition .83 A.2.3 Parametric control83 A.2.4 I

25、nterlocked control83 A.2.5 Synchronization between user applications.83 A.2.6 Alarm reporting 83 A.2.7 Application program execution and I/O control83 A.2.8 Application program transfer 84 A.2.9 Connection management84 A.3 PC object mapping.84 A.3.1 VMD 84 A.3.2 Named Variables84 A.3.3 Unnamed Varia

26、bles86 A.3.4 Program Invocations 86 A.3.5 Domains 86 A.4 Communication function block mapping to MMS objects and services.87 A.4.1 Using communication channels 87 A.4.2 Rules for data type compatibility.87 A.4.3 Device verification88 A.4.4 Polled data acquisition .89 A.4.5 Programmed data acquisitio

27、n .90 A.4.6 Parametric control93 A.4.7 Interlocked control95 A.4.8 Programmed alarm report 97 A.4.9 Connection management101 A.4.10 101 A.5 Implementation specific features and parameters.103 Annex B (normative) PC behavior using ISO/IEC 9506-2.104 B.1 PC communications mapping to MMS 104 B.2 Implem

28、entation specific features and parameters.105 Annex ZA (normative) Normative references to international publications with their corresponding European publications 106 Figure 1 Scope of this part of IEC 61131 8 Figure 2 PC communication model12 Figure 3 Programmable controller functional model.13 F

29、igure 4 Programmable controller hardware model .14 4egaP EN611315:2000Page4 EN611315:2001 BSI 06-2001 Figure 5 PC software model15 Figure 6 Programmable controller power supply19 Figure 7 Type description of status information .21 Figure 8 Interlocked control timeline .25 Figure 9 Function REMOTE_VA

30、R .32 Figure 10 Principle of status signalling33 Figure 11 Timing diagram of the ERROR and STATUS outputs.33 Figure 12 STATUS function block .36 Figure 13 USTATUS function block.37 Figure 14 Timing diagram of the STATUS function block.37 Figure 15 State diagram of STATUS function block.38 Figure 16

31、State diagram of USTATUS function block 39 Figure 17 READ function block .42 Figure 18 Timing diagram of READ function block.43 Figure 19 State diagram of READ function block.43 Figure 20 Programmed data acquisition data flow .44 Figure 21 USEND function block.45 Figure 22 URCV function block .46 Fi

32、gure 23 Timing diagram of USEND and URCV function blocks .46 Figure 24 State diagram of USEND function block 47 Figure 25 State diagram of URCV function block.48 Figure 26 BSEND function block .50 Figure 27 BRCV function block .51 Figure 28 Timing diagram of BSEND and BRCV function blocks52 Figure 2

33、9 State diagram of BSEND function block.53 Figure 30 State diagram of BRCV function block.54 Figure 31 WRITE function block .56 Figure 32 Timing diagram of WRITE function block.57 Figure 33 State diagram of WRITE function block .57 Figure 34 SEND function block .59 Figure 35 RCV function block .60 F

34、igure 36 Timing diagram of SEND and RCV function blocks 61 Figure 37 State diagram of SEND function block.62 Figure 38 State diagram of RCV function block .64 Figure 39 NOTIFY function block 66 Figure 40 ALARM function block .67 Figure 41 Timing diagram of ALARM function block 68 Figure 42 State dia

35、gram of NOTIFY function block69 Figure 43 State diagram of ALARM function block.71 Figure 44 CONNECT function block73 Figure 45 Timing diagram of CONNECT function block .74 Figure 46 State diagram of CONNECT function block75 Figure 47 Example in function block diagram language .80 5egaP EN611315:200

36、0Page5 EN611315:2001 BSI 06-2001 Table 1 Status presenting entities.16 Table 2 PC summary status17 Table 3 Status of I/O subsystem .18 Table 4 Status of processing unit18 Table 5 Status of power supply.19 Table 6 Status of memory.20 Table 7 Status of communication subsystem.20 Table 8 Status of impl

37、ementer specific subsystem 21 Table 9 Presentation of status information 21 Table 10 Device verification features 24 Table 11 Data acquisition features24 Table 12 Control features .25 Table 13 Alarm reporting features.26 Table 14 Startable and stoppable units .26 Table 15 Meaning of I/O State 27 Tab

38、le 16 I/O state.27 Table 17 Execution and I/O control features27 Table 18 Loadable units28 Table 19 Application program transfer features.28 Table 20 Connection management features 29 Table 21 Overview of the communication function blocks 29 Table 22 Semantic of communication FB parameters31 Table 2

39、3 Values of the SCOPE parameter 32 Table 24 Value and interpretation of the STATUS output.34 Table 25 Transitions of the STATUS state diagram .38 Table 26 Action table for STATUS state diagram.39 Table 27 Transitions of USTATUS state diagrams.40 Table 28 Action table of USTATUS state diagram .40 Tab

40、le 29 Transitions of the READ state diagram .43 Table 30 Action table for READ state diagram.44 Table 31 Transitions of the USEND state diagram.47 Table 32 Action table for USEND state diagram 48 Table 33 Transitions of URCV state diagrams.49 Table 34 Action table of URCV state diagram49 Table 35 Tr

41、ansitions of the BSEND state diagram.53 Table 36 Action table for BSEND state diagram 54 Table 37 Transitions of BRCV state diagrams .55 Table 38 Action table of BRCV state diagram55 Table 39 Transitions of the WRITE state diagram .58 Table 40 Action table for WRITE state diagram.58 Table 41 Transit

42、ions of the SEND state diagram .62 Table 42 Action table for SEND state diagram.63 Table 43 Transitions of RCV state diagrams .64 6egaP EN611315:2000Page6 EN611315:2001 BSI 06-2001 Table 44 Action table of RCV state diagram 65 Table 45 Transitions of the NOTIFY state diagram69 Table 46 Action table

43、for NOTIFY state diagram .70 Table 47 Transitions of the ALARM state diagram.72 Table 48 Action table for ALARM state diagram 72 Table 49 Transitions of the CONNECT state diagram76 Table 50 Action table for CONNECT state diagram .77 Table 51 Table titles and relevant tables for compliance80 Table 52

44、 Implementation specific features and parameters .81 Table A.1 Type description mapping .85 Table A.2 Mapping of the SCOPE and SC_ID parameter.85 Table A.3 Size prefix of direct representation86 Table A.4 Transition mapping of the STATUS state diagram .88 Table A.5 Action mapping for STATUS state di

45、agram88 Table A.6 Transition mapping of USTATUS state diagram.88 Table A.7 Action mapping of USTATUS state diagram 88 Table A.8 Transition mapping of the READ state diagram .89 Table A.9 Action mapping for READ state diagram89 Table A.10 Transition mapping of the USEND state diagram .90 Table A.11 A

46、ction mapping for USEND state diagram .90 Table A.12 Transition mapping of URCV state diagram .91 Table A.13 Action mapping for URCV state diagram91 Table A.14 Transition mapping of the BSEND state diagram .92 Table A.15 Action mapping for BSEND state diagram .92 Table A.16 Transition mapping of BRC

47、V state diagram .93 Table A.17 Action mapping for BRCV state diagram93 Table A.18 Transition mapping of the WRITE state diagram95 Table A.19 Action mapping for WRITE state diagram95 Table A.20 Transition mapping of the SEND state diagram .95 Table A.21 Action mapping for SEND state diagram96 Table A

48、.22 Transition mapping of RCV state diagram .96 Table A.23 Action mapping of RCV state diagram .97 Table A.24 Transition mapping of the NOTIFY state diagram 99 Table A.25 Action mapping for NOTIFY state diagram.99 Table A.26 Transition mapping of the ALARM state diagram .100 Table A.27 Action mapping for ALARM state diagram .101 Table A.28 Transitions of the CONNECT state diagram 102 Table A.29 Action mapping for CONNECT state diagram 102 Table A.30 Implementation specific features and parameters103 Table B.1 CreateProgramInvocation service defaults 104 Tabl