I like this add-on aircraft and prefer this Aztec F to the default model D in FSX. I am though disappointed that the ADF receiver does not offer any way of tuning a frequency which includes a number following the decimal point eg 402.5. However have I found a workaround. Through NpCV2.2 and FSUIPC4 I can set the frequency for the ADF using the keyboard and it has to have an entry for all five possible digits (the first will only be a 0 or 1).

04025 produced a magic response! The last entry show as 2 going on 3 on the panel (I’m sure not intended that way by Alabeo!) and the ADF needle whizzed round to point to the beacon. It really works in flight too. Great!

However can anyone help with a problem I have with NpCV2.2? The set up instructions are clear and I chose the option to use the keys on the numpad (Numlock set 0-9) but 2 and 5 do not work. I have assigned these two to K and L and that works okay but it is messy and I would prefer to able to use the intuitive group in the numlock area.

I imagine the problem is something to do with keyboard assignments to commands and I can see that these numbers do feature in the list of commands. But so do the others, so if 0,1,3,4,6-9 all work what have I got wrong with 2 and 5?

Can anyone help? Thanks in advance.

Ideas..
- Review your key settings for numpad 2 & 5 in FSUIPC keys tab, the right side.. Confirm they are correct, matching exactly to what you have with the K & L keys.
- Try removing 2 & 5 from the default commands as a test.
You could also post only the [Keys] section of your FSUIPC.ini file, maybe a second set of eyes looking at it may help.
 

Thanks spokes2112, I appreciate your quick response.

This is the list from the .ini file.  I can see some differences in the 2 and 5 entries but I hesitate to change things without understanding what I'm doing (or undoing!).  eg  value 2  change V to R? and value 5 change S to R?  

[Keys]
2=35,8,L6:R,0     -{End: Press=Lua NpCsetCOM }-
4=34,8,L12:R,0     -{PgDn: Press=Lua NpCsetNAV }-
7=33,8,L2:R,1     -{PgUp: Press=Lua NpCsetADF }-
9=36,8,L15:R,1     -{Home: Press=Lua NpCsetSQK }-
11=46,8,L4:R,1     -{Del: Press=Lua NpCsetAP }-
13=45,8,L14:R,0     -{Ins: Press=Lua NpCsetOBS }-
14=97,8,L1:R,1     -{Num1: Press=Lua NpCkeyData }-
16=96,8,L1:R,0     -{Num0: Press=Lua NpCkeyData }-
18=98,8,L1:V,2     -{Num2: Press=LuaValue NpCkeyData }-
20=99,8,L1:R,3     -{Num3: Press=Lua NpCkeyData }-
22=100,8,L1:R,4     -{Num4: Press=Lua NpCkeyData }-
24=101,8,L1:S,5     -{Num5: Press=LuaSet NpCkeyData (Flag 5) }-
26=102,8,L1:R,6     -{Num6: Press=Lua NpCkeyData }-
28=103,8,L1:R,7     -{Num7: Press=Lua NpCkeyData }-
30=104,8,L1:R,8     -{Num8: Press=Lua NpCkeyData }-
32=105,8,L1:R,9     -{Num9: Press=Lua NpCkeyData }-
34=110,8,L1:R,10     -{Num.: Press=Lua NpCkeyData }-
36=107,8,L1:R,11     -{Num+: Press=Lua NpCkeyData }-
38=109,8,L1:R,12     -{Num-: Press=Lua NpCkeyData }-
40=219,8,L1:R,13     -{[{key: Press=Lua NpCkeyData }-
42=221,8,L1:R,14     -{]}key: Press=Lua NpCkeyData }-
44=111,8,L1:R,15     -{Num/: Press=Lua NpCkeyData }-
46=106,8,L1:R,16     -{Num*: Press=Lua NpCkeyData }-
48=75,8,L1:R,2     -{K: Press=Lua NpCkeyData }-
50=76,8,L1:R,5     -{L: Press=Lua NpCkeyData }-
 

19 hours ago, rog943 said:

value 2  change V to R? and value 5 change S to R?

Yes, exactly... 👍
In the FSUIPC dialog it is very easy to be in the wrong Lua section, IIRC there are 6 lua sections ( take with a grain of salt, from memory ) :
1) Lua [filename] - This will run the lua, "R" 
2) LuaKill [filename] - This will kill the lua, "K"
3) LuaSet [filename] - This will set the flag provided by the param, "S"
4) LuaClear [filename] - This will clear the flag provided by the param, "C"
5) LuaToggle [filename] - This will toggle the flag provided by the param, "T"
6) LuaValue [filename] - This will send a value to the lua variable ipc.param via the UI param, "V"

You can modify your .ini while the sim is running, save it, then go to the FSUPIC dialog, keys tab, press "reload all keys".
That should do it :) 
If it does, ofc delete the pesky K & L assignments.

Thanks spokes2112,

That worked like a charm.  All sorted.  Really appreciate your help.

Roger