37 minutes ago, ludmar said:

As always, the solution is in the user's manual

Not always, but we are trying harder everyday! I'm glad this is all sorted out and working.

I have the same personal challenge but I don't quite get the solution (to make the CDI hardware button work using FSUIPC).

There is no KEY_GPS_NEAREST_BUTTON selection in FSUIPC...

Can you please give me the steps to configure this?  I know there are FSUIPC and RXP .ini files that may need some entries but need some handholding please :)

Ahh.found.it.

It's called "Gps Nearest Button" in FSUIPC

On ‎27‎-‎10‎-‎2017 at 0:59 PM, ludmar said:

Hello,

I use Win10 and P3D V4.1.

With the lastest version of GNS, all work fine with my emuteq. It is possible to use the default GPS key of P3D to use RXP gauge.

I assign the default command with FSUIPC.

The only one which doesn't work is CDI key, I don't know which is the default command. But I use win + F3 combinaison and all is fine.

Lud

Hi Ludmar,

Could you send /enclose the commands you used to get it done. I am not very good at those things, so I might need some step by step guidance.

Sorry for the late reply, have been away.

thanks a lot,

Hans

Hi Hansonius,

here is my FSUIPC.ini :

3=P1,13,C66448,0     -{NAV1_RADIO_SWAP}-
4=P1,17,C66605,0     -{GPS_OBS_BUTTON}-
5=P1,18,C66606,0     -{GPS_MSG_BUTTON}-
6=P1,19,C66609,0     -{GPS_FLIGHTPLAN_BUTTON}-
7=P1,20,C66610,0     -{GPS_VNAV_BUTTON}-
8=P1,21,C66612,0     -{GPS_PROCEDURE_BUTTON}-
9=P1,22,C66623,0     -{GPS_ENTER_BUTTON}-
10=P1,23,C66619,0     -{GPS_CLEAR_BUTTON}-
11=P1,24,C66618,0     -{GPS_MENU_BUTTON}-
12=P1,25,C66617,0     -{GPS_DIRECTTO_BUTTON}-
13=P1,26,C66615,0     -{GPS_ZOOMIN_BUTTON}-
14=P1,27,C66616,0     -{GPS_ZOOMOUT_BUTTON}-
16=P1,12,C66372,0     -{COM_STBY_RADIO_SWAP}-
17=P1,14,C66629,0     -{GPS_BUTTON1}-
18=P1,6,C66631,0     -{GPS_BUTTON3}-
19=P1,7,C66630,0     -{GPS_BUTTON2}-
20=P1,4,C66633,0     -{GPS_BUTTON5}-
21=P1,5,C66632,0     -{GPS_BUTTON4}-
22=P1,15,C66624,0     -{GPS_CURSOR_BUTTON}-
23=P1,9,C66628,0     -{GPS_PAGE_KNOB_DEC}-
24=P1,8,C66627,0     -{GPS_PAGE_KNOB_INC}-
25=P1,11,C66626,0     -{GPS_GROUP_KNOB_DEC}-
26=P1,10,C66625,0     -{GPS_GROUP_KNOB_INC}-
27=P1,16,C66604,0     -{GPS_NEAREST_BUTTON}-

if you don't use FSUIPC, I think the command name is the same in P3D.

Lud

Official event IDs are in the SDK documentation here:

http://www.prepar3d.com/SDKv2/LearningCenter/utilities/variables/event_ids.html

 

Quote

 

Hi Ludmar,

Thanks for the info about FSUIPC ini. I do use FSUIPC5. I suppose it shold be under [buttons] and P1 is the number the hardware

As far as I know there were three steps to install/connect the RXP GNS530 and the Emuteq hardware.

1.Map the buttons on the GNS 530 to key presses in FSUIPC.ini

2. Modify RXPGNS.ini

3. Modify panel.cfg of each aircraft.

This is how it was done in FSX up to know. But maybe You and GNS530V2 have other possibities.

