Marantz-SR9600-rs232c-cs 电路图 维修手册.pdf

《Marantz-SR9600-rs232c-cs 电路图 维修手册.pdf》由会员分享，可在线阅读，更多相关《Marantz-SR9600-rs232c-cs 电路图 维修手册.pdf（25页珍藏版）》请在收音机爱好者资料库上搜索。

1、 RS-232C Control Specification : Rev 00 Marantz America, Inc. 2006 All rights are reserved. Reproduction in whole or in part is prohibited without the written consent of copyright. All specifications might be subject to change without notice. SR9600 RS-232C Control Specification Category : A/V Recei

2、ver Document Version : 1.0 Author(s) : Marantz America, Inc. Date : 2006/08/18 Number of Page : 25 RadioFans.CN 收音机爱 好者资料库 SR9600 RS-232C Control Specification Page: 2 / 25 Document Version 1.0 Company Restricted Table of Contents 1. Introduction.3 1-1. Purpose.3 1-2. Scope.3 1-3. Abbreviations .3 1

3、-4. References.3 2. Global Description.3 2-1. Overview.3 2-2. Block Diagram.3 2-3. Interface connection specification of the product.3 2-4. Assumptions and Dependencies.3 3. Detailed Description.4 3-1. Connection format.4 3-1-1. Physical connection.4 3-1-1-1. Data transmission sequence from Host to

4、Slave.4 3-1-1-2. Data transmission sequence from Slave to Host.4 3-2. Transmission data format.5 3-2-1. Transmission data format from Host to Slave.5 3-2-1-1. Form1: Command.5 3-2-1-2. Form2: Status request.5 3-2-2. Transmission data format from Slave to Host.5 3-2-2-1. Form1: ACK/NAK.5 3-2-2-2. For

5、m2: Status answer and Auto status feedback.5 3-3. The transaction sequences and the regulations.6 3-3-1. The transaction sequences.6 3-3-2. The transaction regulations.6 3-3-3. Specification of Auto status feedback.6 3-3-4. Example of the transactions.6 3-3-5. Examples of the handshaking flowchart.7

6、 3-3-5-1. Example of successful handshaking.7 3-3-5-2. Examples of handshaking error.7 4. Recommendations of Command, Status and Layer definition.8 5. Definitions of Command, Status and Layer.9 5-1. Commands.9 5-1-1. Normal Command list.9 5-1-2. Specific Commands.17 5-2. Status request and Status an

7、swer list.18 5-2-1. Normal Status request and Status (answer and feedback) list.18 5-2-2. Layer of the statuses.23 6. Revision history.25 RadioFans.CN 收音机爱 好者资料库 SR9600 RS-232C Control Specification Page: 3 / 25 Document Version 1.0 Company Restricted 1. Introduction 1-1. Purpose This document was w

8、ritten as a reference specification of products that are controled by the host controller. 1-2. Scope This document would be using by software or hardware engineers for production of the product. 1-3. Abbreviations Abbreviation Description 1-4. References - Hardware Software Interface Specification

9、ver. 1.02 / author: N.Sakamoto - 2. Global Description 2-1. Overview A Host controller can control or watch out the product as a Slave very easily via the communication cable. 2-2. Block Diagram * The product connector is using D-SUB 9pin male. * RS232C cable must use D-SUB 9pin female to connect th

10、e products. 2-3. Interface connection specification of the product uP Interface Signal name Connection device D-Sub Pin Connecter - N.C. - 1 TxD (output) 2 UART RxD (input) RS232C Level shift driver 3 - N.C. - 4 - GND GND 5 - N.C. - 6 - N.C. - 7 - N.C. - 8 - N.C. - 9 RS232C D-SUB (9pin,Male) 2-4. As

11、sumptions and Dependencies HOST (Controller) SLAVE (The product) RS232C cable (straight) Connector D-SUB (9pin, male) RadioFans.CN 收音机爱 好者资料库 SR9600 RS-232C Control Specification Page: 4 / 25 Document Version 1.0 Company Restricted 3. Detailed Description The interface specification between the prod

12、uct and a Host controller is described below. 3-1. Connection format 3-1-1. Physical connection Host (Controller) Slave (the product) (Serial setting ) Baud Rate : 9600bps Data Bits : 8bit Parity : None Stop bit : 1bit Handshaking : None 3-1-1-1. Data transmission sequence from Host to Slave Host (C

13、ontroller) Slave (The product) TxD RxD RxD TxD 1. Host starts a data transmission from TxD. 2. Host performs the data transmission of the number of required bytes, and ends a transmission. 3-1-1-2. Data transmission sequence from Slave to Host Host (Controller) Slave (The product) TxD RxD RxD TxD 1.

14、 Slave starts a data transmission from TxD. 2. Slave performs the data transmission of the number of required bytes, and ends a transmission. TxD RxD GND RxD TxD GND SR9600 RS-232C Control Specification Page: 5 / 25 Document Version 1.0 Company Restricted 3-2. Transmission data format 3-2-1. Transmi

