guitarsrule
Inspired
Hello all.
I would first like to thank Voes for the extensive write-ups and instructions here and on his site, as well as the many people offering assistance on the forum. Programming this stuff takes a lot of time and effort, and supporting others in getting things set up takes a lot of back-and-forth and repetition of tips and advice. Thanks for all the support and patience!
I've made some progress with my FCB1010, but I'm still having some issues. I have the Uno chip, latest firmware (v.1.0.3, and as Voes mentioned in the FAQ on his site, it shows up as v.1.0.2.g in Ripwerx), and my USB-MIDI interface is an E-MU Xmidi 1x1. I've tried Windows 7 64-bit as well as Windows Vista, and I'm controlling an Axe-FX Ultra. I've had mixed results using Ripwerx and the PC Editor for FCB1010.
I've followed the instructions in the "getting started guide" from Voes several times, making sure to initialize the extended memory, set to stompbox mode, and enable sysex receive.
I'm having some issues similar to JJunkie, who posted in one of the first few pages of this thread.
This is happening to me as well; I've tried waiting up to 5 minutes, but the FCB never comes to life after this point. I have to turn the FCB off and then on again in order to fiddle around again. I also get the “____ bytes sent” message.
Another poster said:
When I go through the step that involves holding down 1 and 9 while powering up, the display counts down as expected. When I do the next step involving 1 and 10, the FCB never counts down; if I recall correctly it goes blank indefinitely until I press UP, then returns to displaying "00". I was very careful when installing the Uno chip, and I opened the up the FCB again after reading the above suggestion, but the chip is oriented correctly and close inspection of the pins indicates that nothing was broken or bent during installation.
The procedure to enable sysex receive seems to work fine, and if I go into the global config menu at a later time, LED 7 is still lit.
I've tried sending the sample Ripwerx sysex file that Voes had posted somewhere, but after doing this (and after the FCB shuts down as described above), when I "get patch dump" in Ripwerx, everything is clearly messed up, with crazy numbers everywhere they shouldn't be. A similar thing happens with the PC Editor, but I actually had the most success to date by sending my desired sysex using that program. Even though the "receive patch dump" command returns a mixed-up layout with crazy PC and CC numbers and messed-up global options, when I connect the FCB to the Ultra, it partially works.
Here are some descriptions of what else is going on:
- The upper row of switches is set as stompboxes, and these are sending the proper CCs and turning on/off the appropriate effects, However, the LEDs don't match the starting bypass states of the effects, and in order to change the state of any effect I have to press the switch twice. JJunkie mentioned this as well:
- The expression pedals have been calibrated and programmed and are sometimes functioning now, but not consistently. Sometimes when I press "1" to go to the first preset, it comes up with both expression pedal LEDs on (as desired), and delay engaged as well (not desired). If I turn off the delay with its stomp switch, the expression LEDs also go out and I have no control over their functions. Sometimes when I press "1" again (which ideally would only send a "64" CC for tap tempo), the delay stays off but now the expression pedals/LEDs function again. This doesn't happen every time though.
It seems that I have a MIDI problem of some sort, but I’m not sure what to focus on first. Could my USB-MIDI interface be to blame (E-MU Xmidi 1x1)? Ripwerx does read the correct Uno firmware version from the FCB.
Does the blanking display during sysex receive indicate a problem with the FCB itself, or with the Uno chip?
Thanks again to Voes and to the many others who continue to provide assistance!
-Alex
I went through an ordeal about a week ago using the emu xmidi. What was happening to me was the PC editor software corrupted both my fcb's. I broke down and bought the uno control center software and it fixed all my issues. I was ready to send my eprom back.