I just found out that my rxp 530w won't drive the plane.I have only this one rxp unit and that every time I activate a flightplan the malibu won't follow it. The Ap will only follow waypoints entered the in the default 430.-Am i doing something wrong ?ThanksV

I'm not an expert on the RXP's, but I've heard that you have to manually enter the flight plan yourself in the RXP devices. You can't just import a flight plan and follow it as you do with the typical gauges. This is an RXP thing, not a Carendado thing. Again that's what I understand but others may know better.

Glenn, I do enter the flightplan waypoint by waypoint in my rpx unit but it still does not work.

Check in the panel.cfg and make sure that the RXP 530 entry is for #1, i.e. gaugeXX=rxpGNS!GNS530, x,x,x,x instead of gaugeXX=rxpGNS!GNS530_2, x,x,x,xIf it is GNS530_2 then it is technically the secondary GNS, with the Carenado GNS probably set to the primary GNS.I do not have the Malibu, but in the C210 the Carenado GPS entry that makes it secondary to the RXP 530 is (I bolded the actual Gauge entry for identification):gauge00=CarenadoG430_3D_210!GNS430_nc2, 0,186,134,71Look in the panel.cfg entry and try and identify the Carenado GNS entry which is probably similar, if not identical, to the entry above. If it does not have the _nc2 appended to the end of it try adding it.You will also need to make sure that the RXP 530 entry is set to the primary GNS by making sure that it doesn't have a _2 following the gauge entry.

Edited January 13, 201214 yr by pmanhart

