Lexicon DC-2 User manual

Lexicon, Inc.
DC-2/MC-1 Serial Communications Protocol Printed on: 10/19/00
1 of 44
Serial Communications Protocol Definition
Project: DC-2/MC-1
Updated: May 15,2000
Major rev 0
Minor rev 5
Lexicon, Inc.
3 Oak Park
Bedford, MA 01730-1441
[phone]

Lexicon, Inc.
DC-2/MC-1 Serial Communications Protocol Printed on: 10/19/00
2 of 44
1Documents 4
2 Definitions 4
3 Abbreviations 4
4 General Description 4
5 Physical Layer 5
5.1 DB-9 RS232 Connector 5
5.2 Serial Port Driver 5
5.3 Errors 6
5.4 DC-2/MC-1 Receive Buffer 6
5.5 DC-2/MC-1 Hardware Verification 6
6 Data Link Layer 6
6.1 Errors 7
7 Application Layer 7
7.1 DC-2/MC-1 Asynchronous Notification Packets 7
7.1.1 Wakeup Notification 7
7.1.2 Sleep Notification 8
7.1.3 Front Panel Display Buffer 8
7.1.4 Parameter Change Notification 9
7.2 Acknowledgment Packets 10
7.2.1 Acknowledge 10
7.2.2 No Acknowledge 10
7.3 Host Initiated Command Packets 11
7.3.1 Reset Unit 11
7.3.2 Restore Defaults 11
7.3.3 Send IR Command 11
7.3.4 Get DC-2/MC-1 Unit Configuration 12
7.3.5 Get System Status 14
7.3.6 Get Record/Zone 2 Status 15
7.3.7 Get System Parameter Definition 16
7.3.8 Get System Parameter Values 18
7.3.9 Get Effect Definition by Id 18
7.3.10 Get Effect Parameter Definition 19
7.3.11 Get Effect Parameter Values 20
7.3.12 Get Custom Name 21
7.3.13 Get Input Name by Id 21
7.3.14 Get FPD Control Registers 22
7.3.15 Set System Parameter Values 23
7.3.16 Set Effect Parameter Values 23
7.3.17 Set Effect Name by Effect Id 24
7.3.18 Set System Volume 25
7.3.19 Set Main Balance 25
7.3.20 Set Front/Back Balance 26
7.3.21 Set Active Effect by Id 26
7.3.22 Set Record/Zone2 Input 27
7.3.23 Clear Record/Zone2 Input 27
7.3.24 Set Zone2 Volume 28
7.3.25 Set Zone2 Left/Right Balance 28

Lexicon, Inc.
DC-2/MC-1 Serial Communications Protocol Printed on: 10/19/00
3 of 44
7.3.26 Set Custom Name 28
7.3.27 Set Input Name by Id 29
7.3.28 Set FPD Control Registers 30
7.3.29 Host Wakeup 30
7.3.30 Host Sleep 31
7.3.31 Get Communication Configuration 31
7.3.32 Set Communication Configuration 32
7.3.33 Set Mute 32
7.3.34 Set Output Level Adjustments 33
7.3.35 Send Display String Command 34
8 Internal Use 35
8.1.1 Debug Character 35
8.1.2 PEEK Command 35
8.1.3 POKE Command 35
9 Appendix A Command Codes 35
10 Appendix B Error Codes 37
11 Appendix C DC-2/MC-1 IR-Codes 38
12 Appendix D Input Id’s 39
13 Appendix E Protocol Constants 39
14 Appendix F FPD Control Registers 40
15 Application Notes and Examples 40
15.1 Box initializations: 40
15.1.1 DC-2/MC-1: 40
15.1.2 HOST: 40
15.2 Getting System Wide Status and Setup: 41
15.3 Downloading the System Setup to the DC-2/MC-1: 41
15.4 Simple System Control & System Status: 41
15.5 Examples: 42
15.5.1 Get Unit Configuration 42
15.5.2 Get Effect Definition 43
15.5.3 Set Input Name 43
15.5.4 Send IR Command Example 44

