PMDG737-700 WONT FLY SID

[sbish149 0]

When i load the sid TNT3E from EGBB, fly runway heading,engage AP,lnav and vnav all is fine untilit needs to make a left turn to follow the sid (D018I), instead it does a right turn of about 180deg, ignores D018I and heads direct to DTY34.If i intercept the fmc and adjust heading by 30deg left,start the left turn, then click lnav it follows thepath correctly.A friend of mine has the 737-800 and it flys the sid perfectly and he tells me a lot has changed software wise and i should get the 737-800/900, surely as i have only recently purchased this i dont need to spend another

[Guest gmcallis]

When i load the sid TNT3E from EGBB, fly runway heading,engage AP,lnav and vnav all is fine untilit needs to make a left turn to follow the sid (D018I), instead it does a right turn of about 180deg, ignores D018I and heads direct to DTY34.If i intercept the fmc and adjust heading by 30deg left,start the left turn, then click lnav it follows thepath correctly.A friend of mine has the 737-800 and it flys the sid perfectly and he tells me a lot has changed software wise and i should get the 737-800/900, surely as i have only recently purchased this i dont need to spend another

[sbish149 0]

Graham, I think you have answered my question and i should have known better, i thought by engaging the autopilot sooner it would help.I just know ran this again and didnt select AP till 1100ft and it followed the path (ie turnrd left) albeight a bit wide but thats to be expected i guess.CheersSteve bishop

[ronzie 21]

Graham is on the right track. In order to make that 90 degree turn being that the runway is so close to that waypoint, it would have to do a curve restricted by bank angle. That curve would be on the inside never passing over that waypoint and that cornering might start two miles before that waypoint. You are still over or on the runway at that point.Check the SID chart and see if that is a fly over or fly by waypoint. If it is a fly over you will have to manually fly over it overshooting it and the line yourself up with the next waypoint using HDG if you want to engage the CMD control. If it is a fly by you can turn manually before it abandoning runway heading. Either leave that first waypoint out of the flight plan or after turning via manual or MCP HDG toward the second, if the LEGS stack does not "POP" do a direct-to by LSKing the second waypoint name, then LSK the top missed waypoint, and activate/exe the change. This will give you the course from your present position to that second waypoint.

[G-CIVA 62]

You may also wish to delay you flap retraction & perhaps fly the initial departure at V2 +10/20 kts using SPD INTV, this will reduce the turn radius whilst keeping the SPD (the departure) under control.Kind RegardsSteve Bell

[sbish149 0]

Ok im back on this topic again as similair keep happening on different departures,ie turns left should be right or wont turn at all.For the moment im not going to go into too much detail,I have tested the same routes, same set ups on a friends 737/800 model and this model flys the problem departures on mine with no problem and with no intervention from the pilot.I understand that there are various ways to overcome this prob i have but the question remains:-Why does the 737/800/900 model fly these dep with no problem but the 737/600/700 model not without intervention from the pilot???Any thoughtsSteve Bishop

[DLP084 5]

Hi, there were some changes in the SID/STAR interpretation (for example "turn right direct to fix") with the 800/900. The core 600/700 doesn't support them unless you upgrade them with the 800/900 package. Jan-Paul Schuchna

[downscc 1,327]

No thoughts on why the two models differ... all I know is they are both quite old and when I became interested in creating sidstar files I was using the 800/900 add-on. However, I do have an idea on how to fly the SID based on my actual instrument time and that is you need to be flying the departure using the automation as a tool. I'd like to see the SID chart but I am at work and it will have to wait until I get home to log on to eurocontrol but it looks like it is designed for manual intervention. It certainly isn't a RNAV (RNP) procedure, which do allow the automation to take over most of the workload. No RNAV DP is going to be designed with a 90-deg turn one mile from the runway... that is a moderate risk maneuver that needs a pilot in the loop.

[sbish149 0]

No thoughts on why the two models differ... all I know is they are both quite old and when I became interested in creating sidstar files I was using the 800/900 add-on. However, I do have an idea on how to fly the SID based on my actual instrument time and that is you need to be flying the departure using the automation as a tool. I'd like to see the SID chart but I am at work and it will have to wait until I get home to log on to eurocontrol but it looks like it is designed for manual intervention. It certainly isn't a RNAV (RNP) procedure, which do allow the automation to take over most of the workload. No RNAV DP is going to be designed with a 90-deg turn one mile from the runway... that is a moderate risk maneuver that needs a pilot in the loop.

http://www.nats-uk.ead-it.com/aip/current/...EGBB_6-5_en.pdfRegardssteve

[downscc 1,327]

Per chart thanks to steve's attch:Climb straight ahead to I-BIR D1 or 500' QFE whichever is later, then turn right onto track 169

[sbish149 0]

