Pete Dowson

So what serial port USB driver are you using? I had no end of problems when I used the basic FTDI ones. That's when I looked around and tried the Brainboxes ones. Never any problems since then. See if you can compare drivers and versions between the PC on which it worked and the two on which it doesn't. Pete

In the FSUIPC options, in P3D. As you’d find out very quickly if you read some of the documentation! Pete

Well my PC is very recent. But surely you are not relying on the old style COM ports which used to be available on the motherboard? Try one of the Brainboxes cards or USB adapters. Their drivers are excellent. Pete

Yes. That's certainly a main reason for purchasing it. Please take a look in the User Guide. There are chapters on those facilities. Pete

It is FSUIPC6, not USIPC6. It means "Flight Sim Universal Inter-Process Communication", referring to its basic and original fundamental purpose of supplying Sim data to other programs. What do you mean by "client"? FSUIPC is a DLL module which loaded by and runs inside P3D4 or P3D5. If you are thinking of WideClient, then that is part of WideFS (a separately purchasable product to FSUIPC), and WideClient.EXE is run on a client PC, linking to FSUIPC across a local network. Pete

I've no idea, but I do know that leaving controllers enabled in P3D is asking for trouble if you want to assign in FSUIPC. If you prefer assigning in P3D then all FSUIPC calibration is doing is assigning whatever P3D reports. Pete

FSUIPC's link works whether you purchase or not. It isn't made available after buying, it is always available as many folks use FSUIPC in its free mode -- for supporting FSUIPC applications or WideFS. If you were provided the wrong link in an email from SimMarket then I need to tackle Simmarket about that. You are the first person to report this so i can only assume they've changed something. Please can you send me the actual email you received -- send as Private Message (pm) or attached to an email to petedowsno@btconnect.com. Where are you seeing such messages? There's certainly no "run a later version..." message anywhere in the installer! The process of installing is extremely simple, much more so than many add-ons these days. I'm really bemused about what you are doing. You have so far supplied very little information. Are you trying to install for FSX or for P3D? Which version? The Installer produces a Log file, "FSUIPC4 Install.log" in the folder in which you run it. Please show me that. You can cut-and-paste it into a message here. Pete

As well as what Thomas and John advised, you should complete disable controllers in FSX if you are assigning in FSUIPC, not just de-assign specific axes, otherwise you are liable to get conflicts. Pete

SimMarket have links to installers for all versions of FSUIPC, not just FSUIPC4. The one you need is http://fsuipc.simflight.com/beta/FSUIPC4.zip You can find correct installers and other software from us on fsuipc.com Please read the Installation guide document found within the ZIP. Pete

No. Currently FSUIPC only offers to create SimConnect Message windows (ipc.display). You can of course fashion a GSX-style menu with that, then have a series of event.key lines, one for each possible selection,, which call a function to action that selection. This way you are not restricted to keys 0-9, you can use whatever keys you wish, including those combinations with Ctrl, Shift or whatever. If you don't want them to be passed on to the Sim you'd need to add "LuaTrapKeyEvent=Yes" to the [General] section of the FSUIPC INI file. After a response has been received and actions, use ipc.exit() to terminate the plug-in. Pete

That looks fine. You are making a mistake somewhere. Although John says to leave the WideFS registration blank, with the FSUIPC4 Installer you should not even see a place to enter the WideFS key. The first Registration window to appear will show 3 button selections: FSUIPC4, WideFS7 or Both. You can only select ONE of those. Just select FSUIPC4. Even if you select Both you will get two separate Windows then appearing, one for FSUIPC4 then a different one for WideFS7. If you are seeing anything which allows you to enter details for both FSUIPC and WideFS on the same screen then you are running the wrong installer! For registration all three fields -- Name, Email and Key, must be exactly correst, as shown in the registration details on SimMarket. Most occasions when folks get them wrong they are entering their name differently. best to cut and paste all three parts. Pete

Ah. Right -- so that confirms the port has not sent any data. I think you need to investigate possible problems with the drivers in your Windows setup. Is the COM port an added one, like mine (a BrainBoxes USB to Serial adapter) or one of those heritage type motherboard ports (now apparently discontinued)? I can thoroughly recommend BrainBoxes serial ports, whether PCI, PCI-E or USB adapter. All of my serial port devices are connected to one or other of these -- my complete PFC cockpit uses two such ports, and on a separate PC my Arduino, used to operate relays for the genuine 737 starter switches. Also my Aerosoft (Australia) GA28R Piper Arrow III cockpit, which is also 100% COM serial port driven. Just make sure you have up to date drivers installed. Pete

You need to use a variable to receive the result of the com.write. I don't know where your Close signal is coming from. As far as FSUIPC is concerned it is still connected, at least on my system, otherwise the attempts to write through the Windows functions would not confirm bytes transferred. You say: so I believe it is something different about the installation of drivers on your different PC. Certainly the code for com ports is no different in FSUIPC6 from FSUIPC5. To see the results of the com.write in the Trace you need to have the result stored in a variable, as in the change I did here (if you refer back). Pete

