Dario,

 

This is a wonderful toolset! I'm building a pit and was trying to model an UCP. Your Lua scripts will save me tons of time.

 

Thanks again so much.

Hello,

Num Pad Radio is a great idea and I have been looking for something like this. Unfortunately I can't get it to work correctly with FSX and the latest FSUIPC4.  For example, I cannot get the selection toggle key for the Com or Nav radios to do anything. I used the C and N keys for these toggles (and deleted the standard FSX  keyboard assignments to avoid conflicts). Do all keys used with Num Pad Radio have to be from the Num Pad?  Would appreciate any suggestions.

 

Edit: It seems from what I can tell that you are restricted to using only Numpad keys. It would be useful if non numpad keys could be used to select radios and for other non-numeric entries (like reset) so that you could leave the Num Pad in the Num Lock position and not have to switch back and forth. For example, right now to select a radio using PgUp the Num Lock has to be off. You then have to turn it on to enter the frequency with the numeric keys. Then to select the next radio you have to turn Num Lock off again, etc. Or am I doing something wrong?  I'm not knowledgeable enough to know if allowing the use of non Num Pad keys would be difficult to do. 

Thx,

Al

Disregard the above post! I flushed all key assignments and reinstalled Num Pad Radio and it seems to work w/o any key restrictions. The problem may have been the order in which I resolved key conflicts, so suggest you remove any potential key assignments from FSX before installing Key Pad Radio.

Thank you Dazz.

Al

Disregard the above post! I flushed all key assignments and reinstalled Num Pad Radio and it seems to work w/o any key restrictions. The problem may have been the order in which I resolved key conflicts, so suggest you remove any potential key assignments from FSX before installing Key Pad Radio.

Thank you Dazz.

Al

 

Glad to hear all is well now Ark. And welcome to Avsim!

Hi Dazz,

How difficult would it be to modify the code to have each frequency or transponder digit entered directly into the panel radio display instead of on the green banner? Each radio then would have its own select key (eg, C1 and C2 for com, etc). Just curious to see if the green banner could be eliminated for "realism", and if I eventually might be able to learn enough about lua scripts to do something like that. I have no lua or FSX programming experience at this point. Did you have to write "unseen" code in addtion to the 5 lua scripts, or does the interface to FSUIPC provide everything else needed? I'm sure you can see from these questions how little I understand at this point, and will apologize in advance for what likely is a silly question.
 Thanks again for a great program -- I have passed it on to other simmers.

Al

Hi Dazz,

How difficult would it be to modify the code to have each frequency or transponder digit entered directly into the panel radio display instead of on the green banner? Each radio then would have its own select key (eg, C1 and C2 for com, etc). Just curious to see if the green banner could be eliminated for "realism", and if I eventually might be able to learn enough about lua scripts to do something like that. I have no lua or FSX programming experience at this point. Did you have to write "unseen" code in addtion to the 5 lua scripts, or does the interface to FSUIPC provide everything else needed? I'm sure you can see from these questions how little I understand at this point, and will apologize in advance for what likely is a silly question.

 Thanks again for a great program -- I have passed it on to other simmers.

Al

 

I'm not sure it can be done the way it works now man. 

An example. Max frequency for the COM_1 is 136.97. So if you have at one point a frequency of say 128.00 set and you want to switch to 135.00, when you try to input that 3 for the second digit you'be be pushing 138.00 which is off limits and you'd be stuck there unless you set something like 130.00 then 135.00.

 

I could implement extra logic to reset the units digit to avoid this, but it's not trivial and wouldn't be too realistic anyway, maybe even confusing, I don't know.

 

That's why I can't push the frequency until all digits are typed. Actually there's logic there to prevent out of range freqs from going through.

 

Can I suggest to simply turn off messages?

 

If you want to try it yourself, there's no hidden code or anything like that. The script to tweak would be numpadKeyPress.lua. I'm sorry but I'm into photoscenery now and that's a very time consuming project

Dazz,

Turning off messages is certainly an option once you pick different selection keys for each Com and Nav radio (and, I guess, as long as nothing else needs the single line messages).

Thx,

Al

