T and A Elektroakustik SR-1535 Owners manual

TT Technical Information 7.09.2005

RS232 adapter

R-Link command

R-Link flag

RS232 control of SR1535.

The surround receiver SR1535R with software version 1.13 or higher is compatible to be controlled by
a connected control-system having a RS232 serial output port (PC, CRESTRON home automation
system etc.) through the RS232/R-Link interface adapter. With versions from 1.40 or higher there is
the additional possibility to receive status information from the SR1535R.

For details about connecting and operating the adapter see the user manual of the adapter
“UM_RS232_Adapt.doc”.

Settings for the RS232 interface of the control device are as follows:

Baud rate: 115.200
Data bits: 8
Stop bits: 1
Parity: none
Flow Control: none

T+A RS_232 Protocol

The R-series devices use the standard T+A RS232 command protocol as described in detail in the
documents “TA_RS232_protocol.doc” and “RS_232_Command_Codes.doc”.

Format of the command telegrams

A command telegram to the R-system master device consists of 6 bytes. The complete telegram
should be sent without pauses between the bytes.

Example: SYSTEM_ON command

Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6

Telegram length

Address

(always 0x01)

0x01 0x03 0xC8 0x57 0x02 0x25

Byte 1, 2, 3, 5 : these bytes have the fixed values as shown in the table above for all R-system

Byte 4 : R-Link command according to the table of RCII commands

(R-Link address + R-Link

command + R-Link flag

byte = 0x03)

master devices

(see “RS_232_Command_Codes.doc”)

R-Link

Address

(0xC8=Amplifier/

master device

à see also note

below)

(here: SystemON = 0x57)

à see command table

“appendix 1”

byte

(always 0x02)

Check sum

= sum of bytes 1..5

mod. 0xFF

Byte 6 : check sum == (byte1+byte2+byte3+byte4+byte5) modulo 0xFF

Note:

The R-Link address 0xC8 is used for all standard amplifier commands.
There exist a few additional commands (system commands) for some special functions. For these

commands the address 0xC4 has to be used. At this time there are non of these relevant for surround
control.

Format of the acknowledge (ACK) telegrams

milli-seconds after sending a command, there is either a

The R-System master device will process each received command telegram and it will send an
acknowledge telegram approx. 25...35 ms after receiving the command.

The ACK telegram consists of 2 bytes:
Byte 1 is the RS232 address of the command telegram received before (=byte 1 of the command
telegram = 0x01).
Byte 2 is the acknowledge byte. If this byte is equal to the check sum of the command telegram
(byte_6 of the command) then the command was received correctly. If byte_2 has a value different
from the check sum of the command, an error has occurred (see table below).

Format of the ACK telegram:

Byte 1 Byte 2
RS232 address ACK byte

0x01

After the ACK telegram, the master device is ready for the next command.

= check sum of command: command correctly received
= check sum –1: command ignored (system busy)
= check sum –2: command not executed

Note:
If no ACK telegram is received within 35

hardware problem (cable etc.) or the telegram is erroneous (wrong address, wrong check sum ....)

Special System Commands

Beginning with version 1.40 the SR1535R automatically pushes the status information after it has changed.
Additionally the status can be requested by sending the command 0x64 (Status_1) or 0x43 (Status_2) to the

RLink-address 0xC4 but normally this should not be necessary. We strongly recommend to keep the

number of status requests low to avoid unnecessary RLink-Bus load. The information given is different for each
device and has to be decoded and displayed individually. For further information see the user manual ‘Crestron
T+A Macro’.

Responses of the SR1535R are as follows:

Status 1:

The STATUS_1 is automatically pushed by the SR1535R when any contained information has changed or the
command STATUS_1 was sent to the SR1535R. It is answered by a 9 byte long status telegram having the
following format:

0x01, 0x05, 0xC4, 0x64, Stat_Byte_1, Stat_Byte_2, Stat_Byte_3, Stat_Byte_4, Checksum

-----------------------------------|---------------------------------------------------------------------------|----------------­HEADER (4) STATUS BYTES (4) CHK-SUM (1)

The 4 header bytes (0x01/0x05/0xC4/0x64) are constant.
The 4 status bytes are defined as follows:

Stat_Byte_1

Stat_Byte_2

Stat_Byte_3

b0 Protection 1:= Amplifier is in protection mode

(overload / overheat)
b1 Speaker_A 1:= speaker A output is ON
b2 Speaker_B 1:= speaker B output is ON
b3 Speaker_C 1:= speaker C output is ON
b4 Speaker_D 1:= speaker D output is ON
b5
b6 STANDBY 1:= System is in STANDBY
b7 ON 1:= System is ON

b0

Listen Source
(0...15)

b1
b2
b3
b4

Recording Source
(0...15)

b5
b6
b7

0:= not defined

1:= CD

2:= TUNER

3:= TAPE 1

4:= TAPE 2

5:= TV/Video

6:= AUX 1

7:= AUX 2

8:= AUX 3
9:= DVD
10:= STB
11:= VCR
12:= AUX/AV 1
13:= AUX/AV 2
14:= DBR (Digital Radio)
15:= not def. / future use

b0 LOUDness 1:= Loudness is ON
b1 FLAT 1:= FLAT is ON (= Tone defeat)
b2 DirectStereo 1:= High Quality stereo mode
b3
b4

SurroundMode (0...15) 0:= Surnd (5.1)
b5
b6
b7

1:= Stereo
2:= Mono
3:= Mono I
4:= Mono II

5:= Disco
6:= Hall
7:= Opera
8:= Arena
9:= Club

10:= Church
11:= MCH-Input
15:= Surnd EX/ES
(7.1)

Stat_Byte_4

b0

SourceFormat (0...4) 0:= analog
b1
b2
b3
b4

DecodingMode (0...10) 0:= None

b5

b6

b7

4:=AAC
1:= PCM
2:= Dolby Digital
3:= DTS

1:= Dolby Pro Logic II Movie Mode
2:= Dolby Pro Logic II Music Mode
3:= Dolby Pro Logic II Matrix Mode
4:= Dolby Pro Logic IIx Movie Mode
5:= Dolby Pro Logic IIx Music Mode
6:= Dolby Pro Logic IIx Matrix Mode
7:= Dolby Pro Logic IIx EX compatible Mode
8:= DTS Neo:6 Cinema Mode
9:= DTS Neo:6 Music Mode
10:= DTS ES