Bc2000 (for the BCF2000 & BCR2000)

A USB sniffer detects all "packets" that are sent over USB to a
device. I assume (I don't know for sure yet) that USB devices
communicate using some sort of packet messaging protocol, like TCP/IP
(have to double-check that though... I'm downloading the spec right
now). Hence whatever the "payload" is will be viewable via the
sniffer. So, whether it's a MIDI sysex message or data being copied to
a USB drive, the sniffer will show it and it's up to the user to
figure out how to interpret it. 

I've only seen it referred to as "BCL", hence I thought that might
mean "Behringer Coding Language", but "B-Control Language" makes more
sense. Anyways, I didn't know if users found out about BCL via
Behringer and Behringer's documentation or by sniffing USB
communications and reverse-engineering it. The former would be far
easier than the latter, of course, but I will probably need to do the
latter if I'm going to make heads or tails of what the Enigma editor
sends to a Keystation 88. The reason being that recording the Sysex
data when patches are transfered between the computer and the KSP
didn't show anything useful -- certainly not the data I'd expect to
see. This suggests to me that all the Sysex messages do is set memory
blocks in the KSP to "write" mode or something similar. Unless I'm
missing something, of course, which could easily be the case.

    -Andrew-

--- In bc2000@yahoogroups.com, "Mark van den Berg" <markwinvdb@...> wrote:
...
> "USB sniffer"? I must admit I'm completely out of my depth as to what
> this is and does, so you'd have to enlighten me on this point.
...
> And what do you mean by "the Behringer coding language"?
> There is of course BCL (probably standing for "B-Control Language"),
> which has already been described (almost completely) in the MIDI
> implementation document.
...
> 
> Mark.
>