Updating the MFC shouldn't be this difficult

[powelln09]

Ok guys, I have literally been trying to update my MFC for the greater part of the day. I am a total idiot when it comes to these types of things but I don't give up easily. I have given up! What am I missing? I have to say I have read and sometimes re-read post on here because I'm sure what I am doing wrong is going to be something simple.

I have a PC running Windows 7 and midi ox. I have connected the MFC 101 to the Axe Fx 2 via 5 pin midi, that is USB to AXE, AXE 5 pin midi to MFC 101. I made the adjustments in the I/O menu as stated and on the MFC I changed from expression to midi to receive the data. The two parts I'm not sure about are the settings in midi ox although I have tried every single one I have read or an additional setting I need to change on the MFC. The reason I think that is because after sending the midi file several times I have yet to see a percentage sign or get an error message on the MFC. It just says FW update mode.

I even purchased a USB to midi cable trying to bypass the axe with the same results. Any help would be appreciated. I just watched Chris's latest video still with the same results. It did confirm that I have everything hooked up right. Any thoughts?

[Chris@KatsuKuriMedia]

I bet the problem is in MIDI OX.

Maybe I'll dig out my windows install and play with it. There are a few recent threads with the "magical" speed setting or something like that. Poke around the MFC forum.

[powelln09]

I think your right. I just got an error 17 message but still no percentage completion indication. I can see the MIDI in light blinking on the Axe. I went up and down on the delay setting in midi ox

[Chris@KatsuKuriMedia]

That other thread says 63 is the number to use!

[powelln09]

This is what I have currently. When I hit send file the progress bar comes up in midi ox but MFC doesn't show anything working.
MIDIOX.jpgMIDIOX1.jpg

[cobbler]

Click on the Update help link in my sig

I used my RME MIDI interface. If you are using your Axe then where I hook up the MIDI cable you would...

1. Connect the Axe-Fx II to your computer, through USB.
2. In the Axe-Fx II's MIDI menu, set SendRealtimeSysex to NONE, and UsbAdapterMode to ON.
3. Power down the Axe-Fx II.
4. Connect the Axe-Fx II's MIDI-OUT to the MFC-101's MIDI-IN with a 5-pin MIDI cable.
5. Power on the Axe-FX II.
6. Power on the MFC-101 by reconnecting Cat5 cable, while holding down footswitch 1 (enters firmware update mode).

Be sure to reset the SendRealtimeSysex and UsbAdapterMode params.

I'll modify the step by step in my thread or do a video tomorrow on using the II as the interface.

[surlybrewer]

I just had luck using AXEII as midi device,axe edit open but sending the sysex with MIDIOX (256/15,128/16,check "delay after f7")
Only had MFC midi in cabled to AXEII midi out,unplugged 8 pin/ethernet and used power supply

pretty much just like YEK told me too.....axe edit probably didn't need to be open but it was
Grab a beer and try it!

Yeks MFC-101 How-Tos page - Fractal Audio Systems Wiki

"To upgrade using the Axe-Fx II as a USB-to-MIDI MIDI adapter: Source

Connect the Axe-Fx II to your computer, through USB.
In the Axe-Fx II's MIDI menu, set SendRealtimeSysex to NONE, and UsbAdapterMode to ON.
Power down the Axe-Fx II.
Connect the Axe-Fx II's MIDI-OUT to the MFC-101's MIDI-IN with a 5-pin MIDI cable.
Power on the Axe-FX II.
Power on the MFC-101 by reconnecting Cat5 cable, while holding down footswitch 1 (enters firmware update mode).
Send the new firmware with a MIDI librarian, such as MIDI-OX or SysEx Librarian, from your computer to the Axe-Fx II.
Power down the MFC-101 and Axe-Fx II.
Remove the MIDI cable.
Power on the Axe-Fx II.
In the Axe-Fx II's MIDI menu, set SendRealtimeSysex to the desired value, and UsbAdapterMode to OFF.

