Hi Ed
this isnt just the case for 2.94..
only one in ten times that i launch the editor, with the fcb connected
does it actually read the uno firmware but without the version...
the other nine times it comes back with Behringer and no version
either...
clicking check firmware button never returns the uno version
either..only closing and re launching the editor will do the trick..and
again it can take up to 5 to 10 times before it gets it right..and even
then it still wont show the actual version..only that its the uno
chip...
what do you think?

thanks
joe

Not sure. Send email and we'll find out why.

Ed


--- In fcb1010_uno@..., "jopo696969" <jopo696969@...>
wrote:

Hi Ed
this isnt just the case for 2.94..
only one in ten times that i launch the editor, with the fcb

connected

does it actually read the uno firmware but without the version...
the other nine times it comes back with Behringer and no version
either...
clicking check firmware button never returns the uno version
either..only closing and re launching the editor will do the

trick..and

again it can take up to 5 to 10 times before it gets it right..and

even

then it still wont show the actual version..only that its the uno
chip...
what do you think?

thanks
joe

Not sure.  Send email and we'll find out why.

Ed


--- In fcb1010_uno@..., "jopo696969"
wrote:
>
> Hi Ed
> this isnt just the case for 2.94..
> only one in ten times that i launch the editor, with the fcb
connected
> does it actually read the uno firmware but without the version...
> the other nine times it comes back with Behringer and no version
> either...
> clicking check firmware button never returns the uno version
> either..only closing and re launching the editor will do the
trick..and
> again it can take up to 5 to 10 times before it gets it right..and
even
> then it still wont show the actual version..only that its the uno
> chip...
> what do you think?
>
> thanks
> joe
>

---

Brings words and photos together (easily) with
PhotoMail - it's free and works with Yahoo! Mail.

Yes, both problems must be related to an error in the "sysex
communication" : when the fcb receives the start of a memory dump
sysex message, it keeps listening to incoming bytes until it receives
an end-of-sysex ("F7"). If this end byte doesn't come, "all lights go
out" and the fcb stops working. Until it does receive the end-byte by
retransmitting.
In case of a "version request", the fcb just won't answer if the sysex
request wasn't well formatted (missing bytes) but the pedal won't lock
up as with memory dump.

To find out if your fcb IN-port or PC-MIDI interface has a problem,
try to send the full memory dump sysex or the version request sysex
(F0-00-20-32-01-0C-40-F7) using MidiOX or similar software.


--- In fcb1010_uno@..., jo po <jopo696969@...> wrote:

would my transmit problem be related?..whenever i transmit from the

editor(rcv enabled at all times) all lights go out and wont come back
on untill i either shut off and on again or re transmit....then all i
s well.....