Lexicon, Inc.
DC-2/MC-1 Serial Communications Protocol Printed on: 10/19/00
4 of 44
1 Documents
The following documents should also be used with this document to understand how this protocol can be
used with a DC-2/MC-1.
070-13227 MANUAL,OWNER'S,DC2
070-13278 MANUAL,OWNER'S,MC1
2 Definitions
System Parameter: A user changeable variable that stores a specific value that describes an operating
condition for the DC-2/MC-1 system.
Effect: An effect describes a particular type of processing on the audio data stream.
Effect Parameter: A changeable variable that stores a specific state or condition that controls the way the
effect functions or processes the audio.
HOST: The device initiating or receiving the serial communication packets to/from the DC-
2/MC-1.
DC-2/MC-1: The Lexicon product receiving or transmitting the serial communication packets
to/from the HOST.
Nonvolatile RAM: The area of memory in a DC-2/MC-1 that stores users adjustable parameters. The
Nonvolatile RAM is battery backed, to maintain values during DC-2/MC-1 power
down.
3 Abbreviations
SOP Start of Packet
EOP End of Packet
ACK Acknowledge
NAK No Acknowledge
FPD Front Panel Display
4 General Description
The intention of the DC-2/MC-1 serial port and protocol communication is for an external connected HOST
to control and obtain status from the DC-2/MC-1. The protocol has been designed to focus on two specific
goals. The first, is HOST uploading and downloading of DC-2/MC-1 configuration, and system/effect
setups. The second, is HOST control of basic user adjustable parameters.(i.e. input, volume, balance…)
CD VOL
Lexicon MC-1
HOST Rs-232 Serial Link

Lexicon, Inc.
DC-2/MC-1 Serial Communications Protocol Printed on: 10/19/00
5 of 44
The DC-2/MC-1 uses simple notification, command, response and acknowledgment packets to have
communication transactions with a given HOST. This protocol is designed for point to point
communication between a HOST and DC-2/MC-1. The DC-2/MC-1 Protocol is a 3 layered system. The
DC-2/MC-1 serial protocol allows for the DC-2/MC-1, or the HOST to initiate a communication
transaction. Most transactions are initiated by the HOST. DC-2/MC-1 then responds to the HOST
command with either a response or acknowledgment packet. There are a few asynchronous notifications
that DC-2/MC-1 initiates indicating system changes. Each transaction initiated must wait for a
corresponding response before initiating the next transmission.
The 3 protocol layers are: Physical, Data Link, and Application Layers.
5 Physical Layer
5.1 DB-9 RS232 Connector
Dc-2/MC-1 Typical Host
Ch A Transmit Data 2 2 Rx Data
Ch A Receive Data 3 3 Tx Data
Ch A Ground 5 5 Ground
9 Pin D-Shell
(female) lower
connector
9-Pin D-Shell
(male)
Note: The wiring requirements for a 9 pin to 9 pin serial connection, are a male to female straight through
cable.
5.2 Serial Port Driver
DC-2/MC-1 serial port has been setup to operate as follows:
Operating Mode: Full Duplex
Baud rate: 19.2K baud
Data Size: 8 bits
Parity: Odd
Stop Bits: 1
Physical Layer (RS232)
Data Link Layer
Application Layer

Lexicon, Inc.
DC-2/MC-1 Serial Communications Protocol Printed on: 10/19/00
6 of 44
5.3 Errors
The DC-2/MC-1 will detect parity, framing and data overrun errors. If an error is detected by the DC-
2/MC-1, the DC-2/MC-1 will transmit an NAK packet with a error code of: DC_ERR_PARTIY,
DC_ERR_FRAME, DC_ERR_OVER, corresponding to the error detected. If any of the physical layer
errors are detected, the complete packet is corrupted and the DC-2/MC-1 will reset the transaction and
begin to look for a start of packet byte.
All Error codes are listed in Appendix B Error Codes.
5.4 DC-2/MC-1 Receive Buffer
The DC-2/MC-1 has an internal receive buffer. The buffer is 256 Bytes and will transmit a NAK packet
with an error code of DC_ERR_BUFFER_FULL to the HOST if the buffer is full. If the buffer is full, all
data transmitted to the DC-2/MC-1 will be ignored. Therefore, making the currently transmitted packet, if
partially transmitted invalid.
5.5 DC-2/MC-1 Hardware Verification
This test verifies the RS232 ports are working by comparing the transmitted signal (at pin 2) to the received
signal (at pin 3) . The DC-2/MC-1 transmits a know test signal just following a power up. The DC-2/MC-1
monitors the serial port receivers while transmitting the test signal. If the signals are the same, the test
passes. In order to test this circuit, (1 for Dc-2 and 2 for MC-1) RS232 Wraparound plug(s) are needed and
must be installed at the female D9 connector(s) on the rear panel of the DC-2/MC-1/SDP-3 labeled
“RS232”. The wraparound plug shorts pins 2 to 3, allowing for the MC-1 to receive the signal it is
transmitting. Once installed, power cycle the DC-2/MC-1/SDP-3 and verify the following message is
displayed on the VFD about 20 seconds after power up:
SERIAL PORT A PASSED
SERIAL PORT B PASSED
This message is displayed for about 2 seconds before entering normal operating mode. If either or both
messages are not displayed, the test failed.
6 Data Link Layer
The data link layer is used to define a transmission packet. The layer appends a header and tail that
encloses the transmitted application packet data. The data link header will contain the start of packet byte
and count of bytes to follow. The data link tail will contain the end of packet byte.

