ANSI INCITS472-2011 Information technology - Automation Drive Interface - Transport Protocol -2 (ADT-2)《信息技术.自动化 驱动器接口.传输协议.2(ADT-2)》.pdf

《ANSI INCITS472-2011 Information technology - Automation Drive Interface - Transport Protocol -2 (ADT-2)《信息技术.自动化 驱动器接口.传输协议.2(ADT-2)》.pdf》由会员分享，可在线阅读，更多相关《ANSI INCITS472-2011 Information technology - Automation Drive Interface - Transport Protocol -2 (ADT-2)《信息技术.自动化 驱动器接口.传输协议.2(ADT-2)》.pdf（162页珍藏版）》请在麦多课文档分享上搜索。

1、American National StandardDeveloped byfor Information Technology Automation/Drive Interface Transport Protocol - 2(ADT-2)INCITS 472-2011INCITS 472-2011Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without

2、 license from IHS-,-,-Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-INCITS 472-2011American National Standardfor Information Technology Automation/Drive Interface Transport Pr

3、otocol - 2(ADT-2)SecretariatInformation Technology Industry CouncilApproved June 14, 2011American National Standards Institute, Inc.AbstractThis standard specifies the transport requirements for the SCSI automation drive interface device. Thisstandard permits the SCSI automation drive interface devi

4、ces to attach to application clients andprovides the definitions for their use.This standard does not contain material related to any command structure for automation drive interfacedevices, that is used in conjunction with this standard. For reference to command structure, refer to ADC-3.Copyright

5、American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-Approval of an American National Standard requires review by ANSI that therequirements for due process, consensus, and other criteria for a

6、pproval havebeen met by the standards developer.Consensus is established when, in the judgement of the ANSI Board ofStandards Review, substantial agreement has been reached by directly andmaterially affected interests. Substantial agreement means much more thana simple majority, but not necessarily

7、unanimity. Consensus requires that allviews and objections be considered, and that a concerted effort be madetowards their resolution.The use of American National Standards is completely voluntary; theirexistence does not in any respect preclude anyone, whether he has approvedthe standards or not, f

8、rom manufacturing, marketing, purchasing, or usingproducts, processes, or procedures not conforming to the standards.The American National Standards Institute does not develop standards andwill in no circumstances give an interpretation of any American NationalStandard. Moreover, no person shall hav

9、e the right or authority to issue aninterpretation of an American National Standard in the name of the AmericanNational Standards Institute. Requests for interpretations should beaddressed to the secretariat or sponsor whose name appears on the titlepage of this standard.CAUTION NOTICE: This America

10、n National Standard may be revised orwithdrawn at any time. The procedures of the American National StandardsInstitute require that action be taken periodically to reaffirm, revise, orwithdraw this standard. Purchasers of American National Standards mayreceive current information on all standards by

11、 calling or writing the AmericanNational Standards Institute.American National StandardPublished byAmerican National Standards Institute, Inc.25 West 43rd Street, New York, NY 10036Copyright 2011 by Information Technology Industry Council (ITI)All rights reserved.No part of this publication may be r

12、eproduced in anyform, in an electronic retrieval system or otherwise,without prior written permission of ITI, 1101 K Street NW, Suite 610 Washington, DC 20005. Printed in the United States of AmericaCAUTION: The developers of this standard have requested that holders of patents that may be re-quired

13、 for the implementation of the standard disclose such patents to the publisher. However, nei-ther the developers nor the publisher have undertaken a patent search in order to identify which, ifany, patents may apply to this standard. As of the date of publication of this standard, followingcalls for

14、 the identification of patents that may be required for the implementation of the standard,notice of one or more such claims has been received. By publication of this standard, no positionis taken with respect to the validity of this claim or of any rights in connection therewith. The knownpatent ho

15、lder(s) has (have), however, filed a statement of willingness to grant a license underthese rights on reasonable and nondiscriminatory terms and conditions to applicants desiring to ob-tain such a license. Details may be obtained from the publisher. No further patent search is con-ducted by the deve

16、loper or publisher in respect to any standard it processes. No representation ismade or implied that this is the only license that may be required to avoid infringement in the use ofthis standard.Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo

17、 reproduction or networking permitted without license from IHS-,-,-iContentsPageForewordxIntroduction.xiii1 Scope.12 References.32.1 Normative references 32.1.1 Normative references overview.32.1.2 Approved references.32.1.3 References under development32.1.4 IETF References52.1.5 IEEE references.52

18、.2 Informative references53 Definitions, symbols, abbreviations, and conventions.63.1 Definitions.63.2 Symbols and abbreviations.93.3 Keywords93.4 Editorial conventions.103.5 Notation conventions.123.5.1 Notation for procedures and functions.123.5.2 Notation for state machines.133.5.2.1 Notation for