So, if possible could you tell what to do step by step.

I would be very grateful if you did so.

thanks ,

Hans

 

9 hours ago, Hansonius said:

Hi Ludmar,

Thanks for the info about FSUIPC ini. I do use FSUIPC5. I suppose it shold be under [buttons] and P1 is the number the hardware

As far as I know there were three steps to install/connect the RXP GNS530 and the Emuteq hardware.

1.Map the buttons on the GNS 530 to key presses in FSUIPC.ini

2. Modify RXPGNS.ini

3. Modify panel.cfg of each aircraft.

This is how it was done in FSX up to know. But maybe You and GNS530V2 have other possibities.

So, if possible could you tell what to do step by step.

I would be very grateful if you did so.

thanks ,

Hans

 

This is what I have for the GNS in the Realair Piston Duke using the Emuteq:

In the RealityXP.GNS file located at c:\user\<your user name>\my documents\RealityXP\GNS Simulation\Fltsim folder:

 

[SHORTCUTS]
TOGGLE_WINDOW_1 =
CFLP_1 = WIN+Q
VFLP_1 = WIN+W
CDI_1 = WIN+F9
OBS_1 = WIN+V
MSG_1 = WIN+F13
FPL_1 = WIN+A
VNAV_1 = WIN+C
PROC_1 = WIN+F2
ENT_1 = WIN+F14
CLR_1 = WIN+F5
MNU_1 = WIN+F4
DTO_1 = WIN+F3
RDN_1 = CTRL+SHIFT+I
RUP_1 = CTRL+SHIFT+H
PWR_PUSH_1 = CTRL+SHIFT+Q
PWR_CCW_1 = CTRL+SHIFT+Z
PWR_CW_1 = CTRL+SHIFT+Y
VOL_PUSH_1 = CTRL+SHIFT+T
VOL_CCW_1 = CTRL+SHIFT+R
VOL_CW_1 = CTRL+SHIFT+S
COM_PUSH_1 = WIN+N
COM_OUTR_CCW_1 = WIN+J
COM_OUTR_CW_1 = WIN+K
COM_INNR_CCW_1 = WIN+F6
COM_INNR_CW_1 = WIN+F7
GPS_PUSH_1 = WIN+F11
GPS_OUTR_CCW_1 = WIN+O
GPS_OUTR_CW_1 = WIN+F8
GPS_INNR_CCW_1 = WIN+F10
GPS_INNR_CW_1 = WIN+F12
TOGGLE_WINDOW_2 =
CFLP_2 =
VFLP_2 =
CDI_2 =
OBS_2 =
MSG_2 =
FPL_2 =
VNAV_2 =
PROC_2 =
ENT_2 =
CLR_2 =
MNU_2 =
DTO_2 =
RDN_2 =
RUP_2 =
PWR_PUSH_2 =
PWR_CCW_2 =
PWR_CW_2 =
VOL_PUSH_2 =
VOL_CCW_2 =
VOL_CW_2 =
COM_PUSH_2 =
COM_OUTR_CCW_2 =
COM_OUTR_CW_2 =
COM_INNR_CCW_2 =
COM_INNR_CW_2 =
GPS_PUSH_2 =
GPS_OUTR_CCW_2 =
GPS_OUTR_CW_2 =
GPS_INNR_CCW_2 =
GPS_INNR_CW_2 =
RXP_GPS_MASTER_DEVICE_0 =
RXP_GPS_MASTER_DEVICE_1 =
RXP_GPS_MASTER_DEVICE_2 =
RXP_GPS_MASTER_DEVICE_NEXT =
 

This is my corresponding [Buttons] section of the FSUIPC.ini file in the Modules folder of Prepar3d (note key presses 1 & 2 are for functions not related to the GNS in my INI):

 

