Okay I installed the service pack release a couple weeks or so ago and I set FSX to startup in the 2d panel mode. I configure the FA to do a Apu start, he does all his flow up to the point of switching the apu on but he doesn't do it properly as he on presses the switch down to the on position instead of switching the switch down to start. He then waits and then switches the two switches for teh apu to start providing power to teh plane but nothing happens because teh APU hasn't spooled up. After this happens I have to do it myself and then when it comes to calling the ground crew or using the pa nothing happens. What am I doing wrong?? To get FS2Crew working properly I have to shut FSX down and restart it.

I've had the FO start the APU but not bring it online. I just do that bit myself, if he forgets :Thinking:

Doen't happen everyflight, maybe twice over about 10 flights.

 

Not sure why this happens, perhaps he's just having a bad day.

 

It doesn't affect anything and we just continue like nothings happened :Waiting:

 

Clive

when it comes to calling the ground crew or using the pa nothing happens

 

Hi,

 

Did you check the manual?

 

The audio control panel needs to be setup properly in order to communicate with ground.

 

APU I'm not so sure about... that's never happened to me.

Well it does effect me somehow because everytime the FA doesn't start the APU properly the preflight check list goes wrong because when the window heats are on and I say On he says 'Are you sure about that?' and then when I go to call ground for push back, I have the intcom switches switch on as they should be as per the manual and yet I get no response. Having restarted the FSX and when the Apu is started properly the checklist runs okay and I do get a response from ground etc.

Doen't happen everyflight, maybe twice over about 10 flights.

 

I'm interested in those 2 times. Is there a pattern? Were you doing something different?

Bryan,

 

I've been running the same flight (EGBB>LEMD) for sometime. I'm not sure if there is, to be honest, because I didn't take much notice when he missed it.

 

I will keep an eye on it to see if/when it happens again and what I was doing different.

 

I will let you know

 

Clive

Bryan,

I posted about this same problem earlier in the forum. I have yet to get the FO to start APU properly and I have to start it myself. I tried disabling ezdok to make sure it started in 2d mode and that didn't help either. Any suggestions to try would be great.

Bryan,

I posted about this same problem earlier in the forum. I have yet to get the FO to start APU properly and I have to start it myself. I tried disabling ezdok to make sure it started in 2d mode and that didn't help either. Any suggestions to try would be great.

 

Check your PMs.

 

We'll see if V1.2 helps you.

Hello Bryan,

 

I am currently experiencing the same problem. The FO doesn't start the APU as per CFG and all I hear is the battery discharge alarm. It has only started doing this since yesterday. I did some CFG mods yesterday in case that might be involved. Any suggestions please?

 

Thanks

 

Gareth Wilkinson

It has only started doing this since yesterday. I did some CFG mods yesterday

 

What CFG mods did you make? I suspect that's the problem if it just stopped working.

 

Cheers,

I boiled it down to the PMDG C&D option. In that Mode the FO doesn't actually succeed in starting the APU. He throws the switch OFF-ON-START, but the FAULT light remains lit and the EGT doesn't rise. He brings in the APU GEN and two fuel pumps (FWD 1, Centre L) but to no avail and the batt. continues to discharge. I can manually start the APU at that point and bring in the GEN - FS2Crew Voice control will then proceed normally from there.

 

I have a work-around which may help some. When I load the NGX the panel state defaults to Battery ON, APU running, and IRS to NAV. I then get to C&D state by turning all three OFF. It appears no different to the PMDG C&D, except that FS2Crew then runs by the book. No issues. I can happily live with this.

 

Also, in case this helps, I load my FSX to the Free Flight screen with the default C172, and 2-D cockpit set in FSX). I find I can leave EZCA enabled. I then LOAD a saved situation that puts my NGX/800 at my departure APT straight into in VC mode. Then as I say, I turn all the power off and FS2 Crew runs as per normal.

 

I should mention that I reinstalled FS2Crew 1.4 and also the NGX SP1c. I also let FSX rebuild fsx.cfg but it made no difference to my problem. I am back to my original .cfg file which I am happy with. I also did two system restores but they too made no difference either.

 

Hope this helps. And I realise there are other quicker-into-the-air options in F2Crew!

 

Regards,

 

Gareth Wilkinson

Also, in case this helps, I load my FSX to the Free Flight screen with the default C172,

 

Read the Introduction to the 737NGX. PMDG say you should not do this, you should select the NGX wit the default microlight in the window.

 

Iain Smith

Thanks Iain, I have read that recommendation of course, but I've been loading up to the Trike most of the week and it didn't affect the problem one way of the other. It's not a issue though to load to the Trike again as I don't fly either that or the C172, but saw them as equally 'default'. I would defer to PMGD's advice re their own product so I appreciate the reminder.

 

Regards,