Analog Way ORCHESTRA2 Programmer's Guide - Manual (Page 3)

3
PROGRAMMER'S GUIDE FOR ORCHESTRA
2
v04.00 build 52
1 INTRODUCTION
The Orchestra allows communication through an ASCII code protocol. It treats any character that it
receives on the LAN (TCP/UDP) as a possible command but only accepts legal commands.
There is no starting/ending code needed in a command string. A command can be a single character
typed on a keyboard and does not require any special character before or after it. (It is not necessary to
press "ENTER" on the keyboard). A command can be preceded by a value (See chapter A-2). A command is
case sensitive.
When the Orchestra receives a valid command, it will be executed. Then it will send back the status of
the parameters that have changed due to this command. If the command cannot be executed (value out
of range, device not ready, etc), the Orchestra will just send back the current status of the corresponding
parameters. If the command is invalid, an error response will be returned. All responses end with a
carriage return and a line feed signaling the end of the response character string (see chapter
A-3).
2 REFERENCES

ORCHESTRA
2
firmware updater (on ANALOG WAY web site)

ORCHESTRA
2
reference manual (on ANALOG WAY web site)

ORCHESTRA
2
quick start guide (on ANALOG WAY web site)
3 COMMAND STRUCTURE

Write/Set: [[index,] ...][Value][Command]

Read/Get: [[index,] ...][Command]

Answer: [Command][[index,] ...][Value]
Some commands are “global” and do not require any index. Other commands might need indexes to
specify which screen/element/matrix... need to be affected. Each index should be followed by a comma.