Tascam Bd-mp4k Control I-o Terminals Instructions

TASCAM BD-MP4K Control I-O Terminals

CAUTION
TEAC Corporation (hereafter, “TEAC”) permits the use of the protocol described in this specification document with the prerequisite that the customer consents to the following protocol use agreement conditions.
If you do not consent to the following conditions in the protocol use agreement, you may not use this protocol and should return this document to TEAC. Moreover, be aware that violations of any of the following items in the protocol use agreement is an infringement on the rights of TEAC and could result in the termination of further use and be subject to restitution claims, for example.

Protocol use agreement

1. This agreement comes into effect from the time the customer starts use of this protocol.
2. TEAC grants a nonexclusive and nontransferable “usage” right to the customer in order to develop devices (including software) that are compatible with the covered TASCAM products.
3. The acquisition of this document by the customer does not mean that the customer has acquired any rights, titles or interests in this protocol other than what is specified in this use agreement. The customer should recognize that as a written work belonging to TEAC, this document is protected based on the copyright laws of the signatory nations of the Universal Copyright Convention and the Berne Convention for the Protection of Literary and Artistic Works. Without exception, the intellectual property in this protocol belongs to TEAC or a source that provides it to TEAC.
   1. The customer may not make copies of this specifications document.
   2. The customer may not transfer this specifications document to a third party without obtaining prior permission from TEAC.
   3. Since confidential information that belongs to TEAC is contained in this specifications document, the customer may not disclose it to a third party without obtaining prior permission from TEAC.
4. This specifications document and this protocol are provided as is. TEAC does not provide any guarantee whatsoever that the contents of this specifications document and the protocol are suitable for the specific purpose of the customer or that they are free of error.
5. TEAC cannot respond to customer inquiries about the contents of this specifications document.
6. TEAC will bear no responsibility for any damages (including business losses, business interruption, loss of business data or other financial damages) arising from the use or inability to use this specifications document or this protocol. This applies even if TEAC is informed about the potential for such damage in advance.

Overview

The BD-MP4K (“controlled device”) can be controlled from an external device (“external controller”), such as a computer, through a serial RS-232C and ETHERNET connection.

Specifications

1. Serial RS-232C
   1. Electrical specifications
      Standard: JIS X-5101 (equivalent to the former JIS-C-6361 and EIA RS-232C standards)
      Note that this is not compatible with the RS-422 used in professional VTRs.
      Impedance at receiver:  When measured with an applied voltage between -3 V and +3 V or between -15 V and +15 V, the DC resistance is between 3k ohms and 7k ohms.
      Total load capacitance is 2500 pF or less. Open circuit voltage at transmitter: 25V or less
      Open circuit voltage at receiver: 2V or less When the open circuit voltage at the receiver is 0 V, the signal voltage is between
      Signal voltage: -5 V and +5 V or between -15 V and +15V against a load impedance between 3k ohms and 7k ohms.
      Signal discrimination: Logic “1”: -3V or less Logic “0”: +3V or more
      
   2. Communication format  
      Circuit type Asynchronous / Full-duplex Transmission type Digital binary serial
      Data signal rate (baud rate)
      115200, 57600 or 38400 bits/sec
      During standby, 57600 bits/sec is only available.
      Data bits 8 bits
      Parity bits None
      Stop bits 1 bit
      Maximum data length 600 byte (Start character to End character is included.)
      *Data bits, Parity bits, and Stop bits are fixed.
   3. Connector pin-out
      Connecter D-sub 9pin female (Inch screw thread)Terminal pin-out and input/output signals

      Pin No.	In/Out	Signal name	Description
      1	–	GND	Ground pin
      2	Out	TxD	Data transmitted from this pin
      3	In	RxD	Data received at this pin
      4	–	NC	Not connected
      5	–	S.GND	Signal ground pin
      6	–	NC	Not connected
      7	–	+5V Power	Can use 5V/500mA power supply
      8	–	NC	Not connected
      9	–	NC	Not connected

      Note: Pin 7 is the output terminal of the 5V power supply, so be careful when wiring the cable.

2. IP Control (Ethernet)
   Transmission type Full duplex
   Transfer speed 10 / 100 / 1000 Mbps
   TCP port No. 9030
   Maximum data length 600 Bytes ( Start character to End character is included.
3. Protocol Overview
   The Serial Control Protocol consists of three command characters and parameter characters of variable length.
   C ha racters are the ASCII Code.
   1. RS 232C Protocol
      Controller –> Device Message Example
      Disc Tray (Open)Special Character
      [CR] Carriage Return ASCII Code 0x0D
      Device–> Controller Message Example
      Status = Play
   2. ETHERNET Protocol
      Protocol is TCP. (Transmission Control Protocol)
      Destination Port Number is 9030. fixed)
      Controller –> Device Message Example
      Disc Tray (Open)
      Special Character
      [CR] Carriage Return ASCII Code 0x0D
      Device –> Controller Message Example
      Status = Play
      1 Unit Type is the model category ID. The Blu ray player is “7”.
      Note: The connection between server and client should be held open continuously. If the connection is closed, the client will not be able to see Status notification messages from the server. Only one client connection at a time can be made.