OK I purchased the 800/900 model which has cured all my sid problems i was having.To me this indicates there is a problem with the 600/700 series.Anyway new problem now just on the 800/900 which is, the spd rest 0/flap problem in fmc which i have seen on this forum before.Basically as soon as you engage flaps your speed rest will drop to 0 not flap manov speed.I have uninstalled both models and reinstalled but still the problem exists on 800/900 any help appreciatedsteve bishop

[downscc 1,327]

The speed restraint 0 problem is due to a corrupt 737guages.ini file in the pmdg folder. Not sure what caused it, but if the installer has a repair option I would try it.

[sbish149 0]

The speed restraint 0 problem is due to a corrupt 737guages.ini file in the pmdg folder. Not sure what caused it, but if the installer has a repair option I would try it.

I cant see a repair function in the installer and did look in the guages.ini file as i had seen you suggested before but not sure what im looking for in there and what to change.can you guide me anymore in regards to this ini.file??Thankssteve bishop

[downscc 1,327]

Here is what the PFD section in mine looks like:

[PFD]VLE=270.0FlapPositions=9// Default Values (for 700 too)VMaxFlaps=340.0, 250.0, 250.0, 250.0, 210.0, 195.0, 170.0, 165.0, 156.0//Specific values for -600VMaxFlaps_600=340.0, 250.0, 250.0, 250.0, 210.0, 185.0, 175.0, 160.0, 155.0//Specific values for -700VMaxFlaps_700=340.0, 250.0, 250.0, 250.0, 210.0, 195.0, 170.0, 165.0, 156.0

I believe this is where the speed constraints for flap position comes from.

[sbish149 0]

Here is what the PFD section in mine looks like:

[PFD]VLE=270.0FlapPositions=9// Default Values (for 700 too)VMaxFlaps=340.0, 250.0, 250.0, 250.0, 210.0, 195.0, 170.0, 165.0, 156.0//Specific values for -600VMaxFlaps_600=340.0, 250.0, 250.0, 250.0, 210.0, 185.0, 175.0, 160.0, 155.0//Specific values for -700VMaxFlaps_700=340.0, 250.0, 250.0, 250.0, 210.0, 195.0, 170.0, 165.0, 156.0

I believe this is where the speed constraints for flap position comes from.

This is mine located in c/program files/microsoft games/fsp/pmdg[PFD]VLE=270.0FlapPositions=9// Default Values (for 700 too)VMaxFlaps=340.0, 250.0, 250.0, 250.0, 210.0, 195.0, 170.0, 165.0, 156.0//Specific values for -600VMaxFlaps_600=340.0, 250.0, 250.0, 250.0, 210.0, 185.0, 175.0, 160.0, 155.0//Specific values for -700VMaxFlaps_700=340.0, 250.0, 250.0, 250.0, 210.0, 195.0, 170.0, 165.0, 156.0Looks the same to me, the only other folder i can see with flaps in is hereC:\Program Files\Microsoft Games\Flight Simulator 9\Aircraft\PMDG737-800and there is a cfg file in here[Flaps.0]type=1span-outboard=0.690extending-time=35.000system_type=1damaging-speed=260.000blowout-speed=280.000lift_scalar=1.000drag_scalar=1.000pitch_scalar=1.00flaps-position.0=0.000, 0.000flaps-position.1=1.000, 0.000flaps-position.2=2.000, 0.000flaps-position.3=5.000, 0.000flaps-position.4=10.000, 0.000flaps-position.5=15.000, 0.000flaps-position.6=25.000, 0.000flaps-position.7=30.000, 0.000flaps-position.8=40.000, 0.000[Flaps.1]type=1span-outboard=0.950extending-time=35.000system_type=1damaging-speed=250.000blowout-speed=270.000lift_scalar=1.000drag_scalar=0.000pitch_scalar=-30.0flaps-position.0=0.000flaps-position.1=2.000flaps-position.2=3.000flaps-position.3=4.725flaps-position.4=0.000flaps-position.5=0.000flaps-position.6=0.000flaps-position.7=0.000flaps-position.8=0.000[Flaps.2]type=1span-outboard=0.950extending-time=35.000system_type=1damaging-speed=220.000blowout-speed=230.000lift_scalar=-1.000drag_scalar=0.000pitch_scalar=-30.500flaps-position.0=0.000flaps-position.1=0.000flaps-position.2=0.000flaps-position.3=0.000flaps-position.4=2.000flaps-position.5=2.000flaps-position.6=4.500flaps-position.7=8.000flaps-position.8=8.000[Flaps.3]type=2span-outboard=0.001extending-time=7.5system_type=1damaging-speed=250.000blowout-speed=270.000lift_scalar=0.000drag_scalar=0.000pitch_scalar=0.000flaps-position.0=0.0flaps-position.1=25.0flaps-position.2=25.0flaps-position.3=25.0flaps-position.4=25.0flaps-position.5=40.0flaps-position.6=40.0flaps-position.7=40.0flaps-position.8=40.0is there anything here which does not look right??By the way i did find the repair tool on the installer but that didnt work either..Regardssteve