MCP SERIAL TRANSPORT PROTOCOL REFERENCE MANUAL Manual Part Number 99875163-Rev 5 APRIL 2007 REGISTERED TO ISO 9001:2000 1710 Apollo
MCP Serial Transport Protocol 4 Protocol Control Byte The protocol control byte (PCB) provides information about the frame type, EDC protection u
Section 2. Transport Frame Format 5DATA FIELD The data field can be 0 – 65535 bytes in length. The contents of the data field depend on the fra
MCP Serial Transport Protocol 6
7SECTION 3. TRANSPORT FRAME TYPES I-FRAMES This section defines the I-frames used in the MCP communications protocol. An I-frame (information fra
MCP Serial Transport Protocol 8 Send and receive sequence numbers (N(S), N(R)) The send sequence number, N(S), is the sequence number of the curr
Section 3. Transport Frame Types 9R-FRAMES This section defines the R-frames. An R-frame (receipt frame) is used for the following purposes: •
MCP Serial Transport Protocol 10 Receive Sequence Number (N(R)) The receive sequence number indicates what the next expected sequence number is,
Section 3. Transport Frame Types 11S-FRAMES This section defines the S-frames used in the MCP communications protocol. An S-frame (supervisory
MCP Serial Transport Protocol 12 Request S-frames are sent by a node to request a specific transmission control operation to be performed by the d
Section 3. Transport Frame Types 13Resynchronize Protocol Command Command Code: 0 (0000) S-frame Type: Request/Response Request PCB: 90 (Hex) Re
ii Copyright© 2000-2007 MagTek®, Inc. Printed in the United States of America Information in this document is subject to change without notice. No
MCP Serial Transport Protocol 14 Reset Device Command Command Code: 1 (0001) S-frame Type: Request/Response Request PCB: 91 (Hex) Response PCB: A
Section 3. Transport Frame Types 15Get Communication Parameters Command Command Code: 2 (0010) S-frame Type: Request/Response Request PCB: 92 (H
MCP Serial Transport Protocol 16 Model Number Parameter Parameter ID: 01 (Hex) Description: This parameter is not supported. Serial Number Par
Section 3. Transport Frame Types 17Set Communication Parameters Command Command Code: 3 (0011) S-frame Type: Request/Response Request PCB: 93 (H
MCP Serial Transport Protocol 18 Frame Reject Command Command Code: 5 (0101) S-frame Type: Indication PCB: 85 (Hex) Description: The frame reje
Section 3. Transport Frame Types 19Baud Synchronization Command Command Code: 6 (0110) S-frame Type: Request/Response Request PCB: 96 (Hex) Resp
MCP Serial Transport Protocol 20 Echo Command Command Code: 7 (0111) S-frame Type: Request/Response Request PCB: 97 (Hex) Response PCB: A7 (hex)
Section 3. Transport Frame Types 21 Description: The frame resend indication is used to notify a node that one of its frames was received with d
23SECTION 4. PROTOCOL This section describes the protocol used for nodes to communicate using the frame formats and S-frame command described previ
iii SOFTWARE LICENSE AGREEMENT IMPORTANT: YOU SHOULD CAREFULLY READ ALL THE TERMS, CONDITIONS AND RESTRICTIONS OF THIS LICENSE AGREEMENT BEFORE INST
MCP Serial Transport Protocol 24 R-frame to I-frame Delay Due to limited resources in MagTek's RS232 and USB MCP devices, there is a limita
Section 4. Protocol 25GENERAL PROCEDURES During the protocol, any node may send a frame at any time, regardless of whether it has received a fr
MCP Serial Transport Protocol 26 RESYNCHRONIZATION Resynchronization of the protocol may be attempted at three consecutive levels. If one level
Section 4. Protocol 27 RULES Service Requests Rule 1.1 A node can send a service request (S-frame request) at any time. The node shall not se
MCP Serial Transport Protocol 28 Rule 2.3 A node that sends a BAUD_SYNC request shall continue sending BAUD_SYNC requests until (a) it receives
Section 4. Protocol 29Rule 3.7 A node can accept the connection reset by sending RESYNC response according to Rule 3.3. Any outstanding unconfi
MCP Serial Transport Protocol 30 Rule 4.7 A valid response to an I-frame is sending an R-frame with node’s current receive sequence number in th
Section 4. Protocol 31Rule 5.5 A node that initiated error recovery per Rule 5.2 (using R-frame with poll bit set) processes the next received
MCP Serial Transport Protocol 32 Rule 6.2 If a node receives a RESEND S-frame indication for an outstanding I-frame and the PCB enclosed in the
Section 4. Protocol 33SCENARIOS This section describes different scenarios to illustrate how the protocol works in various situations. The sce
vi ACKNOWLEDGMENT: LICENSEE ACKNOWLEDGES THAT HE HAS READ THIS AGREEMENT, UNDERSTANDS ALL OF ITS TERMS, CONDITIONS AND RESTRICTIONS AND AGREES TO BE
MCP Serial Transport Protocol 34 Service Request Error Handling – no response S (echo req) ÆÆÆ (Rule 1.1) (bwt) S (echo req) ÆÆÆ (Rule 1.4)
Section 4. Protocol 35Resetting a Connection (connection was established and some data may have been exchanged) I (0,0) ÆÆÆ (Rule 4.1) ÅÅÅ R (
MCP Serial Transport Protocol 36 Error Recovery Error Recovery Using R-poll – data frame lost (connection was established and some data may have
Section 4. Protocol 37Error Recovery – intermediate data received (connection was established and some data may have been exchanged) I (0,0) ÆXÆ
MCP Serial Transport Protocol 38 Repeating Baud Synchronization Upon Failure of Error Recovery (connection was established and some data may have
Section 4. Protocol 39Error Recovery During Chain I (0,0)-C ÆÆÆ (Rule 4.1) ÅÅÅ R (1) (Rule 4.7) I (1,0)-C ÆXÆ (Rule 4.1) (bwt) R (0)-poll
MCP Serial Transport Protocol 40 Resend Indication on S-frame – indication processed S (echo req) ÆEÆ (Rule 1.1) ÅÅÅ S (resend ind) (Rule 6.1)
41 SECTION 5. USB This protocol can work as is with a RS-232 interface. However, the protocol needs to be adapted slightly to work with a USB inte
MCP Serial Transport Protocol 42 Each model device shall use a different product identifier. The product identifier can usually be found in the
v TABLE OF CONTENTS SECTION 1. OVERVIEW...
MCP Serial Transport Protocol vi Error Recovery ...
1 SECTION 1. OVERVIEW This document describes the common format of the serial transport frames and defines the protocol for using these frames. Th
MCP Serial Transport Protocol 2
3SECTION 2. TRANSPORT FRAME FORMAT COMMON FRAME FORMAT DEFINITION Below is the diagram of the common frame format: DA SA PCB LEN HEDC DATA EDC
Commentaires sur ces manuels