4. Communication Protocol
   1. Message Structure
      There are three kinds of message, “COMMAND”, “REQUEST”, and “ANSWER /NOTIFICATION”.
   2. ACK (Acknowledge) and NACK (Not
      1.  ACK
         It is an affirmative reply sent to a controller from a device. When data transfer completes properly, a device notify of that to a controller.
      2. NACK
         It is a negative reply sent to a controller from a device. When data transfer does not complete properly, a device notify of that to a controller.

         Name	Value(HEX)	Transmission Requirement
         ACK	‘ack’ (0x61/0x63/0x6B)	The device acknowledged that the command was received normally from the controller.
         NACK	‘nack’ (0x6E/0x61/0x63/0x6B)	The device received the End Character ‘CR(0x0D)’ before receiving the Start Character ‘!(0x21)’. The device does not receive ID’7(0x37)’just after Start Character’!(0x21)’. The device receives an unknown character just after ’!7’. The device receives an unknown command just after ’!7’. Parameter is out of range. The size of data is abnormal. 5msec passed before the device receives the next code necessary to complete the command.

   3. Communication Rules
      
      1. Initiative of Communication
         In the communication between a controller and a device, the controller must have the initiative. However, the Status Information notification automatically from the device is an exception.
         When the device receives a command from the host, the device returns the following.
         • When receiving the command which doesn’t require a status information ACK (‘ack’)
         • When receiving the command which require a status information
           ACK (‘ack’)＋(‘+’) Status information (ANSWER)
         • For the communication failure or an unknown commands etc. NACK (‘nack’)
      2. Communication Sequence
         The host must not send any new command after the previous command before the host receives ACK or NACK, or the timeout (see ”4.3.3. Timeout”) has expired.
      3. Timeout
         After a controller sends a message to a device, the host waits for a reply from the device for 30 ms (IP Control) / 300 ms (RS-232C). When the controller does not receive a reply over 30 ms (IP Control) / 300ms (RS-232C) from the device, the controller sends the same message to the device. However, when the controller does not receive a reply from the device after sending the same message 3 times (that means Tim Out), the controller sends End character ‘CR’ (0x0D) to the device. After that, the controller should execute the recovery process such as retry.
      4. ACK
         Refer to “4.2.1. ACK”.
      5. NACK
         The device returns a NACK immediately after detecting a failure in the communication with the controller (see ”4.2.2. NACK”). If the host receives a NACK, it must stop sending the current remaining command immediately and execute the recovery process such as retry.
      6. Command Interval time
         • Interval time between Characters from a controller must be less than 5ms. The device sends NACK when 5msec passed before the device receives the next character code.
         •  Interval time between Commands is more than 30 ms.
           In case of less than 30 ms as interval time between commands,
           1. Executing the subsequent command is not guaranteed.
           2. When there are buffer spaces of a device for a command, the device will execute the command.
           3. When there is no buffer space of a device for a command, the device does not execute the command, and will send Busy (@0BDERBUSY) to the host instead.
   4. Basic Control Flow
      1. Device Control Flow
         The device sends the controller an ACK (Acknowledgement) and executes that command when the device receives a Control command from the controller. The list of the Control command is shown in “ 5. Command TableIf the device receives an unknown command or an End Character ‘CR’ (0x0D) without a Start Character ‘!’, it causes transmission failure and the device returns a NACK. Refer to ” 4.2.2. NACK ” about NACK transmission condition.
      2. Status Request Flow
         The device returns an ACK and the ANSWER requested by the controller when the device receives the Status Request from the controller. The list of the Status Request and the corresponding answer is shown in 5.3. Current Status RequestWhen a device receives Status Request from a controller, the device sends an ACK to the controller. After that, the device gets the current status, and then sends it to the controller. If the device receives an unknown command or an End Character ‘CR ’ (0x0D) without a Start Character ‘!’, it causes transmission failure and the device returns a NACK. Refer to 4.2.2. NACK ” about NACK transmission condition.
      3. Status Notification Flow
         A device notifies of Status Information listed in “ 5.3. Current Status Request ” whenever the status of the device is changed, such as the transport status, the current track, the storage media status, and other status.A device sends Status Notification to a controller. The controller replies ACK to the device. The device waits for the ACK for Max 30ms. When the device does not receive the ACK from the host, the device sends the same Status Notification to the host again. After that, the device does not send the same Status Notification even if it does not receive an ACK from the host.
         The Status Information is same as the answer for the Status Request listed in “5.3. Current Status Request”.
5. Command Table
   NOTE Italic characters of command mean parameter. (Ex: Hide MENU “!7OSDXX” -> Parameter: XX) “Track” means “Chapter” (during the DVD or BD playback) and “File” (USB and other playback). “Group” means “Title” (DVD or BD playback) and “Track” (Audio CD playback
   1. Key Control

Menu Setting 

Current Status Request

Note-1
The acceptable character set is ISO/IEC8859-1.

Revisions
Ver. 1.00 Initial issue
Ver. 1.01 3. Protocol Overview: “CR” is deleted in the case of “Device -> Controller Message Example”