Kramer Electronics Ltd.
ASPEN-32UFX, ASPEN-1616UX, VS-8UFX
– Protocol 3000
31
Some commands have short name syntax in addition to long name syntax to enable faster
typing. The response is always in long syntax.
The Protocol 3000 syntax is in the following format:
•
Host Message Format:
Start
Address
(optional)
Body
Delimiter
#
Device_id
@
Message
␍
•
Simple Command
– Command string with only one command without addressing:
Start
Body
Delimiter
#
Command
␠
Parameter_1,Parameter_2,…
␍
•
Command String
– Formal syntax with command concatenation and addressing:
Start Address
Body
Delimiter
#
Device_id
@
Command_1
Parameter1_1,Parameter1_2,…|
Command_2
Parameter2_1,Parameter2_2,…|
Command_3
Parameter3_1,Parameter3_2,…|…
␍
•
Device Message Format:
Start Address
(optional)
Body
Delimiter
~
Device_id
@
Message
␍␊
•
Device Long Response
– Echoing command:
Start Address
(optional)
Body
Delimiter
~
Device_id
@
Command
␠
[
Param1,Param2 …] result
␍␊
Extended Protocol 3000
In addition to the standard Protocol 3000 syntax, newer Kramer products use extended syntax
to improve user experience and provide easier deployment and configuration.
For products with many ports and of different types, the extended syntax describes
commands and their parameters in a more intuitive, user-friendly format.
To identify devices supporting extended commands, use the
#HELP
command to list all
supported commands. Commands that begin with the prefix ‘
X-
‘ use extended Protocol 3000
syntax. Extended commands use Port ID (see
) and Signal ID
) instead of the old port naming parameters.
Port ID Format
The port ID is composed of three fields separat
ed by a dot ‘.’
(<
direction_type
>
.
<
port_type
>
.
<
port_index
>), where: