ark1320

Numpad Control (NpC) allows you to directly input Com, Nav, ADF, Transponder, OBS and Autopilot settings in FSX using the keyboard number pad instead of mouse clicks. NpC is a set of freeware LUA scripts that expand and enhance the good work of “dazz” (Dario Iriberri ) that was originally presented here http://forum.avsim.net/topic/336131-...your-keyboard/. One feature of NpC is that most entered values, such as radio frequencies, appear directly on the radio’s display as the digits are entered. NpC requires a registered version of FSUIPC4. The zip file, NpC_v1.0.zip, containing 11 NpC LUA scripts, a quick reference guide, and an instruction manual is attached. Save NpC_v1.0.zip to a temp folder, unzip it and open README-NpCManual_v1.0.pdf for installation and operation instructions. If you decide to install NpC the 11 LUA script files will need to be copied or unzipped into the FSX Modules folder. ark1320, (Al) TxHills, (Dan) Edit: Updated files NpCv1.1 are now attached below in 16Nov2013 post. Edit: Updated files NpCv2.2 are now attached below at Post#5, 15June2015 Now includes support for some third party a/c such as the PMDG 737NGX. An NpC overview video is available at https://www.youtube....h?v=P2p6CHxMOl8 Edit: Updated files NpCv2.21 now attached below at Post#11, 18Dec15

I was looking at working with the autopilot altitude value in 07D4. It uses only 32 bits total, maybe because only values to the nearest 100 ft are displayed? Thanks very much for the info. Al

For the autopilot, the altitude value in meters (and also the heading info in degrees/360) are both multiplied by 65536 (2 to the 16th power). Is this to eliminate fractional values and facilitate rounding somehow? I'm trying to figure out how the individual altitude digits displayed on the autopilot are actually represented in the 4 byte offset, ie, can the digits be mapped to hex characters in each byte of the offset similar to how the frequency digits for a Com radio are represented in the COM offset? Thx, Al

In case it is useful to anyone, what I found regarding the ADF frequency offsets is that just writing to the higher offset, that contains the MS and LS frequency digits, also changes the values of the middle frequency digits at least in terms of what is displayed on the radio panel. So, for example, to change just the MS digit I had to write to both offsets to keep the displayed middle digits unchanged. Interestingly, the converse is not true. You can write to the lower offset to change one of the middle frequency digits without effecting the MS or LS digits. Has to do with how FSX updates the displayed ADF frequency I assume. Al

You are correct in that I was treating the offsets as true memory locations! I guess writing to an offset is more like passing parameters to a function call. A few questions please: It looks like FSUIPC does some checking to make sure values, like a Com radio frequency, is valid when you attempt to write to the offset. Are invalid values just ignored? What is the minimum delay ( using ipc.sleep, I assume) must there be between successive writes, or a read and a write, when updating a radio's displayed frequency ( e.g., at offset 0x311A for Com_1)? Is there a typical delay value to use for repeated access to most offsets? Where can I find out which offsets require a delay after accessing them? What is the size of the variable ipcPARAM, 32 bits? On a control like the standby frequency swap for Com2, ipc.control(66444,1), where can I find out what the 1 does? ADF frequencies involve 2 offsets. Can these be updated independently (i'm trying to update the displayed ADF freq digit by digit as each new digit is entered on the numpad). It seems sometimes writing to the 2nd (higher) offset, which should only effect the first and last ADF digits, also causes a change in the middle digits assocaited with the lower offset. Finally, where could I have looked up the answers to these questions for myself? I am new to FDUIPC and Lua scripts. I apoligize for these basic questions and appreciate your help and patience. Al

My problem was I didn't understand the only "trigger" for updating the radio standby freq display was just the 0x311A address. Thanks for the feedback. Al

