Waxwing Bluetooth API Tutorial (Updated 7/24/26)

Using a 3rd party Bluetooth LE app - like LightBlue - you can look for a Waxwing's name in a scan of advertising BLE devices. It will be advertised in the format of a hashtag plus the serial number. For example, you'll see #525 as a nearby peripheral in the scan list for Waxwing S/N 525. For your own software, it is easiest to scan for the Waxwing's main Service (4dddd48d-cf30-492e-850b-76d57dd76900). That is how the Parks Audio Waxwing app scans for devices.

The Waxwing BLE Service:

4dddd48d-cf30-492e-850b-76d57dd76900

The Service's characteristics:

• TX command to Waxwing: 4dddd48d-cf30-492e-850b-76d57dd76901
• RX Stream from Waxwing: 4dddd48d-cf30-492e-850b-76d57dd76902

The TX command is a characteristic of the main service. It is three bytes of data. The first byte is the Function ID, the second byte is the Function Value, and the third byte does not matter (used for other commands to be documented) so just use zero. The table below shows the values in decimal, but 3rd party programs like LightBlue will typically want hexadecimal.

Tutorial examples:

Sending commands to Waxwing:
1. Start the LightBlue app and find your Waxwing in the list of devices. It shows up as its serial number. Press "Connect".
2. Scroll down to the Waxwing Service (0x4dddd48d-cf30-492e-850b-76d57dd76900).
3. Click on "TX command to Waxwing". The list of available TX commands is described below in the HTML table.
4. Click "Write new value". Now let's set the Waxwing's Volume to Mute. This would be 0 for the function, 0 for the value, and 0 for the unused third byte. In hexadecimal this will be 0x000000. Type 000000 and press send.
5. Click "Write new value". Now let's set the Waxwing's Volume back to 100%. This would be 0 for the function, 32 for the value, and 0 for the unused third byte. In hexadecimal this will be 0x002000. Type 002000 and press send.
6. Click "Write new value". Now let's turn on Magic. This would be 11 for the function, 1 for the value, and 0 for the unused third byte. In hexadecimal this will be 0x0B0100. Type 0B0100 and press send.
7. Click "Write new value". Now let's turn off Magic. This would be 11 for the function, 0 for the value, and 0 for the unused third byte. In hexadecimal this will be 0x0B0000. Type 0B0000 and press send.

Reading Waxwing settings:
1. Start the LightBlue app and find your Waxwing in the list of devices. It shows up as its serial number. Press "Connect".
2. Scroll down to the Waxwing Service (0x4dddd48d-cf30-492e-850b-76d57dd76900).
3. Click on "RX Stream from Waxwing".
4. Press the Subscribe button.
5. Go back by pressing the "<Peripheral" at the top left.
6. Click "TX command to Waxwing".
7. Click "Write new value". Now let's turn ON the RX stream. This would be 99 for the function, 1 for the value, and 0 for the unused third byte. In hexadecimal this will be 0x630100. Type 630100 and press send.
8. Now you'll be receiving a 100-byte packet every 500ms. This packet is described below in the HTML table.
9. Click "Write new value". Now let's turn OFF the RX stream. This would be 99 for the function, 0 for the value, and 0 for the unused third byte. In hexadecimal this will be 0x630000. Type 630000 and press send.

Hopefully, these examples and the table below are all you need to get rolling. There's still a lot to document, so don't hesitate to email me for more assistance.

Waxwing API Terms:

The use of this API is permitted for any lawful purpose - private or commercial - provided that the following restrictions are adhered to:

1. Prohibited Uses:
   • The API must not be used to intentionally harm, damage, or disable devices, including but not limited to, bricking or rendering devices inoperable.
   • The API must not be used for illegal activities or in a manner that violates applicable laws.
   • The API must not be used to intentionally harass a Waxwing user.
2. Liability:
   • The author of this API shall not be liable for any damages resulting from its use in violation of these terms.

Hopefully, these examples and the tables below are all you need to get rolling. There's still a lot to document, so don't hesitate to email me for more assistance.

Three Different Formats

This API involves three related but separate numbering schemes, and the same function can sit at a different index in each one. Don't assume a function's position in one table tells you its position in another — always look it up by name.

• TX Commands — the command byte you actually send to the Waxwing to change a setting.
• RX Settings Stream — the 100-byte packet the Waxwing broadcasts every 500ms reporting its current state. Most functions report at the same index as their TX Command, but not always — see BLE TX Power below for an example where they differ.
• fileSlot Format — the format used by the Waxwing app to save/load settings as a file. This is an app-level format, not something sent over Bluetooth, and it includes some settings (like per-control locks) that don't exist in the other two schemes at all. It also excludes a handful of live, in-the-moment functions (like the RPM tests) that don't make sense to save.

TX Commands (write)

Sent as the 3-byte write described above: [TX Command, Value, 0]. If a row's "RX Stream Index" differs from its TX Command, that's the index where you'll see its current value reported back in the RX stream instead.

RX Settings Stream (read)

The 100-byte packet broadcast every 500ms once you've enabled the stream (TX Command 99). This packet is described below as well as by this publicly shared Google spreadsheet.

fileSlot Format (app save/load)

The format the Waxwing app uses to save and load a full settings file. This is a 63-element array, not something transmitted over Bluetooth — it's purely how the app stores settings on disk.

Notes:

• The following functions are not saved in fileSlot: RPM33, RPM45, RPM78, Azimuth, SineGen, SineGen2, and BLE TX Power.
• BLE TX Power will be added in a future revision. The others are Test Suite functions that we don't want to save and prefer default settings for (if only to prevent a confusing user state).