John Dowson

Also, I have noticed in the JF PA28 Arrow, if I set an ADF frequency (no decimal allowed when selecting) and keep the mouse over the frequency knob, the decimal part increments from 0 to 9 and then back again, changing approx every 4 seconds, and I see ADF Fract Inc/Dec Carry events being sent (9 inc events, followed by 9 dec events, then repeating). So it looks like the ADF for that aiircraft scans the decimal frequencies, although they are not displayed.

What aircraft allow a decimal part for the ADF frequency in the ADF panel? I have checked several aircraft and none I can find so far allow a decimal part to be set. Also please see this - it relates to x-Plane but is still relevant: https://forums.x-plane.org/index.php?/forums/topic/202498-how-to-change-the-decimal-in-the-adf/ John

How are you currently tuning the ADF? This should be possible either using the standard controls or using the FSUIPC ADF frequency offsets. However this can also depend on the aircraft, as some add-ons can implement their own controls (via lvars or custom controls) and not respect the provided controls/events or simvars. I have also noticed that writing to the ADF1/2 standby frequency offsets at 0x0284, 0x0286, 0x0288 and 0x028A was disabled in an earlier version of FSUIPC7. Not sure why this was, but I will re-enable these and check if they are working. Anyway, could you show me your assignments (attach your FSUIPC7.ini file) and let me know which aircraft you are using. Thanks, John

This should make a difference. This will only affect the options that are available to you. John

Those are lvars. To assign an axis to an lvar, the easiest way is to create a preset. First, you need to determine what the maximum and minimum values that the lvar takes (you can list the lvar values when the throttle/mixture levers are at the extremes), and you must also know the maximum and minimum values the axis sends. The preset, which you need to add to your myevents.txt file (create this if not present) will then take the form DuckWorks_Throttle1#@ <conversion> (>L:lvarname) where <conversion> - is the RPM code to convert the axis input value range to that expected by the lvar lvarname - is the name of the lvar that controls the aileron position You can then check the Send Preset to FS in the top-right of the axis assignment panel and assign your axis to the preset DuckWorks Throttle1. There are other posts where I have shown how to use an axis to control an lvar:

I can't help if you don't show me your files. Are you sure that your lua script is running? When using LuaValue, your script should be auto-started from your [Auto] or [Auto.xxx] (profile) section of your FSUIPC ini file.

Can you please attach your FSUIPC7.ini and FSUIPC7.log files, the latter generated with logging for Buttons & keys and Events activated - activate the logging, load your aircraft in MSFS, then press a button or two that is assigned but not working, then exit FSUIPC7 before attaching your files. And if your assignments are using the specific PMDG offsets (e.g. for offset conditions), then make sure you have activated the PMDG data broadcasts in the PMDG config file (details in the PMDG offsets guide). John

I have checked the following presets in the A320-dev version and they all work (i.e. I can see the associated knob rotate): A32NX_LIGHTS_GLARESHIELD2_INC (*) A32NX_LIGHTS_GLARESHIELD2_DEC (*) A32NX_LIGHTS_GLARESHIELD3_INC A32NX_LIGHTS_GLARESHIELD3_DEC A32NX_OH_INTEG_LIGHT_INC A32NX_OH_INTEG_LIGHT_DEC All except the first two (*) also control the brightness for what they are trying to control - with these I can't see any brightness changes (although the knob moves, but that is probably because I don't know where to look! To set to a specific value using calculator code: this doesn't work. It seems that the 'K:2:LIGHT_POTENTIOMETER_SET' event needs 2 parameters (probably what the ':2:' indicates). So try this - it works here: ipc.execCalcCode("25 84 (>K:2:LIGHT_POTENTIOMETER_SET)") So the 25 indicates the percentage, and the 84 the index of the LIGHT POTENTIOMETER simvar that the event is controlling. You can change these values to control the %age and the lights, where 84 indicate glareshield brightness, 87 FCU brightness, 86 the Overhead panel integrated light knob, 85 the pedestal light knob Integ brightness, 83 the pedestal light knob Flood Captain, 90 right PFD brightness, etc I knew some events can take two parameters - this was introduced in an update a few months ago, but I didn't know how you actually used them in calculator code until now, so this has also been a valuable learning experience for me. Hope this helps - let me know how you get on. If you can't get this to work, I will need to see your files - your FSUIPC7.log (with logging for Buttons & Keys and Events activated, as well as Debug level logging set in the WAPI) and FSUIPC7.ini files, together with your lua files. John

Well, the error says it can't find C:\VRInsight\bin\Inst_Panel.exe - does that exist on your new PC? If it does, can you run it? Have you tried re-installing it?

There are no changes between 7.3.21 and 7.3.23 that could affect your VRInsight configuration. What exactly is the problem? Please explain, and also please show me/attach your FSUIPC7.ini and FSUIPC7.log files. I have also attached the exe for 7.3.21 for you to try - temporarily rename your current FSUIPC7.exe (e.g. to to FSUIPC7.exe.7323) and save this to your FSUIPC7 installation folder. I expect you will get the same issue, but if not please also attach your FSUIPC7.ini and .log files for this version. John FSUIPC7.exe

Your license key details will be in the email and also available from your SimMarket account, there is no key file. You have to re-install and enter your key details at the end of the installation process to generate your new key file with your details. You can also just edit the trial FSUIPC7.key file and replace the details in there with your key details. if you do it this way, make sure that you copy all 3 parts (name, address, key) to the correct fields. John

