1. Trang chủ
  2. » Luận Văn - Báo Cáo

Iec 61158 4 2003

1.1K 0 0

Đang tải... (xem toàn văn)

Tài liệu hạn chế xem trước, để xem đầy đủ mời bạn chọn Tải xuống

THÔNG TIN TÀI LIỆU

INTERNATIONAL STANDARD IEC 61158-4 Third edition 2003-05 LICENSED TO MECON Limited - RANCHI/BANGALORE FOR INTERNAL USE AT THIS LOCATION ONLY, SUPPLIED BY BOOK SUPPLY BUREAU Digital data communications for measurement and control – Fieldbus for use in industrial control systems – Part 4: Data link protocol specification Reference number IEC 61158-4:2003(E) Publication numbering As from January 1997 all IEC publications are issued with a designation in the 60000 series For example, IEC 34-1 is now referred to as IEC 60034-1 Consolidated editions The IEC is now publishing consolidated versions of its publications For example, edition numbers 1.0, 1.1 and 1.2 refer, respectively, to the base publication, the base publication incorporating amendment and the base publication incorporating amendments and Further information on IEC publications • • IEC Web Site (www.iec.ch) Catalogue of IEC publications The on-line catalogue on the IEC web site (http://www.iec.ch/searchpub/cur_fut.htm) enables you to search by a variety of criteria including text searches, technical committees and date of publication On-line information is also available on recently issued publications, withdrawn and replaced publications, as well as corrigenda • IEC Just Published This summary of recently issued publications (http://www.iec.ch/online_news/ justpub/jp_entry.htm) is also available by email Please contact the Customer Service Centre (see below) for further information • Customer Service Centre If you have any questions regarding this publication or need further assistance, please contact the Customer Service Centre: Email: custserv@iec.ch Tel: +41 22 919 02 11 Fax: +41 22 919 03 00 LICENSED TO MECON Limited - RANCHI/BANGALORE FOR INTERNAL USE AT THIS LOCATION ONLY, SUPPLIED BY BOOK SUPPLY BUREAU The technical content of IEC publications is kept under constant review by the IEC, thus ensuring that the content reflects current technology Information relating to this publication, including its validity, is available in the IEC Catalogue of publications (see below) in addition to new editions, amendments and corrigenda Information on the subjects under consideration and work in progress undertaken by the technical committee which has prepared this publication, as well as the list of publications issued, is also available from the following: INTERNATIONAL STANDARD IEC 61158-4 Third edition 2003-05 LICENSED TO MECON Limited - RANCHI/BANGALORE FOR INTERNAL USE AT THIS LOCATION ONLY, SUPPLIED BY BOOK SUPPLY BUREAU Digital data communications for measurement and control – Fieldbus for use in industrial control systems – Part 4: Data link protocol specification  IEC 2003  Copyright - all rights reserved 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 the publisher International Electrotechnical Commission, 3, rue de Varembé, PO Box 131, CH-1211 Geneva 20, Switzerland Telephone: +41 22 919 02 11 Telefax: +41 22 919 03 00 E-mail: inmail@iec.ch Web: www.iec.ch Com mission Electrotechnique Internationale International Electrotechnical Com m ission Международная Электротехническая Комиссия PRICE CODE XW For price, see current catalogue –2– 61158-4  IEC:2003(E) CONTENTS FOREWORD 24 Introduction 27 0.1 General 27 0.2 Nomenclature for references within this standard 27 Scope and object 29 1.1 Overview 29 1.2 Specifications 30 1.3 Procedures 32 1.4 Applicability 32 1.5 Conformance 32 Normative references 32 Terms and definitions 33 3.1 Reference model terms and definitions 33 3.2 Service convention terms and definitions 35 3.3 Common terms and definitions 36 3.4 Type 1: Additional terms and definitions 39 3.5 Type 2: Additional terms and definitions 45 3.6 Type 3: Additional terms and definitions 52 3.7 Type 4: Additional terms and definitions 54 3.8 Type 5: Additional terms and definitions 55 3.9 Type 6: Additional terms and definitions 55 3.10 Type 7: Additional terms and definitions 65 3.11 Type 8: Additional terms and definitions 67 Symbols and abbreviations 69 4.1 Common symbols and abbreviations 69 4.2 Type 1: Additional symbols and abbreviations 69 4.3 Type 2: Additional symbols and abbreviations 73 4.4 Type 3: Additional symbols and abbreviations 74 4.5 Type 4: Additional symbols and abbreviations 78 4.6 Type 5: Additional symbols and abbreviations 79 4.7 Type 6: Additional symbols and abbreviations 79 4.8 Type 7: Additional symbols and abbreviations 80 4.9 Type 8: Additional symbols and abbreviations 81 DL-protocol elements common to multiple DL-protocol Types 84 5.1 Frame check sequence 84 Type 6.1 6.2 6.3 6.4 6.5 6.6 6.7 1: Overview of the DL-protocol 88 Three-level model of the DLL 88 Service provided by the DLL 91 Structure and definition of DL-addresses 97 Service assumed from the PhL 109 Functions of the DLL 112 Functional classes 114 Local parameters, variables, counters, timers and queues 116 LICENSED TO MECON Limited - RANCHI/BANGALORE FOR INTERNAL USE AT THIS LOCATION ONLY, SUPPLIED BY BOOK SUPPLY BUREAU 61158-4  IEC:2003(E) –3– Type 1: General structure and encoding of PhIDUs and DLPDUs, and related elements of procedure 130 7.1 PhIDU structure and encoding 130 7.2 Common DLPDU structure, encoding and elements of procedure 130 Type 8.1 8.2 8.3 8.4 8.5 8.6 8.7 8.8 8.9 8.10 8.11 8.12 8.13 8.14 8.15 8.16 8.17 8.18 8.19 8.20 8.21 8.22 8.23 8.24 1: DLPDU-specific structure, encoding and elements of procedure 139 Establish Connection (EC) DLPDU 141 Disconnect Connection (DC) DLPDU 143 Reset Connection (RC) DLPDU 146 Compel Acknowledgement (CA) DLPDU 147 Compel Data (CD) DLPDU 154 Exchange Data (ED) DLPDU 162 Data (DT) DLPDU 170 Status Response (SR) DLPDU 178 Compel Time (CT) DLPDU 181 Time Distribution (TD) DLPDU 182 Round-Trip-Delay Query (RQ) DLPDU 184 Round-Trip-Delay Reply (RR) DLPDU 186 Probe Node DL-address (PN) DLPDU 188 Probe Response (PR) DLPDU 191 Pass Token (PT) DLPDU 192 Execute Sequence (ES) DLPDU 201 Return Token (RT) DLPDU 208 Request Interval (RI) DLPDU 209 Claim LAS (CL) DLPDU 210 Transfer LAS (TL) DLPDU 212 Wakeup (WK) DLPDU 216 Idle (IDLE) DLPDU 217 Spare DLPDUs 218 Reserved (not to be used) DLPDUs 220 Type 9.1 9.2 9.3 9.4 9.5 9.6 9.7 9.8 9.9 9.10 1: DLPDU-parameter structure and encoding 221 Structure and encoding of EC-P ARAMETERS 221 Structure and encoding of DC-P ARAMETERS 226 Structure and encoding of RC-P ARAMETERS 226 Structure and encoding of SD-Parameters 228 Structure and encoding of SR-parameters 235 Structure and encoding of TD-parameters 237 Structure and encoding of RQ-parameters 239 Structure and encoding of RR-parameters 240 Structure and encoding of PN-parameters 240 Structure and encoding of DD-parameters 242 10 Type 10.1 10.2 10.3 10.4 1: DL-service elements of procedure 243 Operation of the DL(SAP)-address, buffer and queue management services 243 Operation of the connection-mode services 247 Operation of the connectionless-mode services 288 Operation of the scheduling guidance services 300 LICENSED TO MECON Limited - RANCHI/BANGALORE FOR INTERNAL USE AT THIS LOCATION ONLY, SUPPLIED BY BOOK SUPPLY BUREAU –4– 61158-4  IEC:2003(E) 1: DL-support subprotocol 310 Scope 310 Overview of LAS operation 310 DL-support subprotocol definition 311 Elements of Procedures for receiving SPDUs 345 12 Type 12.1 12.2 12.3 12.4 12.5 12.6 1: Other DLE elements of procedure 347 DLE initialization 347 LAS behavior and operation 351 DL-support operation 358 DL-bridge elements of procedure and bridge sub-protocol 363 DL-management-information 393 Implementation profiles 398 13 Type 1: PICS proforma 404 13.1 Introduction 404 13.2 Scope 404 13.3 Normative references 404 13.4 Definitions 404 13.5 Abbreviations 404 13.6 Conformance 405 13.7 Instructions 405 13.8 Identification 406 13.9 Implementation profile 407 13.10 Major low-level capabilities 411 13.11 Major high-level capabilities 425 14 Type 14.1 14.2 14.3 14.4 14.5 2: Overview of the DL-protocol 434 General 434 Services provided by the DL 436 Structure and definition of DL-addresses 437 Services assumed from the PhL 439 Functional classes 441 15 Type 2: General structure and encoding of PhIDUs and DLPDUs and related elements of procedure 442 15.1 Overview 442 15.2 Media access procedure 442 15.3 DLPDU structure and encoding 445 15.4 Lpacket components 447 15.5 DLPDU procedures 449 15.6 Summary of DLL support services and objects 450 16 Type 16.1 16.2 16.3 16.4 16.5 16.6 16.7 16.8 2: Specific DLPDU structure, encoding and procedures 453 Modeling language 453 DLS user services 455 Generic Tag Lpacket 461 Moderator Lpacket 461 Time distribution Lpacket 463 UCMM Lpacket 465 Keeper UCMM Lpacket 465 TUI Lpacket 466 LICENSED TO MECON Limited - RANCHI/BANGALORE FOR INTERNAL USE AT THIS LOCATION ONLY, SUPPLIED BY BOOK SUPPLY BUREAU 11 Type 11.1 11.2 11.3 11.4 61158-4  IEC:2003(E) 16.9 16.10 16.11 16.12 16.13 Link parameters Lpacket and tMinus Lpacket 467 I’m alive Lpacket 469 Ping Lpackets 470 WAMI Lpacket 472 Debug Lpacket 472 2: Objects for station management 474 General 474 ControlNet object 475 Keeper object 485 Scheduling object 508 TCP/IP interface object 517 Ethernet link object 524 18 Type 2: Other DLE elements of procedure 529 18.1 Network Attachment Monitor (NAM) 529 18.2 Calculating link parameters 536 19 Type 19.1 19.2 19.3 19.4 19.5 19.6 19.7 19.8 19.9 2: Detailed specification of DL components 544 General 544 Access Control Machine (ACM) 544 TxLLC 561 RxLLC 565 Transmit Machine (TxM) 568 Receive Machine (RxM) 571 Serializer 577 Deserializer 578 DLL management 579 20 Type 20.1 20.2 20.3 20.4 20.5 20.6 3: Overview of the DL-protocol 582 General 582 Overview of the medium access control and transmission protocol 582 Transmission modes and DL-entity 583 Service assumed from the PhL 588 Operational elements 590 Cycle and system reaction times 605 21 Type 3: General structure and encoding of DLPDUs, and related elements of procedure 609 21.1 DLPDU granularity 609 21.2 Length octet (LE, LEr) 610 21.3 Address octet 610 21.4 Control octet (FC) 613 21.5 DLPDU content error detection 616 21.6 DATA_UNIT 617 21.7 Error control procedures 618 22 Type 22.1 22.2 22.3 22.4 3: DLPDU-specific structure, encoding and elements of procedure 619 DLPDUs of fixed length with no data field 619 DLPDUs of fixed length with data field 621 DLPDUs with variable data field length 622 Token DLPDU 624 LICENSED TO MECON Limited - RANCHI/BANGALORE FOR INTERNAL USE AT THIS LOCATION ONLY, SUPPLIED BY BOOK SUPPLY BUREAU 17 Type 17.1 17.2 17.3 17.4 17.5 17.6 –5– –6– 61158-4  IEC:2003(E) 22.5 22.6 22.7 22.8 22.9 ASP DLPDU 625 SYNCH DLPDU 625 Time Event (TE) DLPDU 625 Clock Value (CV) DLPDU 625 Transmission procedures 626 23 Type 23.1 23.2 23.3 3: Other DLE elements of procedure 629 DL-entity initialization 629 States of the media access control of the DL-entity 629 Clock synchronization protocol 635 25 Type 5: 671 26 Type 26.1 26.2 26.3 26.4 26.5 26.6 26.7 26.8 26.9 6: Connection-oriented DL-protocol and related matters 673 Connection mode data transfer using TDMA principles 673 Bus access and data transmission 673 Overview of bus synchronization 675 Connection mode data transfer 678 DLM-connectionless service 706 Other real-time services 720 Bridge architecture and operation 724 Bus configuration 726 Conformance 736 27 Type 6: MAC elements of procedure 738 27.1 Procedures related to bus startup and bus operation 738 27.2 Medium access control (MAC) 743 28 Type 28.1 28.2 28.3 28.4 28.5 7: Overview of the DL-protocol 746 Overall description of medium allocation 746 Types of entities 748 Addressing 751 Flow control 757 Graphical representation 759 29 Type 7: General structure and encoding of PhIDUs and DLPDUs and related elements of procedure 760 29.1 DLPDU formats and components 760 29.2 Description of each DLPDU component 760 29.3 PhIDU structure and encoding 762 29.4 Common DLPDU structure, encoding and elements of procedure 763 29.5 Valid DLPDU types 763 29.6 DLL timers 765 LICENSED TO MECON Limited - RANCHI/BANGALORE FOR INTERNAL USE AT THIS LOCATION ONLY, SUPPLIED BY BOOK SUPPLY BUREAU 24 Type 4: Data Link Protocol Definition 640 24.1 Overview of the DL-protocol 640 24.2 General structure and encoding of PhIDUs and DLPDUs, and related elements of procedure 651 24.3 DLPDU-specific structure, encoding and elements of procedure 657 24.4 DL-service elements of procedure 661 24.5 Route mechanism 664 24.6 Link-access system 668 24.7 Local variables, counters and queues 668 61158-4  IEC:2003(E) –7– 30 Type 7: DLPDU-specific structure, encoding and element of procedure 771 30.1 General 771 30.2 Buffer read 771 30.3 Buffer write 771 30.4 Buffer transfer 771 30.5 Specified explicit request 772 30.6 Free explicit request 778 30.7 Messaging 781 30.8 Acknowledged messaging 786 30.9 Numbering of acknowledged messages 790 30.10 Behavior with mismatched parameters 792 7: DL-service elements of procedure, interfaces and conformance 795 General 795 Producer/consumer entity 795 Protocol elements by service 798 Bus arbitrator operation 806 Bridges 813 Interfaces 820 Conformance 822 32 Type 32.1 32.2 32.3 32.4 32.5 32.6 32.7 8: DL-protocol 825 Overview 825 DL-service Interface (DLI) 825 Peripherals data link (PDL) 829 Basic Link Layer (BLL) 864 Medium Access Control (MAC) 880 Peripherals network management for layer (PNM2) 912 Parameters and monitoring times of the DLL 920 Annex A (informative) – Types 1, 2, (synchronous), (first FCS), 6, and 8: Exemplary FCS implementations 926 Annex B B.1 B.2 B.3 B.4 (informative) – Type 1: Formal protocol finite state machines 928 Basic reception and transmission FSMs 928 FSMs for DLCs 940 FSMs for scheduling 946 FSMs for bridges 946 Annex C C.1 C.2 C.3 C.4 C.5 C.6 (informative) – Type 1: DLPDU and DL-addressing short-form summaries 947 Fields used in short-form summaries 947 DLPDU short-form summary grouped by function 949 DLPDU short-form summary in alphabetic order of DLPDU names 951 DLPDU short-form summary in alphabetic order of DLPDU acronyms 952 DLPDU FC code-point assignment matrix – overview and detail 953 SD-parameters (status and data-description parameters) of CA, CD, ED and DT DLPDUs 956 EC parameters of EC DLPDUs 959 Parameters of DC and RC DLPDUs 961 Parameters of TD, RQ and RR DLPDUs 963 Parameters of PN, PT, ES and RI DLPDUs 965 Addressing summary extracted from figures and tables of 6.3 967 C.7 C.8 C.9 C.10 C.11 LICENSED TO MECON Limited - RANCHI/BANGALORE FOR INTERNAL USE AT THIS LOCATION ONLY, SUPPLIED BY BOOK SUPPLY BUREAU 31 Type 31.1 31.2 31.3 31.4 31.5 31.6 31.7 –8– 61158-4  IEC:2003(E) (informative) – Type 2: Indicators and Switches 971 Purpose 971 General indicator requirements 971 Common indicator requirements 971 Module status indicator 972 Network status indicators 972 Switches 975 Annex E E.1 E.2 E.3 E.4 E.5 E.6 (normative) – Type 3: DL-Protocol state machines 977 Overall structure 977 Variation of state machines in different devices 979 DL Data Resource 979 FLC / DLM 984 MAC 1009 SRU 1038 Annex F (informative) – Type 3: Exemplary token procedure and message transfer periods 1056 F.1 Procedure of token passing 1056 F.2 Examples for token passing procedure 1057 F.3 Examples for message transfer periods – asynchronous transmission 1061 F.4 Examples for message transfer periods – synchronous transmission 1062 Annex G G.1 G.2 G.3 G.4 G.5 G.6 (informative) – Type 7: Object Modeling 1063 Modeling of the IDENTIFIER object 1063 Description of the IDENTIFIER object attributes 1064 Modeling of the QUEUE object 1068 Description of the QUEUE object attributes 1068 Modeling of the BUFFER object 1069 Description of the BUFFER object attributes 1069 Annex H H.1 H.2 H.3 H.4 H.5 (informative) – Type 7: Topology of multi-segment DL-subnetwork 1070 Introduction 1070 Global specification 1070 Local specification 1071 Properties 1071 Methods 1072 Annex I (informative) – Type 7: Management of transmission errors 1075 I.1 Transmission of RP_DAT_XX 1075 I.2 Transmission of a free RP_RQ(1/2) 1075 I.3 Transmission of the specified RP_RQ1 1076 I.4 Transmission of RP_MSG_NOACK 1077 I.5 Transmission of RP_MSG_ACK 1079 Annex J (informative) – Type 8: Implementation possibilities of definite PNM2 functions 1082 J.1 Acquiring the current configuration 1082 J.2 Comparing the acquired and stored configurations prior to a DL-subnetwork error 1085 BIBLIOGRAPHY 1092 INDEX 1094 LICENSED TO MECON Limited - RANCHI/BANGALORE FOR INTERNAL USE AT THIS LOCATION ONLY, SUPPLIED BY BOOK SUPPLY BUREAU Annex D D.1 D.2 D.3 D.4 D.5 D.6 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 61158-4  IEC:2003(E) – 1086 – — At a certain DL-subnetwork position there is a slave with another device code A comparison is carried out by the Check_Configuration function J.2.2 Check_Configuration function The Check_Configuration function is described with the Check_Configuration.request and Check_Configuration.confirm primitives The Check_Configuration.request primitive has no parameters Besides the result (+ or -), the confirmation contains in the event of an error an error_code and an add_code with the error position in the ring (see Table J.4) Table J.4 – Check_Configuration Argument Request Confirm M Result (+) S Result (-) error_code slave_position S M M result (+): No error has been detected, that is, the two configurations are identical result (-): An error has been detected, that is, the two configurations are not identical error_code: This parameter describes the type of error Possible errors are the respective meanings of the slave_position: — No configuration available; slave_position does not have a meaning — The configuration became shorter; slave_position indicates the first missing slave — The configuration became larger; slave_position indicates the first additional slave — Additional slave to W1 of slave_position — The slave with the slave_position number is missing — The slave with the slave_position number is a slave with an incorrect device code slave_position: Slave_position contains the error position in the ring J.2.3 Compare_Slave function The Compare_Slave function compares the device code and the ring segment level of two slaves and returns the result of the comparison in the result and error_code parameters (see Table J.5) 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 LICENSED TO MECON Limited - RANCHI/BANGALORE FOR INTERNAL USE AT THIS LOCATION ONLY, SUPPLIED BY BOOK SUPPLY BUREAU Parameter name 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 61158-4  IEC:2003(E) – 1087 – Table J.5 – Compare_Slave Parameter name Argument saved_data current_data Request Confirm M M M Result (+) S Result (-) error_code S M saved_data: current_data: This parameter contains the ID code and the ring segment level of a slave of the currently acquired configuration result (+): The two slaves have the same ID code and ring segment level result (-): The two slaves have different ID codes and/or ring segment levels error_code: Error_code describes the type of distinction The following is possible: — The ring segment level of the slave in the currently acquired configuration is higher — The ring segment level is lower — The ID codes are different A ring segment level which is too high or too low has a higher priority than an invalid ID code Thus, error_code gives no information on the ID code when the ring segment level is incorrect However, if a wrong ID code is reported, the ring segment level is definitely okay J.2.4 J.2.4.1 State Machine for Comparing the Configuration Data General Figure J.3 shows the state machine for comparing two configurations 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 LICENSED TO MECON Limited - RANCHI/BANGALORE FOR INTERNAL USE AT THIS LOCATION ONLY, SUPPLIED BY BOOK SUPPLY BUREAU This parameter contains the ID code and the ring segment level of a slave which is stored in the master's configuration 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 61158-4  IEC:2003(E) – 1088 – READY 4, 5, 6, 7, 8, CHECK_CONFIG J.2.4.2 States of the state machine READY The state machine is ready to execute the Check_Config function CHECK_CONFIG The configurations are being compared by means of the Check_Config function Table J.6 describes the state transitions 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 LICENSED TO MECON Limited - RANCHI/BANGALORE FOR INTERNAL USE AT THIS LOCATION ONLY, SUPPLIED BY BOOK SUPPLY BUREAU Figure J.3 – State machine for comparing two configurations 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 61158-4  IEC:2003(E) – 1089 – Table J.6 – State transitions of the state machine for comparing two configurations Initial state event \condition ⇒ action Transition Follow-up state READY READY Check_Config.request \quantity of current identified slaves == ⇒ Check_Config.confirm (-) with error_code = 'no configuration available' READY READY Check_Config.request \quantity of identified slaves != ⇒ slave_no = 1, m = slave quantity in current configuration, n = slave quantity in stored configuration, Compare_Slave.request(saved_config.[slave_no], current_config.[slave_no]) CHECK_CONFIG CHECK_CONFIG Compare_Slave.confirm (+) \slave_no < n AND slave_no < m ⇒ slave_no++, Compare_Slave.request(saved_config.[slave_no], current_config.[slave_no]) CHECK_CONFIG CHECK_CONFIG Compare_Slave.confirm (+) \slave_no == n AND slave_no == m ⇒ Check_Config.confirm (+) READY CHECK_CONFIG Compare_Slave.confirm (+) \slave_no < n AND slave_no == m ⇒ Check_Config.confirm (-) with error_code = 'the configuration became shorter' and slave_position = slave_no + READY CHECK_CONFIG Compare_Slave.confirm (+) \slave_no == n AND slave_no < m ⇒ Check_Config.confirm (-) with error_code = 'the configuration became longer' and slave_position = slave_no + READY CHECK_CONFIG Compare_Slave.confirm (-) \error_code == 'ring segment level higher than expected' ⇒ Check_Config.confirm (-) with error_code = 'additional slave at W1 of slave_position' and slave_position = slave_no - READY CHECK_CONFIG Compare_Slave.confirm (-) \error_code == 'ring segment level lower than expected' ⇒ Check_Config.confirm (-) with error_code = 'slave missing' and slave_position = slave_no READY CHECK_CONFIG Compare_Slave.confirm (-) \error_code == 'different ID codes' ⇒ Check_Config.confirm (-) with error_code = 'wrong slave' and slave_position = slave_no READY 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 LICENSED TO MECON Limited - RANCHI/BANGALORE FOR INTERNAL USE AT THIS LOCATION ONLY, SUPPLIED BY BOOK SUPPLY BUREAU Power_On 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 61158-4  IEC:2003(E) – 1090 – J.2.4.3 State Machine for Comparing One Line of Two Configuration Matrices Figure J.4 shows the state machine for comparing one line of two configuration matrices READY 5, 2, CHECK_ID Figure J.4 – State machine for comparing one line of two configuration matrices J.2.4.4 States of the state machine READY The state machine is ready to execute the Compare_Slave function CHECK_RING_SEGMENT_LEVEL The Compare_Slave function was called The ring segment levels are compared CHECK_ID After the comparison of the ring segment levels the ID codes are compared as well This comparison only takes place when the ring segment levels are identical Table J.7 describes the state transitions 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 LICENSED TO MECON Limited - RANCHI/BANGALORE FOR INTERNAL USE AT THIS LOCATION ONLY, SUPPLIED BY BOOK SUPPLY BUREAU CHECK_RING_ SEGMENT_ LEV EL 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 61158-4  IEC:2003(E) – 1091 – Table J.7 – State transitions of the state machine for comparing one line of two configuration matrixes Initial state event \condition ⇒ action Transition Power on Follow-up state READY READY Compare_Slave.request ⇒ compare ring segment levels CHECK_RING_ CHECK_RING_SEGMENT_LEVEL ring segment level higher than expected ⇒ Compare_Slave.confirm (-) with error_code = 'ring segment level higher than expected' READY CHECK_RING_SEGMENT_LEVEL ring segment level lower than expected ⇒ Compare_Slave.confirm (-) with error_code = 'ring segment level lower than expected' READY CHECK_RING_SEGMENT_LEVEL ring segment level are not identical ⇒ compare the ID codes CHECK_ID CHECK_ID ID codes are identical ⇒ Compare_Slave (+) READY CHECK_ID ID codes are not identical ⇒ Compare_Slave (-) with error_code = 'different ID codes' READY LICENSED TO MECON Limited - RANCHI/BANGALORE FOR INTERNAL USE AT THIS LOCATION ONLY, SUPPLIED BY BOOK SUPPLY BUREAU 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 SEGMENT_LEVEL 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 – 1092 – 61158-4  IEC:2003(E) BIBLIOGRAPHY IEC 60559:1989, Binary floating-point arithmetic for microprocessor systems IEC 60847:1989, Characteristics of LANs IEC 60870-5-1:1990, Telecontrol equipment and systems – Part 5-1: Transmission protocols – Transmission frame formats 15 IEC 60955:1989, Process data highway, Type C (PROWAY C), for distributed process control systems IEC 61131-2:1992, Programmable controllers – Part 2: Equipment requirements and tests ISO/IEC 2022:1994, Information technology – Character code structure and extension techniques ISO/IEC 3309:1993, Information technology – Telecommunications and information exchange between systems – High-level data link control (HDLC) procedures – Frame structure ISO/IEC 8802 (all parts), Information technology – Telecommunications and information exchange between systems – Local and Metropolitan area networks ISO/IEC TR 8802-1:1997, Specific requirements – Part 1: Overview of Local Area Network Standards ISO/IEC 8802-2:1998, Specific requirements – Part 2: Logical link control ISO/IEC 8802-3:1996, Specific requirements – Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications ISO/IEC 8802-5:1998, Specific requirements – Part 5: Token ring access method and physical layer specifications ISO/IEC 8802-4:1990, Information processing systems – Local area networks – Part 4: Tokenpassing bus access method and physical layer specifications ISO/IEC 9314-2:1989, Information processing systems – Fibre Distributed Data Interface (FDDI) – Part 2: Token Ring Media Access Control (MAC) ISO/IEC 9646, Information technology – Open Systems Interconnection – Conformance testing methodology and framework ISO/IEC 9646-1:1994, Part 1: General concepts ISO/IEC 9646-2:1994, Part 2: Abstract test suite specification ISO/IEC 10646-1:1993, Information technology – Universal Multiple-Octet Coded Character Set (UCS) – Part 1: Architecture and Basic Multilingual Plane 15 This publication has been deleted in the IEC and is no longer available 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 LICENSED TO MECON Limited - RANCHI/BANGALORE FOR INTERNAL USE AT THIS LOCATION ONLY, SUPPLIED BY BOOK SUPPLY BUREAU ISO/IEC 1177:1985, Information processing – Character structure for start/stop and synchronous character oriented transmission 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 61158-4  IEC:2003(E) – 1093 – ISO/IEC 15802-1:1995, Information technology – Telecommunications and information exchange between systems – Local and metropolitan area networks – Common specifications – Part 1: Medium Access Control (MAC) service definition ISO 8509:1987, Information processing systems – Open System Interconnection – Service Conventions ITU-T V.41, Code-independent error-control system ANSI X3.66:1979 (R1990), Advanced data communication control procedures (ADCCP) ANSI X3.159-1989, Information Systems – Programming Language C IEEE Std 1451.1:1996, Smart Transducer Interface for Sensors and Actuators – Network Capable Application Processor (NCAP) Information Model IEEE Std 1451.2:1997, Smart Transducer Interface for Sensors and Actuators – Transducer to Microprocessor Communication Protocols and Transducer Electronic Data Sheets (TEDS) Formats Internet Engineering Task Force (IETF), Request for Comments (RFC) : RFC 791:1981, Internet Protocol RFC 793:1981, Transmission Control Protocol RFC 1213:1991, Management Information Base for Network Management of TCP/IPbased internets : MIB-II RFC 1643:1994, Definitions of Managed Objects for the Ethernet-like Interface Types IETF : March 2, 2001, The DHCP Client FQDN Option 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 LICENSED TO MECON Limited - RANCHI/BANGALORE FOR INTERNAL USE AT THIS LOCATION ONLY, SUPPLIED BY BOOK SUPPLY BUREAU ANSI X3J16 / ISO WG21 committee draft working paper for a C++ standard 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 – 1094 – 61158-4  IEC:2003(E) INDEX 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 LICENSED TO MECON Limited - RANCHI/BANGALORE FOR INTERNAL USE AT THIS LOCATION ONLY, SUPPLIED BY BOOK SUPPLY BUREAU Addressing See 6.3 service access points single (DLSAP-address), 38 single or group of (DL(SAP)-address), 38 Bridges Functionality, 40, 88, 89, 90, 114, 115, 216, 220, 275, 323, 324 Requirements, 98, 117, 129, 134, 179, 217, 231, 232, 236, 244, 248, 303, 322, 394, 397, 400, 413 DLPDU modification, 87, 132 Reserved addresses, 105, 107, 108 Connectionless service Data exchange See 8.5–8.7, 9.4.1, 10.3.3 Listener query See 10.3.4 remote-acknowledged Data transfer See 8.7, 10.3.1 Connection-oriented service Connection establishment See 8.1, 9.1, 10.2.1 Connection release See 8.2, 9.2, 10.2.1 Reset See 8.3, 9.3, 10.2.2 State transition diagram for a DLCEP, 247 , 940 Subscriber query See 10.2.3 variables and timers See 6.7.4 delocalization, 133 Delocalization, 39 , 134 DL(SAP)-address See Addressing, service access points, single or group DLE initialization, 347 – 49 State transition diagram, 347 , 932 DL-management information See clause 12.4.3.1 DL-paths, 88, 89, 221, 249, 275, 384, 396, 427, 959 DLSAP, 37 DLSAP-address See Addressing, service access points, single DL-time, 41, 43, 119, 237 also 8.9–8.12, 9.6–9.8, 10.4.1 Fractional Duty Cycle (FDC), 44 , 90, 115, 127, 216, 317, 323, 326 Requirements, 244, 248, 249, 313, 316, 320, 341, 346, 398 Link extended, 38 local, 37 Link Active Scheduler (LAS), 41 See also Token, Scheduler token Functionality, 89, 115 Requirements, 126–29, 137, 143, 145, 147, 154, 162, 170, 178, 180, 182, 183, 184, 186, 188, 189– 90, 192, 194–97, 203–5, 209, 212, 213–15, 216, 218, 232, 264, 301, 304, 310, 345, 410, 414 also clause 11 Reserved addresses, 108 timers, 45 Link Master (LM), 42 Functionality, 90, 115 Requirements, 126–29, 211, 215, 345, 348, 359, 360, 361, 362, 363, 394, 398, 414 timers, 42 Profiles, implementation See clause 12.6 Quality of Service (QoS) DLCEP class, 91 DLCEP data delivery features, 91 DLPDU authentication, 92 Maximum confirm delay, 92 – 93 Maximum DLSDU size, 93 – 94 Priority, 91 – 92 Queuing policy, 94 – 96 Remote DLE confirmed, 97 Residual activity, 92 Scheduling, 93 Timeliness, 44 , 96 – 97 Redundancy within the Data Link Layer, 88, 275, 384 See also Bridges and DL-paths Scheduling service Compel service See 10.4.2 Implicit scheduling See 10.4.3 Sequence scheduling See 10.4.3 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 61158-4  IEC:2003(E) – 1095 – 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 LICENSED TO MECON Limited - RANCHI/BANGALORE FOR INTERNAL USE AT THIS LOCATION ONLY, SUPPLIED BY BOOK SUPPLY BUREAU Sequence subsetting See 10.4.4 SPDU Definitions See 11.3 Requirements See 12.3, 11.4 SPDUs See clause 11 Timeliness, 245, 246–47 See also Quality of Service (QoS) Timers DLCEP related usage of, 266, 272, 274, 277, 279, 280–82, 284, 286, 287, 288 DLCEP retransmission request monitor, 125 DLCEP sent segments monitor, 123 Immediate response recovery delay usage of tx_irrd_timer_usage Immediate response recovery delay monitor, 118 Implementation considerations, 44 Maximum confirm delay usage of, 251, 253, 255, 256, 257, 258, 259, 260–61, 262, 265, 268, 269, 270, 274, 279–80, 283, 284, 285, 286, 288, 289, 290, 291, 292, 293, 296, 298, 299 Maximum confirm delay monitor, 120 Node time counter, 119 Node timer, 43 update, 301 usage of, 184 Remaining duration counter, 117 Residual activity monitor, 125 Residual activity stimulus, 125 Slot time, 43 , 116 usage of, 190 Time distribution period usage of, 301, 304 Time distribution period monitor, 120 User response delay usage of, 253–56, 258 Token Delegated token, 39, 44 creation of, 41, 139, 192, 201 usage of, 41, 42, 89, 131, 135–37, 139, 141, 142, 145, 147, 150, 156, 164, 173, 174, 175, 182, 185, 217, 218, 310 Dominant token, 39 , 135, 139, 141 Reply token, 39, 45 assumption of, 190 creation of, 89, 131, 139, 187, 188 usage of, 41, 42, 89, 118, 139, 141, 148, 154, 162, 173, 174, 175, 177, 178, 183, 236, 249 Scheduler token, 44 assumption of, 137, 139, 143, 145, 178, 180, 182, 184, 188, 192, 197, 205, 209, 210, 212, 215, 218, 348, 353 dropping of, 192, 201, 208, 212, 214, 215 retention of, 214, 215 usage of, 41, 117, 135–37, 139, 141, 142, 145, 147, 150, 155, 156, 164, 173, 175, 183, 184, 185, 189, 190, 191, 194, 195, 203, 212, 216, 218, 351 – 52 Type Addressing connection endpoint (DLCEP), 39 scheduling endpoint (DLSEP), 40 Bridges, 39 DLCEP-address See Addressing, connection endpoint DL-Connection (DLC) multi-peer, 42 peer, 43 DLSEP-address See Addressing, scheduling endpoint Paths, 40 Type DLPDU, 46 fixed tag, 47 generic tag, 47 guardband, 47 moderator, 48 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 – 1096 – 61158-4  IEC:2003(E) Type Bridges, 39 DL-Connection (DLC) multi-peer, 56 peer, 43 , 56 ——————— LICENSED TO MECON Limited - RANCHI/BANGALORE FOR INTERNAL USE AT THIS LOCATION ONLY, SUPPLIED BY BOOK SUPPLY BUREAU 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 Standards Survey The IEC would like to offer you the best quality standards possible To make sure that we continue to meet your needs, your feedback is essential Would you please take a minute to answer the questions overleaf and fax them to us at +41 22 919 03 00 or mail them to the address below Thank you! Customer Service Centre (CSC) or Fax to: IEC/CSC at +41 22 919 03 00 Thank you for your contribution to the standards-making process Nicht frankieren Ne pas affranchir A Prioritaire Non affrancare No stamp required RÉPONSE PAYÉE SUISSE Customer Service Centre (CSC) International Electrotechnical Commission 3, rue de Varembé 1211 GENEVA 20 Switzerland 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 LICENSED TO MECON Limited - RANCHI/BANGALORE FOR INTERNAL USE AT THIS LOCATION ONLY, SUPPLIED BY BOOK SUPPLY BUREAU International Electrotechnical Commission 3, rue de Varembé 1211 Genève 20 Switzerland 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 Q1 Please report on ONE STANDARD and ONE STANDARD ONLY Enter the exact number of the standard: (e.g 60601-1-1) Q6 standard is out of date R standard is incomplete R standard is too academic R standard is too superficial R title is misleading R I made the wrong choice R other Q2 Please tell us in what capacity(ies) you bought the standard (tick all that apply) I am the/a: Q3 Q7 I work for/in/as a: (tick all that apply) manufacturing R consultant R government R test/certification facility R public utility R education R military R other timeliness quality of writing technical contents logic of arrangement of contents tables, charts, graphs, figures other Q8 Q4 Q5 Q9 This standard meets my needs: (tick one) not at all nearly fairly well exactly R R R R I read/use the: (tick one) French text only English text only both English and French texts This standard will be used for: (tick all that apply) general reference R product research R product design/development R specifications R tenders R quality assessment R certification R technical documentation R thesis R manufacturing R other Please assess the standard in the following categories, using the numbers: (1) unacceptable, (2) below average, (3) average, (4) above average, (5) exceptional, (6) not applicable 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 R R R Please share any comment on any aspect of the IEC that you would like us to know: LICENSED TO MECON Limited - RANCHI/BANGALORE FOR INTERNAL USE AT THIS LOCATION ONLY, SUPPLIED BY BOOK SUPPLY BUREAU purchasing agent R librarian R researcher R design engineer R safety engineer R testing engineer R marketing specialist R other If you ticked NOT AT ALL in Question the reason is: (tick all that apply) 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 LICENSED TO MECON Limited - RANCHI/BANGALORE FOR INTERNAL USE AT THIS LOCATION ONLY, SUPPLIED BY BOOK SUPPLY BUREAU 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

Ngày đăng: 24/07/2023, 01:20

Xem thêm:

TÀI LIỆU CÙNG NGƯỜI DÙNG

  • Đang cập nhật ...

TÀI LIỆU LIÊN QUAN