15、ssion data format from Host to Slave There are two kinds of transmission data form from Host shown below. 3-2-1-1. Form1: Command Command is a data that requests some status change. Start character : COMMAND : see “Command list” End character (CR) : 0Dh 3-2-1-2. Form2: Status request Status request

16、is a data that requests a answer of some status. Start character : Request status : see “Status request list” Request character : ? End character (CR) : 0Dh 3-2-2. Transmission data format from Slave to Host There are two kinds of transmission data form from Slave shown below. 3-2-2-1. Form1: ACK/NA

17、K ACK is a reply data from Slave when Slave got an acceptable command data from Host. (ACK is sent to Host when Slave has no related status by the Command.) Start character : , ACK : 06h, End character (CR) : 0Dh NAK is a reply data from Slave when Slave got an incorrect Command data, Status request

18、 data or some other data from Host. Start character : , NAK : 15h, End character (CR) : 0Dh 3-2-2-2. Form2: Status answer and Auto status feedback Status answers are reply data when Slave got an acceptable Request status or Command data from Host. Auto status feedbacks are send to Host data when a S

19、laves status is changed. Start character : Answer character : see “Status list” End character (CR) : 0Dh A ACK 06h CR 0Dh start A NAK 15h CR 0Dh start start command “xxx:”+”.” end 0Dh start request status “xxx:?”+”.” end 0Dh start status “xxx:”+”.” end 0Dh SR9600 RS-232C Control Specification Page:

20、6 / 25 Document Version 1.0 Company Restricted 3-3. The transaction sequences and the regulations 3-3-1. The transaction sequences The transactions have three kinds of sequence. *A transaction is a Command from Host then Slave will be an answer by Status answer, ACK or NAK. *A transaction is a Statu

21、s request from Host then Slave will be an answer by Status answer or NAK. *A transaction is Auto status feedback from Slave when a Slaves status changed. (If the auto status feedback is enabled.) 3-3-2. The transaction regulations The transactions have some kinds of regulation. * An answer (ACK, NAK

22、 or Status answer) transmittion by Slave has to finish within 500ms when got a Command or a Status request from Host. * Host must not transmit an another Command or Status request until it receives a answer by a previous Command or Status request or it passes a term of waitinng time from a finishing

23、 of previous transmission of a Command or a Status request . * Slave has to finish a transaction under 500ms when it sends Auto status feedback data. 3-3-3. Specification of Auto status feedback There are some specific regulations about Auto status feedback. * The product status has segmented into f

24、our layers of 1, 2, 3 and 4. * The status of layer 1 are assigned most kindly status to Host. (The statuses of layer 2 are assigned kindly status, the statuses of layer 3 are not so need status to Host and the statuses of layer 4 are probably no wished statuses.) * Each layer status can control tran

25、smit enable or disable by Host command. (The product default would be all disables.) * Slave sends auto status feedback by itself when the status is changed and if the status feedback is enabled. * The product defined and segmentationed layers are takeing in status list. 3-3-4. Example of the transa

26、ctions TxD RxD RxD TxD Example of the transactions max. 0.5sec a transaction a transaction Command Status answer , ACK or NAK Status request Status answer max. 0.5sec SR9600 RS-232C Control Specification Page: 7 / 25 Document Version 1.0 Company Restricted 3-3-5. Examples of the handshaking flowchar

27、t 3-3-5-1. Example of successful handshaking S LA V EH O S T C o m m and a cce pta ble R e que st a cce pta ble C o m m and A C K S ta tus re qu est S ta tus an sw er R elate d S ta tus answ e r or A u to statu s fee db ack C h ang ed so m e statu s! The product can reply ACK instead of related stat

28、us, if the product can not send the related status immediatly. 3-3-5-2. Examples of handshaking error S L A V EH O S T C o m m a n d in c o rre c t R e q u e s t in c o rre c t C o m m a n d N A K S ta tu s re q u e s t N A K SR9600 RS-232C Control Specification Page: 8 / 25 Document Version 1.0 Com

29、pany Restricted 4. Recommendations of Command, Status and Layer definition - All Commands, Statuses and Layers will be defined other specific document. - MANDATORY The product MUST have Commands and the Statuses same as a remote controller buttons (IR controller) of the product. - All Commands are r

30、equired working by discreate as ON/OFF commands. (It means that do not support TOGGLE command only. ) - All Commands and Statuses are defined same chharacter size except ACK/NAK on the product. ( Recommended character length : 36 characters ) - It permits attaching 0 x0A character to a reply charact

31、ers from the product. In this case, must suppose that the object is followed altogether. - Recommend to supports numbers or values direct setting command, if it has variable numbers or values. SR9600 RS-232C Control Specification Page: 9 / 25 Document Version 1.0 Company Restricted 5. Definitions of Command, Status and Layer This section is told how to define “Command”, “Status” and “Layer” of this product. 5-1. Commands This chapter will show the commands of this product. 5-1-1. Normal Command list Command Reply from Slave TOGGLE “PWR:0” OFF “PWR:1” POWER ON “PWR:2” “PWR:1”, “PWR:2” TOGGLE