Lexicon, Inc.
DC-2/MC-1 Serial Communications Protocol Printed on: 10/19/00
7 of 44
Data Link Header:
Byte Number Description Value
First Byte(0) Start of Packet(SOP) 0xF1
Byte(1) DLL Data Count nn
Application Header:
Byte(2) Command nn
Byte(3) APP Data Count(number of application data bytes to Follow) nn
Application Data:
Byte(4) Data[0] nn
Byte(5) Data[1] nn
… Data[…] nn
Last Data Byte -1 Data[Data Count -1] nn
Data Link Tail:
Last Byte End of Packet (EOP) 0xF2
6.1 Errors
If the number of DLL data bytes received is the same as the data count and an EOP has not been received,
the DC-2/MC-1 responds by transmitting a NAK packet with an error code
DC_ERR_INVALID_PACKET. The DC-2/MC-1 then continues to look for a SOP byte and will not
process the erroneous application packet. The HOST can use this as an indicator to retransmit the corrupted
packet.
7 Application Layer
7.1 DC-2/MC-1 Asynchronous Notification Packets
DC-2/MC-1 has been designed to transmit the asynchronous notification packets following these system
changes:1. Power On
2. Entering Standby
3. Front Panel Display update and
4. Parameter Value Changes.
The notification packets are defined as follows:
7.1.1 Wakeup Notification
By transmitting the Wakeup Notification, DC-2/MC-1 indicates the unit has just “powered on” or reset and
is ready to receive host commands. If no acknowledgment is received within ACK_TIMEOUT, DC-2/MC-
1 will continue to operate. This notification is primarily for the HOST to know the status of the DC-2/MC-
1.
7.1.1.1 Notification Packet Description
Application Header:
Command DC_WAKEUP 0x01
Data Count 0 0x00
Application Data:
N/A

Lexicon, Inc.
DC-2/MC-1 Serial Communications Protocol Printed on: 10/19/00
8 of 44
7.1.1.2 Host Response Expected
Following the transmission of the Wakeup notification DC-2/MC-1 will wait for an ACK.
7.1.1.2.1 Actions to Response Codes
ACK DC-2/MC-1 continues to operate.
NAK Error Code DC-2/MC-1 will retransmit the Wakeup Notification until it receives an ACK
or it reaches the RETRANSMIT_COUNT. If the RETRANSMIT_COUNT
is exceeded then DC-2/MC-1 continues to operate.
7.1.2 Sleep Notification
By transmitting the Sleep Notification, DC-2/MC-1 indicates the unit is shutting down into a standby mode.
Because the hard power switch could be activated independently of the DC-2/MC-1 system software, hard
power down will not be notified. Acknowledgment of the Sleep Notification is not required. This
notification is primarily for the HOST to know the operating status of the DC-2/MC-1.
7.1.2.1 Notification Packet Description
Application Header:
Command DC_SLEEP 0x02
Data Count 0 0x00
Application Data:
N/A
7.1.3 Front Panel Display Buffer
DC-2/MC-1 will transmit the front panel display buffer following the update to the DC-2/MC-1 front panel
display. The DC-2/MC-1 front panel display is 2 X 20 ASCII character display. The HOST can control the
operation of this notification message by FPD internal control registers. Individual notifications can be
enabled or disabled and the minimum transmit interval can be adjusted. Transmission of the display buffer
is asynchronous to other host/DC-2/MC-1 communication and will only transmit following the completion
of any communication exchanges in progress or pending. The FPD control register command packets are
described in section 7.3.14 Get FPD Control Registers.
7.1.3.1 Notification Packet Description
Application Header:
Command DC_FPD 0x03
Data Count 42 0x2A
Application Data:
Data[0] - Data[21] Line1 ch ch ch… 0x00
Data[22] - Data[42] Line2 ch ch ch … 0x00
7.1.3.2 Data Description
Line1 Data Type: Null(0x00) terminated ASCII character string.
Max Length: DISP_LINE_LENGTH defined in Appendix E Protocol Constants.
Line2 Data Type: Null(0x00) terminated ASCII character string.
Max Length: DISP_LINE_LENGTH defined in Appendix E Protocol Constants.

