Bc2000 (for the BCF2000 & BCR2000) group photo

Yahoo Groups archive

Bc2000 (for the BCF2000 & BCR2000)

Index last updated: 2026-04-28 23:16 UTC

Message

Re: [bc2000] BCR2000 and the NoOS message - Help please

2008-03-24 by Karl Lurman

Sounds like a dodgy midi cable. Unless you don't have the cable going
in correctly. It should go midi out (from the usb) to midi in (on the
bcr) and midi out (on the bcr) to midi in (on the usb). I too have had
the misfortune of using the behringer update proggy and had the same
NOOS experience. Luckily I was able to borrow a USB->midi adaptor, but
prior to that I tried to make my own midi cable (with a few loose
wires I had around the place). It seemed as though it was working,
because the midi lights would flash when I tried to send the sysex
file to the unit, however the update would not occur. It was only
until I used a proper cable that I saw the progress indicator on the
index (an increasing number and small cycling animation).

Good luck dude!
Karl

On Tue, Mar 25, 2008 at 4:07 AM, Jim Burrill (UK) <smogthemog@...> wrote:
>
>
>
>
>
>
> I have just purchased BCR2000 off of Ebay and all was well when I got
>  it. I required it for live MIDI control of Mamba Black Laser show
>  software. It was running v1.07 OS when I got it and upon trying to
>  update it using the POXY Behringer update program it now only reads
>  NooS in the LED display :(
>  This now means I have no USB acsess and can only OS dump via MIDI from
>  the PC. Well I have tried that about 50 times now but to no avail.
>  I am running Windows XP Pro SP2 and with an Ebay bought USB to MIDI
>  interface cable.
>  I have pressed the STORE/LEARN buttons opon switch on (to give the LOAD
>  sequence) and dumped the file to it via MIDI but nothing. The display
>  dosen't change at all. The MIDI light flashes but nothing at the end.
>
>  Any help will be greatly appreciated.
>  Thanks
>  Jim Burrill
>
>

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.