I am trying to learn a little about Lua scripts and FSUIPC4 offsets, but clearly I do not understand some basic concepts. The FSUIPC Offset table says the standby frequency for radio Com_1 is stored as 4 BCD characters in the 2 bytes starting at 0x311A. Therefore I expected the Lua script statements ipc.writeUB(0x311A, 37); ipc.writeUB(0x311B, 35); to change the standby frequency for Com_1 to 123.25 since 37 decimal is the 8 bit value 0010 0101 which if interpreted as 2 BCD char is 25, and decimal 35 is the 8 bit value 0010 0011 which if interpreted as 2 BCD characters is 23. The leading frequency digit is always 1 and need not be written. Since the above instructions had no effect on the displayed Com_1 standby frequency ( nothing I seem to do does ), I am way off base somewhere. I assumed once new values were written to the appropriate offset, the new frequency would immediately be displayed on the radio panel. Would appreciate any guidance. Thx, Al

I am learning how to write Lua scripts for use with FSUIPC. Is there a Lua syntax checker that anyone would recommend that will check for basic errors and thus help with debugging? Thx, Al

It works now! I noticed this time when I started FSX I got the "do you trust this software" message, which I didn't get before. So either I failed to restart FSX or reboot the computer, or both, to activate the new dll. Dumb! Sorry I bothered you, Al

Pete, I copied the FSUIPC4.dll that was in the FSUIPC4909d.Zip file above into my modules folder, thus replacing the old dll, but it did not cure the probelm, only OBS1 responds as before. Is there something else I need to do? Thx, Al

Good point about the number keys. I use the num pad to enter the frequency digits, and it looks like the program will not even respond to the number keys across the top of the keyboard. At least initially I'm usung the followig assignments: C, N, T, and Shift+F1 to select the Com, Nav, Transponder, and ADF radios, respectively, * (on the numpad) to turn the program on and off, X to load the standby frequency, and the Backspace key as Reset. I like the F in Shift+F1 to indicate the ADF and this key combo is apparently unused in FSX. If using the Backspace key can lead to problems ( I'm relatively new to FSX) then maybe the / numpad key would be a good alternative for Reset. Thanks again for the help. Al

Thank you very much for the help. I will give it a try. Al Update: For anyone interested, the program referenced above is a free add-on called Num Pad Radio. Essentially you can select a radio ( Com 1 or 2, Nav 1 or 2, ADF 1 or 2, and Transponder) and enter the frequency directly using the Numpad. The latest version is available near the end of the AVSIM thread here. You can use just about any keys to select the radios ( ie, you are not limited to the numpad for radio selection) as long as you first delete any potential key conflicts in FSX before reassigning them in FSUIPC4. Al

Currently setting frequencies or codes into the Com, Nav , ADF, and Transponder is cumbersome at best using the keyboard or mouse. The mouse radio hot spots are often difficult to use when flying (at least for me), and the keyboard tuning method ( using the + and - keys) is not particularly convenient either. What would be convenient, I think, is to key in the radio you want to tune ( e.g., C1, N2, T, etc) and then be able to enter the frequency (or code) numbers directly as a 4 or 5 number sequence (depending on the radio) using the keyboard number keys. And so my question to those who have the experience to know is, does this sound like a difficult programing task? Could the macro capability of FSUIPC4 be used to do this somewhat conveniently, at least for an a/c with a basic radio stack like in the C172? Thanks, Al

The FSUIPC4.INI and FSUIPC4.KEY files are backed up -- twice! Thanks again for the timely support. Regards, Al

Wow, what great support! Thanks very much Pete. One mundane question: When a new FSUIPC release is installed, are the current FSUIPC control assignments and calibrations carried over, or does everything have to be re-entered? Thx, Al

FSUIPC4 seems to be blocking the selection of the Nav 2 OBS when using the keyboard. In the C172 ( or Mooney Bravo) VC I can adjust the Nav1 OBS with either the mouse or the key combination Shift+V (and then the + or - keys), and I can adjust the Nav2 OBS with the mouse, but no combination of Shift+V #key will let me adjust the 2nd OBS. Any key combination Shift+V # activates OBS1. However, if I temporarily disable FSUIPC4 (by renaming the FSUIPC4.dll file) the keyboard sequence Shift+V 2 selects OBS2 as expected. I use FSUIPC4 to program buttons, switches, and axes associated with my Saitek yoke and pedals, but have not programmed any keys, and the FSUIPC4.ini file does not show an programmed keys or even have a [Keys] section. There are no joystick buttons or axes assigned in FSX, and no controllers enabled . I have a Win7 system. Thanks for any help. Al