logged SUPPORT REQUESTED: a340-300 / WINWING MCDU Periodic Freezing

[Arty57]

Good day. I have been trying to sort this out ever since initial release (day 1).  Originally the WINWING MCDU did not work with the a340.  Now after five updates to the a340 and a similar amount to SimApp Pro (SAP) the MCDU works, but not consistently or reliably, at least for me.

I am on SAP 1.16.75.  I am on a340-300 1.0.5.  All WINWING hardware has firmware checked and is current.  The symptom of this failure is as follows.  Initialize plane at gate on APU.  Enable SAP.  MCDU and FCU/EFIS come alive and function. Set fuel and weights via EFB and Simbrief. Flight Plan into MCDU via SOP.  When everything is set depart as normal.  Every flight at some point the MCDU freezes.  Screens locked. LSKs and buttons still function as can be seen on virtual cockpit MCDU. Only the physical MCDU is affected and only then the screen.  This usually occurs within the first ten minutes of flight, sometimes sooner, sometimes later.  When this happens a power cycle of my switched and powered USB3 8 port hub restores functionality of the MCDU and it operates without issue until the next occurrence at which time a power cycle is needed again.  Rinse and repeat throughout the entirety of the flight, two, three even five hours.  I have never once experienced a flight without an MCDU freeze and most flights are two or more.

As I type this I am engaged on a test flight KLAS to KBOS.  In the first 30 minutes of this five hour flight I have had two MCDU freezes.  The MCDU is the only component in the WINWING chain that is affected.  The virtual cockpit MCDU and physical FCU and EFIS continue to work as expected and all functions of those components are available.  I have Airbuses from other vendors, Fenix and FSL, that operate the same way (MCDU, FCU/EFIS via SAP) that have dozens of flights each, never once with a lockup or freeze. Only the iniBuilds a340 exhibits this consistent anomalous behavior and failures.  A solution is desired and requested.  Please assist.

-Braun T

Edited December 17, 2025 by Arty57

[Kristof1234]

don't have this issue with the whole wing setup 2 efis fcu and mcdu. Using latest firmware and simapp pro software software also rowsfire overhead panel with mobifilight all works like a charm.

[A340iB-2025]

I do have the same problem as Arty57 with the ww MCDU. On a 1 hour blocktime flight, at least 2 freezes. What I do for now is, changing the MCDU from CPT-side to Copilot-side within the SimAppPro- then it will work again for some time, until the next freeze.

Edited December 18, 2025 by A340iB-2025

[Silo01]

I also see these freezes of the physical mcdu screen. Sometimes it does not freeze for like 6 hours but normally as soon as I have a freeze, on that specific flight it will freeze every like 30 minutes after the initial freeze. Unplugging and re-plugging the mcdu works. I get no freezes in other aircraft than the 340.

[Airbumps2501]

Does anybody know if this may be a WW SimAppPro issue or an issue with the way inibuilds is making the data available to SimAppPro?

I have the same problem and REALLY REALLY REALLY want to just be able to use Spad.Next or Mobiflight to display the MCDU screen as opposed to having to use SimAppPro. Can we get a comment on this from anybody at iniBuilds?

[DISPALL]

1.07 and same issue it freezes constantly, reconnecting helps but yeah it's a bit immersion breaking. I am on the latest update.

[Pilot061]

Same thing happened to me yesterday

[Warper]

Same here.  For my next flight, I'll use the MCDU through Spad.next, without SimApp Pro, to see if the problem disappears. Latest SimApp Pro update and latest MCDU firmware (1.04)

[richboy2307]

Hi everyone

Thanks for your reports.

Our team has investigated the issue, from what we are able to see is that the connection is still open from our module (data is continually transmitting, and being listened to hence why control inputs work), however their module stops rendering the display in such instances. 

We have also raised the same with WINCTRL (previously WW) for further investigation on their end. We are hopeful a solution can be found soon.

Temporary solution is toggle between Cpt or Co-Pilot side in SAP whenever you notice this.
Thanks for your patience meanwhile!

[Warper]

On 1/16/2026 at 9:59 PM, Warper said:

Same here.  For my next flight, I'll use the MCDU through Spad.next, without SimApp Pro, to see if the problem disappears. Latest SimApp Pro update and latest MCDU firmware (1.04)

Yesterday I did a flight of almost 9 hours, with a snippet of spad.next and the latest beta version of Spad.next (the stable version is not yet compatible with Inibuilds CDUs) and it worked perfectly, there was no screen freezing

[Eurosky]

So are you guys getting the Wingwing  FCU, 32 AGP, MCDU etc to work with the Ini A340? I can't get anything to light up. Using latest SimAppPro. Everything working with the Fenix but nothing from Winwing works on the latest Ini A340 on my end. 

Found the problem. I have a dual MCDU setup (Capt & FO). With a dual MCDU setup nothing will work. I assume dual MCDU is not supported. Disabling/unplugging one MCDU and ops normal. 

This is the answer i got from WinWing support in regard to dual MCDU support:

Dear customer, currently due to issues of the Inibuild A340 plane model, we can only support MCDU of Captain side.

Please wait for the plane model manufacturer to update the plane.

Edited Tuesday at 07:07 AM by Eurosky

[IniSteve]

23 hours ago, Eurosky said:

 

Dual support question answered here -