Page 1 of 1

Problem with MCDU CPT

Posted: Sun Jan 05, 2025 12:26 pm
by dkreiskott
Hello Jean Luc,

there is a problem with the CPT MCDU.
The MCDU sometimes only reacts after 1-2 seconds to a key press and only if you hold the key down.
At first I thought that my MCDU was defective. But that is not the case.
I carried out the following tests:

1. Replaced USB cable, no change

2. MCDU in the Skalarki Profiler in test mode reacts immediately to every key press.

3. All displays (SD/EWD/ND/PFD) closed only both MCDUs are active, MCDU CPT still do not react immediately.

4. The MCDU CPT was flashed to MCDU FO using firmware from Skalarki. The MCDU reacts immediately to every key press.

5. MCDU flashed back to CPT, then the key delay is back!

The MCDU is not really usable like this because constant key presses are not recognized. I would urge you to check this.

The latest version 61.11 is in use
Thanks and regards

Re: Problem with MCDU CPT

Posted: Sun Jan 05, 2025 1:09 pm
by jeehell
Hello

I do not have any other reports, I do not have any skalarki hardware to test on, and I haven't made any changes in skalarki interface for a long time...
Have you tested through the GUI MCDU to see if it reacts normally? Is it on a remote PC? Antivirus or firewall?

Re: Problem with MCDU CPT

Posted: Sun Jan 05, 2025 1:28 pm
by dkreiskott
Hello Jean Luc,
thanks for the quick reply.

The configuration is as follows with 2 computers.

Computer1:
P3D v5.4, FMGS Server, EGPWS, Sound, Intercom, IO Skalarki for FCU, EFIS, L/D Gear and Loudspeaker Panel

Computer2:
all Upper Pedestal Components from Skalarki, Lower Pedestal from FSCockpit

The firewall is deactivated and no antivirus is installed on both PCs.
I have also deactivated Microsoft Defender.

Both computers are Intel i7 with 32 and 16 GB RAM and fast graphics cards. The computers shouldn't be the problem.

I've had this problem since a few months now and always thought that the hardware was defective.
I've tried various things but never found a solution.

So this morning I started to rule it out using the firmware, as my FO MCDU always works perfectly.

What surprises me is that if I switch off the correct FO MCDU and flash the CPT MCDU to FO, it then works perfectly.

I tested what happens when I run the CPT MCDU on Computer1, but the problem is there too, nothing changes.

No, I haven't tested the GUI MCDU, but I can still do that.

Re: Problem with MCDU CPT

Posted: Mon Jan 06, 2025 1:09 pm
by dkreiskott
Today I have tested the GUI MCDU.
It works perfect on every click, no delay.

Question for the others with Skalarki MCDU.
Which Profiler version are you using (i.e. 5.1.xxxxxxx) and has anyone ever had the problem with the key delay on the CPT MCDU?

Re: Problem with MCDU CPT

Posted: Mon Jan 06, 2025 5:07 pm
by balu69
Hi Dieter
i have the 5.1.600.1000 and have no problem with delays.

Re: Problem with MCDU CPT

Posted: Mon Jan 06, 2025 9:32 pm
by jeehell
The soft MCDU and the hardware one more or less use the same mechanism for sending keys...
Have you tried to flash CPT MCDU firmware on your physical FO MCDU?
Have you tried unplugging all other hardware except the defective MCDU?
In skalarki profiler, in test mode, do you see any buttons that may be blocked in pushed position?

Re: Problem with MCDU CPT

Posted: Tue Jan 07, 2025 8:01 am
by dkreiskott
jeehell wrote: Mon Jan 06, 2025 9:32 pm The soft MCDU and the hardware one more or less use the same mechanism for sending keys...
Have you tried to flash CPT MCDU firmware on your physical FO MCDU?
Have you tried unplugging all other hardware except the defective MCDU?
In skalarki profiler, in test mode, do you see any buttons that may be blocked in pushed position?
No, I did not flash the FO MCDU as a CPT, but I can still try that.
Yes, I connected the MCDU to the Prepar3d computer (1) via USB, there is no other USB hardware from Skalarki there, but that is where the problem also occurs.
In test mode, every button on the CPT MCDU works immediately, which is also the reason why I don't think it is defective.

I have since installed the latest version of Profiler, but that hasn't worked either, no change.
I'm slowly running out of ideas as to what could be wrong.