MFC-101 connected to Axe-FX II does nothing.

[Robboman]

I had a similar problem, turned out to be physical connection of the rj-45 jack to the plug on the cable. In my case, simply bending the plastic tab thingy on the cable somewhat outwards caused the plug to seat into the jack more firmly.. the pins in the jack need to be straight to properly seat themselves into the little slots on the plug.

Look closely inside the jack (on both the MFC and the Axe) to see if the pins look straight.. I think I read where someone else reached in and re-aligned\straightened the pins using a small screwdriver or something.

All in all.. way to flakey for me, I went back to a single 7-pin midi cable with wallwart in the rack.

 

[dbarrow]

I had a similar problem, turned out to be physical connection of the rj-45 jack to the plug on the cable. In my case, simply bending the plastic tab thingy on the cable somewhat outwards caused the plug to seat into the jack more firmly.. the pins in the jack need to be straight to properly seat themselves into the little slots on the plug.

Look closely inside the jack (on both the MFC and the Axe) to see if the pins look straight.. I think I read where someone else reached in and re-aligned\straightened the pins using a small screwdriver or something.

All in all.. way to flakey for me, I went back to a single 7-pin midi cable with wallwart in the rack.

Upon further inspection, the 7-pin cable didn't work properly, either. I was getting "Name Timeout" on the MFC, so I suppose there wasn't two-way communication using the MIDI cable either. I sent the unit back to Fractal, since it was clearly defective.

 

[RockeRx]

Hi dbarrow, I was wondering if you could tell me if/how this issue was resolved. I've been having the exact same problem using the cat5 since I got my MFC last year, despite trying all of the usual suggestions. As a result, I'm using midi and the wall wart but would obviously prefer cat5. Did this end up being a defective MFC?