AMX UDM-0404 - Manual (Page 92)

UDM Hub Control Protocol
80 UDM-0404 4x4 Multi-Format Distribution Hub
For example:
BUTTON_EVENT[dvTP,3] // POWER TV
{
PUSH:
{
SEND_STRING UDM,"$C0" // SLIP command
wait 2
SEND_STRING UDM,"87,$01,$01,$01,$02,21"
wait 4
SEND_STRING UDM, "$C0" // SLIP command
}
}
By comparison, the equivelant code written for UDP would be:
BUTTON_EVENT[dvTP,3] // POWER TV
{
PUSH:
{
SEND_STRING UDM,"87,$01,$01,$01,$02,21"
}
}
Command Format
UDM commands consist of a command value, together with a number of relevant parameters (normally 6
bytes in total) which are transmitted to the hub, generally described as follows:
The data packet returned by any command may be longer than described - any additional data in a packet may
be ignored. Some endeleo tools and diagnostics use this extra information, but it is not required for control
purposes
Command and Reply Example - Port Connection
Command values differ for each command as do the values and length of the accompanying data.For example,
to connect port 1 to VGA input 2 on the UDM the command format is as follows:
So the data values which must be sent to the hub would be:
The waits used in the example above are not required.
Byte # 0 1 2 3 4 5 6..n
Byte value Command
value
User
defined
Data value 1 Data value 2 Data value 3 Data value 4 Other data
for some
commands
Byte # 0 1 2 3 4 5
Byte value 1 User defined Port Input Sub Input Input Type
Byte # Value Description
0 1 Command value for Connect Input to Port
1 0 User defined - can be any value - this first byte is normally replaced in the reply with a
Status value, other User defined values are just returned unaltered in the reply from the
hub and can be used for checking etc
2 1 Port number
3 2 Input number
4 1 Sub input number (for a VGA input all sub inputs are used in the connection so this value
is not used - it is only important when specifying connections for composite input types)
5 0 VGA type (other types are listed in the command description later in the document)