You say you are "now" having issues. does that mean you didn't before? Before what? The complete first section appears to be commented out. However, if you used it in anything like its current form you do an ipc.exit no matter whether the port is opened successfully or not. How are you detecting that the com port is being closed? I've run your script here, only changing two things: 1 the com port: the only one I have is "com3", 2 the com.write line to num = com.write so i can see if data was sent. I then used the Lua tracing option (in the Logging Tab) to see the numbers: 468312 LUA.2: beginning "E:\FSUIPC6\comtest.lua" 468312 LUA.2: E:\FSUIPC6\comtest.lua:1 468312 LUA.2: Global: ipcPARAM = 0 468344 LUA.2: E:\FSUIPC6\comtest.lua:23 468344 LUA.2: Global: dev = 2 468344 LUA.2: E:\FSUIPC6\comtest.lua:14 468344 LUA.2: E:\FSUIPC6\comtest.lua:25 468344 LUA.2: Waiting for an event in "E:\FSUIPC6\comtest.lua" 468344 LUA.2: Offset Change event: calling "NoseGr" in "E:\FSUIPC6\comtest.lua" 468359 LUA.2: E:\FSUIPC6\comtest.lua:15 468359 LUA.2: Local: offset = 3056 468359 LUA.2: Local: value = 16383 468359 LUA.2: E:\FSUIPC6\comtest.lua:17 468359 LUA.2: Local: value = 100.01831501832 468359 LUA.2: E:\FSUIPC6\comtest.lua:19 468359 LUA.2: Global: sentence = <A100 468375 LUA.2: E:\FSUIPC6\comtest.lua:21 468375 LUA.2: Global: num = 5 468406 LUA.2: E:\FSUIPC6\comtest.lua:23 468406 LUA.2: Waiting for an event in "E:\FSUIPC6\comtest.lua" Note that report "num = 5", showing 5 bytes were sent. So then I tested with a deliberate close, inserting com.close(dev) before the function. 1032578 LUA.3: beginning "E:\FSUIPC6\comtest.lua" 1032578 LUA.3: E:\FSUIPC6\comtest.lua:1 1032578 LUA.3: Global: ipcPARAM = 0 1032609 LUA.3: E:\FSUIPC6\comtest.lua:12 1032609 LUA.3: Global: dev = 2 1033469 LUA.3: E:\FSUIPC6\comtest.lua:23 1033469 LUA.3: E:\FSUIPC6\comtest.lua:14 1033484 LUA.3: E:\FSUIPC6\comtest.lua:25 1033484 LUA.3: Waiting for an event in "E:\FSUIPC6\comtest.lua" 1033484 LUA.3: Offset Change event: calling "NoseGr" in "E:\FSUIPC6\comtest.lua" 1033484 LUA.3: E:\FSUIPC6\comtest.lua:15 1033484 LUA.3: Local: offset = 3056 1033484 LUA.3: Local: value = 16383 1033484 LUA.3: E:\FSUIPC6\comtest.lua:17 1033484 LUA.3: Local: value = 100.01831501832 1033484 LUA.3: E:\FSUIPC6\comtest.lua:19 1033500 LUA.3: Global: sentence = <A100 1033500 LUA.3: E:\FSUIPC6\comtest.lua:21 1033500 LUA.3: Global: num = 0 1033500 LUA.3: E:\FSUIPC6\comtest.lua:23 1033500 LUA.3: Waiting for an event in "E:\FSUIPC6\comtest.lua" You'll see that because the port was closed, num = 0, i.e. zero bytes were written. So it is definitely working properly. Pete

Button numbers are determined not by FSUIPC but by the data read from the USB device. It is impossible for FSUIPC to change them, and once assigned the button number in the assignment can't change by itself. As Thomas says, FSUIPC numbers the buttons from 0 to 31. Internally Windows does the same, but it adds 1 for display, giving 1-32. This has always been the same and does not change by itself. If you assign in FSUIPC you should disable controllers completely in P3D otherwise you will get conflicts and the sort of confusion you are currently suffering. Pete

The biggest problem is that you are using the very first, very buggy, version of FSX. You should update. The SP2 update fixed a lot of things and is free -- just download and install. But questions first: In the FSX Modules folder are there some FSUIPC4 files apart from the Install log and FSUIPC4.DLL itself? There should be the log, the settings file (ini) and if you registered your key file containing your registration. Please check. If there is a Log please show that. If there's no log or settings file and the FSUIPC menu isn't appearing, then FSUIPC isn't being loaded. In that case the file to see is the DLL.XML file. Now I see something very odd. You say you reinstalled Windows then FSX. But something created an DLL.XML file before you installed FSUIPC, which is odd. Did you install something else beforehand? The SDK or something? Anyway, I fear the DLL.XML file may be corrupt. you can find it here: C:\Users\fambr\AppData\Roaming\Microsoft\FSX\DLL.XML Paste its contents, as a text file, here, please. But first I strongly recommend that you install the SP2 update (or at least the SP1 update!) Oh, one last thing. I see you let FSX install into the worst place possible under Windows 10 (Win10 wasn't thought of back in 2005): SetupPath=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ Under Windows 10, unless you turn off assorted Win10 protections, the Program Files folders are readable, but not writable unless you run your programs with administrative privileges. FSUIPC needs to be able to write the Log and Settings back to the Modules folder, so you will probably have to run FSX by right clicking and selecting "as administrator", or changing the compatibility setting in its Properties to do that. Pete

