Updating the MFC shouldn't be this difficult

[powelln09]

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!

Well Bummer! That would have been too easy. The usb/midi I have isn't marked in or out just red and black so I have tried switching them around. No luck.

[cobbler]

You have the AXE II windows USB driver installed I hope?

I created an updated step by step using the AXE II as the MIDI adaptor. Start from scratch and see what happens.

Updating MFC on Win7 using MIDI-OX and the AXE II as a USB to MIDI adaptor

[powelln09]

You have the AXE II windows USB driver installed I hope?

I created an updated step by step using the AXE II as the MIDI adaptor. Start from scratch and see what happens.

Updating MFC on Win7 using MIDI-OX and the AXE II as a USB to MIDI adaptor

I have actually deleted and re-installed the drivers twice. My set up looks like yours to a tee. I even tried a hard reset on the MFC.

[cobbler]

I dont know what to say. If you got a connection with MIDI OX then its got to be the settings. You have said you have experimented with them so I dont know how to help you. i would start at 40 for both buffer settings and go up in incrememts of 10 till you get to 150 and see.

Sorry.

[powelln09]

Thanks for your help cobbler.

[powelln09]

**UPDATE** Ok so today I was able to update to the new firmware in the axe (9.02) and updated all the banks using midi ox. The setting that worked was buffers at 110. After being able to do all this I still get nothing on the MFC. The only thing I can think of is the midi cable. I tried two different computers with different operating systems with the same results. The midi cable I'm using is a "Live Wire MID-315 RED 15ft". If I'm reading the reviews right it should have all 5 pins hooked up?

[cobbler]

Other than the obvious making sure you are MIDI out on the II or another MIDI interface and MIDI IN on the MFC it must be the cable or MIDI port. If you are at the UPATE MODE screen on the MFC it is just wating for the signal.

[powelln09]

I just put on ohm meter on the midi cable and I got reading of 1.2 on all the pins except pin three which read .04. I'm not an electrician but I would think all these should read the same right?

[Tubehead]

I'm not able to update the MFC either using a Midiman 1X1. I am trying to go direct from the PC through the MIDIMan to the MFC using MidiOx. I do not see what value going through the AxeFx would bring. Can I not just use the MidiMan?

The MFC seems stuck on the FW UPDATE status and does not start to display any progress at all. I have played with the buffers and other settings but MidiOx works just fine when updating the AFX2 to 9.02. I just don't get it. Why is the MFC being stubborn?

... and yes, I did set the MFC to MIDI instead of Expansion Port.

[powelln09]

I feel your pain Tubehead. I have even tried using a usb to midi cable with no results. MFC is just as good as a paper weight right now.

[cobbler]

I'm not able to update the MFC either using a Midiman 1X1. I am trying to go direct from the PC through the MIDIMan to the MFC using MidiOx. I do not see what value going through the AxeFx would bring. Can I not just use the MidiMan?

The MFC seems stuck on the FW UPDATE status and does not start to display any progress at all. I have played with the buffers and other settings but MidiOx works just fine when updating the AFX2 to 9.02. I just don't get it. Why is the MFC being stubborn?

... and yes, I did set the MFC to MIDI instead of Expansion Port.

I have never had to change that to MIDI regardless of going through the II or my MIDI interface. I have always left it on expansion.

My thread link in my sig had a step by step using my RME UFX MIDI and then I updated it the other day with a step by step using the II. Most people have been able to get it to work with buffer values anywhere from 40 to 130. With my UFX MIDI I used 60 and it was good. On the II I needed to change it to 90. I am lost for what else to say other than to make sure your cables are good and you are going to MIDI IN on the MFC. Sorry.

[powelln09]

Latest Screen shot....Now when I use it the "edited" light comes on?

[ATTACH=CONFIG]14242[/ATTACH

[powelln09]

IT WORKED!!!!!!!!!!!!! Finally. So after all of that it was a bad brand new midi cable. Thank you guitar center! All my settings were set at 256/16 and buffer at 90. Worked the first time. Big THANK YOU to cobbler for helping me out!

[Tubehead]

I got around my issues by using a different software.

Downloads - Bome's Send SX - Bome Software - Freeware for sending and receiving any MIDI messages

[Aces]

I finally managed to update my MFC today. Originally, when reading the instructions posted here, I was trying to update my MFC by using a USB to midi cable. The USB was plugged into my computer and then into the MFC. What I failed to realise was that the instructions said to use a dedicated midi cable FROM THE AXE and not a usb to midi cable from the computer. I purchased a midi cable yesterday and tried the instructions again (MFC was connected to Axe FX II by midi cable and usb from computer to Axe so that I could install the firmware.)

It worked first time!!! Thanks to those who took the effort to help out us noobies ;o)

