zenkick
Inspired
New Axe FX II + MFC-101 - Problems (Solved!)
I am going to to forward this information to FAS support as well, but wanted to at least see if the community has encountered this issue, or has any thoughts. I apologize for the long-windedness, but I want to avoid any wasted traffic suggesting the obvious.
I received my Axe FX II and MFC-101 today, and much to my surprise (brand new from FAS, mind you) - I'm encountering issues immediately with the two-way communication between the Axe FX II and MFC-101.
Before hooking anything up, I read the MFC quick start guide. I powered up the MFC (only power - nothing connected to the Axe yet), went into Edit menu, changed the midi port to EXPANSION, went into Mode menu, changed to AXE FX II. I then exited/saved and removed power from the MFC to shut it down.
I then ran a CAT5E cable (straight NOT x-over) from the expansion port on the MFC-101 to the same port on the Axe FX II.
I then powered up the Axe. The Axe booted along with the MFC (since it was getting power from the Axe -- that's good.)
After about 30 seconds of watching the "midi in" led flash on the Axe, and glancing at the MFC's display of X000, the MFC replied with the dreaded "AXE-FX NAME TIMEOUT".
Of course the first thing I did was Google the forum here to see what others were saying. Most everything was user error -- forgot to set the mode or midi on the MFC; used a cross-over cable instead of straight; had an old firmware on their Axe;
I unplugged the ethernet and grabbed two more: one CAT5, one CAT6 (yes, both straight.)
I then checked the Axe FX II firmware. It was shipped to me with 5.04. That seemed recent enough. I then reset the system settings via utility. That seemed easy enough.
I powered down the Axe, connected a different cable - same behavior. I repeated with the third cable - same behavior.
I then tried to choose a preset from the MFC. That worked - the preset changed, the midi light flashed on the Axe. However, the preset on the Axe took about *1 second* to change (I hope that is not normal.)
Next I decided to upgrade the firmware of the Axe to 5.07. I disconnected the MFC, I power cycled the Axe, and did the firmware upgrade. It worked fine. I confirmed 5.07 was installed. I then reset defaults again, for good measure.
I switched back to the first cable (CAT5E). Same behavior - "AXE-FX NAME TIMEOUT". I confirmed the mode and midi was correct on the MFC (again.)
I then checked on the MFC firmware. It was 1.04 (I believe - I'm upstairs typing now, sounds about right.)
I then reset the MFC (powered with #11 held down, confirmed.)
I then powered down the Axe FX, removed the ethernet, and powered it back up. I jammed with a couple presets for a while. That was at least fun.
In some of the search results here, users were reverting back to midi - either single cable 7pin with phantom, or even two generic 5pin with power on the MFC. I gave the latter a shot (I don't have a 7 pin handy.)
I powered the Axe down. I then connected two all-purpose 5pin midi cables (they work - they are the same ones I used on my Vetta in a previous life) - in to out, out to in. I ran power to the MFC. I changed the midi setup to MIDI. I power-cycled it - confirmed the midi setup was MIDI. I then powered up the Axe - same behavior.
Next I remembered reading about the midi thru/out being off by default on the Axe FX II. I reset system defaults again, confirmed it was off, turned it on, and power cycled everything again - same behavior.
Not related to this particular issue, but in troubleshooting this, I noticed that sometimes if I choose a screen from the front panel of the FX, the new screen will pop up, but then it will immediately go back to the previous screen. I'm going to look into that one more - but it seems like it only happened when the MFC was connected.
My conclusion is that something is defective with my very expensive investment, which is unsettling.
Thoughts? Have I missed something?
Thanks in advance.
-Dave
I am going to to forward this information to FAS support as well, but wanted to at least see if the community has encountered this issue, or has any thoughts. I apologize for the long-windedness, but I want to avoid any wasted traffic suggesting the obvious.
I received my Axe FX II and MFC-101 today, and much to my surprise (brand new from FAS, mind you) - I'm encountering issues immediately with the two-way communication between the Axe FX II and MFC-101.
Before hooking anything up, I read the MFC quick start guide. I powered up the MFC (only power - nothing connected to the Axe yet), went into Edit menu, changed the midi port to EXPANSION, went into Mode menu, changed to AXE FX II. I then exited/saved and removed power from the MFC to shut it down.
I then ran a CAT5E cable (straight NOT x-over) from the expansion port on the MFC-101 to the same port on the Axe FX II.
I then powered up the Axe. The Axe booted along with the MFC (since it was getting power from the Axe -- that's good.)
After about 30 seconds of watching the "midi in" led flash on the Axe, and glancing at the MFC's display of X000, the MFC replied with the dreaded "AXE-FX NAME TIMEOUT".
Of course the first thing I did was Google the forum here to see what others were saying. Most everything was user error -- forgot to set the mode or midi on the MFC; used a cross-over cable instead of straight; had an old firmware on their Axe;
I unplugged the ethernet and grabbed two more: one CAT5, one CAT6 (yes, both straight.)
I then checked the Axe FX II firmware. It was shipped to me with 5.04. That seemed recent enough. I then reset the system settings via utility. That seemed easy enough.
I powered down the Axe, connected a different cable - same behavior. I repeated with the third cable - same behavior.
I then tried to choose a preset from the MFC. That worked - the preset changed, the midi light flashed on the Axe. However, the preset on the Axe took about *1 second* to change (I hope that is not normal.)
Next I decided to upgrade the firmware of the Axe to 5.07. I disconnected the MFC, I power cycled the Axe, and did the firmware upgrade. It worked fine. I confirmed 5.07 was installed. I then reset defaults again, for good measure.
I switched back to the first cable (CAT5E). Same behavior - "AXE-FX NAME TIMEOUT". I confirmed the mode and midi was correct on the MFC (again.)
I then checked on the MFC firmware. It was 1.04 (I believe - I'm upstairs typing now, sounds about right.)
I then reset the MFC (powered with #11 held down, confirmed.)
I then powered down the Axe FX, removed the ethernet, and powered it back up. I jammed with a couple presets for a while. That was at least fun.
In some of the search results here, users were reverting back to midi - either single cable 7pin with phantom, or even two generic 5pin with power on the MFC. I gave the latter a shot (I don't have a 7 pin handy.)
I powered the Axe down. I then connected two all-purpose 5pin midi cables (they work - they are the same ones I used on my Vetta in a previous life) - in to out, out to in. I ran power to the MFC. I changed the midi setup to MIDI. I power-cycled it - confirmed the midi setup was MIDI. I then powered up the Axe - same behavior.
Next I remembered reading about the midi thru/out being off by default on the Axe FX II. I reset system defaults again, confirmed it was off, turned it on, and power cycled everything again - same behavior.
Not related to this particular issue, but in troubleshooting this, I noticed that sometimes if I choose a screen from the front panel of the FX, the new screen will pop up, but then it will immediately go back to the previous screen. I'm going to look into that one more - but it seems like it only happened when the MFC was connected.
My conclusion is that something is defective with my very expensive investment, which is unsettling.
Thoughts? Have I missed something?
Thanks in advance.
-Dave
Last edited: