cessna729

Sorry for double post, having problems with a firewall!! cessna729.

Hi Stefan, Have you had a look at the LOWG.xml file in your LevelD folder to see how Navigraph have coded the ABIRI 1G SID? I'm not at my X-Plane PC at the moment so cant check, but the JEPPESEN LOWG/GRZ ABIRI ONE GOLF SID I have to hand (it's a bit old, 27May09) says; "Climb on 168 deg track, when passing GRZ-NDB and 2200ft turn RIGHT 270 deg heading, intercept GRZ R-238 to ABIRI." And it also states that "a minimun climb gradient is required of 468ft per nm (If unable to comply to use SID GRZ-2X)", and "all initial turns with MAX 205kts and a bank angle of at least 20deg." IMHO, it appears that the path GRZ-VOR to initiation of the RIGHT turn should Terminate upon two things happening "passing GRZ-NDB and 2200ft" Does it look like the Navigraph data complies? My guess is Navigraph have coded it as seperate paths; 1st path terminates passing GRZ-NDB, then 2nd path contant Hdg till terminating at 2200ft. hense the CRJ-200 (good-ol-girl that she is) just does what she's been told to do (by Navigraph data), but if you pass 2200ft before GRZ-NDB, the 2200A waypoint never gets triggered. One thing the CRJ-200 may not like is if Navigraph use the same waypoint names "GRZ" for the VOR and "GRZ" for the NDB and possibly even (GRZ) for the conditinal waypoints (as in previous posts). cessna729.

Hi joga, Yes it appears that if the Navigraph data has 2 or more Waypoint's of the same type within the same sub-section of the SID, STAR, Transition or Approach you "may" encounter a problem. As you noticed the names need to be "unique". I just modified all the offending BIG's in the Bigin Hill Transition to be "unique" and meaningful. eg BIG_R279 for "cross the 279deg radial of the BIG VOR", BIG_R295 for "crossing the 295deg radial" ect. but they could probably be almost anything as long as they are "unique". Now I'll leave you all in peace, and return to trying to get my missing (banned/Special) KASE approaches working. 8-) cessna729