Hi there fellow simmers.I recently programmed a little LUA pluggin (thanks Barry for the idea) to allow tuning the radios (COM1, COM2, NAV1, NAV2, ADF1, ADF2) and the transponder using the numpad of a keyboard and a couple extra keystrokes.It requires licensed FSUIPC4Basically you assign a key to select COM1, or COM2, another one for NAV1 or NAV2, a third one for ADF1 or ADF2 and one for the transponder.Once you have your selection, you can type in the frequency (or squawk code) with the numpad and it will be set to the standby radio selected (or the transponder)Finally a keystroke can be assigned to the swap function to swap the active and stanby frequencies in the selected radioThought I'd post it here and maybe get some feedback on bugs or any suggestions before uploading it to the Avsim Library.Download link

 

It may just be me, but I can't get your download link to work.

 

Thanks,

 

Tim

 

Hi there fellow simmers.I recently programmed a little LUA pluggin (thanks Barry for the idea) to allow tuning the radios (COM1, COM2, NAV1, NAV2, ADF1, ADF2) and the transponder using the numpad of a keyboard and a couple extra keystrokes.It requires licensed FSUIPC4Basically you assign a key to select COM1, or COM2, another one for NAV1 or NAV2, a third one for ADF1 or ADF2 and one for the transponder.Once you have your selection, you can type in the frequency (or squawk code) with the numpad and it will be set to the standby radio selected (or the transponder)Finally a keystroke can be assigned to the swap function to swap the active and stanby frequencies in the selected radioThought I'd post it here and maybe get some feedback on bugs or any suggestions before uploading it to the Avsim Library.Download link

 

It may just be me, but I can't get your download link to work.

 

Thanks,

 

Tim

 

 

Try this:

 

link to v1.3 

 

 

Just curious to see if the green banner could be eliminated for "realism",

 

 

Sorry to dig up an old thread, but I am using this LUA script and love it.  It helps to reduce the footprint/cost of my sim.  I looked at the LUA code and tried to figure out how to integrate setting the HDG, CRS, or BARO values, but am at a loss.  Is there any way this could be incorporated into a new version?  Again, many thanks!

 

 

Expanding on the GREAT work dazz did - here is a set of scripts that do some of the things being asked

• For Coms, Navs, ADF and transponder the codes appear in the radio display (not on the ribbon banner at the top) as they are entered
• Autopilot entry funcitions available - Altitude, vertical speed, heading (these do not appear until the entry is complete)
• OBS heading set (OBS1 and OBS2 available).  Note that the heading bug is set using the heading set function associated with the autopilot

Here's the link - http://www.mediafire...b2oj1qm5at3b18i

 

Here's the Forum post regarding this - http://forum.avsim.net/topic/423405-setting-fsx-radios-obss-and-autopilot-using-the-keyboard-numberpad/

Great stuff guys. I'll give it a go tomorrow. Thanks for the kind words and for the contribution to the community

Great piece of work...I discovered it only last week.

 

The original version had an autopilot function (NpCSetAP.lua) but there is no equivalent in version 1.3. I have tried using the old code but it doesn't work: I get the autopilot in the message line and it cycles through Altitude / Vertical Speed / Heading as per the original instructions but none of the entries will activate. It appears that the old code conflicts with v. 1.3 or am I doing something wrong? If not, would it be possible to re-instate the Autopilot functions? They would be very useful as their entry into the A/P panel is as cumbersome as any other comm/nav equipment.

 

Thanks!

Correction to my earlier post. The version with autopilot functions is 1.1 by Al Klayton, not the original author dazz. Nonetheless, adding those functions is especially useful.

Hello,

 

Does this allso work with fs9?

 

I'm not a big programmer, but have had succes with basic fsuipc programming for buttons, switches etc. for my home cockpit. I'm restoring an old 727 flight deck, and would like the old analog radios to work. I've succesfully managed to do so with one NAV radio so far by writing a line in fsuipc.ini for each and every NAV frequency which took me some time as you might imagine! 

As I'm now going to interface one more NAV radio + two COM radios, I was kind of hoping there might be another way around programming these!

 

I was thinking I could somehow use your great script to approach this in an easier way.

 

The physical radio is made up of rotary swithes, each sending a button press via the i/o card to fsuipc.

 

Lets say button1 is pressed, Can that set the ten'th in the freq. ie. 108.00?

Button2 pressed = 109.00

Button3 pressed = 110.00

... and so on...

 

And button10 to set the decimal: 108.10

Button11 = 108.20

... and so on...

 

I'd really appreciate any inputs that could lead me in the right direction!

 

Thanks,

Lasse