[Chris@KatsuKuriMedia]

you could have used that usb-midi cable direct from the computer to the MFC. whatever program you're using to send the file, just send it via the USB-Midi interface, not over USB to the axe. i show it in my video, in case you need it for next time:

How to Update the MFC-101 Firmware | Katsu Kuri Media Blog

[Johnnyh64]

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 foot-switch 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."

This finally worked for me after about 6 tries.

I started with Bome's SendSX and surprisingly everything transferred very easily the first time. It read 100%. The problem is that the MFC actually needs to read "Firmware Update Complete" or something like that. I thought 100% is good enough for me, so I shut it off and hell if I didn't get just about every error known to man. I started off with an Error 14 then an error 18. I figured it was because I was using a program that was substantially different than MidiOX (which I heard from so many people that the update failed unless you typed in exact buffer numbers). This was getting frustrating. But, I did stick with MidiOX and the numbers quoted above and it finally worked. My MFC came back to life and asked if I wanted to "Revert". I didn't know what it meant but I said yes, and it seemed to work. It's now at 2.15.

I think it would help immensely if we had a look-up table for the codes that we are receiving. This is basic hardware programing 101 and we are getting feedback, we just don't know what any of it means. I had an "error 4", and "error 6" , "error 14", "error 16" and I think an "error 18", although I'm not 100% sure of all of them. Anyway, FAS please post the error codes so we know which way to do things. It's a guessing game at best and we don't want to ultimately fry our system.

That's my story and I'm sticking to it.

I'm starting to think that Bome's SendSX is the way to go as it was so much easier and had no errors. I just think I needed to shut it down or end it with an F7 so the MFC would realize it was finished. SendSX was flawless the first time. I think I messed up on all the other parts (ie turning the Axe parameters back, shutting down SendSX right away, hooking the hardware back up properly after the sysex dump, etc. Anyway, food for thought.

[yek]

I think it would help immensely if we had a look-up table for the codes that we are receiving. This is basic hardware programing 101 and we are getting feedback, we just don't know what any of it means. I had an "error 4", and "error 6" , "error 14", "error 16" and I think an "error 18", although I'm not 100% sure of all of them. Anyway, FAS please post the error codes so we know which way to do things. It's a guessing game at best and we don't want to ultimately fry our system. That's my story and I'm sticking to it.

I think it would help immensely if you took a look at par. 14.2 of the manual. ;-)

[Johnnyh64]

I think it would help immensely if you took a look at par. 14.2 of the manual. ;-)

O.k. Yek, guilty as charged.

I have to admit that I am absolutely bewildered by all of the different avenues of information. I was trying to find what sysex program is right to do this. Was it in the manual? MidiOX, Snoize, Axe Edit, Bome's Send SX, etc...non that I could find...was it online in the forums? Hmmm, maybe. What thread was that though? Now I have to go to the support page to download the correct version. But in another thread I'm told different numbers to input into my Midi Sysex dumper, I'm told 3 different ways to hook up my MFC to my unit one is for Mac OSX and the other is for PC Windows but the 64 bit version is just a little bit different, so...and let's not forget the hardware hookup. If I do it wrong, I might blow up my MFC and/or my AXe. So please forgive me for missing paragraph 14 sub-section 2 in the manual! LOL...I know you mean well and are just trying to point others in the right direction. I'm just tired and need my milk and cookies.

[yek]

Yeah, it's understandable. I think the problem is that MIDI (or MIDI-over-USB) is not an adequate communications protocol for transferring big chunks of program material, in order to update device firmware.

With my Ultra I had to use a MIDI-USB device or cable and that often meant trouble.

Now I'm using the Axe-Fx II itself as an USB/MIDI-adapter (as explained in the MFC How-Tos). Together with Snoize Sysex Librarian (Mac only), at default settings, the Cat5 connection (for power) and a MIDI cable, updating succeeds each time, without issues.
And I've done a lot of updating, for beta testing purposes.

Unless there's a cable problem. I've had to throw away a lot of MIDI cables over time...