Never said that! though she still does have a few problems with Holding The dips in fps that I have recorded, (are IMHO caused by the FMS's calculation of "conditional waypoints and dealing with "suss Navigraph data at the same time), have never given me problems on my Windows 7 64bit machine, but I suspect that other users on less spec'd hardware or much more likely who are running other programs/background proceses are experencing "stutters", which detract from their enjoyment of flying such a fantastic aircraft. Sign me up, I'd go for it!! Come off it. Given what you and Javiar have achieved with the CJR-200 in the last year, I'd put money on it. Any who.. thanks for the best X-plane, Plane going.. cessna729.

I think you right, re-naming a few is no problem, but I've a feeling this may be more wide-spread , and as soon as you update the Navigraph data "our quick fixes will be gone". Any who... Just flew the ILS 27L with the (non radar vectored BIG Transition, yes the one we fixed!!) and it went quite well, even maintaining the published approach speeds the CRJ-200 turns much tighter with it puting in the max 25 deg bank on the first go, but it did not too bad for a 1st attempt (shown on the left). 2nd attempt is next with 1/2 bank set and compare that with the published Transition, not bad for the Birthday girl (The CRJ-200 that is!). Note I switched from the Autopilot NAV source from FMS to NAV1 at ILL10 as the FMS wanted to take me to land on the main terminal buildings for some strange reason?? cessna729.

Give yourself a pat on the back because I couldn't have figured it out if you hadn't spotted "BIG" being "bogus". this may also explain why I've been having problems writing the "Missing Aspen (KASE) approaches, as I'd just been using other existing Navigraph approaches as templates (just checked 1 of the template approaches I used.....you guessed it "multiple same name waypoints"!!!). Thanks for your & joaga's help. Update: Just done a quick check of the EGLL.xml Navigraph Cycle 1202 file and have found possible "multiple same name AppTr_Waypoint in App_Transition's". The ILS27R possible error in the BIG App_Transition's, same as found in ILS27L!! I suspect they can get away with "same name" but not "same name, same type". So the BIG App_Transition will need the AppTr_Waypoint's re-named. I wonder how many more "ERRORS" like this are out there? cessna729.

Fixed It!!!! :) I just re-named the BIG's & it now looks alot better!! compare with Published App_Trans BIG The EGLL ILS27L bit now looks like this: <App_Transition Name="BIG"> <AppTr_Waypoint ID="1"> <Name>BIG</Name> <Type>Normal</Type> <Latitude>51.330875</Latitude> <Longitude>0.034811</Longitude> <Speed>220</Speed> <Altitude>0</Altitude> <AltitudeCons>0</AltitudeCons> <AltitudeRestriction>at</AltitudeRestriction> <Flytype>Fly-by</Flytype> <BankLimit>25</BankLimit> <Sp_Turn>Auto</Sp_Turn> </AppTr_Waypoint> <AppTr_Waypoint ID="2"> <Name>BIG09</Name> <Type>Normal</Type> <Latitude>51.338206</Latitude> <Longitude>-0.204222</Longitude> <Speed>180</Speed> <Altitude>7000</Altitude> <AltitudeCons>0</AltitudeCons> <AltitudeRestriction>above</AltitudeRestriction> <Flytype>Fly-over</Flytype> <BankLimit>25</BankLimit> <Sp_Turn>Auto</Sp_Turn> </AppTr_Waypoint> <AppTr_Waypoint ID="3"> <Name>BIG_R279</Name> <Type>VorRadialIntc</Type> <Latitude>51.330875</Latitude> <Longitude>0.034811</Longitude> <Speed>0</Speed> <Altitude>7000</Altitude> <AltitudeCons>0</AltitudeCons> <AltitudeRestriction>above</AltitudeRestriction> <Hdg_Crs>0</Hdg_Crs> <Hdg_Crs_value>320</Hdg_Crs_value> <Flytype>Fly-by</Flytype> <BankLimit>25</BankLimit> <RadialtoIntercept>279</RadialtoIntercept> <Sp_Turn>Auto</Sp_Turn> </AppTr_Waypoint> <AppTr_Waypoint ID="4"> <Name>BIG_R295</Name> <Type>VorRadialIntc</Type> <Latitude>51.330875</Latitude> <Longitude>0.034811</Longitude> <Speed>0</Speed> <Altitude>6000</Altitude> <AltitudeCons>0</AltitudeCons> <AltitudeRestriction>above</AltitudeRestriction> <Hdg_Crs>0</Hdg_Crs> <Hdg_Crs_value>048</Hdg_Crs_value> <Flytype>Fly-by</Flytype> <BankLimit>25</BankLimit> <RadialtoIntercept>295</RadialtoIntercept> <Sp_Turn>Right</Sp_Turn> </AppTr_Waypoint> <AppTr_Waypoint ID="5"> <Name>BIG_R303</Name> <Type>VorRadialIntc</Type> <Latitude>51.330875</Latitude> <Longitude>0.034811</Longitude> <Speed>0</Speed> <Altitude>0</Altitude> <AltitudeCons>0</AltitudeCons> <AltitudeRestriction>at</AltitudeRestriction> <Hdg_Crs>0</Hdg_Crs> <Hdg_Crs_value>093</Hdg_Crs_value> <Flytype>Fly-by</Flytype> <BankLimit>25</BankLimit> <RadialtoIntercept>303</RadialtoIntercept> <Sp_Turn>Auto</Sp_Turn> </AppTr_Waypoint> <AppTr_Waypoint ID="6"> <Name>BIG_3500</Name> <Type>DmeIntc</Type> <Latitude>51.330875</Latitude> <Longitude>0.034811</Longitude> <Speed>0</Speed> <Altitude>3500</Altitude> <AltitudeCons>0</AltitudeCons> <AltitudeRestriction>above</AltitudeRestriction> <Hdg_Crs>0</Hdg_Crs> <Hdg_Crs_value>360</Hdg_Crs_value> <Flytype>Fly-by</Flytype> <BankLimit>25</BankLimit> <DMEtoIntercept>9.0</DMEtoIntercept> <Sp_Turn>Left</Sp_Turn> </AppTr_Waypoint> <AppTr_Waypoint ID="7"> <Name>ILL10</Name> <Type>Normal</Type> <Latitude>51.465578</Latitude> <Longitude>-0.167408</Longitude> <Speed>0</Speed> <Altitude>3000</Altitude> <AltitudeCons>0</AltitudeCons> <AltitudeRestriction>at</AltitudeRestriction> <Flytype>Fly-by</Flytype> <BankLimit>25</BankLimit> <Sp_Turn>Auto</Sp_Turn> </AppTr_Waypoint> </App_Transition> Hopfully the next version of the CRJ will be a bit more tolerant of "suss navigraph data" because I Iexpect there are alot more like that!! cessna729.

