User guide

Communication Options

ACK Sysex 31

Sysex over TCP 33

Sysex through a Web Server 34

Different ways of communicating with the Matrix3s.

ACK Sysex

This feature allows you to "wrap" any other sysex that you send to any LX-300 DSP inside a "please-ack-me"

wrapper sysex, so that you can get an acknowledgement for the sysex without having to mess around with master-

port stuff (and without getting spammed by acks for less important sysexes)

The format for the sysex wrapper is this:

25 = sxExternalControlSubsystem

XX = destination DSP IDs, or broadcast (7f broadcast, no checksum) Who gets the COMMAND

06 = EXTSUB_CMD_ACK_WRAPPER

XX = DSP ID indicating which DSP(s) should send acks (frame id 01 = 00) WHO ACKS

XX XX XX XX XX = 5-byte tag-value, will be copied into the ack

(set by the user for what ever value they want to put in here – must be 7-bit clean)

[...] = Insert the main sysex here (omit the F0, Checksum, and F7)

xx = Checksum (a 00 place holder required if no checksum.)

Important

The 5-byte tag value must be 7bit clean. This means that each byte must be in the range of 00 to 7f inclusive. (this

is the same range for all data bytes in CASL)

ACK

The format of the ACK sysex that is sent back in response is this:

25 = sxExternalControlSubsystem

3E = MDSUBSYS_REPLY_ID

XX = Source DSP ID (i.e. the DSP that sent the ack)

44 = EXTSUB_CMD_ACK_REPLY

XX XX XX XX XX = 5-byte tag value, as specified in original sysex

xx = Checksum

Example 1: Check Frame ID 01 Firmware

Say you wanted to send a "Check Firmware Version" sysex to all LX-300s, and you want an ACK back just from

Frame ID 01. Here is what you could send: