Not really anyway to to determine this aside from trying different things. Assuming both the Axe-Fx and the MFC are set to use the EtherCon port, try a very, very short CAT5 cable.Yes, I just want to know if there's any way to know if the problem is in mfc's hardware or the axe's
when I connect it via expansion
That's what "expansion port" isSo you’re trying to connect it via EtherCon?
Does it work with a 5 pin midi cable
the mfc connects smoothly to the axe via midi
The OP states that it doesn't power on with the expansion port. Regardless of the settings it should power on.While your MFC is connected to the power supply did you make sure you changed the MFC to use the Expansion Port?
From the manual:
3.2 Selecting a Port
The MFC-101 sends and receives data only on one port type at a time. As of MFC firmware 3.0, the default is Ether – the AXE-FX port, where an EtherNet or EtherCON cable can be connected.
1. Press EDIT footswitch to enter EDIT MODE.
2. Press MIDI footswitch for the MIDI menu to arrive at the USE PORT screen:
3. Press INCR or DECR to select “MIDI”, “EXPANSION”, (to use EtherNet/EtherCON) or “FASLINK”. Note that “FASLINK” requires a FASLINK compatible adapter or device such as the XA-2 Axe-Fx II Adapter. Do not connect to XLR audio jacks or damage could occur.
4. Press EXIT to return to PERFORMANCE MODE.
Yes I did thatWhile your MFC is connected to the power supply did you make sure you changed the MFC to use the Expansion Port?
From the manual:
View attachment 61576
Any bent or broken pins in the AxeFx or MFC ethernet sockets?
If a live USB cable had ever been accidentally put into the ethernet/expansion port on the back of the AxeFX at some time in it's past it could have blown some components. You could try lifting the lid on the AxeFX and inspect the resistors etc around the ethernet port to see if any are charred.