Pete Dowson

What's wrong with the documented control? I assume you did look at the Lua library document provided in your FSUIPC Documents folder? ipc.control(65750,0) Pete

Firewalls are always a problem. If you are concerned you can make Wideclient an exception somewhere, but if you have a good security setting on your router that should keep the outside world off. Having firewalls between your own computers on your own Network always seems a bit over the top to me -- if the router is accessible to the whole network in any case I don't see how a firewall between them helps. It's just a nuisance. Pete

Good idea. I have the Prosim 738 which has this. That's where I tested. But no gauges as instrumentation is provided by Prosim. So I tested using the offsets. However, I looked in the Aircraft.CFG and it doesn't have a standby value for either ADF. I'll test again, but I have no expectations -- the swap ADF1 control works on ADF1 in any case, ad the swap ADF2 swaps ADF1 too. I'm pretty sure it's an old FS bug carried forward all this time. [LATER] Confirmed. Changing the Aircraft.CFG appropriately doesn't help. ADF2 Radio Swap still swaps ADF1 frequencies, not ADF2. Pete

You never need to add client names yourself, and you shouldn't edit that section. The clients are listed when detected by the server, and the numbers need to stay as assigned because they are used to identify button presses from the clients in Button assignments. Pete

If you speciffy the Server Name (or, better, the IP address) you need also to specify the Potoocol, as it clearly tells you in the documentation. This is because you are effectively telling it to ignore the broadcast information which would otherwise instruct it. Both WideClient and WideServer produce logs which may contain diagnostic information. Have you bothered to look at those? That's what they are for, to help! Pete

The list of all those which are actually FS controls is actually installed with all the other FSUIPC documents which you've presumably never read in the FSUIPC Documents subfolder in your FS Modules folder. The list of added controls supplied and supported by FSUIPC is in the Advanced User's document. Of course any macros or lua plug-in installed into the Modules folder also result in entries in the drop-down list too. I'm constantly amazed by how many folks don't seem to notice what they get when they install FSUIPC, even though the Installation and Registration document included in the download ZIP, alongside the Installer itself, does actually tell them. :sad: Pete

The ADF complete set control is a SimConnect Event, so documented in the Simconnect SDK. Like all controls it only writes, not reads. The parameter is the frequency value in Hz, in BCD format (Binary Coded Decimal -- like the offsets), as you saw in your logging. Pete

I've just released FSUIPC 4.949n. This contains support for reading (only) the ADF standby frequencies. Details are in the accompanying "Changes" PDF, but here they are too: 72. Additional offsets are now provided for the ADF standby frequencies, as follows: 0284 2 bytes ADF1 Standby Frequency: main 3 digits, in Binary Coded Decimal. A frequency of 1234.5 will have 0x0234 here and 0x0105 in offset 0286. 0286 2 bytes Extended ADF1 standby frequency. The high byte contains the 1000’s digit and the low byte the fraction, so, for a frequency of 1234.5 this offset will contain 0x0105. 0288 2 bytes ADF2 Standby Frequency: main 3 digits, in Binary Coded Decimal. A frequency of 1234.5 will have 0x0234 here and 0x0105 in offset 028A. 028A 2 bytes Extended ADF2 standby frequency. The high byte contains the 1000’s digit and the low byte the fraction, so, for a frequency of 1234.5 this offset will contain 0x0105. Note that there appears to be no way to actually write to the standby frequencies, so writing these offsets will do nothing except mess up the last value read. If this can be fixed at some time, it will be. Additionally the ADF2 radio swap control appears to be broken – it swaps the ADF1 frequencies instead of ADF2. This applies to FSX, FSX-SE and P3D at least up to version 3.2. Pete

But if both are renamed, ond only FSUIPC4 is listed, with no EXE's, how are all those other external DLLs and EXE's being listed in the SimConnect log file? There's still something fishy here. 0.03115 DLL Loaded: Path="radar.dll" Version="3.0.0.0" 3.04454 DLL Loaded: Path="Oculus.dll" Version="3.0.0.0" 3.04582 DLL Loaded: Path="ControllableCamera.dll" Version="<Unknown>" 3.04651 File not found: Path="C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\SODE\SimObjectDisplayEngine.exe" 3.04697 File not found: Path="C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Aerosoft\AirportController\APController.exe" 3.04768 File not found: Path="Captain_Sim\727\cs.sound.dll" 3.04815 File not found: Path="Captain_Sim\727\Captain_Sim.p727.menu.dll" 3.04859 File not found: Path="C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Sode\SimObjectAnimationModule.dll" 3.21380 DLL Loaded: Path="Modules\FSUIPC4.dll" Version="4.9.4.9" The FSUIPC entry is now good, and the FSUIPC4.LOG shows it is running fine. And the ONLY things now not loading which were loading before are: 4.04911 Exe Launched: Path="fsdreamteam\couatl\couatl.exe" CommandLine="" Version="3.0.0.3187" 4.06729 Exe Launched: Path="C:\Program Files (x86)\EZCA\EZCA.exe" CommandLine="" Version="1.1.8.7" 4.06900 Exe Launched: Path="C:\Program Files (x86)\SPAD\Spad.exe" CommandLine="" Version="0.5.0.0" So all you want is an EXE.XML with those three in it. Or, maybe better, run them using FSUIPC's "[Programs]" facility instead. Note that you don't have BGLMANX.DLL loading so COUATL.EXE is pretty useless in any case I think. Are you trying to use GSX? That needs BGLMANX for sure. At least you have FSUIPC now. I'm afraid I can't really help with the other things. You'll need to work out how those other DLLs are being referenced as well as the two EXE's it can't find -- somewhere you have another set of DLL.XML and EXE.XML files. Look in the ProgramData folder, where the Scenery.CFG file is. Pete

