LUSP Message Table Notes
Throughout this document, SysEx messages are broken out using "Message Tables". These tables provide a consistent method of describing the contents of each message class. The tables are organized with separate "rows" for each related group of bytes (refered to as "fields") and "columns" which break up the attributes of each field. For example, the "System Configuration" message table is defined as follows:

Transmit only
Byte #  Value HEX  Description  Notes 
1 F0  Sysex ID (Start) 
2 06  Lexicon ID 
3 09  MPX 1 ID 
4 0bbb bbbb  Device ID  0-127
5 00  System Configuration 
6-7 0n  Major Version (1 byte)  The number that appears to the left of the decimal point on the power up display. Example: V1.00 
8-9 0n  Minor Version (1 byte)  ...
... ...  ... ...
The first column indicates the "Byte #" of a particular field. Whenever possible, this column provides an index into the packet for that field (row). In some cases, this index is not fixed due to fields which have a variable size which preceed it.

The second column indicates the "Value" of the particular field, usually in hex (sometimes in binary). In some cases the value is fixed number ("Lexicon ID") while others can change from message to message. "Values" that can change are represented using a combination of numbers and letters. Binary numbers, for instance, are represented using the lower case letter 'b' for each variable bit in the value ("Device ID: 0bbb bbbb. The 'b's can be '1's or '0's). Hex numbers which can use different numbers in the lower nibble are represented with lower case letter 'n's (Major Version: 0n. The 'n' can be any hex number between 0 and F).

Although only a single "0n" is indicated in the "Value" column for certain fields, these fields will often consist of multiple bytes (each of which uses the format: 0n). This is due, in part, to the nibblizing scheme used in this SysEx implementation (see the previous section), but also due to capability of a single field to describe a group of more than 1 byte (strings, for example). In these cases, the "Description" column usually indicates how many bytes of actual data are contained in the field. I say "actual" data because all of the data bytes following the header (bytes 1-5) are in the "nibblized" format: each byte is broken up into 2 separate bytes. The first byte contains the low nibble and the second byte contains the high nibble. The "number of bytes" indicated in this column, therefor, is for the data after it has been de-nibblized.