Jump to content
Sign in to follow this  
ardix

Milviz B55: help with RXP GNS430/530

Recommended Posts

Hi all, I've installed RXP GNS430/530 editing the cfg with these lines: http://www.milviz.com/forum/viewtopic.php?f=59&t=2897

 

Here it is the result:

b55_milviz_1.jpg

 

GNS530 (com1-nav1) linked to the HSI

GNS430 (com2-nav2) linked to the RMI

 

The only problem is that I can't make the NAV/GPS function to work with the GNS530. It seems linked only with the GNS430. It's a bit weird, since you use the HSI to follow a GPS track, so I expected this to be linked to the GNS530 (com1-nav1) instead of to the GNS430 (com2-nav2).

 

Is it possible to link it to the GNS530?

 

Hope it's clear.

 

Regards.

Share this post


Link to post
Share on other sites

Not sure what you mean by not being able to make the Nav/GPS function work.  Do you mean it's not driving the AP, or you can't switch between Nav and GPS? 

Looks like you're in Nav mode here on the 530 and GPS mode on the 430 - to switch, use the CDI button, if that's the issue.  Otherwise, perhaps something in your rxpgps.ini file.

 

Some options may be different depending on your preferences, but you'll want to have your rxpgps.ini file set up something like this:

 

 [GNS530]
LinkGPS=On
Popup=15531
AutoPilotMode=2
Radios=1
LinkCdiKey=On
AutoApproach=On
LinkVor=1
LcdStyle=off
AutoWidth=500
AutoHeight=570
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
[GNS430]
Popup=15432
AutoPilotMode=0
Radios=2
LinkCdiKey=Off
AutoCdiMode=0
AutoApproach=Off
LinkVor=2
LcdStyle=Off
AutoWidth=500
AutoHeight=570
Trainer=
NoKeyClick=Off
DisableRxTx=Off
AutoPowerOn=off
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
 

Hope this helps,

 

Scott

Share this post


Link to post
Share on other sites

thanks for your answer.

 

I try to explain in other words. What I want to do is to slave the GNS530 CDI button to the HSI, so I can use the GPS function. Now I can slave only using the GNS430 CDI button, but seems not logic to me...

 

Hope it's clear now.

Share this post


Link to post
Share on other sites

Works fine on my B55 using the rxpgns.ini settings I just posted.  How is your rxpgns.ini set up?

 

Scott

Share this post


Link to post
Share on other sites

I'm using your file right now and I can't make it to work.

 

example:

 

I set a DCT TO ABCD airport on GNS530, then i press the CDI button to switch on GPS mode. Nothing happens on the HSI.

I do the same thing on the GNS430, the HSI is now slaved to the gps.

 

What I want to do is to reverse this setting, so I can use the GNS530 as my main unit (NAV1, GPS, both slaved to the HSI).

Share this post


Link to post
Share on other sites

OK, here's a post I made from way back when which contains the panel.cfg I use.  Note my first quote, as I now remember I had the same problem with early configs.  The key had something to do with order, but it's been long enough that I don't remember the details.

 

---- begin old post:

 

Wayne's config didn't properly drive the HSI for me - a problem I had with some of the example panel.cfg files before the SP as well. The order of 430 and 530 matters.

Here's my panel.cfg with 530 and 430 and popups enabled. You may want to reposition the popup positions to taste, but this seem to be working well. Note, you must have an rxpgns.ini with idents that match for the popups to work. Usual disclaimers apply about backups, risk etc.

Hope this helps,

Scott

// This Panel.cfg file created by FS Panel Studio panel editor utility - http://www.fspanelstudio.com
// Built Sunday, June 24, 2012 at 17:41 FSPS Build:21603
[Window Titles]
Window00=B55 Preflight
Window01=GPS
Window02=Reality XP GNS 530 WAAS - RXP_CONFIG_TOOL - DO NOT CHANGE
Window03=Reality XP GNS 430 WAAS - RXP_CONFIG_TOOL - DO NOT CHANGE
[VIEWS]
VIEW_FORWARD_WINDOWS=MAIN_PANEL,THROTTLE_PANEL,GPS_PANEL
VIEW_FORWARD_DIR=10.000, 0.000, 0.000
//--------------------------------------------------------
[Window00]
Background_color=0,0,0
size_mm=500,243
window_size_ratio=1.000
position=0
visible=0
ident=70
window_size= 0.400, 0.324
window_pos= 0.000, 0.040
gauge00=B55_XMLGauges!B55_Preflight, 0,0,500,243
//--------------------------------------------------------
[Window01]
Background_color=0,0,0
size_mm=1280,650
window_size_ratio=1.000
position=2
visible=0
ident=GPS_PANEL
window_size= 0.710, 0.552
window_pos= 0.290, 0.480
gauge00=rxpGNS!GNS530, 0,0,640,468
gauge01=B55_XMLGauges!FBS_KR 87 ADF, 640,268,640,134
gauge02=rxpGNS!GNS430, 640,0,640,268
gauge03=B55_XMLGauges!FBS_KAP140, 640,402,640,163
gauge04=B55_XMLGauges!FBS_GTX330, 0,468,640,170
//--------------------------------------------------------
[Window02]
window_pos=0.7070305,0.000000
window_size=0.2929695,0.3375
visible=1
ident=15531
zorder=99
gauge00=rxpGNS!GNS530,0,0,100,100

