Failing to turn on the LEDs in IO mode

[Edsko de Vries]

(This is my second attempt sending this message, not sure what happened to the first. Apologies if you received this twice.)

Hi,

I recently received and installed my EurekaPROM. As indicated in a previous message, it boots up just fine, reports itself as the EurekaPROM 3.2 in I/O mode, and I receive the expected MIDI events when I press some of the switches. For example, aseqdump reports 

 28:0   Control change          0, controller 104, value 1
 28:0   Control change          0, controller 105, value 1

when I press and then release the first foot switch; in raw hex, using amidi, I get

B0 68 01
B0 69 01

All of this is as expected and matches the spec in https://www.eurekasound.com/eurekaprom/io . However, when I try to send MIDI signals to the device to turn on any of the LEDs, nothing happens. aseqdump confirms that my application is sending the right signal:

128:0   Control change          0, controller 106, value 1

but the LED for pedal 1 does not turn on. Indeed, I can try doing by sending raw MIDI, just to make sure there isn't anything else being sent:

amidi -S "B0 6A 01" -p hw:3,0,0

but again nothing happens on the FCB1010. Every time I send some signals to the FCB, the RED light on my MIDI-to-USB cable lights up, so something is happening, but I guess the wrong thing.

I realize that it's difficult to debug this at a distance, but 

* If anyone has any pointers on what I could try, that would be much appreciated

* If there any known-to-work software utility that I could try to run to check if there is something else wrong?

* If this is not a software issue, what else could be wrong? I guess it could conceivably be the USB-to-MIDI cable, even though it's brand new and it does work just fine in the device-to-computer direction. Is this at a likely candidate?

Many thanks in advance,

-Edsko

[Steven Caldwell]

Maybe the -p flag needs to go first. I'm not really that familiar with that command.

amidi -p hw,3,0,0 "B0 6A 01"

[Edsko de Vries]

That makes no difference unfortunately. There is something more fundamental broken. I've ordered a new MIDI-to-USB cable to see if that perhaps is the issue. I can't think if anything else, unless the device needs more than just the MIDI CC message before it does anything?

[Steven Caldwell]

Hi,

If you have a computer (Mac or PC), you can download the free trial of Bome MIDI translator Pro (scroll down for the link) and test your FCB-1010 in IO mode with the attached Bome MIDI Translator Pro  project file.

On power up it will turn off all pedal lights.

Pressing a switch 1-10 will toggle the switch's LED status.  I tested it with my FCB1010.

If you need further help I'm on the Bome Forum.

[Edsko de Vries]

Thanks for the pointer Steven, that will be a useful reference!

I received a more expensive MIDI-to-USB cable today, which reports itself as actually two devices on the computer; one for input and one for output (Midimate eX). With this cable it works! I have no idea what goes wrong with the other MIDI cable (Omnitronic UM-30). I actually have two of these cables, both of them brand new, and neither of them works, at least not for output to the FCB1010 (works just fine for input from the FCB1010), even though it has two MIDI DIN plugs, one marked "input" and one marked "output". No idea what's going on; unfortunate, because I bought that cable specifically because it was a bit longer. 

Oh well, at least it's working now. Thanks for the help. Once I have my application a bit more developed, I will share here :)

-Edsko

[Steven Caldwell]

Sounds good. So a simple cable problem I guess.