A320 FMGS B34

[jeehell]

Oops sorry Stefan it seems I edited your post instead of creating a new one....

[stefangr]

Oops sorry Stefan it seems I edited your post instead of creating a new one....

Hi JL,

no problem The line StatusTitle=xxx is working fine, thanks.

Stefan

[stefangr]

Hi JL,

in my configuration I have one server PC (FS + JL Server) and one client PC (all JL displays). When I use the starter.exe on the client PC I often have the problem that the opening of all applications stucks somewhere in the middle. For example the FO MCDU is opening up, but not moving to the right place and no further applications are started any more.

I am then closing down the starter on the client PC including all applications, restarting it, and sometimes I need 5 tries until the starter is running through the end, opening all apps and connecting them to the client.

I think it might have something to do with the CPU performance. When the starter runs and opens up the applications, the task manager reports 100% CPU usage. When being in flight later, it only uses about 50-60%. Maybe it would help if the applications are not started up in that fast sequence? Maybe one could have another parameter in the starter.ini to set a pause in seconds before the next application is being started.

Thanks
Stefan

[OmniAtlas]

I think a simple batch file could also be written to delay the next program start.

Did you check the save window position on the display modules?

Regards,
Ben

[stefangr]

I think a simple batch file could also be written to delay the next program start.

Did you check the save window position on the display modules?

Regards,
Ben

Yes, of course the window position is saved, and they are positioned fine if all runs through until the end. But often it stucks.

Regards
Stefan

[adonismartinez]

Good day Jeehell.

Version B34 , works great, specially some mcdu enhancements.

Indeed two things I found with the PTU:

1) A soon as engine two is started (keeping engine one off for a pair of minutes) I can hear the ptu several times:, a pair of thing to consider:

a) The PTU logic is : inhibited during the first engine start and automatically tested during the second engine start. we should hear it only once at start up

b)The power transfer unit came into action automatically when the differential pressure between the green and the yellow systems is greater than 500 PS, but the ptu is not holding the pressure in one of the systems. It is shutting off as soon as pressure equalizes, when presure drops ptu starts again, and this continues intermitently, PTU is supposed to hold pressure, the same thing happened in flight by shutting down one engine driven pump. Also the ecam related memo, showed a dual hydraulic failure...


The PTU therefore allows the green system to be pressurized on the ground when the engines are
stopped with yellow electrical pump on, so in FCTLs page you should be able to move control surfaces, not sure if it actually happens.


Also in flight a single hydraulic failure brings plane into alternate law.... Alternate laws occurs at a double failure of any system

Thanks agains for your assistance, I hope this can be helpful

Best regards.
Adonis

[dodiano]

A single Hydraulic failure does not bring the plane to alternate law. Your statements of the PTU are not correct.

regards

Roberto

[adonismartinez]

Hi Dodiano

Im refering to Jeehells software, thats what happened in my tests flights


In real life nor any single failure will degrade AP modes, dual failures will.

Regards

Adonis

[OmniAtlas]

The PTU is inhibited when:

Ø First engine is being started. This is identified as when the nosewheel steering disconnect pin is in and only one ENG MASTER switch is ON. (PTU operation is tested on second engine start)

Ø Cargo doors are operated (Yellow electric normally powers cargo doors, this prevents draining low output of electric pump or accidentally powering Green Hydraulic)

Ø Parking brake is ON and only one ENG MASTER switch is ON

Ø PTU pb is off

Note: If a cargo door is operated and then the 2^nd engine is started within 40 seconds a PTU fault message may be given (due to inhibition during test period).

[adonismartinez]

Good day Ominiatlas.

Great, you got very accurate things. Also PTU inhibition at start up is designed to not interfere with single-engine-taxi out-procedures.

Best Regards

Adonis