I've been less that impressed by the small mouse areas for operating
the GNS knobs with a Reality XP GNS installed, so I've been looking for a way
to use the Carenado 3d knobs to operate the RXP GNS.

This will only work if you have a registered copy of FSUIPC installed, and if
you are willing to do a bit of tedious editing... so not for the non-techie folks ^_^

I would welcome comments from anyone who can figure out an easier way
to accomplish this BTW :huh:

So, here goes (you have been warned)

1. Set the panel to show the Carenado GPS (run CAR530.exe if in doubt)

2. Manually edit the panel.cfg file:

//--------------------------------------------------------
[Window00]
Background_color=8,8,8
size_mm=524,378
visible=0
ident=10000
window_size= 0.312, 0.400
position=6
no_luminous=1
zorder=7


//gauge00=GPS530_3D_CT206!GPS_530, 0, 0,520,378
//gauge01=B200KA!ToggleCAR530, 64, 0,384, 32

//--------------------------------------------------------
[Window01]
position=5
window_size=0.297619,0.342857
visible=0
zorder=2
ident=10010
gauge00=rxpGNS!GNS530,0,0,100,100

//--------------------------------------------------------
[Vcockpit01]
Background_color=0,0,0
size_mm=512,512
visible=0
pixel_size=513,513
texture=$Panel_1

gauge00=rxpgns!gns530, -10, -5, 537, 392
gauge01=CT206H!ToggleCARG1100, 64,0, 256, 32

Now the RXP GNS should appear in the panel and pop up by clicking the
top bezel

3. Edit the rxpgns.ini file for this plane to set popup=10010

Now the GNS pops back if you click on the popup panel.
BTW, with instrument reflections off, the popup on the VC screen also
works, but I actually prefer the reflections on, so I leave it that way.

4. Now things get interesting. Create a text file and call it C206_530_knobs.lua

Here is the text that goes into this file

-- Read knobs on GNS530 for CT206,  Version 7

-- Initialize

if GPS_init ~= 1 then
G_PAGE=0
G_GROUPS=0
G_FRAC=0
G_WHOLE=0
GPS_init=1
end


while 1 do
if ipc.readLvar("L:GPS_PAGE") == 357 then
ipc.keypress(123,3)
ipc.writeLvar("L:GPS_PAGE", 0)
G_PAGE=0
ipc.sleep(100)
end
if ipc.readLvar("L:GPS_PAGE") < G_PAGE then
ipc.keypress(123,3)
G_PAGE = ipc.readLvar("L:GPS_PAGE")
ipc.sleep(100)
end
if ipc.readLvar("L:GPS_PAGE") > G_PAGE then
ipc.keypress(124,3)
G_PAGE = ipc.readLvar("L:GPS_PAGE")
ipc.sleep(100)
end
if ipc.readLvar("L:GPS_CLICK_PAGE") ~= 0 then
ipc.keypress(115,3)
ipc.writeLvar("L:GPS_CLICK_PAGE", 0)
ipc.sleep(100)
end
if ipc.readLvar("L:GPS_GROUPS") == 357 then
ipc.keypress(113,3)
ipc.writeLvar("L:GPS_GROUPS", 0)
G_GROUPS=0
ipc.sleep(100)
end
if ipc.readLvar("L:GPS_GROUPS") < G_GROUPS then
ipc.keypress(116,3)
G_GROUPS=ipc.readLvar("L:GPS_GROUPS")
ipc.sleep(100)
end
if ipc.readLvar("L:GPS_GROUPS") > G_GROUPS then
ipc.keypress(117,3)
G_GROUPS=ipc.readLvar("L:GPS_GROUPS")
ipc.sleep(100)
end
if ipc.readLvar("L:GPS_FRAC") < G_FRAC then
ipc.keypress(118,3)
G_FRAC = ipc.readLvar("L:GPS_FRAC")
ipc.sleep(100)
end
if ipc.readLvar("L:GPS_FRAC") > G_FRAC then
ipc.keypress(119,3)
G_FRAC = ipc.readLvar("L:GPS_FRAC")
ipc.sleep(100)
end
if ipc.readLvar("L:GPS_CLICK_FRAC") ~= 0 then
ipc.keypress(120,3)
ipc.writeLvar("L:GPS_CLICK_FRAC", 0)
ipc.sleep(100)
end
if ipc.readLvar("L:GPS_WHOLE") < G_WHOLE then
ipc.keypress(121,3)
G_WHOLE = ipc.readLvar("L:GPS_WHOLE")
ipc.sleep(100)
end
if ipc.readLvar("L:GPS_WHOLE") > G_WHOLE then
ipc.keypress(122,3)
G_WHOLE = ipc.readLvar("L:GPS_WHOLE")
ipc.sleep(100)
end
ipc.sleep(100)
end

continued in next post

Continued from above...

 

Place the lua file that you created, into the FSX "Modules" folder.

 

5. OK, if you got this far, the next steps are:

 

Find the Main Reality XP rxpgns.ini file. Not the one for the airplane.

 

It will have key definitions in it. If you already have the GNS530 keys defined, you will have to

adapt the lua code above to match.  If not, here are the key definitions I use:

 

530_LKNOBO_L=SHIFT+CTRL+f10
530_LKNOBO_R=SHIFT+CTRL+f11
530_LKNOBI_L=SHIFT+CTRL+f7
530_LKNOBI_R=SHIFT+CTRL+f8
530_LKNOBPUSH=SHIFT+CTRL+f9
530_RKNOBO_L=SHIFT+CTRL+f5
530_RKNOBO_R=SHIFT+CTRL+f6
530_RKNOBI_L=SHIFT+CTRL+f12
530_RKNOBI_R=SHIFT+CTRL+f13
530_RKNOBPUSH=SHIFT+CTRL+f4

 