Lexicon, Inc.
DC-2/MC-1 Serial Communications Protocol Printed on: 10/19/00
9 of 44
The DC-2/MC-1 includes 8 custom characters that are defined to display increments of a display block.
(i.e. Volume Bar) The custom characters are ASCII character codes 08 - 0F(hex). The codes are used as
follows:
'08' - left 1 bar
'09' - left 2 bars
'0A' - left 3 bars
'0B' - left 4 bars
'0C' - Full Cell
'0D' - Underscore
'0E' - right 3 bars
'0F' - not in use
7.1.3.3 HOST Response
The DC-2/MC-1 does not look for any response from the HOST.
7.1.4 Parameter Change Notification
DC-2/MC-1 will transmit predetermined parameter change notifications. If a parameter value is changed
due to any user action or system action the DC-2/MC-1 will transmit the current value of the parameter that
is changing.
7.1.4.1 Notification Packet Description
Application Header:
Command DC_PARAM_CHG_MSG 0x04
Data Count 2 0x02
Application Data:
Data[0] ParamId nn
Data[1] Value nn
7.1.4.2 Data Description
ParamId:DataType: Unsigned 8 bit integer
Max: Set by the System Parameter Count in the “Unit Configuration Packet”.
Value: The Current Value for this system parameter.
Data Type: Unsigned 8 bit integer
Max: Set by the Max Value per the System Parameter Definition response
Packet for the Parameter Id of this packet.
7.1.4.3 HOST Response
The DC-2/MC-1 does not look for any response from the HOST.
7.1.4.4 Supported System Parameters
The following parameters will be supported by this Parameter Change Notification:
Parameter DC-2/MC-1 Parameter Name
Current Effect PROGRAM
Mute MUTE
System Volume VOLUME
Balance LR_BALANCE
Input Selection INPUT
Record/Zone 2 On/Off RECORD_ENABLED
Zone 2 Volume Z2_VOL

Lexicon, Inc.
DC-2/MC-1 Serial Communications Protocol Printed on: 10/19/00
10 of 44
Zone 2 Balance Z2_BAL
Zone 2 Mute Z2_MUTE
Bass BASS
Treble TREBLE
Loudness LOUDNESS
Tilt TILT
Menu Background On/Off MENU_BKGND
The parameter definitions for each of these parameters can be obtained by querying the DC-2/MC-1 with
the DC_CMD_GET_SYS_PARAM_BY_NAME command. The DC_RESP_SYS_PARAM_DEF will
contain the ParamId for each of the parameters. The ParamId may change with s/w version changes, but the
Parameter Name will not.
7.2 Acknowledgment Packets
Acknowledge and No Acknowledge packets are used to communicate transmission, packet and data
validation status. Both the HOST and DC-2/MC-1 can transmit and receive these packets.
7.2.1 Acknowledge
7.2.1.1 Packet Description
Application Header:
Command DC_ACK 0xE0
Data Count 1 0x01
Application Data:
Data[0] Command nn
7.2.1.2 Data Description
Command:
DataType: Valid DC-2/MC-1 command as defined in Appendix A Command Codes.
7.2.2 No Acknowledge
7.2.2.1 Packet Description
Application Header:
Command DC_NACK 0xE1
Data Count 2 0x02
Application Data:
Data[0] Command nn
Data[1] ErrorCode nn
7.2.2.2 Data Description
Command:
DataType: Valid DC-2/MC-1 command as defined in Appendix A Command Codes.
ErrorCode:
DataType: Error code as defined in Appendix B Error Codes.