Update to the EGLL BIG Transition problem: NATS UK have published a different chart for Initial Approach Procedures (Without Radar Control) to ILS RWY 27L/R via BIG Chart at http://www.ead.eurocontrol.int/eadbasic/pamslight-5FCF51A91997CECBC58D2BDE1A28E1EC/7FE5QZZF3FXUS/EN/Charts/AD/AIRAC/EG_AD_2_EGLL_7-14_en_2011-10-20.pdf which shows the extra waypoints!! So appart from the "naming" of Waypoints 1, 3, 4, 5 & 6 all being "BIG", the navigraph data is looking not to bad, the RadialsToIntercept and the DME distances appear OK. so my next step when I get home is to try "re-naming" & see if that corrects the anomaly. cessna729.

Emalice, you have definately spotted somthing strange as can be seen from this screen plot of the MFD (my a/c is on the ground at EGKB "Biggin Hill"), according to the published approach ILS27 L&R & published BIGGIN STAR, after passing the Biggin VOR it should be Radar Vectors to intercept the 27 ILS at EGLL (shown as ILL10 on screen shot), but the MFD shows BIG09, another BIG fix north West, then a 3rd BIG fix off the top right habd corner of the MFD screen, before sorting it's self out at ILL10. Update: NATS UK have published a dirrerent chart for Initial Approach Procedures (Without Radar Control) to ILS RWY 27L/R via BIG Chart at http://www.ead.euroc..._2_EGLL_7-14_en which shows the extra waypoints!! The bit of the Navigraph data that may be causing you the CRJ problems if it's the same in your version, is around Waypoint 4 in this fragment; I don't trust Waypoint's 2 and 3 either: <App_Transition Name="BIG"> <AppTr_Waypoint ID="1"> <Name>BIG</Name> <Type>Normal</Type> <Latitude>51.330875</Latitude> <Longitude>0.034811</Longitude> <Speed>220</Speed> <Altitude>0</Altitude> <AltitudeCons>0</AltitudeCons> <AltitudeRestriction>at</AltitudeRestriction> <Flytype>Fly-by</Flytype> <BankLimit>25</BankLimit> <Sp_Turn>Auto</Sp_Turn> </AppTr_Waypoint> <AppTr_Waypoint ID="2"> <Name>BIG09</Name> <Type>Normal</Type> <Latitude>51.338206</Latitude> <Longitude>-0.204222</Longitude> <Speed>180</Speed> <Altitude>7000</Altitude> <AltitudeCons>0</AltitudeCons> <AltitudeRestriction>above</AltitudeRestriction> <Flytype>Fly-over</Flytype> <BankLimit>25</BankLimit> <Sp_Turn>Auto</Sp_Turn> </AppTr_Waypoint> <AppTr_Waypoint ID="3"> <Name>BIG</Name> <Type>VorRadialIntc</Type> <Latitude>51.330875</Latitude> <Longitude>0.034811</Longitude> <Speed>0</Speed> <Altitude>7000</Altitude> <AltitudeCons>0</AltitudeCons> <AltitudeRestriction>above</AltitudeRestriction> <Hdg_Crs>0</Hdg_Crs> <Hdg_Crs_value>320</Hdg_Crs_value> <Flytype>Fly-by</Flytype> <BankLimit>25</BankLimit> <RadialtoIntercept>279</RadialtoIntercept> <Sp_Turn>Auto</Sp_Turn> </AppTr_Waypoint> <AppTr_Waypoint ID="4"> <Name>BIG</Name> <Type>VorRadialIntc</Type> <Latitude>51.330875</Latitude> <Longitude>0.034811</Longitude> <Speed>0</Speed> <Altitude>6000</Altitude> <AltitudeCons>0</AltitudeCons> <AltitudeRestriction>above</AltitudeRestriction> <Hdg_Crs>0</Hdg_Crs> <Hdg_Crs_value>048</Hdg_Crs_value> <Flytype>Fly-by</Flytype> <BankLimit>25</BankLimit> <RadialtoIntercept>295</RadialtoIntercept> <Sp_Turn>Right</Sp_Turn> </AppTr_Waypoint> <AppTr_Waypoint ID="5"> <Name>BIG</Name> <Type>VorRadialIntc</Type> <Latitude>51.330875</Latitude> <Longitude>0.034811</Longitude> <Speed>0</Speed> <Altitude>0</Altitude> <AltitudeCons>0</AltitudeCons> <AltitudeRestriction>at</AltitudeRestriction> <Hdg_Crs>0</Hdg_Crs> <Hdg_Crs_value>093</Hdg_Crs_value> <Flytype>Fly-by</Flytype> <BankLimit>25</BankLimit> <RadialtoIntercept>303</RadialtoIntercept> <Sp_Turn>Auto</Sp_Turn> </AppTr_Waypoint> <AppTr_Waypoint ID="6"> <Name>BIG</Name> <Type>DmeIntc</Type> <Latitude>51.330875</Latitude> <Longitude>0.034811</Longitude> <Speed>0</Speed> <Altitude>3500</Altitude> <AltitudeCons>0</AltitudeCons> <AltitudeRestriction>above</AltitudeRestriction> <Hdg_Crs>0</Hdg_Crs> <Hdg_Crs_value>360</Hdg_Crs_value> <Flytype>Fly-by</Flytype> <BankLimit>25</BankLimit> <DMEtoIntercept>9.0</DMEtoIntercept> <Sp_Turn>Left</Sp_Turn> </AppTr_Waypoint> <AppTr_Waypoint ID="7"> <Name>ILL10</Name> <Type>Normal</Type> <Latitude>51.465578</Latitude> <Longitude>-0.167408</Longitude> <Speed>0</Speed> <Altitude>3000</Altitude> <AltitudeCons>0</AltitudeCons> <AltitudeRestriction>at</AltitudeRestriction> <Flytype>Fly-by</Flytype> <BankLimit>25</BankLimit> <Sp_Turn>Auto</Sp_Turn> </AppTr_Waypoint> </App_Transition> Note: I only have cycle 1202 Navigraph data at the moment on my Win 7 64bit machine, so I can't tell yet if it's the Navigraph Data in error or the CRJ's interpretation of it (i.e a "math problem"), all I can see on my machine is a periodic slight dip in the recorded fps as the FMS calculates all those "conditional waypoints". I am lucky enough to have a Flight Sim Only machine with a 4.5GHz i7 990X with 12GB ram & a GTX580 graphics card and have switched off all unnecessary Windows services and programs, so this slight fps drop dosn't cause me any problems (so far!!). cessna729.