19、 state machines overview.133.5.2.2 Sub-state machines133.5.2.3 Transitions143.5.2.4 Messages, requests, and event notifications143.5.3 Notation for communication sequence diagrams.144 General164.1 Architecture.164.1.1 Architecture introduction164.1.2 ADT protocol layers.174.2 Default operating param

20、eters.194.3 ADT state machines204.3.1 Introduction204.3.2 ADT Port state machine.204.3.2.1 ADT port state machine overview.204.3.2.2 P0:Initial state.214.3.2.3 P1:Login state.224.3.2.4 P2:Logged-In234.3.2.5 P3:Logged-Out state.244.3.3 Link negotiation state machine244.3.3.1 Link negotiation state ma

21、chine overview244.3.3.2 Precedence of Port Login exchanges.254.3.3.3 Common renegotiation conditions264.3.3.4 N0:Idle state264.3.3.5 N1:Negotiating state.274.3.3.6 N2:Accept Sent state284.3.3.7 N3:Accept ACK Sent state294.3.3.8 N4:Agreed state29Copyright American National Standards Institute Provide

22、d by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-ii4.3.4 Transmitter state machine.304.3.4.1 Transmitter state machine overview.304.3.4.2 T0:Entering state.314.3.4.3 T1:Active state314.3.4.4 T2:Paused state314.3.5 Transmitter error r

23、ecovery state machine324.3.5.1 Transmitter error recovery state machine overview324.3.5.2 TE0:Idle state324.3.5.3 TE1:Initiating Recovery state334.3.5.4 TE2:Retry Initiate Recovery state.334.3.6 Receiver error recovery state machine334.3.6.1 Receiver error recovery state machine overview334.3.6.2 RE

24、0:Idle state.344.3.6.3 RE1:Pending Recovery state344.3.6.4 RE2:Recovering state.354.4 ACK Offset354.5 Frame Number Counters364.5.1 Frame Number Counters overview364.5.2 Next Frame To Send counter.364.5.3 Expected Frame Number counter364.6 Link layer error recovery.374.6.1 Error detection.374.6.1.1 E

25、rror detection overview.374.6.1.2 Error detection by the frame sender.374.6.1.3 Error detection by the frame receiver374.6.2 Error recovery384.6.2.1 Corrupted frame384.6.2.2 Error recovery for symbol framing errors384.6.2.3 Recoverable error.384.6.2.4 Retryable error394.6.2.5 Protocol error394.6.2.6

26、 Resource limitation error.404.7 Hard reset.414.8 I_T nexus loss.414.9 Transport protocol variations from SAM-4414.10 Acknowledgement time-out period434.10.1 Acknowledgement time-out period calculation.434.10.2 . Acknowledgement time-out period negotiation434.10.2.1 Acknowledgement time-out period n

27、egotiation introduction.434.10.2.2 Discovering another ADT ports acknowledgement time-out period parameters434.10.2.3 Altering another ADT ports acknowledgement time-out period444.10.2.4 Exception conditions.445 Physical layer.455.1 Physical layer introduction455.2 Electrical Characteristics.455.2.1

28、 ADT compliance points455.2.2 Cabling.455.2.3 Sense connection455.2.4 sADT signal connection.465.2.5 Transmit-receive connections475.2.5.1 Transmit-receive connections introduction.475.2.5.2 Serial transmit-receive connections475.2.5.3 Ethernet transmit-receive connections48Copyright American Nation

29、al Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-iii5.2.6 Ethernet LED connections.485.3 Connection Instances.495.3.1 Sense connection instances495.3.2 sADT signal connection instances.495.3.3 Serial tra

30、nsmit-receive connection instances.495.3.4 Ethernet transmit-receive connection instances505.3.5 Ethernet LED connection instances.515.4 Connector pin-out.526 Connection layer536.1 Connection layer introduction.536.2 Connection layer connection service definitions.566.2.1 Connect request.566.2.2 Con

31、nected service confirmation.576.2.3 Connect Received service indication.576.2.4 Send service request.576.2.5 Sent service confirmation.586.2.6 Receive service request.596.2.7 Received service confirmation.596.2.8 Disconnect service request606.2.9 Disconnect Immediate service request616.2.10 Disconne

32、cted service confirmation616.2.11 Disconnect Received service indication.626.2.12 Reset service request636.2.13 Reset Received service indication.636.3 sADT port support of connection services636.3.1 Data transmission636.3.2 Data reception646.3.3 Performing a reset.646.4 iADT port support of connect

33、ion services.656.4.1 Connection establishment656.4.2 Data transmission666.4.3 Data reception666.4.4 Closing a connection676.4.5 Performing a reset.686.5 Service discovery for iADT ports using the iADT Discovery protocol696.5.1 Service discovery introduction.696.5.2 Service discovery message.696.5.3