//--------------------------------------------------------
[Window03]
window_pos=0.686667,0.526882
window_size=0.312500,0.210000
visible=1
ident=15431
zorder=99
gauge00=rxpGNS!GNS430,0,0,100,100

//--------------------------------------------------------
[Vcockpit01]
file=C310_VC_01.bmp
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$C310_VC_01
gauge00=MilVizC310!MilVizC310_XMLSound, 657,4,17,16
//gauge01=B55_XMLGauges!FBS_GNS430_2, 0,367,640,262
gauge02=B55_XMLGauges!FBS_KAP140, 0,767,640,163
gauge03=B55_XMLGauges!FBS_KR 87 ADF, 0,630,640,134
gauge04=B55_XMLGauges!B55_DME, 649,32,300,150
gauge05=B55_XMLGauges!B55_Preflight, 0,0,1,1
//--------------------------------------------------------
[Vcockpit02]
file=C310_VC_02.bmp
size_mm=512,512
visible=0
pixel_size=1024,1024
texture=$C310_VC_02
gauge00=B55_XMLGauges!FBS_GTX330, 0,376,512,136
//gauge01=B55_XMLGauges!FBS_GNS530_1, 0,0,512,374
//--------------------------------------------------------
[Vcockpit03]
Background_color=0,0,0
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$C310_VC_03
gauge00=rxpGNS!GNS430, 0,10,1024,433
//--------------------------------------------------------
[Vcockpit04]
Background_color=0,0,0
size_mm=512,512
visible=0
pixel_size=1024,1024
texture=$C310_VC_04
//gauge00=B55_XMLGauges!FBS_GTX330, 0,376,512,136
gauge01=rxpGNS!GNS530, 0,8,512,384
[Vcockpit05]
file=C310_VC_01_FR.bmp
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$C310_VC_05
//gauge00=B55_XMLGauges!FBS_GNS430_2, 0,707,640,262
gauge00=MilVizC310!MilVizC310_XMLSound, 657,4,17,16
gauge01=B55_XMLGauges!BK_AudioPanel, 0,0,640,128
//gauge03=B55_XMLGauges!FBS_GNS530_1, 0,103,640,468
//gauge02=B55_XMLGauges!FBS_GTX330, 0,571,640,136
//--------------------------------------------------------
[Vcockpit06]
file=C310_VC_02_FR.bmp
size_mm=512,512
visible=0
pixel_size=1024,1024
texture=$C310_VC_06
gauge00=B55_XMLGauges!FBS_KAP140, 0,106,512,131
gauge01=B55_XMLGauges!FBS_KR 87 ADF, 0,0,512,106

Day=255,255,255
Night=85,85,85
Luminous=140,140,140
[Default View]
X=0
Y=0
SIZE_X=8192
SIZE_Y=3384

 

Scott

Share this post


Link to post
Share on other sites

Found another little problem. I can't zoom on the GNS430 to make the 2d unit appear (popup window). It works for the GNS530, but not with the GNS430. Not a big problem, since I can still use SHIFT+3 and SHIFT+4.

 

b55_milviz_2.jpg

Share this post


Link to post
Share on other sites

Not sure this is a problem with the MV product...


Please contact oisin at milviz dot com for forum registration information.  Please provide proof of purchase if you want support.  Also, include the username you wish to have.
 

Share this post


Link to post
Share on other sites

Indeed it is not... This is why I've written a topic here and not in your support forum, since the problem is related to the RealityXP integration (which you don't fully support), not the plane itself.

 

%5Burl=

 

 

Share this post


Link to post
Share on other sites

LOL... alright... thanks for that... (i was wondering)


Please contact oisin at milviz dot com for forum registration information.  Please provide proof of purchase if you want support.  Also, include the username you wish to have.
 

Share this post


Link to post
Share on other sites

Indeed it is not... This is why I've written a topic here and not in your support forum, since the problem is related to the RealityXP integration (which you don't fully support), not the plane itself.

 

http://%5Burl=

Run the RXP config program it should create the VC clickspot for the popup.


| FAA ZMP |
| PPL ASEL |
| Windows 11 | MSI Z690 Tomahawk | 12700K 4.7GHz | MSI RTX 4080 | 32GB 5600 MHz DDR5 | 500GB Samsung 860 Evo SSD | 2x 2TB Samsung 970 Evo M.2 | EVGA 850W Gold | Corsair 5000X | HP G2 (VR) / LG 27" 1440p |

 

 

Share this post


Link to post
Share on other sites

 

 


Found another little problem. I can't zoom on the GNS430 to make the 2d unit appear (popup window). It works for the GNS530, but not with the GNS430.

 

Sorry, the rxpgns.ini that I gave you is what I'm using now.  The old posting of mine that I copied in for the panel was slightly older.  As noted in that posting, the ID's from the two configs have to match.

 

Go in to your rxpgns.ini and under [GNS430] change the ID.  To match the panel config I gave you, you should have "Popup=15431" for the 430.  That should fix things right up.

 

Sorry for the confusion.

 

Scott

Share this post


Link to post
Share on other sites

Ok. I'll try. Could you please provide the latest panel.cfg, which you use right now?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...