3=P1,12,K81,40  -{Key press: win+Q}-
4=P1,0,K89,11  -{Key press: ctl+shft+Y}-
6=P1,13,K87,40  -{Key press: win+W}-
9=P1,7,K75,40  -{Key press: win+K}-
10=P1,6,K74,40  -{Key press: win+J}-
11=P1,5,K118,40  -{Key press: win+F7}-
12=P1,4,K117,40  -{Key press: win+F6}-
13=P1,14,K78,40  -{Key press: win+N}-
14=P1,16,K120,40  -{Key press: win+F9}-
15=P1,17,K86,40  -{Key press: win+V}-
16=P1,18,K124,40  -{Key press: win+F13}-
17=P1,19,K65,40  -{Key press: win+A}-
18=P1,20,K67,40  -{Key press: win+C}-
19=P1,21,K113,40  -{Key press: win+F2}-
20=P1,10,K119,40  -{Key press: win+F8}-
21=P1,11,K79,40  -{Key press: win+O}-
22=P1,8,K123,40  -{Key press: win+F12}-
23=P1,9,K121,40  -{Key press: win+F10}-
24=P1,15,K122,40  -{Key press: win+F11}-
25=R1,27,K72,11  -{Key press: ctl+shft+H}-
26=R1,26,K73,11  -{Key press: ctl+shft+I}-
27=P1,25,K114,40  -{Key press: win+F3}-
28=P1,24,K115,40  -{Key press: win+F4}-
29=R1,23,K116,40  -{Key press: win+F5}-
30=P1,22,K125,40  -{Key press: win+F14}-
31=P1,29,K81,11  -{Key press: ctl+shft+Q}-
32=P1,28,K84,11  -{Key press: ctl+shft+T}-
33=P1,1,K90,11  -{Key press: ctl+shft+Z}-
34=P1,3,K82,11  -{Key press: ctl+shft+R}-
35=P1,2,K83,11  -{Key press: ctl+shft+S}-
 

And this is my entry in the panel.cfg file for the Realair (pop-up without bezel to undock and palce on Emuteq:

 

[Window03]
size_mm=100,100
window_pos=0.744792,0.000000
window_size=0.255208,0.336475
visible=1
always_visible=1
zorder=99
background_color=0,0,0
ident=15531
gauge00=rxpGNS2!GNS_530_1,-28,-12,155,150 //0, 0,100,100 use for emuteq

Hope that helps

David

 

 

Hi,

to explain a little more, the first line for exemple : 3=P1,13,C66448,0     -{NAV1_RADIO_SWAP}-

- P1 is the number of the ardware

- 13 is the number of the button

- C66448 is the P3D command.

- NAV1_RADIO_SWAP is the name of the command in FSIUPC

With the version 2 of GNS there is no need to use keybord definition in RXPGNS.ini if the option "Settings Panel -> Use Simulator GPS Commands" is on.

You can assign command directly through FSUIPC as a standart command.

So you can use the part of my FSUIPC setting (only remplacing P1 by the number of your hardware) or you can assign by yourself with classic FSUIPC interface.

If it is not clear I will try to make more explanation.

Lud

 

Hi Ludmar and David,

Thanks a lot for the detailed info. In a couple of days I'll have time to try if I can get it working, I'll let you guys know!

Hans

On 5-11-2017 at 2:25 PM, Hansonius said:

Hi Ludmar and David,

Thanks a lot for the detailed info. In a couple of days I'll have time to try if I can get it working, I'll let you guys know!

Hans

Hi guys,

With your help things worked out well the RXP/Emuteq combination is working as it should.

The RXP GNS530v2 is a wonderful piece of software!

Thanks a lot for the detailted instructions.

Hans

1 hour ago, Hansonius said:

Hi guys,

With your help things worked out well the RXP/Emuteq combination is working as it should.

The RXP GNS530v2 is a wonderful piece of software!

Thanks a lot for the detailted instructions.

Hans

Great news Hans, glad you are up and running. You are quite right - RXP/Emuteq is an awesome combination!