Harman Kardon SIG2.0 Owners Manual - Page 9

Example Of Message Exchange

Get Harman Kardon SIG2.0 PDF manuals and user guides View all Harman Kardon SIG2.0 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 9 highlights

SIGNATURE BUS PROTOCOL MASTER DOCUMENT Revised 2-24-98 EXAMPLE OF MESSAGE EXCHANGE The Signature 3.0 starts by sending a Request for Software Version command to the Signature 2.0 COMMAND: Preamble Target Byte Device Type Target Unit ID in a single 3.0 / single 2.0 system. Source Device Type Source Unit ID Data Length Command Modifier Command Byte 7Eh 20h 01h 30h 01h 02h 01h 77h Data Byte(s) None Checksum Byte 35h The Signature 2.0 acknowledges by sending an Acknowledge of Request for Software Version command to the Signature 3.0 ACKNOWLEDGE: Preamble Target Byte Device Type Target Unit ID in a single 3.0 / single 2.0 system. Source Device Type Source Unit ID Data Length Command Modifier Command Byte 7Eh 30h 01h 20h 01h 02h 01h F7h Data Byte(s) None Checksum Byte 35h 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 RESPONSE: in a single 3.0 / single 2.0 system. Preamble Target Byte Device Type Target Unit ID Source Device Type Source Unit ID Data Length Command Modifier Command Byte 7Eh 30h 01h 20h 01h 04h 02h 77h Data Byte(s) 0205h Checksum Byte 2Dh The Signature 3.0 then acknowledges by sending an Acknowledge of Response to Request for Software Version command to the Signature 2.0 ACKNOWLEDGE: in a single 3.0 / single 2.0 system. Preamble Target Byte Device Type Target Unit ID Source Device Type Source Unit ID Data Length Command Modifier Command Byte Data Byte(s) 7Eh 20h 01h 30h 01h 02h 02h F7h None Checksum Byte 34h Page 9 of 20

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
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
30
h
20
h
01
h
01
h
01
h
02
h
7E
h
77
h
None
35
h
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
20
h
30
h
01
h
01
h
01
h
02
h
7E
h
F7
h
None
35
h
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
20
h
30
h
01
h
01
h
02
h
04
h
7E
h
77
h
0205
h
2D
h
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
30
h
20
h
01
h
01
h
02
h
02
h
7E
h
F7
h
None
34
h
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.