An upgrade may require you to reset the MFC-101 to its factory settings. If so, it will be stated in the release notes. To reset the MFC-101, power on while holding switch #11. Note: this will cause you to lose your configured settings! You can save these on forehand and restore these afterwards.

MIDI utilities may need to be configured to work "slowly" in order to perform a successful upgrade. For example, in MIDI-OX set Low Level I/O Buffers to 256 or 128 (size) and 16 (number), Milliseconds Between Buffers to 60 ms, and make sure the Delay after F7 setting is ticked. Use View > Sysex to bring up the Sysex view window, then go to Sysex > Configure to configure the buffers. Also verify that the options MIDI FIlter and Pass Sysex are ticked.

If you're experiencing problems, open the Utility > Preset page on the Axe-Fx, because this makes sure the Axe-Fx is not sending out stuff which could interfere with the update process."

[sundance_kiddsg]

am a self confess idiot when it comes to such things..
which is why i am grateful to the kind souls here that have taken time out to give guys like us a break by recording instructional videos.
i followed this one to a t and it worked fabulously.
just follow the onscreen annotation.
http://m.youtube.com/#/watch?v=zEZ23o3grPc

[cobbler]

This is what I have currently. When I hit send file the progress bar comes up in midi ox but MFC doesn't show anything working.
MIDIOX.jpgMIDIOX1.jpg

Do you have your cable going from MIDI OUT on the II to MIDI IN on the MFC?

[Stringtheorist]

Use Sysex Librarian. Works fine for me.

[MrGuitarabuse]

can try to change 256 to 128 see if moves better

[powelln09]

can try to change 256 to 128 see if moves better

Thanks MrGuitarabuse for the tip. I did try 128 with various combinations with no luck.

[powelln09]

Do you have your cable going from MIDI OUT on the II to MIDI IN on the MFC?

Yes. Everything is hooked up right and that was confirmed by watching the video's. I think it has to do with midi ox because I have a usb to midi cable and took the Axe out completely with the same results.

[powelln09]

Thanks for the tips guys. I will try them tonight when I get home and I will let you know how it goes.

[hussamd]

This is what I have currently. When I hit send file the progress bar comes up in midi ox but MFC doesn't show anything working.
MIDIOX.jpgMIDIOX1.jpg

I use 128 for the buffer size and it works the first time.

You only clicked on the left pane to select the Axe USB. I think you need to click on the Axe in the right panes of your first picture in both boxes to select it. There should be 4 highlighted boxes in that window.

[tvegas99]

Every time I've updated my MFC it's never been easy, I always go first with the recommended buffer size and then find a size OVER 100 is what actually works, 110 was what worked for me this time.

If you don't see a percentage and FW UPDATE is all you are seeing (this happened to me as well) it was because AXE 2 was not showing up as the output in the MIDI routing window

[boltrecords]

I tried many different delay settings until finally finding one that worked.
63 was the number for me.
Just keep trying different numbers till one works. It should get closer to 100% as you get closer to the magic number.

[powelln09]

Well I have tried all these suggestions with no luck so I'm not sure what's going on. I think my next step will be to try a different computer since I have had problems with this computer not seeing USB drives. I'm not really sure how that could be the problem though because it appears the midi signal is getting to the axe because the midi in light blinks. I'm at a loss. Thanks for the suggestions!

[powelln09]

Is there any setting on the MFC that may have been turned on/off that could be blocking the midi file? I just find it strange that weather I'm using the Axe or a USB/Midi cable I get nothing on the MFC in the update mode window. No percentages or error messages but the Midi lights are blinking when I attempt to send the file.

[Chris@KatsuKuriMedia]

No setting I know of. Sometimes the in/out cable connection seems right, but try switching them. If the axe MIDI is blinking, your computer is probably sending it.

The UNO used to say In and Out on the cables, but they changed it at one point to say "To MIDI in" and "To MIDI Out" because everyone plugged them in wrong!