Are you using the common FSUIPC6 install for both P3D4 and P3D5? Assuming so, your FSUIPC settings will be the same for both. (If not you should copy the INI file from one to the other). Since then there'll be no difference in either the NGX or FSUIPC, the difference much be in P3d. And the most likely is a conflict with P3D settings. Check that you definitely have controllers disabled in P3D5. Pete

The settings are saved in the FSUIPC4.INI file. The only way of losing them is to edit, delete or corrupt the file. If no Log is being produced then FSUIPC is not being loaded, which is why there's no menu. Your DLL.XML file is probably corrupt or missing. you could try simply running the FSUIPC4 installer again. That might fix it. If not you need to find your DLL.XML file and show us that. It'll be in your FSX AppData folder, where the FSX.CFG file is. If you can't find it, look in the Install log -- it'll show the DLL.XML folder, logged when it adds FSUIPC to it. Pete

Assuming you have your assignments for these in FSUIPC, then the only part FSUIPC plays is sending the assigned control on to P3D. If you aren't assigning in FSUIPC then it is playing no part whatsoever in this. So, no, FSUIPC can't help. But of course you should update to the latest version in any case as we can only support current versions. From what you describe I would guess that you have conflicting controls. If using FSUIPC for assignments make sure you have controllers disabled in P3D -- not just un-assigned, you need to actually disable controllers. Otherwise it definitely sounds like the A2A aircraft you installed are not fully compatible with P3D5. Pete

No, WideFS can only connect to one sim at a time, so it can read the data needed from one but cannot write it to the other. I thought the shared cockpit facilities did all the syncing of aircraft and sceneries for you? Perhaps you need to investigate WideView which was, and maybe still is, the go-to software for linking multiple PCs running FS or P3D. Pete

With any toggle control which you wish to use a latching switch instead of a button you need to look to see if there's an FSUIPC offset which will tell you the state. In this case there is -- this is the entry in the Offsets list (in your FSUIPC documents folder): 132C 4 NAV/GPS switch. 0=NAV, 1=GPS Ok First assign both switch positions to that control. Then find the assignment lines in the settings file (FSUIPC4.INI) and edit them to make them conditional on the offset value. See the section ADDING OFFSET CONDITIONS in the Advanced users manual (page 27 or thereabouts). Note that the simple alternative is simply to assign the switch to the same control in either position, and just make sure it's in sync with your panel when you start. Pete

Since FSUIPC4 ceased development a while back, and that recent change was only to do with the recognition of different ways that SimConnect gets installed with some Windows 10 installations, I think you are okay sticking to 4.974a since that works for you. I'm afraid I don't have any PMDG aircraft and only have access to FSX-SE these days, so I doubt I'll be able to do that. Was 4.975a working well for you otherwise? If not you'd need to supply Install and run-time Logs for us to check. You also say but of course this thread was concerned with FSUIPC6, not FSUIPC4. Pete

That reallt can only mean that the Honeycomb yoke (or more likely its software) is sending "on" signmals for its buttons even when you haven't pressed them or switched them on. Two things there: 1. John looked at your settings and you don't have any for that device. 2. you should ALWAYS disable controllers in FSX if you are making assignments in FSUIPC. it's one or the other, else you'll get conflicts. That's where you need to look. I bet that's where the problem lies! If it is a standard USB joystick device (e.g. recognised as Windows as such -- look at Game Controllers) it needs no special driver. mostly those drivers are used for software which isn't very good at deciding how to use a device. You might find it beneficial to uninstall their drivers. Pete

The latter is more reasonable. Large increments are obtained by fast multiple clicking or repeating keys/buttons, which are interpreted as accelerations. The typical small increment is 512 units for the full joystick range of -16384 to +16383, so with 32768 units altogether there should be 64 steps altogether. Not sure how you only get 10, though I suppose acceleration may account for it. But I've no idea what could cause a change over time. See if the Logging shows anything changing, as Thomas suggests. Pete

Direct Wind Control is a hack in the 32-bit code of FSX and P3D, and is not applicable to the 64-bit P3D4 and P3D5 versions. There are no hacks implemented in FSUIPC5 and FSUIPC6 which abide strictly to the SimConnect interface. There are no plans to implement any hacks in the future. Sorry. Pete