Owner's Manual

4
AMX Duet™ Support
e AV shall be fully compatible with AMX Duet™ Dynamic Device Discovery Protocol (DDDP) e following description of Dynamic Device
Discovery comes from the AMX website (www.amx.com). Dynamic Device Discovery is part of AMX’s Duet™ platform, which combines the proven
reliability and power of NetLinx with the extensive capabilities of the Java 2 Micro Edition (J2ME) platform. When integrating a serial or IP device
from a manufacturer embedding the Dynamic Device Discovery Protocol (DDDP), Duet recognizes the device and loads the appropriate Duet
module, which automatically installs the new device. AMX’s NetLinx Master can then nd and install the Duet device module either from a library
on the master, from AMX’s Web site, or from the manufacturer’s Web site. Duet also allows for device swapping so that programming changes are
not required when devices with DDDP are removed or replaced – a huge benet for end users. e Duet platform is an extension AMX’s InConcert®
manufacturer partner program, which was developed to ensure seamless communication between partners’ devices and the AMX control system.
Data is specied in the ASCII format. All ASCII characters between the quotes “” should be recognised/transmitted. “\r” is a carriage return (0x0D)
Command: “AMX\r”
AV40 Response:
“AMXB<Device-SDKClass=Receiver><Device-Make=ARCAM><Device-Model=AV40><Device-Revision=x.y.z>\r”
AVR30 Response:
“AMXB<Device-SDKClass=Receiver><Device-Make=ARCAM><Device-Model=AVR30><Device-Revision=x.y.z>\r”
AVR20 Response:
“AMXB<Device-SDKClass=Receiver><Device-Make=ARCAM><Device-Model=AVR20><Device-Revision=x.y.z>\r”
AVR10 Response:
“AMXB<Device-SDKClass=Receiver><Device-Make=ARCAM><Device-Model=AVR10><Device-Revision=x.y.z>\r”
Where
x.y.z = RS232 protocol version number.
Control 4 SDDP Support
e AV shall be fully compatible with the Control 4 SDDP discovery protocol.
Crestron Connected Support
e AV shall be fully compatible with the Crestron Connected discovery protocol.
Zone numbers
e following zone numbers are dened:
 0x01 – Zone number 1. (Zone 1 is the master zone. Commands that appear zone-less refer to the master zone)
 0x02 – Zone number 2.
Answer codes
e following answer codes are dened:
 0x00 – Status update.
 0x82 – Zone Invalid.
 0x83 – Command not recognised.
 0x84 – Parameter not recognised.
 0x85 – Command invalid at this time.¹
 0x86 – Invalid data length.
¹Certain commands cannot be processed when the Setup Menu is being displayed. An answer code of 0x85 will be returned in these circumstances. Also,
commands for tuner control cannot be processed when the tuner input is not selected, etc.
State changes as a result of other inputs
It is possible that the state of the AV may be changed as a result of user input via the front panel buttons or via the IR remote control. Any change
resulting from these inputs is relayed to the RC using the appropriate message type.
For example, if the user changed the front panel display brightness using the DISPLAY button on the front panel, a display message (dened below)
would be sent to the RC. A similar action would be taken for all other state changes (including decode mode changes).
Reserved Commands
Commands 0xF0 to 0xFF (inclusive) are reserved for test functions and should never be used.
Example command and response sequence
As an example, the command to simulate the RC5 command “16-16”, volume up:
STR ZONE CC DL Data 1 Data 2 ETR
0x21 0x01 0x08 0x02 0x10 0x10 0x0D
Assuming that the command was accepted by the AV Receiver and is being processed, the AV responds to this command with the following sequence:
STR ZONE CC AC DL Data 1 Data 2 ETR
0x21 0x01 0x08 0x00 0x02 0x10 0x10 0x0D