Yes it is - everything in the FSUIPC lua library document is specific to FSUIPC. - it is the FSUIPC lua library after all!

First, can you try just assigning (a key or button) to the available presets (that I mentioned earlier) for glareshield and/or o/h integ lights inc/dec (if you haven't already) - do they work for you? Also make sure that you are also using the latest version of FSUIPC7, v7.3.23. I will switch to the dev version and check this tomorrow and let you know if they work here. If they work, it should be straightforward to use something similar on an axis/potentiometer, or to send/set a fixed value.

I have checked and there is no SDK for the DC-6. Take a look at the available lvars (Add-ons -> WASM -> List Lvars) and the available presets (https://hubhop.mobiflight.com/presets/). John

You need to also install the PFC driver (PFC.dll) - see fsuipc.com. This topic is for a trial license for MSFS2020, not FSX. I do not provide trial licenses for FSUIPC4 (for FSX).. Do you want a trial license for FSUIPC7 for MSFS2020?

No they don't, as I have explained several times. Offsets will be written starting from the offset specified and to the number of offsets required by the type and size of the data you are writing, and when you read from an offset it will read that offset and the consecutive ones up to the size if the data type you are reading. Everything works as it should, and nothing "leaks". You just need to understand how memory addresses work. Of course not, as that would just call the getnumbersfromtext function each time the offset changed - that is obviously not what you want.... Whatever you like - you have to wrap your script in a function, e.g. based upon the last script you posted function getnumbersfromtext(spdstate) return tonumber(spdstate:match"%d+[%d.,]*") end funcyion decodeString(offset, spdstate) if (string.find(spdstate, "%-") and string.find(spdstate, "%*")) then ipc.writeUB(0x66C5,1) ipc.writeUB(0x66C6,1) elseif string.find(spdstate, "%-") then ipc.writeUB(0x66C5,1) ipc.writeUB(0x66C6,0) elseif string.find(spdstate, "%*") then ipc.writeUB(0x66C5,0) ipc.writeUB(0x66C6,1) else ipc.writeUB(0x66C5,0) ipc.writeUB(0x66C6,0) end if string.find(spdstate, "SPD") then ipc.writeUB(0x66C7,1) else ipc.writeUB(0x66C7,0) end if string.find(spdstate, "MACH") then ipc.writeUB(0x66C8,1) else ipc.writeUB(0x66C8,0) end if string.find(spdstate, "%-") then ipc.writeSW(0x66C1, 0) -- speed hast to be forced to 0, when the dashes appear in managed mode, otherwise there will be interferences with the dashes else speed = getnumbersfromtext(spdstate) speed100 = speed*100 ipc.writeUW(0x66C1, speed100) -- logging "speed100" with U16 in the simulator and a 2 byte integer in MobiFlight end end -- of function decodeString event.offset (0xABCD, "STR", 9, "decodeString") If you are planning to use lua, you should look at some on-line lua tutorials. Also take a look at the example lua scripts provided, which are located in your FSUIPC documents folders. There are also plenty of examples in these forums. John

I have moved your comment to a new topic. What do you mean by this? What values are you looking for? Does the DC6 have an SDK, similar to the PMDG 737? If it provides an sdk with additional data that I can use, then I can add this to offsets, as I do with the PMDG 737. Otherwise, maybe check the available lvars. Looks like the DC-6 also uses custom controls in the same way as the PMDG 737 - check the FAQ section on how to use these (although the FAQ refers to the PMDG 737, it should also apply to the DC-6). There are also > 100 presets available for this aircraft, so check them out. Also check-out other posts in this forum on using the DC-6. John

@salsero_at Do you still have this issue? If you want me/us to help you, please supply the required files (see my last comment), otherwise I will close this support request. John

I understand this, but do understand what you mean when you say it isn't working...how do you know this? What errors are you getting? Are you using FSUIPC7, and if so what does that report for the WAPI? Try also setting Debug level logging for the WAPI, and show me/attach your FSUIPC7.log file first, as this will tell me if FSUIPC7 is connecting to the WASM or not. Doesn't matter - you can still download and re-install, as this will also re-install the WASM module. John

What do you mean by "no longer work"? Is it still in your Community folder? What does the FSUIPC_WASM.log say? Have you tried re-installing it? Later: note that you should NOT be using the version of FSUIPC7 posted above - that is now over a year old. Please download and install the latest version, 7.3.23. The installer will also install the WASM for you.

@chickster25 I have just taken a look at this in more detail. The preset works reasonably ok here but only moves the lever between the discreet 4 or 5 positions. However, I can fully control the lever by assigning with Send to FS as normal axis using the Axis Spoiler Set control. Make sure there is no calibration being performed - go to page 6 of the calibration tab and remove any calibration by clicking Reset in the spoilers.

I am very surprised that works... If you remove the general button section from your FSUIPC7.ini file, it will get added back with the default values. The ButtonRepeat rate is not read from a profile button section..... John

License sent. John

But, as I keep saying, ypu shouldn't do this.... If you are storing a number in an offset as a 2-byte word, you should store it starting on a 2-byte offset, e.g. at 66C0 or 66C2. It way seem to work, but you can get problems if you don't do this, depending on how the offset is accessed... Rather than have it run in an endless loop, you can use the event.offset function, using offset 0xABCD, so that you update each time that offset changes value - this would be more efficient.

What version of the A320 are you using? The MF presets for the glareshield lights are for the dev version only - did you try in that version?