May 8, 201214 yr Hey all- I have an peculiar issue that I can't seem to pin down. While doing some VOR to VOR navigation last night and some approach testing using NAV1 / VLOC mode (thanks FS Instant Approach tool!) and noticed that it's a no go with the RXP v1.6 under VLOC. The CDI recognizes the approach course and indicated the course divation correctly on the EHSI however, the plane will fly right through the course and never joins the course. Keep in mind I have integrated the RXP 430, running c90 SP2 and have the rxp.ini as indicated below. I am leaning towards something wrong the RXP.ini feeding the course information to the NAV 1 / OBS, I just don't know what it would be. The EHSI take takes the course just fine, the AP just refuses to slave to the CDI. Is there another GPS/NAV toggle I am missing somewhere outside of the OBS selection at the top of the VC panel? If anyone with the RXP 430 v1.6 and the GRP_Lock=On in the RXP.ini wants to give it a test for me and verify that in fact your A/P will slave to NAV1 VLOC (and not just show deviation on the EHSI) I would much apprecaite it. I need to pin this down as I really like to fly with the radios. Side note, the Direct To fed from the RXP works just fine and the A/P slaves to and follows GPS mode. Here is my rxp.ini for reference: [GNS430] popup=10010 AutoPilotMode=2 Radios=1 LinkCdiKey=On AutoCdiMode=0 AutoApproach=Off LinkVor=1 LcdStyle=Off AutoWidth=500 AutoHeight=210 Trainer= NoKeyClick=Off DisableRxTx=Off AutoPowerOn=Off AutoRadiosOff=On GndSpdFromDeltaLatLon=Off AutoCourse=Off LinkObs=On ShadinFuel=On RadioSyncMode=Full Brightness=-1.000000 CrossFill=Off TCAD=Off Taws=On TawsVolume=60 TAWS_ALRT_TYPE_NEG_CLIMB_RATE=0 TAWS_ALRT_TYPE_IMMINENT_OBST_IMPACT_CAUT=0 TAWS_ALRT_TYPE_REDUCED_OBST_CLEARANCE_CAUT=0 TAWS_ALRT_TYPE_IMMINENT_TERR_IMPACT_CAUT=0 TAWS_ALRT_TYPE_REDUCED_TERR_CLEARANCE_CAUT=0 TAWS_ALRT_TYPE_IMMINENT_OBST_IMPACT_WRNG=0 TAWS_ALRT_TYPE_REDUCED_OBST_CLEARANCE_WRNG=0 TAWS_ALRT_TYPE_IMMINENT_TERR_IMPACT_WRNG=0 TAWS_ALRT_TYPE_REDUCED_TERR_CLEARANCE_WRNG=0 CPU=0 HardwareDevice=Off HardwareIdx=0 LinkGPS=On [sETTINGS] Dimmer=Off SimpleMouse=Off KeyOnFocus=On Benjamin Van Eps
May 9, 201214 yr If anyone with the RXP 430 v1.6 and the GRP_Lock=On in the RXP.ini wants to give it a test for me and verify that in fact your A/P will slave to NAV1 VLOC (and not just show deviation on the EHSI) I would much apprecaite it. Wanted to try this with the released version of 1.6 before commenting, but... this has worked flawlessly for me since the pre-release and still does. The one part of this I don't understand is "GRP_Lock=On". ?? The only substantive difference between your rxpgns.ini and mine is that I have LinkVor set to 0 for this plane, not 1. Reading Bert's earlier comments, I'm not sure which is correct so perhaps he can clarify for the released version of 1.6, but this has worked for me from the beginning. Scott
May 9, 201214 yr Author I think all is well now. I am not exactly sure what was going on. I updated to SP2 and started a clean flight from C&D and everything worked as expected. Quite nicely. I didn't mean GRP_Lock... rather LinkGPS=on. Why wouldn't you use LinkVOR? Doesn't that just turn on the the needle on both the OBS and HSI? Benjamin Van Eps
May 9, 201214 yr LinkVOR=0 means that the VOR gauge shows the NAV signal, even when GPS mode is selected. The HSI will slave to the GPS course. That is good if you have an RMI gauge and you would like to use it to track a VOR while in GPS mode. At least that is what I think it does.. Bert
May 9, 201214 yr Author Thanks guys - all dialed in now. I redid the rxp.ini and updated C90 with SP2. I don't know what did the trick but doing some testing last night yielded no issues what so ever. Everything worked as I would have expected. Thanks for your help testing and tracking down the issue. Benjamin. Benjamin Van Eps
Create an account or sign in to comment