Old 744 Forum

Archived posts

IDU automatic switching

Page: 1

Author Post
Member
Registered: May 2010
Posts: 99
Location: Brussels
Hi |-|ardy,

Could you have a look at this please?

PSX version 10.0.4
Situ Training 705 - TO E

Captain outboard DU failure during takeoff roll.
No automatic transfer to inboard DU.

According to FCOM 10.20 Display Failure Automatic Switching I'm under the impression that with both inboard and lower display selectors in NORM the PFD should automatically have been displayed on the inboard DU.

Regards,
Sylvain
Member
Registered: Apr 2012
Posts: 68
Hello Hardy,

I can confirm same occurrence in the same situ (i.e. no automatic transfer) since 10.0.2 (when I first noticed it 8) ).

I was under the similar impression as Sylvain (but I am armchair captain only :) ).

Cheers,
_______________
Andrej
Member
Registered: May 2010
Posts: 843
Perhaps an internal IDU processor failure which fails to recognise that its CRT/LCD screen has failed? :P

If the CB for the IDU is pulled in this scenario, the PFD will switch to the Inboard IDU (The EIU recognises the IDU power failure).

Rgds
JHW
Moderator
Registered: May 2009
Posts: 5140
Intentional. See tooltip text on outboard IDU malfunction.
Moderator
Registered: May 2009
Posts: 5140
Hi all,

if the current malfunction design is too confusing, I'll consider a slight change for the next PSX update.

The current design has three variations:

1. Fault in brightness control: Undetected flicker, hence no automatic transfer.
2. Fault in screen control: Undetected blackout, hence no automatic transfer.
3. Power loss in IDU: Detected fault, hence with automatic transfer.

I designed it this way simply to provide three different training scenarios:

1. Flicker (instruments still legible): Distract the pilot.
2. Undetected blackout: Force the pilot to transfer the IDU manually.
3. Detected fault: Demonstrate an automatic transfer.



Suggestion for a new design:

1. Flicker with long blackout pauses: Force the pilot to transfer the IDU manually.
2. Detected fault, programmed on Instructor: Demonstrate an automatic transfer.
3. Detected fault, consequence of power loss: Demonstrate an automatic transfer.



Like before, the three variations are linked as follows:

1. "Severe" is not selected on malfunctions menu.
2. "Severe" is selected on malfunctions menu.
3. Triggered by electrical system consequences.

The advantage here: variation #2 can also be triggered by the Instructor tools, and not only by electrical system consequences.


So, keep it or leave it? Any opinions? :-)


Cheers,

|-|ardy
« Last edit by Hardy Heinlin on Fri, 15 May 2015 15:49:41 +0000. »
Moderator
Registered: May 2009
Posts: 5140
The new IDU malfunction design is now implemented in 10.0.5-beta9 (item 0.5.0045):

http://aerowinx.com/forum/topic.php?id=2939


|-|ardy
Member
Registered: May 2010
Posts: 99
Location: Brussels
Great stuff Hardy! 👍🏼

Thanks,
S.

Page: 1

Old 744 Forum is powered by UseBB 1 Forum Software