Hopefully they do not conflict with anything else on your system.

 

6. Last step... tell FSUIPC to run the lua code when the C206 is loaded.

 

Edit the FSUIPC4.ini file (in your Modules folder, where your lua program also resides)

and add the following lines

 

[LuaFiles]
1=C206_530_knobs   <<< or whatever number is next, if you have other lua files

[Auto.CT206H]
1=Lua C206_530_knobs

 

Bingo!  That should do it.

 

Congratulations if you got this to work!

 

If you look at the lua code, you can see that I treat the right knobs carefully

since they go from zero to 357 if you turn them counter-clockwise.. the animation

is also screwed up in that case.  I have reported it to Carenado as a bug, so a future

Service Pack may change this. Keep that in mind ^_^

Hi Bert,

Just a quick question on these gauges, do you see a big difference from the default 530 to the Reality XP version ?

I hate the small mouse areas too and they are real frustrating in turbulance.   I do not think I am up to doing that much editing so I will have to live with this serious flaw in my opinion.   Hopefully  Carenado will come up with an update.

 

Mike

Hi Bert,

Just a quick question on these gauges, do you see a big difference from the default 530 to the Reality XP version ?

 

Yes, like a crummy imitation GNS (pardon the language) to the real thing..

Hi Bert,

Just a quick question on these gauges, do you see a big difference from the default 530 to the Reality XP version ?

 

Even though there really isn't anyone running RXP these days, I'd still recommend the 530 and or 430W.  

 

What they can do above and beyond the stock GPS500:

 

Ability to enter an entire flight plan, modify it, select different active legs, add DP's and STARs, etc

Terrain awareness

Auto identify tuned navaids in NAV1 (example if you tune LAX even though you're not navigating to it it will display radial and distance - 530 only)

More updated nav database (most recent version summer 2011 - good if you fly online)

WAAS approaches possible (even with APR on autopilot armed on most planes)

A few other neat things...  the RXP stuff for me is basically equivalent to the Navigraph subscription for bigger jets (but RXP only gets nav updates once in a while)

 

Even though there really isn't anyone running RXP these days, I'd still recommend the 530 and or 430W.  

 

 

Hi Guys,

Thanks for your answers. Been thinking of getting the 530 for the stationair but seems abit expensive at $50

Hi Guys,

Thanks for your answers. Been thinking of getting the 530 for the stationair but seems abit expensive at $50

 

Depends... I use it in the RealAir Lancair and Duke, in the C337, in the C206, in the C182, in the RV7, etc

 

At some point, it is not that much money on a "per aircraft" basis.

Even though there really isn't anyone running RXP these days, I'd still recommend the 530 and or 430W.  

 

What they can do above and beyond the stock GPS500:

 

Ability to enter an entire flight plan, modify it, select different active legs, add DP's and STARs, etc

Terrain awareness

Auto identify tuned navaids in NAV1 (example if you tune LAX even though you're not navigating to it it will display radial and distance - 530 only)

More updated nav database (most recent version summer 2011 - good if you fly online)

WAAS approaches possible (even with APR on autopilot armed on most planes)

A few other neat things...  the RXP stuff for me is basically equivalent to the Navigraph subscription for bigger jets (but RXP only gets nav updates once in a while)

 

...and lets not forget the built in TCAS functionality for those who are willing to shell out an extra $100. Sadly I am not yet one of them, however :-(

 

 

...and lets not forget the built in TCAS functionality for those who are willing to shell out an extra $100. Sadly I am not yet one of them, however :-(

 

Yeah, the 430 and 530 feel just fine when I amortize the cost over the number of planes I use them in and the time I've had them.  Somehow, though, I've just never quite been able to justify the extra hundred for the "unlimited" pack in my mind.  It just feels...  I dunno, just that much over the top.

 

Scott

I would rather buy a few more aircraft or scenery's then purchase the unlimited pack.    The LinkGPS=On entry in the RXPGNS.ini works good for me for those aircraft that have to GPS units.

 

Mike

Can I ask some?

 

When the reality XP GPS is added to the VC cockpit,  it's bezel and 3d knobs and buttons are from the airplane itself? not reality XP?

 

So you guys have small mouse pointing area problem and the Carenado needs to fix it ?

(Sorry my poor English..)

Carenado has provided a 3d model for the RXP GNS, yes.

 

And yes, the mouse area for the right inner knob is very small

and hard to find..

 

Set the panel to show the Carenado GPS (run CAR530.exe if in doubt)

Hi Bert,

Interesting post this. Just one small question. You state "Set the panel to show the Carenado GPS " (run CAR530.exe if in doubt). so when you have done editing do you install the 530 via the config setup or what? and one last thing where is this file kept  the Main Reality XP rxpgns.ini file. Not the one for the airplane. 

This is all done by hand.. the edits shown at the beginning of this thread will install the RXP GNS in the panel.

(assuming you have the RXP GNS installed on your system!)

 

The "main" rxpgns.ini file is in Reality XP\Common\Settings.  Search for it.

 

Also add an rxpgns.ini file to the C206 panel folder, copy it from another airplane, use the RXP WAAS app,

or use this

[GNS530]
Popup=10010
AutoPilotMode=2
Radios=1
LinkCdiKey=On
AutoApproach=Off
AutoCourse=Off
LinkVor=1
LinkGPS=On
TCAD=On
LcdStyle=Off
AutoWidth=500
AutoHeight=360
Trainer=
NoKeyClick=Off
GndSpdFromDeltaLatLon=Off

[GTX327]
VFRCode=1200

[SETTINGS]
Dimmer=On
SimpleMouse=Off