Lexicon, Inc.
DC-2/MC-1 Serial Communications Protocol Printed on: 10/19/00
11 of 44
7.3 Host Initiated Command Packets
The DC-2/MC-1 serial communication protocol has been designed to respond to the following commands
as described below. Each command is transmitted to the DC-2/MC-1 with the identified parameters. If the
command is successfully received and processed by the DC-2/MC-1, the unit will respond with the
described response packet or action.
7.3.1 Reset Unit
Commands the DC-2/MC-1 to soft reset.
7.3.1.1 Command Packet Description
Application Header:
Command DC_CMD_RESET 0x10
Data Count 0 0x00
Application Data: N/A
7.3.1.2 DC-2/MC-1 Response
The DC-2/MC-1 will perform and internal reset. After reset the DC-2/MC-1 will go through a soft power-
up initialization. This includes transmitting the “Wakeup Notification Packet”. A soft reset does not
reinitialize the DC-2/MC-1. Nonvolatile RAM is maintained.
7.3.2 Restore Defaults
Commands DC-2/MC-1 restore the system and effect parameters to the factory defaults.
7.3.2.1 Command Packet Description
Application Header:
Command DC_CMD_RESTORE_DEFAULTS 0x13
Data Count 0 0x00
Application Data:
N/A
7.3.2.2 DC-2/MC-1 Response
The DC-2/MC-1 will reset, clear any saved system and effect parameters in Nonvolatile RAM, and restore
the factory default system and effect parameters. After reset the DC-2/MC-1 will go through a soft power-
up initialization. This includes transmitting the “Wakeup Notification Packet”.
7.3.3 Send IR Command
Transmits IR command key codes to the DC-2/MC-1.
7.3.3.1 Command Packet Description
Application Header:
Command DC_CMD_IR 0x14
Data Count 1 0x01
Application Data:
Data[0] KeyCode nn
7.3.3.2 Data Description
KeyCode:
Data Type: Unsigned 8 bit integer.
Valid Values: Appendix C DC-2/MC-1 IR-Codes

Lexicon, Inc.
DC-2/MC-1 Serial Communications Protocol Printed on: 10/19/00
12 of 44
7.3.3.3 DC-2/MC-1 Response
The KeyCode is processed as a valid IR code. No acknowledgment will be sent from DC-2/MC-1.
7.3.3.4 Data Validation
The KeyCode data will be verified as a legal IR code. If the Code is not valid the DC-2/MC-1 will not
respond.
7.3.4 Get DC-2/MC-1 Unit Configuration
Request to DC-2/MC-1 for it’s current unit configuration. DC-2/MC-1 will respond with “Unit
Configuration Packet”. The HOST should use this information to determine if any information saved by the
HOST is current.
7.3.4.1 Command Packet Description
Application Header:
Command DC_CMD_GET_CONFIG 0x15
Data Count 0 0x00
Application Data: N/A
7.3.4.2 DC-2/MC-1 Unit Configuration Response Packet
Application Header:
Command DC_RESP_UNIT_CONFIG 0x80
Data Count 25 0x19
Application Data:
Data[0] ProductId nn
Data[1] Software Type nn
Data[2] Software Level nn
Data[3] Software Major Revision nn
Data[4] Software Minor Revision nn
Data[5] Protocol Major Revision nn
Data[6] Protocol Minor Revision nn
Data[7] Total Number of System Parameters nn
Data[8] Total Number of Effects nn
Data[9] TimeStamp[0] ch
Data[10] TimeStamp[1] ch
Data[11] TimeStamp[2] ch
Data[12] TimeStamp[3] ch
Data[13] TimeStamp[4] ch
Data[14] TimeStamp[5] ch
Data[15] TimeStamp[6] ch
Data[16] TimeStamp[7] ch
Data[17] TimeStamp[8] ch
Data[18] TimeStamp[9] ch
Data[19] TimeStamp[10] ch
Data[20] TimeStamp[11] ch
Data[21] TimeStamp[12] ch
Data[22] TimeStamp[13] ch
Data[23] TimeStamp[14] ch
Data[24] TimeStamp[15] 0x00

Lexicon, Inc.
DC-2/MC-1 Serial Communications Protocol Printed on: 10/19/00
13 of 44
7.3.4.3 Data Description
ProductId: This unsigned 8 bit value describes the product.
Product ID
Lexicon Dc-2 1
Lexicon MC-1 2
JBL Synthesis SDP-3 3
Software Type: An unsigned 8 bit value indicating the current configuration of the unit’s
software. The following table shows the values assigned to the available types:
SW Type
THX 1
AC3 2
DTS 3
Software Level: The following table shows the values assigned to the possible software levels:
SW Level
RELEASED 0
PRE_ALPHA 1
ALPHA 2
BETA 3
GAMMA 4
UNSUPPORTED 5
*Note: SW level indicates the status of the DC-2/MC-1 internal application software.
Software Major Revision: An unsigned integer value indicating the unit’s major software version. The host
should use this information to determine if new effects, effect parameters, or
system parameters have been added or removed.
Software Minor Revision: An unsigned integer value indicating this units minor software version. Indicates
the units software operation has changed but effects, effect parameters, or system
parameters have not changed.
Protocol Major Revision: An unsigned integer value indicating the serial communication protocol major
version. The host should use this value to determine if new commands,
notifications, or response packets have been added or deleted from this
specification.
Protocol Minor Revision: An unsigned integer value indicating the serial communication protocol minor
version. The host should use this value to determine if the existing commands,
notifications, or response packets have changed in this specification
Total Number of System Parameters: An unsigned integer value indicating the maximum number of
system parameters for this version of software. This should be used to determine
the data count for the “DC-2/MC-1 System Parameter Values Packet” and “Set
System Parameter Values Packet”.
Total Number of Effects: An unsigned integer value indicating the maximum number of effects available
for this version of software. This should be used to determine the maximum
EffectId used in the “Get Effect Definition Packet”, “Get Effect Parameter
Definition Packet”, “Set Effect Name Packet” , and “Set Effect Parameter
Values Packet”.

