PMDG WIND DATA REQUEST feature readme

03SEP13
================================================================================
====================
This folder exists to enable FMC WIND DATA REQUEST functionality, currently avai
lable in the
PMDG 777 product line.
The feature currently requires some text editing steps to use. We expect automat
ed support from the
major weather programs (AS2012, Opus, REX, FSGRW etc.) soon.
If you are a developer of a weather program and wish to support the feature auto
matically, see the
description of the format below. The FMC is programmed to accept this format and
you will need to
provide an option in your program that allows for the export of a file to our fo
lder using this
exact format. Please contact Ryan Maziarz at rmaziarz@precisionmanuals.com if yo
u have any questions
about supporting this feature.
================================================================================
====================
Here are the steps to produce a file that the FMC can use for the WIND DATA REQU
EST feature with
AS2012's tab-delimited format (which we've chosen to use for our file):
1. Plan a flight using your choice of flight planner.
2. Export the full route, including SIDs and STARs, to the FSX .pln format. The
full route is not
required explicitly - the system will match whatever waypoints exist in the FMC'
s flightplan - but
if you do include the full route it will allow the FORECAST entries to populate
as well.
3. In AS2012, import the .pln you created in step 2 on the Flight Plan page and
process it.
4. In the lower output window of AS2012's Flight Plan page, find the "Winds alof
t by waypoint:"
section.
5. Copy this section starting and ending with the lines that have the departure
and arrival airports
on them. Do not copy the header lines that say 6K, 30K and so on. Make sure you
copy the line below
the line with the destination airport on it too as this contains the higher alti
tudes.
It should look like this in the example of a KPHX to KSFO route:
KPHX
16)

186@02(24)

190@03(20)

159@18(-31)
112@14(-73)

221@07(8)

160@24(-40)

185@09(-6)

149@24(-52)

163@12(-

143@20(-66)

BXK
155@10(-16)

273@03(23)

250@03(19)

240@05(7)

173@08(-5)

138@14(-31)
139@18(-40)
134@28(-52)
138@31(-65)
107@22(-74)
CURIV 257@07(22)
250@08(19)
212@08(7)
184@11(-6)
166@14(17)
163@19(-31)
172@23(-41)
181@34(-53)
167@31(-65)
142@13(-71)
DECAS 253@05(21)
243@07(19)
212@10(7)
159@10(-6)
159@14(17)
171@20(-32)
167@26(-41)
165@34(-53)
163@32(-65)
139@14(-71)
PMD
139@03(19)
156@07(16)
206@14(8)
186@14(-6)
189@12(-17)
157@20(-32)
140@29(-41)
144@33(-53)
147@23(-65)
172@11(-71)
LANDO 170@05(19)
164@08(16)
205@16(7)
191@16(-6)
190@13(17)
167@20(-32)
154@27(-41)
155@30(-53)
159@24(-65)
174@12(-71)
AVE
200@05(18)
195@09(16)
199@18(6)
201@27(-6)
207@22(-16)
181@25(-31)
173@29(-41)
167@30(-53)
177@20(-65)
185@16(-70)
BSR
277@07(14)
218@12(14)
202@23(6)
209@31(-6)
212@37(-17)
206@51(-31)
196@58(-42)
197@54(-52)
208@46(-64)
189@25(-68)
CARME 277@07(14)
218@12(14)
202@23(6)
209@31(-6)
212@37(17)
206@51(-31)
196@58(-42)
197@54(-52)
208@46(-64)
189@25(-68)
ANJEE 277@07(14)
218@12(14)
202@23(6)
209@31(-6)
212@37(17)
206@51(-31)
196@58(-42)
197@54(-52)
208@46(-64)
189@25(-68)
SKUNK 277@07(14)
218@12(14)
202@23(6)
209@31(-6)
212@37(17)
206@51(-31)
196@58(-42)
197@54(-52)
208@46(-64)
189@25(-68)
BOLDR 277@07(14)
218@12(14)
202@23(6)
209@31(-6)
212@37(17)
206@51(-31)
196@58(-42)
197@54(-52)
208@46(-64)
189@25(-68)
MENLO 277@07(14)
218@12(14)
202@23(6)
209@31(-6)
212@37(17)
206@51(-31)
196@58(-42)
197@54(-52)
208@46(-64)
189@25(-68)
KSFO
277@07(14)
218@12(14)
202@23(6)
209@31(-6)
212@37(17)
206@51(-31)
196@58(-42)
197@54(-52)
208@46(-64)
189@25(-68)
6. Paste that section into a new text file and save it in the <FSX root folder>\
PMDG\WX folder with
the naming convention ICAO1ICAO2.wx. For the example above this would be KPHXKSF
O.wx
7. Press WIND DATA REQUEST at LSK 6R on the WIND page in the airplane and it wil
l automatically

load these values into the FMC. Note that it is best if your cruise altitude is
already entered on
the PERF INIT page before you do this as it helps the algorithm narrow down the
correct altitudes
to use.
================================================================================
====================
If you are using a weather program other than AS2012, you can make this work wit
h a bit of manual
editing to get it into the tab-delimited format AS2012 uses. As programs add aut
omated support for
the feature, this will not be necessary:
WAYPOINT

(wind direction)@(winds speed)(temperature)

The altitudes that need to be included in the tab-delimited table for each waypo
int are:
6000
30000

9000
34000

12000
39000

18000
44000

24000
49000

The FMC will automatically select suitable altitude values for every waypoint of
the flightplan,
including the FORECAST entries.