Harman Kardon SIGNATURE 2.0 (serv.man11) User Manual / Operation Manual ▷ View online
SIGNATURE
B
US
P
ROTOCOL
M
ASTER
D
OCUMENT
Revised 2-24-98
Page 6 of 20
The Command Modifier is a byte that distinguishes what type of command
is being sent.
HEX
is being sent.
HEX
Command Type
01
Action request
02
Action response
Provides additional information required by the Command byte.
The Command byte is the action that is desired.
The Data Length is a word representing the total number of bytes
(including Command Modifier and Command bytes, but not the Data
Length byte itself or the Checksum byte) in the data portion of the
message. Minimum length is 02h.
(including Command Modifier and Command bytes, but not the Data
Length byte itself or the Checksum byte) in the data portion of the
message. Minimum length is 02h.
Source
Device Type
Target
Device Type
Target
Unit ID
Source
Unit ID
Command
Modifier
Data
Length
Preamble
Byte
Command
Byte
Data
Byte(s)
Checksum
Byte
Source
Device Type
Target
Device Type
Target
Unit ID
Source
Unit ID
Command
Modifier
Data
Length
Preamble
Byte
Command
Byte
Data
Byte(s)
Checksum
Byte
Source
Device Type
Target
Device Type
Target
Unit ID
Source
Unit ID
Command
Modifier
Data
Length
Preamble
Byte
Command
Byte
Data
Byte(s)
Checksum
Byte
The Source Unit ID is a byte that distinguishes which unit of a given type
the message is coming from (i.e. CD player #1 versus CD player #2). The
Unit ID is set in the menu system of the unit that the message is coming
from, default = 01h. If you are using more than one of any given unit, you
will need to modify this byte.
the message is coming from (i.e. CD player #1 versus CD player #2). The
Unit ID is set in the menu system of the unit that the message is coming
from, default = 01h. If you are using more than one of any given unit, you
will need to modify this byte.
Source
Device Type
Target
Device Type
Target
Unit ID
Source
Unit ID
Command
Modifier
Data
Length
Preamble
Byte
Command
Byte
Data
Byte(s)
Checksum
Byte
Provides additional information required by the Command byte.
The Data bytes consist of information that is required to complete the
Command. The Data bytes are detailed throughout the rest of this
document.
Command. The Data bytes are detailed throughout the rest of this
document.
Source
Device Type
Target
Device Type
Target
Unit ID
Source
Unit ID
Command
Modifier
Data
Length
Preamble
Byte
Command
Byte
Data
Byte(s)
Checksum
Byte
Provides additional information required by the Command byte.
The Checksum is a byte whose value confirms/voids the validity of a
received message. It is computed by adding up all of the bytes Preamble
through the last Data byte, and then taking the 1s complement of the lower
eight bits of that sum (i.e. add up all the bytes, truncate to eight bits, and
invert each of the bits). If the result equals 7Eh, add 01h. See the page 7
for an example.
received message. It is computed by adding up all of the bytes Preamble
through the last Data byte, and then taking the 1s complement of the lower
eight bits of that sum (i.e. add up all the bytes, truncate to eight bits, and
invert each of the bits). If the result equals 7Eh, add 01h. See the page 7
for an example.
Source
Device Type
Target
Device Type
Target
Unit ID
Source
Unit ID
Command
Modifier
Data
Length
Preamble
Byte
Command
Byte
Data
Byte(s)
Checksum
Byte
SIGNATURE
B
US
P
ROTOCOL
M
ASTER
D
OCUMENT
Revised 2-24-98
Page 7 of 20
E
XAMPLE OF
M
ESSAGE
C
REATION
Create a Power On command from a Signature 3.0 to a Signature 2.0
in a single 2.0 / single 3.0 system.
Preamble = 7Eh
Length = 03h
Modifier = 01h
Target Device Type = 20h
0111 1110b (7Eh)
0010 0000b (20h)
0000 0001b (01h)
0011 0000b (30h)
0000 0001b (01h)
0000 0011b (03h)
0000 0001b (01h)
0000 0010b (02h)
+ 0000 0001b (01h)
0010 0000b (20h)
0000 0001b (01h)
0011 0000b (30h)
0000 0001b (01h)
0000 0011b (03h)
0000 0001b (01h)
0000 0010b (02h)
+ 0000 0001b (01h)
0 1101 0111b (sum = 0D7h)
1101 0111b (truncating = D7h)
0010 1000b (inverting bits = 28h)
0010 1000b (28h
≠
7Eh, so don’t add 01h)
Checksum = 28h
Command = 02h
Target Unit ID = 01h
Source Device Type = 30h
Source Unit ID = 01h
Data = 01h
Source
Device Type
Target
Device Type
Target
Unit ID
Source
Unit ID
Command
Modifier
Data
Length
Preamble
Byte
Command
Byte
Data
Byte(s)
Checksum
Byte
30h
20h
01h
01h
01h
03h
7Eh
02h
01h
28h
SIGNATURE
B
US
P
ROTOCOL
M
ASTER
D
OCUMENT
Revised 2-24-98
Page 8 of 20
A
CKNOWLEDGMENT
C
OMMAND
:
A
CKNOWLEDGE
:
Source
Device Type
Target
Device Type
Target
Unit ID
Source
Unit ID
Command
Modifier
Data
Length
Preamble
Byte
Command
Byte
Data
Byte(s)
Checksum
Byte
30h
20h
01h
01h
01h
Computed
7Eh
Command
Data
See page 7
Source
Device Type
Target
Device Type
Target
Unit ID
Source
Unit ID
Command
Modifier
Data
Length
Preamble
Byte
Command
Byte
Data
Byte(s)
Checksum
Byte
20h
30h
01h
01h
02h
02h
7Eh
See Below
None
See page 7
The acknowledge Command Byte is formed by adding 80h to the received Command Byte.
Example:
HEX
HEX
COMMAND DESCRIPTION
05
Command to Mute
85
Acknowledge
The receiving unit transmits the “Acknowledge” response to let the sending unit know that
the message has been successfully received.
the message has been successfully received.
The Data Byte(s) are not included in the Acknowledge message.
An Acknowledge is required after EVERY message sent, in either direction.
SIGNATURE
B
US
P
ROTOCOL
M
ASTER
D
OCUMENT
Revised 2-24-98
Page 9 of 20
E
XAMPLE OF
M
ESSAGE
E
XCHANGE
C
OMMAND
:
A
CKNOWLEDGE
:
R
ESPONSE
:
A
CKNOWLEDGE
:
The Signature 3.0 starts by sending a Request for Software
Version command to the Signature 2.0
in a single 3.0 / single 2.0 system.
Source
Device Type
Target
Device Type
Target
Unit ID
Source
Unit ID
Command
Modifier
Data
Length
Preamble
Byte
Command
Byte
Data
Byte(s)
Checksum
Byte
30h
20h
01h
01h
01h
02h
7Eh
77h
None
35h
Source
Device Type
Target
Device Type
Target
Unit ID
Source
Unit ID
Command
Modifier
Data
Length
Preamble
Byte
Command
Byte
Data
Byte(s)
Checksum
Byte
20h
30h
01h
01h
01h
02h
7Eh
F7h
None
35h
The Signature 2.0 acknowledges by sending an Acknowledge of
Request for Software Version command to the Signature 3.0
in a single 3.0 / single 2.0 system.
Source
Device Type
Target
Device Type
Target
Unit ID
Source
Unit ID
Command
Modifier
Data
Length
Preamble
Byte
Command
Byte
Data
Byte(s)
Checksum
Byte
20h
30h
01h
01h
02h
04h
7Eh
77h
0205h
2Dh
The Signature 2.0 then sends a Response to Request for
Software Version command to the Signature 3.0 with data of rev. 2.5
in a single 3.0 / single 2.0 system.
Source
Device Type
Target
Device Type
Target
Unit ID
Source
Unit ID
Command
Modifier
Data
Length
Preamble
Byte
Command
Byte
Data
Byte(s)
Checksum
Byte
30h
20h
01h
01h
02h
02h
7Eh
F7h
None
34h
The Signature 3.0 then acknowledges by sending an Acknowledge of
Response to Request for Software Version command to the Signature 2.0
in a single 3.0 / single 2.0 system.
Click on the first or last page to see other SIGNATURE 2.0 (serv.man11) service manuals if exist.