85 Use Cases
Scenario
IMPORTANT
If the T 0 pp 0 command in the optional list query process is not executed, the corresponding
information for the correct use of the A command must be taken from the x messages.
OPTIONAL: Check List Positions for MU IDs, further information about the MUs and saved Names
The list items must be queried for MU ID, further MU information and stored names.
See chapter 5.1 and 5.2.2 for further information on the used commands resp. received messages.
<CR><LF>
SList[0x00] 00000281 30 00 FC 00<CR><LF>
>
In list position 1, which is addressed with
0x00, an MU with MU ID 0x281 is stored.
Furthermore it can be seen from the
SList[] response that the MU works in zone
4, is in allocation mode Single Delegate,
the hardware type is a Single MU with one
button, the RF connection is established
and voting is disabled.
<CR><LF>
RightNameL[0x00]
004800650072007200200046007500630068007
300000000000000000000<CR><LF>
>
The MU at list address 0x00 has the name
shown in the middle column, which is
represented in hexadecimal numbers
separated by 0x00. Using an ASCII
conversion chart it can be translated to
Herr Fuchs.
1) Microphone of MU is activated resp. deactivated
See chapter 4.1 and 4.2 for further information on the used commands resp. received messages.
The first number in the parameter set of
the A command is the MU ID, which is
addressed. The second number defines
whether the microphone is activated or
deactivated; in this example, 1 stands for
activation of the microphone.
The third parameter represents the
hardware type and via the MU flags the
MU zone and the allocation mode. This
information must be correctly extracted
from the SList[] response and transferred
to the tf parameter of the A command. In
this case the information with the values
0x30, 0x00, 0xFC and 0x00 in the SList[]
response leads to the tf value 0x30 which
must be inserted into the A command.
<CR><LF>
Q 00000281 01 0C<CR><LF>
>
The Q message, which is sent back from
the CU to the controller after successful
sending of the A command, now confirms
the allocation or deallocation event of a
MU to a certain stream. In this case it is
an allocation event (second parameter is
0x01, besides the allocation event it
shows that the MU is a Single Delegate)
which assigns the MU to stream 1 (third
parameter is 0C).