User guide

30 = sxTCPSubsystem

7f = broadcast

0F = LXTCP_CONTROL_COMMAND_ADD_CUSTOM_PARSE_PREFIX

[...] = prefix bytes of desired sysex, not including F0

xx = Checksum

EXAMPLE: if all your client cares about is the EXTSUB_CMD_ACK_REPLY sysexes generated above, it could send

the following sysexes to lxtcpcomd to indicate that:

Client Type is LXTCP_FORWARD_CUSTOM

Send all sysexes that start with "F0 1F 7e 25 3E 00 44"

RS-232 and RS-422 ACK Details

When connected via serial, you will only get an ack back from the LX-300 you are physically connected to. The

other LX-300s will generate acks if the wrapper asks them to, but the routing to get those acks back to the correct

LX-300's serial port is not implemented. Use 0x3B (BOXNET_LOCAL_DSP) as the DSP ID for sending ACK when

connected via serial.

When connected via lxtcpcomd (Ethernet), you can get acks back from any or all DSPs.

Sysex over TCP

To use the EtherTracks module as if it were a very fast serial port, have your control program make a TCP connection

to port 2980 of the EtherTracks card. Once the TCP connection is established, you may immediately begin sending

MIDI sysex control messages to the LX-300, as documented elsewhere.

Sysex over TCP