Hi joga, what your describing sounds like XP10's over active responce to "turbulence", but just to make sure, can you try & fly the offending SID with Environment -> Weather -> Set Weather uniformly for whole world -> then click the CAVOK button on left hand side 3/4 way down screen, then exit weather page. If you still get the same effect, try and plot the effect on your airspeed-trend display by going: Settings -> Data Input & Output -> Data Set -> put ticks in the 2 right hand boxs for frame rate & speeds then exit the Data Input & Output page, Fly the offending SID again, and as soon as you get the effect again go Settings -> Data Input & Output, then click on Data See Tab, then tick the F-act, f-sim, cpu, & Vind boxes (un-tick the rest), then using your mouse at the left or right side of the screen, move through the data to see if anything "ties up" with your "speed-trend problem". You could also try turning up your Flight-Model setting on Operations & Warnings to 2, & see if that inproves things. Failing that just post your 1204 or 1205 LJLJ.xml file. As far as I know the X-plane data resources (1212.04) is not used by the FMS in JRollon's CRJ, it uses the Navigraph data in X-Plane 10\Aircraft\CRJ-200\plugins\CRJAvionics\navdata folder, so Robin's X-plane data souldn't likely to be causing your problem. cessna729.

Emalice & joga, are you both trying to use Navigraph Cycle 1205 data? because I had a quick try using the version I've got (1202) and so far havn't had any problems with my Win 7 (64bit) XP10.05r1, CRJ-200 ver 1.45. Could the Navigraph 1205 data for the airports your trying to use be sus? because I couldn't find a BERT1L SID at EJLJ for instance! has the data changed that much between 1202 & 1205? If your using Windows try looking in X-Plane 10\Aircraft\CRJ-200\plugins\CRJAvionics\navdata\LevelD_Proc folder for the "airport_ICAO_code.xml" where "airport_ICAO" is the airport your having the problem, eg. joga, you would need to look for LJLJ.xml file and compare it with the published SID (or winzip it and post it as an attachment to the forum for us to check). cessna729.