Lexicon, Inc.
DC-2/MC-1 Serial Communications Protocol Printed on: 10/19/00
14 of 44
TimeStamp: Is a null terminated ASCII text string describing the build date and time of the
current ROM. The Format of this text string is:
“yy/mm/dd(sp)hh:mm”
yy- is the last two digits of the year (i.e. year 1999 = 99, year 2000 = 00)
mm - is the month
dd- is the day
(sp) - is an ASCII space character (0x20)
hh - is the hour
mm - is the minute
7.3.5 Get System Status
Request to DC-2/MC-1 for it’s current system status. DC-2/MC-1 will respond with “System Status
Packet”.
7.3.5.1 Command Packet Description
Application Header:
Command DC_CMD_GET_SYS_STATUS 0x16
Data Count 0 0x00
Application Data:
N/A
7.3.5.2 System Status Response Packet
Application Header:
Command DC_RESP_SYS_STATUS 0x81
Data Count 10 0x0A
Application Data:
Data[0] System Volume nn
Data[1] Current Input nn
Data[2] Current EffectId nn
Data[3] Current Input Sample Rate nn
Data[4] Current Input Format nn
Data[5] Mute Active nn
Data[6] Effect Bypass Active nn
Data[7] Left/Right Balance nn
Data[8] Front/Back Balance nn
Data[9] Video Synch nn
7.3.5.3 Data Description
System Volume:
Data Type: Unsigned 8 bit integer.
Maximum Value: 92
Conversion: 0 = -80 dB
92 = +12 dB
Current Input:
Data Type: Unsigned 8 bit integer.
Definition: Appendix D Input Id’s
Current EffectId:

Lexicon, Inc.
DC-2/MC-1 Serial Communications Protocol Printed on: 10/19/00
15 of 44
Data Type: Unsigned 8 bit integer.
Maximum Value: Set by “Total Number of Effects” in the “Unit Configuration”
Packet.
Current Input Sample Rate
Data Type: Unsigned 8 bit integer.
SAMPLE RATE
RATE_UNKNOWN 0
RATE_44 1
RATE_48 2
RATE_88 3
RATE_96 4
Current Input Format:
Data Type: Unsigned 8 bit integer.
DATA STREAM TYPE
INSTREAM_UNKNOWN 0
INSTREAM_AC3 1
INSTREAM_PCM 2
INSTREAM_ANALOG 3
INSTREAM_DTS 4
INSTREAM_AC3_20 5
INSTREAM_AC3_51 6
Mute Active:
Data Type: Boolean.
TRUE: System Mute is Active
FALSE: System is unmuted.
Effect Bypass Active:
Data Type: Boolean.
TRUE: Effect Bypass is Active
FALSE: Effect Bypass is not Active.
Left/Right Balance:
Data Type: Unsigned 8 bit integer.
Maximum Value: 32
Conversion: 0 = Left
32 = Right
Front/Back Balance:
Data Type: Unsigned 8 bit integer.
Maximum Value: 32
Conversion: 0 = Front
32 = Back
Video Synch:
Data Type: Boolean.
TRUE: DC-2/MC-1 has detected Video Synch for current video input
FALSE: DC-2/MC-1 can not detect Video Synch for the current video input
7.3.6 Get Record/Zone 2 Status
Request to DC-2/MC-1 for current Record/Zone2 Status. DC-2/MC-1 will respond with “Record/Zone2
Status Packet”.
7.3.6.1 Command Packet Description