Okay. I've added offsets to read both ADF2 active and standby frequencies, but there's no way to change the standby ADF2 value. The aircraft you are using has a workaround to do the swap. That doesn't apply in general. The ADF2 complete set control only sets the active and you can't swap because the swap control doesn't work. I've tried all sorts of fiddles to make it work, but unless you have an add-on which has been coded to do it some other way, as you have, then the ADF2 standby is a wasted resource. I've reported it to L-M and can only hope they fix the Rado Swap control, at least. There are vacant slots in the controls table, so maybe some of those might do the ADF1 and 2 standby complete sets,, but I doubt it. I haven't the time or patience to try them all, just in case! If you think it might be useful I can let you have the version of FSUIPC4 with the new offsets, but otherwise it will simply be part of the next release, whenever. Pete

But what about all the DLLs which are loading but which are not listed in your DLL.XML? I really needed to see a log consistent with your earlier information, not one relating to completely different files. Try renaming both EXE.XML and DLL.XML, so nothing else will load, THEN re-run the FSUIPC4 Installer, test again, and show me just the early parts of the SimConnect log. I am only suggesting that since things seem to be in such a complete mess! How else to simplify matters so we can both understand what is going on? (But it need not be a separate DRIVE, just a new folder, like "E:\P3D"). Pete

See the stuff in the FSUIPC Documents subfolder. in your FS Modules folder. Did you not even read the Installation document packaged with the FSUIPC installer which tells you what is installed and where? Pete

And why were you not seeing text documents? It is NOT "FSUIPC.LOG" but "FSUIPC4.LOG". I only needed the first section, where it is loading stuff in any case. Look: 0.03235 DLL Loaded: Path="radar.dll" Version="3.0.0.0" 4.04425 DLL Loaded: Path="Oculus.dll" Version="3.0.0.0" 4.04546 Panels data export found and set to 559FF2F8 4.04547 DLL Loaded: Path="ControllableCamera.dll" Version="<Unknown>" 4.04618 File not found: Path="C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\SODE\SimObjectDisplayEngine.exe" 4.04663 File not found: Path="C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Aerosoft\AirportController\APController.exe" 4.04911 Exe Launched: Path="fsdreamteam\couatl\couatl.exe" CommandLine="" Version="3.0.0.3187" 4.06729 Exe Launched: Path="C:\Program Files (x86)\EZCA\EZCA.exe" CommandLine="" Version="1.1.8.7" 4.06900 Exe Launched: Path="C:\Program Files (x86)\SPAD\Spad.exe" CommandLine="" Version="0.5.0.0" 4.06980 File not found: Path="Captain_Sim\727\cs.sound.dll" 4.07044 File not found: Path="Captain_Sim\727\Captain_Sim.p727.menu.dll" 4.07093 File not found: Path="C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Sode\SimObjectAnimationModule.dll" 4.07200 DLL Load Failed: Error=-1 Path="Modules\FSUIPC4.dll" I see it is successfully loading "radar.dll" and "Oculus.dll", and it fails to load "cs.sound.dll" "Captain_Sim.p727.menu.dll" and "SimObjectAnimationModule.dll" because it can't find them. Now NONE of those are listed in the DLL.XML file you posted earlier! Also How can that be? And none of the ones you do list are loaded at all. I am thinking you are looking in the wrong place for these things. Also, I only just noticed, but the DLL.XML you did show has this entry: <Launch.Addon> <Name>SPAD</Name> <Disabled>False</Disabled> <Path>C:\Program Files (x86)\SPAD\Spad.exe</Path> </Launch.Addon> which is for an EXE file! That should not be there! It belongs in the EXE.XML file! And you have many entries in the EXE.XML, two of which are bad -- SimObjectDisplayEngine, and APController! You have Couatl.exe loading but the BGLManx.DLL it depends on is not being loaded. So all in all, nothing corresponds with what you posted before and it looks to be in a mess. The attempt of SimConnect to load FSUIPC4 is logged, but with Error -1. I've no idea what error -1 means. I've never seen one before. All the documented SimConnect errors are positive numbers. I think you have somehow got your P3D installation into a real mess. I can only suggest you start again, uninstall it and try reinstalling it some place differently, to avoid the mess with FSX. And edit the Registry to remove the FSX installation pointers. Pete