Hi Kyle, see update in post 11.cessna729.

It lives behind this KEY on the CDU , it unlocks the following functions. plus alot of other clever stuff Unfortunately, at the moment the VNAV key is not enabled yet in the JRollon CRJ (see Javier's excellent CRJ200_Manual_1.1.0.pdf & CRJ200_Tutorial_1.1.0.pdf) cessna729. update: Just figured out what that magenta "arc" is for!! The current JRollon CRJ-200 does have a similar capability. Say you have to decend, and be at a FIX e.g. PIERS at 8800ft ALT. (see pics below) It's a magenta line or arc that moves down towards the aircraft in MFD, its an indication of where the CRJ will be in terms of ALT selected if you maintain your current decent rate (eg -400 fpm), and it works very well. despite my poor flying, (see below). "I'd been wondering what that magenta arc had been doing for some time!.

Hi Kyle, your not alone in pondering CRJ's descent performance, read what a "realworld" CRJ captain had to say about the "real CRJ". cessna729.

utah77, Sorry you're so unhappy with the answer I gave, but if you had taken the time to read it all, you would have been able to see on the first line of the quote from Javier's Tutorial. You then go on to say. You entitled to your opinion, but in my humble opinion it is as a FULL implementaion of a FMS as you are likely to find on X-plane, and as Philipp & the "Real Operator's Guide FMS-4200 v4.0, Flight Management System for the Bombardier Regional Jet CRJ-100/200 by Rockwell Collins, Inc" say, VNAV is an option and not all "Real CRJ-200's" have it!cessna729.

As the "boss says", you need to make sure the parking brake is fully ON, This is not enough. You need it at least this much. Before the GPU can be enabled. You could always use the keyboard key "V" to toggle the Parking Brake. p.s,Japo32 I know its the wrong Forum but I couldn't wait to say She is looking fantastic (ECJ-32)! :wub: When can I put my pre-order in? edit: corrected my error, as Philip correctly said by default it's "V" not "B" for toggle max brakes, (I forgot I had re-defined my machine to give "B" for brakes, cos it's easyer for old codgers like me to remember , so on my machine both V & B toggle the brakes).

Hi danhenri, Which airport? have you tried another airport? and are you starting X-Plane "cold & dark on the ramp", or "engines running"? And are you starting X-Plane with the CRJ-200 loaded or are you starting with another aircraft then swop to the CRJ? Are you using the latest version CRJ Ver 1.4.5? cessna729.

Hi utah77, Not too sure what you mean by "T/D", if you mean "Top of Descent", have a look at the CRJ200_Tutorial_1.1.0.pdf, on page 42, where Javier describes the following: cessna729.

No appologies for quoting the whole post!!! It's looking fantastic!! I especially like the dirt & grime coming out of the panels in the underside & the leading edge of the tail!I want one.!.. I want one!!... I want one!!.. I want one!! cessna729.

Hi danhenri, Have you made sure you have set the parking brake before attempting to hit the EXT AC POWER button? (see page 9 of the excellent CRJ200_Tutorial_1.1.0.pdf) cessna729.

You could always try re-fueling on a carrier!! Any who! Phillip's trick with the Waypoints.txt works. I added "0MY01|40748314|-73985538|" and I get my own WayPoint for this Landmark!! cessna729.

You bet! Using inflight refueling from Javier's C-130!! cessna729.

We can hope it will get included in one of Philipp's updates! Just be don't forget to back up first!, because I expect there may be some "dependencies" & it might cause problems!!. i.e. crash the FMS if you get it wrong!. rad_ = angle in radians, you could rearrage the formula: angle in degrees = angle in radians * 180 / Pi, or you could search Google for a "degrees to radians converter" Edit: I'd skip the next bit and just read Phillip's next post!! I havn't tried it myself (yet), but if I was going to have a play, I would try and insert a FIX normally using the CDU first, pick something that's a minor fix, then save the FLPN, exit X-plane, edit the FLPN usind a good text editor that understands XML formating e.g. Notepad++ or similar, and search for every occurrence of the FIX you inserted earlyer and re-name that FIX & correct the item pairs: <lat_><rad_>radians</rad_></lat_> <lon_><rad_>radians</rad_></lon_>Or it your'e alot clever than me (which isn't difficult these days!) , come up with a python script to do it for you! . Note: the JRollon's CRJ-200's FMS is alot more capable/complicated than the standard X-plane FMS so it might not like you "tinkering with it's files!! - Be warned!!

Hi Stefan, I've come accross something similar with a couple of aicraft with XP10, a persistance or memory of settings/parameters on reloading the CRJ especially, and the only way to get rid of it is to ensure the "save preferences box & "start each flight with engines running" box are un-ticked" on the "Operations & warnings page" under "Settings" menu, then exit X-Plane compleatly, and then Re-start X-plane & re-load the CRJ. Very stange behaviour. It's almost as if the CRJ or XP10 is not always initalizing it's self into the same state if you loaded a different aircraft earlyer in that X-plane session before the CRJ or changed location a couple of times before loading the CRJ. cessna729. Update: I set location to LOWK then tried entering your route LOWK to LOWG, then re-locating to LOWG and entered LOWG to LOWK and got 50-51nm between airports each time I used the ARR-DEPT key to select DEPT Rwy & ARR STAR & APP. I tried both cold & dark & engines running, with no problem on my Windows 7 (64bit), XP10.05r1 & CRJ-200 Ver 1.4.5 apart from if I kept switching location back & forth swopping POSINIT's & IRS re-aligns, after the 2nd or 3rd location shift on selecting the approach to be used I'd get a CTD (It happened twice, but I can't realy blame the CRJ when that happens, but this is the crash_log.txt showing the two CTD's incase it helps): Product: X-Plane 10.05r1 Unhandled exception: EXCEPTION_ACCESS_VIOLATION (C0000005) Virtual Mem Free: -1689903104, Malloc'ed Mem: 294001673, Largest Contig Block: 2145771520 Flags=0, Address = 0x71800a72 0) 0x71800a72 (MSVCR100.dll + 68210) 1) 0x72363abe (win.xpl + 15038) Product: X-Plane 10.05r1 Unhandled exception: EXCEPTION_ACCESS_VIOLATION (C0000005) Virtual Mem Free: -1715240960, Malloc'ed Mem: 296504572, Largest Contig Block: 2145783808 Flags=0, Address = 0x723d0a72 0) 0x723d0a72 (MSVCR100.dll + 68210) 1) 0x72133abe (win.xpl + 15038)