Hi Phil,I don't think it's secondary.have a look.This is my panel.cfg--------// CARENADO P46T MALIBU JETPROP DLX// Copyright © Carenado 2012 - All Rights Reserved//*********************************************************[Window Titles]Window00=G500Window01=Toggle_ManualWindow02=Toggle_ControlWindow03=GP530Window04=GP430Window05=GP530XPWindow06=GP430XPWindow07=INFO[VIEWS]VIEW_FORWARD_DIR=-1.000, 0.000, 0.000//--------------------------------------------------------[Window00]Background_color=0,0,0 size_mm=1024,1024window_size_ratio=1.000 position=8visible=0ident=MAIN_PANELwindow_size= 0.500, 0.666window_pos= 0.010, 0.310no_luminous=1gauge00=G500_P46T!g500_config, 0,0,1,1gauge01=G500_P46T!g500, 0,0,1024,1024gauge02=PA46T!ToggleCARG500, 0,0,1024,50//--------------------------------------------------------[Window01]Background_color=0,0,0 size_mm=713,1000position=0visible=0ident=793window_size= 0.351, 0.817window_pos= 0.520, 0.020zorder=5gauge00=PA46TManual!manual, 0,0,711,998//--------------------------------------------------------[Window02]Background_color=0,0,0 size_mm=500,261position=0visible=0ident=796window_size= 0.200, 0.200window_pos= 0.010, 0.145zorder=5gauge00=PA46T!Control_windows, 0,0,500,261//--------------------------------------------------------[Window03]Background_color=0,0,0 size_mm=512,512visible=0ident=10000window_size= 0.300, 0.400window_pos= 0.530, 0.305no_luminous=1zorder=6gauge00=GPS_530_3D_P46T!gps_500, 0,0,512,512gauge01=PA46T!ToggleCAR530, 0,0,512,30//--------------------------------------------------------[Window04]Background_color=0,0,0 size_mm=524,310visible=0ident=10010window_size= 0.310, 0.300window_pos= 0.525, 0.715no_luminous=1zorder=7gauge00=GPS_430_3D_P46T!GNS430_nc2, 0,0,528,310gauge01=PA46T!ToggleCAR430, 0,0,512,30//--------------------------------------------------------[Window05]Background_color=0,0,0 size_mm=512,512window_size_ratio=0.600 position=3visible=0ident=10020nomenu=1window_size= 0.300, 0.400window_pos= 0.530, 0.305no_luminous=1zorder=8gauge00=rxpGNS!GNS530, 0,0,512,512gauge01=PA46T!ToggleXP530, 0,0,512,30//--------------------------------------------------------[Window06]Background_color=0,0,0 size_mm=512,512visible=0ident=10030nomenu=1window_size= 0.300, 0.400window_pos= 0.528, 0.710no_luminous=1zorder=9gauge00=;rxpGNS!GNS430, 0,0,512,290gauge01=;PA46T!ToggleXP430, 0,0,512,30//--------------------------------------------------------[Window07]file=info.bmp size_mm=419,181window_size_ratio=1.000 position=0visible=1ident=142window_size= 0.250, 0.120window_pos= 0.010, 0.020//--------------------------------------------------------[Vcockpit01]Background_color=0,0,0 size_mm=1024,1024visible=0pixel_size=1024,1024texture=$Panel_1gauge00=GAUGEP46T!Gauge_Eng13D, 768,343,256,343gauge01=GAUGEP46T!Gauge_Eng23D, 768,0,256,343gauge02=GAUGEP46T!Gauge_Volts_Amps, 7,521,318,279gauge03=GAUGEP46T!Gauge_Anum_L, 87,805,328,212gauge04=GAUGEP46T!Gauge_Button_Anum, 422,803,600,217gauge05=GAUGEP46T!Gauge_Clock, 332,518,279,279gauge06=PA46TJ!GPSVSI, 0,0,2,2//--------------------------------------------------------[Vcockpit02]Background_color=0,0,0 size_mm=1024,1024visible=0pixel_size=1024,1024texture=$Panel_2gauge00=WX_Gauge_3D_P46T!WXGauge, 9,9,492,309gauge01=GPS_530_3D_P46T!gps_500, 7,337,493,358gauge02=Radio_P46T!RadioAdf, 524,670,496,100gauge03=GPS_430_3D_P46T!GNS430_nc2, 517,259,497,258gauge04=DIGTTRANS_P46T!transponder, 516,529,501,126gauge05=Radio_P46T!RadioTrans, 520,126,496,112gauge06=Radio_P46T!RadioAudio, 520,8,498,98gauge07=GAUGEP46T!Gauge_Anum_R, 381,786,635,229gauge08=GAUGEP46T!Gauge_Engine_Trend, 14,711,299,298//--------------------------------------------------------[Vcockpit03]Background_color=0,0,0 size_mm=512,512visible=0pixel_size=1024,1024texture=$Panel_3gauge00=GAUGEP46T!Gauge_Autopiloto, 0,0,512,119gauge01=GAUGEP46T!Gauge_Anum, 0,120,384,177gauge02=GAUGEP46T!Gauge_Anum_APSEL, 0,299,384,174gauge03=P46T_Cabin_alt!C340_PRESS, 0,0,1,1//--------------------------------------------------------[Vcockpit04]Background_color=0,0,0 size_mm=1024,1024visible=0pixel_size=1024,1024texture=$Panel_4gauge00=rxpGNS!GNS530, 8,337,493,358gauge01=;rxpGNS!GNS430, 517,260,497,258//--------------------------------------------------------[Vcockpit05]Background_color=0,0,0 size_mm=1024,1024visible=0pixel_size=1024,1024texture=$Panel_5gauge00=G500_P46T!g500_config, 0,0,10,10gauge01=G500_P46T!g500_3D, 0,0,768,515Day=255,255,255Night=223,255,255Luminous=246,115,119[Default View]X=0Y=0SIZE_X=8192SIZE_Y=6143----------

Strange. Here is my process:1. Program the flightplan into the RXP 530.2. Arm the FD by left clicking once on the FD/AP switch, and set the desired altitude on the AVSS.3. On departure, I arm the altitude and set runway heading, and after takeoff I left click twice on the FD/AP switch to turn on the FD and the AP.4. Once the aircraft is established in a stable climb, I switch the autopilot to NAV mode.

Seems to work fine here. I do the same as audiohavoc and have no problems.Martin

