Bc2000 (for the BCF2000 & BCR2000)

--- In bc2000@yahoogroups.com, "rpcfender" <rpcfender@...> wrote:
> F0 00 20 32  00  -   Request Command?
> F0 00 20 32  7F  -   Request Command as well (don't know why there are 
> 2values)

The general BCF/BCR sysex message format is:

System Exclusive       = $F0
Manufacturer Behringer = $00 $20 $32
Device ID              = $00..$0F(=ID on actual device) or $7F(=any)
Model                  = $14(=BCF2000) or $15(=BCR2000) or $7F(=any)
Command                = miscellaneous
(DATA BYTES            = depends on Command)
End Of Exclusive       = $F7

So the byte after the Behringer identifier bytes ($00 $20 $32)
indicates the Device ID.

On the BCF/BCR you can set this value via "Global Setup" (press
EDIT+STORE, then use encoder 5). The range as shown in the BC's
display is 1-16, although in MIDI messages the corresponding value is
"minus 1", so from $00 to $0F.

However, MIDI messages have another option for the Device ID, namely
the "wildcard" $7F, meaning "any device". (This "wildcard" protocol is
basically the same as the one used for the Model byte, which
immediately follows the Device ID byte in these MIDI messages.)

Any particular BCF/BCR only SENDS messages using its own Device ID,
but REACTS to MIDI messages mentioning either its own Device ID or the
wildcard $7F.

I found out the hard way that the Device ID value indeed matters
when I tried to use your script program on my BCR when I had (for some
reason) changed my BCR's Device ID to some outrageous value like 9:
the BCR didn't respond to the program until I had switched back its
Device ID to 1!

Incidentally, (at least under Windows XP) the Device ID is also
mentioned in the USB MIDI device's name as shown on the computer (but
differently in USB drivers versions 1.1.1.1 and 1.2.1.3!). Changing
the Device ID on the BC while it's connected to the computer via USB
may lead to terrible MIDI device errors, so you should be careful with
that.

Mark.