ATTENTION!! This is not a "bash FW or MRC" thread! This thread is for pilots to report issues with the MCB-E on their new planes ONLY!
So after getting the new F/A-18C and not having an issue with the MCB-E like I did with the L-39 and F-22, I decided to do an experiment as the F-18 got a Graupner RX versus the XPS RXs I was using in the other two. I found that swapping out the XPS RX in the F-22 for a Graupner RX solved my issue with that bird.
Since so many people are having issues with the Multi-function Control Box E (MCB-E), I thought I'd start a thread for everyone to post up their specific issues with it, and what you did to solve them, if anything. Maybe with enough information Freewing and Motion can figure out what specifically to look at for a fix. If they keep putting the MCB-E in new releases without any changes, there will be a lot of unhappy folks when they get their new plane and it doesn't work right or causes a crash on maiden. I hope that this thread can assist FW and MRC with improving the quality of the MCB-E.
So here's what I'm asking everyone to do. If you have or have had issues with control surfaces acting crazy when you have everything hooked into the MCB-E, post up all of the details you can regarding the issue, including any changes to the power system from stock, what brand and type of RX, etc. See my examples below.
To date, the MCB-E has been included in the following planes:
L-39 80mm
F-22 90mm
F/A-18C 90mm
I have had all 3, so here's what I've observed.
L-39
First pre-order, all stock, everything hooked to the MCB-E
XPS Nano2 end-pin 6-ch RX
JR XP9303 converted to 2.4GHz using the XPS radio module
Upon initially hooking everything up stock to my RX, the rudder and nose steering stopped working when the landing gear was deployed. When the gear was retracted, the rudder worked fine (and the nose steering was disabled as normal). Nothing I did solved the issue until I unplugged the rudder and nose steering from the MCB-E and put them on a Y-harness direct to the RX. After that, everything worked fine and I had no issues for the time I had the plane (20+ flights). I had originally submitted a ticket with MRC for a replacement MCB-E. When it finally came in I installed it in stock form and once again had the rudder issue. Original was sent back to MRC, and they said it worked fine in testing.
F-22
First pre-order, all stock, everything hooked to the MCB-E
XPS Nano2 end-pin 6-ch RX with the X10 channel expander
JR XP9303 converted to 2.4GHz using the XPS radio module
Upon initially hooking everything up stock to my RX, the rudder and nose steering stopped working when the landing gear was deployed, and both rudder servos and the steering servo would chatter and deflect the rudders up to 8mm. When the gear was retracted, the rudders worked fine (and the nose steering was disabled as normal). Nothing I did solved the issue until I unplugged the rudders and nose steering from the MCB-E and put them on a tri-harness (used for landing gear) direct to the RX. After that, everything worked fine and I had no issues from then on. Eventually I converted the power system from stock 6S to a JF90 12S system with a Castle CC20 Pro BEC. I never tried putting everything back stock on the MCB-E and just left the rudders and steering Y'd direct to the RX.
Today I made two flights with the F-22 still using XPS and rudders/steering removed from the MCB-E. I recently bought a Graupner Mz-24 and have been slowly converting all my planes over. So I decided to do that with the F-22 today after returning home from the field. But first I wanted to see if I still had the same issues as I had not tried it with the new power system. Hooked everything back up to the MCB-E, and the gremlins returned. So I pulled out the XPS RX and put in a Graupner GR-16L with everything hooked to the MCB-E, and now it works fine.
F/A-18C
First pre-order, all stock, everything hooked to the MCB-E
Graupner GR-16L RX
Graupner Mz-24
Everything worked correctly out of the box, no issues. Maiden flight plus one today, no issues.
So after getting the new F/A-18C and not having an issue with the MCB-E like I did with the L-39 and F-22, I decided to do an experiment as the F-18 got a Graupner RX versus the XPS RXs I was using in the other two. I found that swapping out the XPS RX in the F-22 for a Graupner RX solved my issue with that bird.
Since so many people are having issues with the Multi-function Control Box E (MCB-E), I thought I'd start a thread for everyone to post up their specific issues with it, and what you did to solve them, if anything. Maybe with enough information Freewing and Motion can figure out what specifically to look at for a fix. If they keep putting the MCB-E in new releases without any changes, there will be a lot of unhappy folks when they get their new plane and it doesn't work right or causes a crash on maiden. I hope that this thread can assist FW and MRC with improving the quality of the MCB-E.
So here's what I'm asking everyone to do. If you have or have had issues with control surfaces acting crazy when you have everything hooked into the MCB-E, post up all of the details you can regarding the issue, including any changes to the power system from stock, what brand and type of RX, etc. See my examples below.
To date, the MCB-E has been included in the following planes:
L-39 80mm
F-22 90mm
F/A-18C 90mm
I have had all 3, so here's what I've observed.
L-39
First pre-order, all stock, everything hooked to the MCB-E
XPS Nano2 end-pin 6-ch RX
JR XP9303 converted to 2.4GHz using the XPS radio module
Upon initially hooking everything up stock to my RX, the rudder and nose steering stopped working when the landing gear was deployed. When the gear was retracted, the rudder worked fine (and the nose steering was disabled as normal). Nothing I did solved the issue until I unplugged the rudder and nose steering from the MCB-E and put them on a Y-harness direct to the RX. After that, everything worked fine and I had no issues for the time I had the plane (20+ flights). I had originally submitted a ticket with MRC for a replacement MCB-E. When it finally came in I installed it in stock form and once again had the rudder issue. Original was sent back to MRC, and they said it worked fine in testing.
F-22
First pre-order, all stock, everything hooked to the MCB-E
XPS Nano2 end-pin 6-ch RX with the X10 channel expander
JR XP9303 converted to 2.4GHz using the XPS radio module
Upon initially hooking everything up stock to my RX, the rudder and nose steering stopped working when the landing gear was deployed, and both rudder servos and the steering servo would chatter and deflect the rudders up to 8mm. When the gear was retracted, the rudders worked fine (and the nose steering was disabled as normal). Nothing I did solved the issue until I unplugged the rudders and nose steering from the MCB-E and put them on a tri-harness (used for landing gear) direct to the RX. After that, everything worked fine and I had no issues from then on. Eventually I converted the power system from stock 6S to a JF90 12S system with a Castle CC20 Pro BEC. I never tried putting everything back stock on the MCB-E and just left the rudders and steering Y'd direct to the RX.
Today I made two flights with the F-22 still using XPS and rudders/steering removed from the MCB-E. I recently bought a Graupner Mz-24 and have been slowly converting all my planes over. So I decided to do that with the F-22 today after returning home from the field. But first I wanted to see if I still had the same issues as I had not tried it with the new power system. Hooked everything back up to the MCB-E, and the gremlins returned. So I pulled out the XPS RX and put in a Graupner GR-16L with everything hooked to the MCB-E, and now it works fine.
F/A-18C
First pre-order, all stock, everything hooked to the MCB-E
Graupner GR-16L RX
Graupner Mz-24
Everything worked correctly out of the box, no issues. Maiden flight plus one today, no issues.
Comment