Lexicon, Inc.
DC-2/MC-1 Serial Communications Protocol Printed on: 10/19/00
16 of 44
Application Header:
Command DC_CMD_GET_REC_STATUS 0x17
Data Count 0 0x00
Application Data:
N/A
7.3.6.2 Record/Zone2 Status Response Packet
Application Header:
Command DC_RESP_REC_ZONE2_STATUS 0x82
Data Count 5 0x05
Application Data:
Data[0] Zone2 Volume nn
Data[1] Assigned Input nn
Data[2] Zone2 Mute Active nn
Data[3] Record Active nn
Data[4] Zone2 Balance nn
7.3.6.3 Data Description
Zone2 Volume:
Data Type: Unsigned 8 bit integer.
Maximum Value: 92
Conversion: 0 = -80 dB
92 = +12 dB
Assigned Input:
Indicates the input that is currently assigned for the record/zone2 outputs.
Data Type: Unsigned 8 bit integer.
Definition: Appendix D Input Id’s
Zone2 Active:
Data Type: Boolean.
TRUE: Zone2 Outputs are active.
FALSE: Zone2 Outputs are not active.
Record Active:
Data Type: Boolean.
TRUE: Digital Record Output is active
FALSE: Digital Record Output is not Active.
Zone 2 Balance:
Data Type: Unsigned 8 bit integer.
Maximum Value: 32
Conversion: 0 = Left
32 = Right
7.3.7 Get System Parameter Definition
There are two ways to request a DC-2/MC-1 system parameter definition. The first is by Parameter Id and
the second by parameter name. DC-2/MC-1 will respond with “System Parameter Definition Packet”.
7.3.7.1 Get System Parameter Definition by Id Command Packet
Error! Not a valid link.
7.3.7.2 Data Description
ParamId:DataType: Unsigned 8 bit integer

Lexicon, Inc.
DC-2/MC-1 Serial Communications Protocol Printed on: 10/19/00
17 of 44
Max: Set by the System Parameter Count in the “Unit Configuration Packet”.
7.3.7.3 Data Validation:
The ParamId must be a valid parameter number. If it is not the DC-2/MC-1 will respond with a NAK
packet and error code DC_ERR_ INVALID_PARAM_NUMBER.
7.3.7.4 Get System Parameter Definition by Name Command Packet
Application Header:
Command DC_CMD_GET_SYS_PARAM_BY_NAME 0x19
Data Count strlen(ParamName) + 1 nn
Application Data:
Data[0]-Data[DataCount-1] ParamName ch ch ch … 0x00
7.3.7.5 Data Description
ParamName:
Data Type: Null(0x00) terminated ASCII character string.
Max Length: PARAM_NAME_LENGTH defined in Appendix E Protocol Constants.
7.3.7.6 Data Validation:
The ParamName must be a valid Parameter name. If it is not the DC-2/MC-1 will respond with a NAK
packet and error code DC_ERR_ INVALID_PARAM_NAME.
7.3.7.7 System Parameter Definition Response Packet
This packet describes the defining information for a given system parameter.
Application Header:
Command DC_RESP_SYS_PARAM_DEF 0x83
Data Count 3 + strlen(ParamName) + 1 nn
Application Data:
Data[0] ParamId nn
Data[1] MaxValue nn
Data[2] Value nn
Data[3]- Data[DataCount-1] ParamName ch ch ch … 0x00
7.3.7.8 Data Description
ParamId: The Integer Id assigned to this system parameter.
Data Type: Unsigned 8 bit integer
Max: Set by the System Parameter Count in the “Unit Configuration Packet”
MaxValue: Maximum Value allowed for this system parameter.
Data Type: Unsigned 8 bit integer
Max: 255
Value: The Current Value for this system parameter.
Data Type: Unsigned 8 bit integer
Max: MaxValue(in this Packet)
ParamName:
Data Type: Null(0x00) terminated ASCII character string.
Max Length: PARAM_NAME_LENGTH defined in Appendix E Protocol Constants.

Lexicon, Inc.
DC-2/MC-1 Serial Communications Protocol Printed on: 10/19/00
18 of 44
7.3.8 Get System Parameter Values
Request to DC-2/MC-1 for all current system parameter values. DC-2/MC-1 will respond with the “System
Parameter Values Packet”.
7.3.8.1 Command Packet Description
Application Header:
Command DC_CMD_GET_SYS_PARAM_VALUES 0x1A
Data Count 0 0x00
Application Data:
N/A
7.3.8.2 System Parameter Values Response Packet
Application Header:
Command DC_RESP_SYS_PARAM_VALUES 0x84
Data Count SYS_PARAM_COUNT nn
Application Data:
Data[0] sys_param_value[0] nn
Data[1] sys_param_value[1] nn
Data[…] sys_param_value[…] nn
Data[SYS_PARAM_COUNT-1] sys_param_value[SYS_PARAM_COUNT-1] nn
7.3.8.3 Data Description
sys_param_value:
Data Type: Unsigned 8 bit integer Array.
Max: Dependent on the parameter definition.
7.3.9 Get Effect Definition by Id
Request to DC-2/MC-1 for an effect definition. DC-2/MC-1 will respond with “Effect Definition Packet”.
7.3.9.1 Command Packet Description
Application Header:
Command DC_CMD_GET_EFFECT 0x1B
Data Count 1 0x01
Application Data:
Data[0] EffectId nn
7.3.9.2 Data Description
EffectId:Data Type: Unsigned 8 bit integer
Max: Set by the Effect Count in the “Unit Configuration Packet”.
7.3.9.3 Data Validation:
The EffectId must be a valid Effect Id. If it is not the DC-2/MC-1 will respond with a NAK packet and
error code DC_ERR_ INVALID_EFFECT_ID.
7.3.9.4 Effect Definition Response Packet

