ASCII Commands (Luna U 1.2.1)

This is the list of ASCII Commands supported by this device. An ASCII command always follows the same structure:

#|Destination|Source|Type^Target^Command|Arguments|CRC|CRLF

This format uses 3 separator characters for different levels of separating each value in the message:

• Message separator ‘|':
  This separates a message into 7 blocks (if you include the start ‘#’ and end <CRLF>)
• Block separator ‘^':
  This splits a block into logical elements. This is used to split the command in the message type, ‘command’ and 'target’
• Value separator '>':
  This splits up a logical single value in their primitives, for example: a target consists of a channel type and a channel index, split by '>'

Messages are Case sensitive, if the example shows the text in uppercase, this should always be uppercase!

Destination

The target device. This consists of 2 parts: Device>Address.

Device
This is the device type: LUNA_U

Address
This is the user-configurable device address, default: 1. You can also leave this field empty, this results in all Luna U devices that receive this command to respond.

Device Matching

If the device type or address does not match, the message will be ignored. Device Address 0 is a special address and will always match (this can be seen as a broadcast)

Source (optional)

The source address is optional when sending, but the device will always fill this field with its own address.

Type

The type explains what the message wants to do. There are 3 supported message types:

Command, Target, Arguments

These 3 parameters are explained together, because they influence each other. The command dictates the meaning of the argument, while the target distinguishes which exact setting you want to change. the target can also influence the valid range of the argument.

Some commands (like the mixer) can have a range arguments (for the mixer: all mixer volumes are an individual argument). In this case, the argument looks like: idx>val[^idx2>val2], where the part in between the brackets [] can appear 0 or more times.

• idx, ídx2, ...: the argument index
• val, val2, ...: the value at the specified index

VOLUME

Set a single Volume in dB

Argument (volume)
the requested Volume in dB

ROUTE

change the routing of a zone

Argument (input)
the input that is selected in that zone. -1 = Mixed (not settable), O = OFF, 1 = input 1 ,...

MUTE

mute an audio channel

Argument (enabled)
is the audio channel muted

MIXER

mixer slider for zones

Argument (volume)
mixing volume

CRC

The CRC block is calculated over the message starting from and including the first pipe "|", up to and including the last pipe before the CRC Block. These CRC's can ensure message integrity if desired.

The examples in the table above are example for calculating the CRC, they may not be a valid command for the LUNA-U

The CRC can ensure data integrity across unreliable data channels (RS232, RS485), but they are by no means a security measure! If someone has the knowledge and means to maliciously alter a message, correcting the CRC becomes trivial for the attacker. We support different kinds of CRC for maximum flexibility, but we recommend not using any so you do not get a false sense of security.

Stop bytes

The final 2 characters are denoted as <CRLF>, they mean "Carriage Return, Line Feed" or simply put a new line. Depending on the tool used to create the command, you can have different representations:

• CRLF
• \r\n
• 0x0D 0x0A

We support both CRLF and LF only