I just found out that my rxp 530w won't drive the plane.I have only this one rxp unit and that every time I activate a flightplan the malibu won't follow it. The Ap will only follow waypoints entered the in the default 430.-Am i doing something wrong ?ThanksV

What are the contents of your rxpgns.ini file for this plane?Mine has this in it:[GNS530]Popup=10020AutoPilotMode=2Radios=1LinkCdiKey=OnAutoApproach=OffLinkToVor=OnAutoCourse=OnLinkVor=1 is fine too... btw.

Like so...[GNS530]Popup=15531AutoPilotMode=2Radios=1LinkCdiKey=OnAutoCdiMode=0AutoApproach=OffLinkVor=1LcdStyle=OnAutoWidth=500AutoHeight=360Trainer=NoKeyClick=OffDisableRxTx=OffAutoPowerOn=OffAutoRadiosOff=OnGndSpdFromDeltaLatLon=OffAutoCourse=OnLinkObs=OnShadinFuel=OnRadioSyncMode=FullBrightness=-1.000000I also contacted carenado about this and they quoted the rxp guide. I can't make that work either... I left click on the fpl and it does make a sound but nothing happens.---------In page 8 of the Reality XP GNS WASS User´s Guide.pdf says:8 - Export Flight Plan: Using the right mouse button on the click spot exports the active flight plan in a Flight Simulator compatible file. The flight plan filename contains the UTC date and time and is saved in the following folders:FS9:“My DocumentsFlight Simulator Files”FSX:“My DocumentsFlight Simulator X Files”NB: it can take up to 5 seconds between a flight plan changes and the file saves. An audible warns when the file is actually saved.Flight Simulator is only capable of loading a flight plan file which starts and finishes with an “airport” waypoint type. As such, the GNS WAAS 430XP/530XP exported flight plan overrides the first and last waypoint type to “airport”. This permits creating the flight plan on the GNS, exporting it to a file and then loading it with Flight Simulator for proper ATC operations.

2. Arm the FD by left clicking once on the FD/AP switch, and set the desired altitude on the AVSS.3. On departure, I arm the altitude and set runway heading, and after takeoff I left click twice on the FD/AP switch to turn on the FD and the AP.

Small detail.. after 2. leave the FD active, and after takeoff click once on the switch to turn on the AP.

I also contacted carenado about this and they quoted the rxp guide. I can't make that work either... I left click on the fpl and it does make a sound but nothing happens.

Ok, lets go slow... If you enter a flightplan into the GNS530 and set the CDI on the GNS to "GPS",it will drive the autopilot in it's "NAV" mode.No need to export the flightplan.If you want the flightplan to visually show up on the G500 MFD, you need to export this plan to FSX,or enter it into the FSX flight planner as well. Otherwise you have to look at the GNS530 to see themagenta track / waypoints etc.

Edited January 13, 201214 yr by Bert Pieke

Ok, lets go slow... If you enter a flightplan into the GNS530 and set the CDI on the GNS to "GPS",it will drive the autopilot in it's "NAV" mode.

I actually did that but the plane won't follow the plan.Not sure why.Re: exporting the plan to fsx.That is another problem I'm having because somehow I can't export it.

How can I get the RXP530 flight plan to show up on the MFD?

If you want the flightplan to visually show up on the G500 MFD, you need to export this plan to FSX,or enter it into the FSX flight planner as well. Otherwise you have to look at the GNS530 to see themagenta track / waypoints etc.

That's a detail I left out. I use FSBuild and it is set to export the flight plan to FSX, although I don't have to load the flight plan via the FSX flight planner to get it to show on the GNS500. Simply programming the flight plan in the RXP GNS530 seems to do the trick.

That's a detail I left out. I use FSBuild and it is set to export the flight plan to FSX, although I don't have to load the flight plan via the FSX flight planner to get it to show on the GNS500. Simply programming the flight plan in the RXP GNS530 seems to do the trick.

So if I understood correctly, all you do is program the fp in the RXP GNS530 and it comes up on the MFD automatically for you? I've tried that, but it doesn't seem to work.