Lexicon, Inc.
DC-2/MC-1 Serial Communications Protocol Printed on: 10/19/00
19 of 44
Application Header:
Command DC_RESP_EFFECT_DEF 0x85
Data Count 2 + strlen(EffectName) + 1 nn
Application Data:
Data[0] EffectId nn
Data[1] MaxParameters nn
Data[2]- Data[DataCount-1] EffectName ch ch ch … 0x00
7.3.9.5 Data Description
EffectId:Data Type: Unsigned 8 bit integer
Max: Set by the Effect Count in the “Unit Configuration Packet”.
MaxParameters: Maximum number of parameters assigned to this effect.
EffectName:
Data Type: Null(0x00) terminated ASCII character string.
Max Length: EFFECT_NAME_LENGTH defined in Appendix E Protocol Constants.
7.3.10 Get Effect Parameter Definition
Request to DC-2/MC-1 for an effect parameter definition. DC-2/MC-1 will respond with “Effect Parameter
Definition Packet”.
7.3.10.1 Command Packet Description
Application Header:
Command DC_CMD_GET_EFFECT_PARAM_DEF 0x1C
Data Count 2 0x02
Application Data:
Data[0] EffectId nn
Data[1] ParamId nn
7.3.10.2 Data Description
EffectId:Data Type: Unsigned 8 bit integer.
Max: Set by the Effect Count in the “Unit Configuration Packet”.
ParamId:Data Type: Unsigned 8 bit integer.
Max: Set by the Parameter Count in the “Effect Definition Packet”.
7.3.10.3 Data Validation:
The EffectId must be a valid Effect Id. If it is not the DC-2/MC-1 will respond with a NAK packet and
error code DC_ERR_ INVALID_EFFECT_ID. The ParamId must be a valid Parameter number. If it is not
the DC-2/MC-1 will respond with a NAK packet and error code DC_ERR_
INVALID_PARAM_NUMBER.
7.3.10.4 Effect Parameter Definition Response Packet

Lexicon, Inc.
DC-2/MC-1 Serial Communications Protocol Printed on: 10/19/00
20 of 44
7.3.10.5 Data Description
EffectId:Data Type: Unsigned 8 bit integer.
Max: Set by the Effect Count in the “Unit Configuration Packet”.
ParamId:Data Type: Unsigned 8 bit integer.
Max: Set by the Parameter Count in the “Effect Definition Packet”.
MaxValue: Maximum Value allowed for this parameter.
Data Type: Unsigned 8 bit integer
Max: 255
Value: The Current Value for this parameter.
Data Type: Unsigned 8 bit integer
Max: MaxValue(in this Packet)
7.3.11 Get Effect Parameter Values
Request to DC-2/MC-1 for an effect’s parameter values. DC-2/MC-1 will respond with “Effect Parameter
Values Packet”.
7.3.11.1 Command Packet Description
Application Header:
Command DC_CMD_GET_EFFECT_PARAM_VALUES 0x1D
Data Count 1 0x01
Application Data:
Data[0] EffectId nn
7.3.11.2 Data Description
EffectId:Data Type: Unsigned 8 bit integer.
Max: Set by the Effect Count in the “Unit Configuration Packet”.
7.3.11.3 Data Validation:
The EffectId must be a valid Effect Id. If it is not the DC-2/MC-1 will respond with a NAK packet and
error code DC_ERR_ INVALID_EFFECT_ID.
7.3.11.4 Effect Parameter Values Response Packet
Application Header:
Command DC_RESP_EFFECT_PARAM_DEF 0x86
Data Count 4 0x04
Application Data:
Data[0] EffectId nn
Data[1] ParamId nn
Data[2] MaxValue nn
Data[3] Value nn