ASPEN-32UFX, ASPEN-1616UX, VS-8UFX – Protocol 3000
For more information about Protocol 3000 commands, see:
• Understanding Protocol 3000 on page 30.
• Kramer Protocol 3000 Syntax on page 30.
• Protocol 3000 Commands on page 34.
Understanding Protocol 3000
Protocol 3000 commands are structured according to the following:
• Command – A sequence of ASCII letters (A–Z, a–z and -). A command and its
parameters must be separated by at least one space.
• Parameters – A sequence of alphanumeric ASCII characters (0–9, A–Z, a–z and some
special characters for specific commands). Parameters are separated by commas.
• Message string – Every command entered as part of a message string begins with a
message starting character and ends with a message closing character.
A string can contain more than one command. Commands are separated by a pipe (|)
character.
• Message starting character:
# – For host command/query
~ – For device response
• Device address – K-NET Device ID followed by @ (optional, K-NET only)
• Query sign – ? follows some commands to define a query request
• Message closing character:
␍ – Carriage return for host messages (ASCII 13)
␍␊ – Carriage return for device messages (ASCII 13) and line-feed (ASCII 10)
• Command chain separator character – Multiple commands can be chained in the same
string. Each command is delimited by a pipe character (|). When chaining commands,
enter the message starting character and the message closing character only at the
beginning and end of the string.
Spaces between parameters or command terms are ignored. Commands in the string do
not execute until the closing character is entered. A separate response is sent for
every command in the chain.
Kramer Protocol 3000 Syntax
The Kramer Protocol 3000 syntax uses the following delimiters:
• ␍ = Carriage return (ASCII 13 = 0x0D)
• ␊ = Line feed (ASCII 10 = 0x0A)
• ␠ = Space (ASCII 32 = 0x20)
To Next Page
Loading...
Need help?
General