34、Service discovery transmission processing.736.5.4 Service discovery message reception processing.737 Link layer757.1 Basic frame format757.2 Encoding.757.3 ADT frame header767.4 Checksum.777.5 Link service information units787.5.1 Link service frames overview.787.5.2 Payload size type consistency787

35、.5.3 Acknowledgement information units787.5.3.1 Acknowledgement information units introduction787.5.3.2 ACK information unit.797.5.3.3 NAK information unit.797.5.3.4 Interleaving acknowledgement and other frame types.80Copyright American National Standards Institute Provided by IHS under license wit

36、h ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-iv7.5.4 Port login information unit807.5.5 Port logout information unit837.5.6 Pause information unit.847.5.7 NOP information unit847.5.8 Initiate Recovery information unit.857.5.9 Initiate Recovery ACK informa

37、tion unit857.5.10 Initiate Recovery NAK information unit857.5.11 Device Reset information unit857.5.12 Time-out information unit.867.5.13 Link service exchange lifetime.887.5.13.1 Link service exchange types.887.5.13.2 Simple link service exchange lifetime.887.5.13.3 Negotiation exchange lifetime.88

38、7.5.13.4 Time-out discovery exchange lifetime.887.6 Sessions.898 Transport layer.908.1 SCSI Encapsulation908.1.1 SCSI encapsulation overview908.1.2 SCSI Command information unit.918.1.3 SCSI Task Management information unit928.1.4 SCSI Response information unit938.1.5 SCSI Transfer Ready information

39、 unit.958.1.6 SCSI Data information unit968.1.7 SCSI encapsulation exchange lifetime978.1.8 SCSI Command - Expanded information unit978.1.9 Reception of Encapsulated SCSI Information Units in exceptional circumstances988.2 Fast Access998.2.1 Fast Access overview998.2.2 Payload size type consistency9

40、98.2.3 Request for VHF Data information unit998.2.4 VHF Data information unit1008.2.5 AER information unit1008.2.6 AER Control information unit.1008.2.7 AER - Expanded information unit.1008.2.8 AER - Expanded Control information unit1018.2.9 Fast Access exchange lifetime1018.2.9.1 Fast Access exchan

41、ge types1018.2.9.2 VHF Data exchange lifetime.1018.2.9.3 AER Control exchange lifetime.1028.2.9.4 AER exchange lifetime1028.2.9.5 AER - Expanded Control exchange lifetime1028.2.9.6 AER - Expanded exchange lifetime1029 SCSI Application layer.1039.1 SCSI Transport protocol services overview1039.2 Tran

42、sport layer protocol services to support Execute Command.1059.2.1 Send SCSI Command transport protocol service1059.2.2 SCSI Command Received transport protocol service1069.2.3 Send Command Complete transport protocol service.1069.2.4 Command Complete Received transport protocol service.1079.2.5 Send

43、 Data-In transport protocol service1089.2.6 Data-In Delivered transport protocol service1099.2.7 Receive Data-Out transport protocol service.109Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without licens

44、e from IHS-,-,-v9.2.8 Data-Out Received transport protocol service.1109.2.9 Send Data-Out transport protocol service1109.2.10 Data-Out Delivered transport protocol service.1119.2.11 Receive Data-In transport protocol service1119.2.12 Data-In Received transport protocol service1129.3 Task management

45、protocol services1129.3.1 Send Task Management Request transport protocol service1129.3.2 Task Management Request Received transport protocol service1139.3.3 Task Management Function Executed transport protocol service.1139.3.4 Received Task Management Function-Executed transport protocol service.11

46、49.4 Application client error handling1159.5 SCSI mode parameters1159.5.1 Disconnect-Reconnect mode page1159.5.2 Protocol-Specific Port mode page.1159.5.3 Protocol-Specific Logical Unit mode page.115Annex A .116A.1 Introduction.116A.2 SCSI command with no data phase.116A.3 SCSI Command with data in1

47、16A.4 SCSI Command with data out119Annex B .121B.1 Introduction.121B.2 Receiver-detected retryable error.122B.3 Receiver-detected retryable error with multiple active IUs.122B.4 Lost IU with no further traffic.124B.5 Lost ACK with recovery driven by out-of-order ACK.125B.6 Lost IU with recovery driv

48、en by out-of-order NAK126B.7 Lost NAK with recovery driven by timeout127B.8 Non-retryable error.128B.9 Lost ACK with errors on next IU.129B.10 Delayed response with recovery driven by timeout130Annex C .131C.1 Introduction.131C.2 Field values common to all frames.131C.3 DT device initiates a login a

49、fter power-up131C.4 Automation device initiates login after power-up133Annex D .136Annex E .139E.1 Introduction.139E.2 Ambiguous connection establishment order.139E.3 Automation device-initiated connection established first141E.4 DT device-initiated connection established first.142E.5 Login sent before second connection established143E.6 Connection recei