Magtek MCP Manuel d'utilisateur

Naviguer en ligne ou télécharger Manuel d'utilisateur pour Équipement Magtek MCP. MagTek MCP User Manual Manuel d'utilisatio

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer

Résumé du contenu

Page 1 - SERIAL TRANSPORT PROTOCOL

MCP SERIAL TRANSPORT PROTOCOL REFERENCE MANUAL Manual Part Number 99875163-Rev 5 APRIL 2007 REGISTERED TO ISO 9001:2000 1710 Apollo

Page 2

MCP Serial Transport Protocol 4 Protocol Control Byte The protocol control byte (PCB) provides information about the frame type, EDC protection u

Page 3 - SOFTWARE LICENSE AGREEMENT

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

Page 4

MCP Serial Transport Protocol 6

Page 5

7SECTION 3. TRANSPORT FRAME TYPES I-FRAMES This section defines the I-frames used in the MCP communications protocol. An I-frame (information fra

Page 6

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

Page 7 - SECTION 1. OVERVIEW

Section 3. Transport Frame Types 9R-FRAMES This section defines the R-frames. An R-frame (receipt frame) is used for the following purposes: •

Page 8

MCP Serial Transport Protocol 10 Receive Sequence Number (N(R)) The receive sequence number indicates what the next expected sequence number is,

Page 9

Section 3. Transport Frame Types 11S-FRAMES This section defines the S-frames used in the MCP communications protocol. An S-frame (supervisory

Page 10 - MSB LSB

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

Page 11

Section 3. Transport Frame Types 13Resynchronize Protocol Command Command Code: 0 (0000) S-frame Type: Request/Response Request PCB: 90 (Hex) Re

Page 12

ii Copyright© 2000-2007 MagTek®, Inc. Printed in the United States of America Information in this document is subject to change without notice. No

Page 13 - Chain Indicator (CI)

MCP Serial Transport Protocol 14 Reset Device Command Command Code: 1 (0001) S-frame Type: Request/Response Request PCB: 91 (Hex) Response PCB: A

Page 14

Section 3. Transport Frame Types 15Get Communication Parameters Command Command Code: 2 (0010) S-frame Type: Request/Response Request PCB: 92 (H

Page 15 - Poll Indicator (POLL)

MCP Serial Transport Protocol 16 Model Number Parameter Parameter ID: 01 (Hex) Description: This parameter is not supported. Serial Number Par

Page 16 - Data Field

Section 3. Transport Frame Types 17Set Communication Parameters Command Command Code: 3 (0011) S-frame Type: Request/Response Request PCB: 93 (H

Page 17 - S-frame Type (STYP)

MCP Serial Transport Protocol 18 Frame Reject Command Command Code: 5 (0101) S-frame Type: Indication PCB: 85 (Hex) Description: The frame reje

Page 18 - Command Code (CC)

Section 3. Transport Frame Types 19Baud Synchronization Command Command Code: 6 (0110) S-frame Type: Request/Response Request PCB: 96 (Hex) Resp

Page 19 - Result Code

MCP Serial Transport Protocol 20 Echo Command Command Code: 7 (0111) S-frame Type: Request/Response Request PCB: 97 (Hex) Response PCB: A7 (hex)

Page 20

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

Page 22 - Serial Number Parameter

23SECTION 4. PROTOCOL This section describes the protocol used for nodes to communicate using the frame formats and S-frame command described previ

Page 23

iii SOFTWARE LICENSE AGREEMENT IMPORTANT: YOU SHOULD CAREFULLY READ ALL THE TERMS, CONDITIONS AND RESTRICTIONS OF THIS LICENSE AGREEMENT BEFORE INST

Page 24

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

Page 25

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

Page 26 - Result Code Request Data

MCP Serial Transport Protocol 26 RESYNCHRONIZATION Resynchronization of the protocol may be attempted at three consecutive levels. If one level

Page 27

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

Page 28

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

Page 29 - SECTION 4. PROTOCOL

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

Page 30

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

Page 31 - Section 4. Protocol

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

Page 32

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

Page 33

Section 4. Protocol 33SCENARIOS This section describes different scenarios to illustrate how the protocol works in various situations. The sce

Page 34

vi ACKNOWLEDGMENT: LICENSEE ACKNOWLEDGES THAT HE HAS READ THIS AGREEMENT, UNDERSTANDS ALL OF ITS TERMS, CONDITIONS AND RESTRICTIONS AND AGREES TO BE

Page 35

MCP Serial Transport Protocol 34 Service Request Error Handling – no response S (echo req) ÆÆÆ (Rule 1.1) (bwt) S (echo req) ÆÆÆ (Rule 1.4)

Page 36

Section 4. Protocol 35Resetting a Connection (connection was established and some data may have been exchanged) I (0,0) ÆÆÆ (Rule 4.1) ÅÅÅ R (

Page 37

MCP Serial Transport Protocol 36 Error Recovery Error Recovery Using R-poll – data frame lost (connection was established and some data may have

Page 38 - Rule 6.6

Section 4. Protocol 37Error Recovery – intermediate data received (connection was established and some data may have been exchanged) I (0,0) ÆXÆ

Page 39

MCP Serial Transport Protocol 38 Repeating Baud Synchronization Upon Failure of Error Recovery (connection was established and some data may have

Page 40 - Establishing a Connection

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

Page 41 - Resetting a Connection

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)

Page 42

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

Page 43

MCP Serial Transport Protocol 42 Each model device shall use a different product identifier. The product identifier can usually be found in the

Page 44 - Sending Chained Data

v TABLE OF CONTENTS SECTION 1. OVERVIEW...

Page 45 - Error Recovery During Chain

MCP Serial Transport Protocol vi Error Recovery ...

Page 46

1 SECTION 1. OVERVIEW This document describes the common format of the serial transport frames and defines the protocol for using these frames. Th

Page 47 - SECTION 5. USB

MCP Serial Transport Protocol 2

Page 48

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

Pas de commentaire