Interesting, but I'm not sure how useful it is. L:Vars are specific to the gauges which are part of the add-on aircraft. It looks like they've implemented parts of the ADF2 logic using L:Vars, probably because of the lack of proper support in FS. In other words, it's a work-around. No. That is bound to be the actual frequency in Hz in BCD format. Values not in the correct range for ADFs will just be ignored. I would experiment here, but there is no default aircraft with two ADFs both with standby's as far as I know. I'll see what else I can do. Maybe reading the standby frequency, then using ADF2 Complete Set with the value can solve the lack of a swap control, and reading the active, using Complete Set with the new standby value, THEN using it again with the saved active will do the job of ADF2 standby complete set. First I shall get the standby frequencies into offsets, then perhaps you could try that logic there, since you have such an aircraft? Pete

FSUIPC makes no distinction about the source of the button press. So could this be a question for Spad? Have you tried Button logging in FSUIPC to see what the difference is, apart from the button numbers? Pete

Sorry, I've no idea. How would it get it on the FS PC? I thought you implied it would work there? If it did and it uses FSUIPC, then WideFs would solve it on a client PC -- there's nothing to it other than paying for it and installing it, so what's "not simple"? What would Teamspeak do with this frequency when it has it? I didn't think it had anything to do with FS, but then I've never used it. If it doesn't use FSUIPC then you are in the wrong Forum. Maybe this explains your confusion? Pete

Sorry, i cannot really support add-on aircraft. Many do their own thing. You need their support. Pete

I know how to use the ADF2_COMPLETE_SET control. They are simple decimal Hz. decimal That's no problem. But what does the swapping? Are you clicking a button on screen? Is the value in the control the one which was in the STBY frequency display or the current one? Pete

No no! I mean the FSUIPC4.LOG file -- the LOG which FSUIPC always makes anew when FS is started! You said you hadn't deleted it, so it is still there from when things were okay! Please check again! That is fine. So there MUST be a log in the Modules folder called "SimConnect01.log" (or similar). I'm beginning to think the files I need to see are there but you are simply not seeing them. You are either looking in the wrong place or you are not recognising them. Check that you are allowing Windows Explorer to show the proper names -- select the "Organize" menu in Explorer, then Folder Options. -- View, and ensure the option named "Hide extensions for known file types" is NOT checked. Then look again. I'm to bed now. Tomorrow is another day ... Pete

There have only ever been TWO purchasable FSUIPCs -- FSUIPC3 and FSUIPC4. Once you purchase either one then all versions are freely updated as you wish and as expected of you. Same with WideFS -- only WideFS 6 and Wide FS7. All previous versions of both were free. First off, WHY do you want to use range assignments? Also what is so obscure about them? You simply move the lever, make the assignments and so on, for up to 10 separate areas and if needed differently for up and down. It is all included in the FSUIPC User guide. did you read that? Anyway, for flaps there are already calibration facilities for all steps of your flap lever, provided you first choose the aircraft withn the number of detents you need. And spoiler calibration sets both the Armed and Flight detents, which is all any aircraft has. I think you are expecting something in the Assignments which is really all to do with Calibration! You are, maybe, just looking in the wrong place? Calibration can apply to FS assignments, which is why it is separate from assignment. Pete

So it is still there, with the old date? Simconnect MUST create a log if instructed correctly! Please show me the SimConnect.INI file you made and tell me where you placed it! Pete

Please enable Event logging in FSUIPC and try that so we can see if any standard events are used. Pete

Hmmm. I need to see a SimConnect log please. See the FAQ subforum here for details of how to make one. BTW did you delete the last log from when things were "okay"? Pete

How were you using the standby ADF frequencies in any case? Pete

Well there's an entry in the Registry saying that FSX is there too, and the FSUIPC installer is installing itself there too. It's just lucky that the Installer installs for P3D after FSX! So what did that do which could possibly stop FSUIPC4 even being loaded? Makes no sense at all. Are you sure that FSUIPC4 is not being loaded when you rename the DLL.XML and rerun the FSUIPC installer to get a DLL.XML which only loads FSUIPC? Try that again and check the add-ons menu and look for an FSUIPC4.LOG again. (You must have a log there already from when "everything was okay", by the way). Pete