Leaderboard

There's no copyright claim on the original script, so I've uploaded my version of it here... Original file courtesy of Manolo Velez. You'll need to open this in the SIOC utility. Open SIOC.exe Choose "Edit Script" Files -> Import TXT (and select this attached file) Save As... (it'll compile as an .ssi file) Once compiled you may need to click the "Reload" button in the man SIOC utility window. All done! (hopefully) I'm a novice when it comes to this stuff, so I'm afraid I can offer no support. (See latest version below...)

Hi @jonas_llubi, @Abt. I share you frustration with this. In fact, I spent the last 6 hours vibe coding an AI-assisted solution for a SIOC script that correctly handles the COM1/2 active/standby frequencies for both 25kHz and 8.33kHz frequencies. I also changed the logic so that it truly does work as a slave device, in that if MSFS changes the frequency itself (or another app like BATC etc does) then the updated frequency will appear in the panel, and it won't keep overriding MSFS. Limitations: It's really nasty code, made with the assistance of AI. Works with MSFS2020, but not yet tested for MSFS 2024. The SIOC script also doesn't appear to work for the Nav radios. I based it off the originally provided SIOC scripts from opencockpits (I'm not sure if I can share it openly with you, but there is no copyright notice on the original), and that original script doesn't work for Nav radios in MSFS2020 either. For me, the COM 1/2 radios were much more important. I can revisit the NAV modes later perhaps. In testing, the display does sometimes go black, and the panel appears to fail. To fix it, you have to just press the "Reload" button in the SIOC utility. I changed the logic so that it always initialises with the active COM1/2 frequencies from MSFS so that it doesn't reset anything if you have to restart multiple times in the middle of a flight. I hope it works as a stop-gap until something better comes along though! Edit: The NAV VOR and ADF radios don't work, but the ILS mode frequency and course values do work! If you're interested, let me know and I can send the script to you privately. Linguini

Urgent Fix / Update Some Things slipped through, sorry for the Inconvenience! Version 0.8.9 - Fixed Lua Scripts not properly stopped/started (and therefor not working) - Fixed InputEvents.txt (detected B-Vars) not being created - Fixed Version-Check not notifying about new Dev-Builds

A brief note to thank your and Pete for your wonderful FSUIPC product. I've been using it for about 20 years and have found it superior for controlling my aged CH products. They are still working in spite of their aging POTS while FSUIPC irons out the bumps and jerks of the old systems. Keep up the good work! Jim Driskell

This really shouldn't happen... I have realized that I made a mistake with the 7.4.18 release...I have been testing the SDK for MSFS2024 and accidentally built the final release of 7.4.18 with the SDK from this version, instead of the version for MSFS2020. Sorry about that - I have corrected this now and have updated the installers with this correct build. Could you therefore please re-download and try again. if you get the same issue, please show me / attach your FSUIPC7.log file. Note that I have kept the version number the same, at 7.4.18, but the build date has been updated to 3rd November, so please check thar you are using this version (you may need to clear your browser cache to download this version. I have also attached this version below, but you should really re-install as the WASM has also been rebuilt. You can prevent this by setting the following ini parameter under the [General] section of your FSUIPC7.ini file: OpenOnStart=Never John

Top tip. Also I never realised about the profile thing. If I got a new paint I'd have to point it to the appropriate profile. In the end I'd have l list as long as your arm of Comanches. 😂 Thanks for your time John. I expect I'll be back in the future with more 'insurmountable problems' 🙄

Ok, that can happen. Thats fine - whatever works for you. Just pointing out that for most things, the various FSUIPC logging facilities should be proficient enough, but you do have to 'connect the dots; as you say. Yes - you need to do it this way anyway if the position lvar only changes the position but not the actual function/lights.

Note that you can see available lvars by listing them (Add-ons=>WASM->List Lvars) - no need to use the MSFS behaviors dialog, except as a last resort (i.e. usually to discover b-vars or h-vars). No problem about the incorrect lvar name - these things happen...! Now you have the correct name, you should check if setting that directly works to control the switch. If so, the assignments can be simplified as you don't need the compound condition on the position of your switches, and you only need to send the one one command to change the lvar two positions instead of three (e.g. switch up, pause, switch up). Anyway, you should try and understand those assignments and try to assign yourself the next time you want to make a conditional assignment. I will help if you run into problems, but you should have enough info in this thread to make a start. Regards, John

I don't know - I don't have this aircraft. Have you tried it? Use the Add-ons->WASM->Execute Calculator Code menu option, and try sending each of the following: 30 (>L:VC_Miscellaneous_trigger_VAL, number) 31 (>L:VC_Miscellaneous_trigger_VAL, number) to see if those move the switch. They should work, as that lvar controls the dome switch (with parameters 38 and 39). Also try the following: 10 (>L:VC_POSITION_LIGHT_SW, number) 0 (>L:VC_POSITION_LIGHT_SW, number) 20 (>L:VC_POSITION_LIGHT_SW, number) to see if those move the switch. If they work, we can simplify the assignments. If you still have issues, please activate WAPI Debug level logging (Log -> WAPI -> Debug) and logging for Buttons & Keys, and show me / attach your FSUIPC7.ini file and FSUIPC7.log file, the latter showing you using the assigned buttons. And always exit FSUIPC before attaching files please. John

Yes, I understood. Just trying to point out that when using two switches, one for each light, its never going to work in the same way as one 3-position switch to control the lights. The honeycomb light switches are designed for on/off of each of the lights, so however you implement this is going to be a fudge, but maybe ne that you can live with. And no need for the pictures either... Yes, that's fine. No, but you can assign to a preset and then make that assignment conditional on an offset value. Or just also add the lvar VC_Miscellaneous_trigger_VAL to an offset, and just use assignments with offset conditions, as I advised. If you can just tell me what you want the switch position to be in the UP/UP state I can show you how to do this - its easier to do it this way than in lua.

Hi John. you are really the BEST !!! Very very professional and always helping in a very short time. Thanks a lot again Claudio Damiani

Not doing too bad, thanks. And yes, I try to remain hopeful, but seems to get harder by the day...!

Thanks John. Greets..Hope you are well..

FSUIPC7 7.5.3 and likely other external apps using SimConnect and crashing FS24 SU3 1.5.10.0 are solved in FS24 SU3 1.5.12.0 It was even mentioned in the release notes! For now I a happy simmer again.

Thanks John Followed your instructions and now works great Thanks for your time and knowhow. I started Flight Sim about 20 years ago and using the mouse didn't appeal so building switch panels became part of the hobby, but it was only with FSUIPC with yourself and Pete (hope he is keeping well) that i could get them to work. Kind Regards Brian

Thank you, I moved FSUIPC to starting first, and changed the MaxClients to 128. Now Everything is working well.

Just a quick note to say thanks again John, I learned how to do the LUA scripts today and it works for the two runway turnoff lights on one button, I will now use for various other combos I want to do on the iFly!! For the benefit any newbies wanting to do iFly RWY TURNOFF on/off on one button, I am attaching the files, you just put them in the FSUIPC main install folder and instead of selecting Preset for the buttons, select "FS Control" and look for the commands "LuaIflyRFWYON or ...OFF., iFlyRwyOFF.lua iFlyRwyON.lua

First, to understand profiles you should read the section User profiles for all control settings, on page 22 of the FSUIPC7 User manual/guide. Profiles are enabled automatically. Having profiles in separate files is generally only used if you have many profiles and these are quite large, as it separates them into different files. You do not have to use this feature when using profiles if you don't want to, but if you have already switched to profiles-in-separate files then thats ok. The changes you made will only be saved in the profile (and in the profile-specific file) if you clicked the profile-specific checkbox (in the assignments panel) when adding the assignment, and when you have added the currently loaded aircraft to a profile (or have created a new profile for the aircraft). Check your FSUIPC7.ini - they will have been added there to the general sections if you did not specify profile-specific. Note that when you create a new profile for an aircraft, or add an aircraft to an existing profile, it is a good idea to shorten the aircraft name (listed under the [Profile.xxx] section of your FSUIPC7.ini file) to a substring that matches all variants of that aircraft. This will prevent issues with the profile not being loaded when you use a new variant. Alternatively, you can set the UseAirLocForProfiles in parameter to Yes to perform matching on the aircraft folder name instead, but if you want to use this then do it now before adding the aircraft name/title to the profile. Again, see that section in the User manual for more details. John

Thank you for this... The above "Pause" control (c1152) idea was a perfect solution to operate multiple switches in the PMDG 737's and 777's in both MSFS2020 & 2024. I was experiencing the same symptom where only the last sequential switch in a group would operate. Adding the pause control allows all sequential switches to work as expected. Regards,

New Version for the Plugin (only): v0.8.8 - Plugin - Version Reporting: The Version now also includes its Buildtime to help differentiating between Development-Builds - Rewrite of the MSFS Connector: Almost everything is now done natively through SimConnect, the MobiFlight Module is now only required for Calculator Code! - KVAR Command Syntax Change: KVAR Commands can be either a Sequence with each KVAR having exactly one (!) required Parameter -OR- can be exactly one KVAR with 0 to 5 Parameters! - KVAR as Variable: K-Vars or SimEvents can be used as Variable. The initial Value will always be 0 and only change if the Event is ever received (and only reflects the first Index) - Support for FSUIPC Byte Arrays: The Offset Variable now Supports reading a whole Offset Range as Byte Array (Contributed by ngreatorex) - e.g. reading the whole PMDG CDU Offset Range at once. Note that they are only intended to be used in Lua Scripts! - The AVAR Variable Syntax now also supports the Prefixes 'E:' and 'L:' to read Environment and Local Variables (aka L-Vars) - Lua Scripts: the 'SimCommand' Function does not support vJoy Commands anymore. Use the new dedicated 'JoystickCommand' Function which allows sending separate down/up Commands. - Fixed: B-Var Commands not working after switching a Session - FSUIPC Connector (FSX/P3D/MSFS) now allows Commands to be sent when the Simulator is paused - MSFS Connector now allows Commands to be sent when the Simulator is paused - XP Connector now allows Commands to be sent when the Simulator is paused - Visual Overhaul of the Action Designer UI: Elements and Commands now have separate & collapsable Trees and their Appearance was overhauled - Action Designer UI: Copy & Paste now also supports a whole List of Items - i.e. Copying all Manipulators from one Element to another. - Action Designer UI: Added Increment/Decrement Buttons for some Text Fields - Gauge Element (Composite Action): A Range of Markers is now saved as such and the whole Ranged can be edited/changed at once (only for new Marker Ranges). The Syntax for a Marker Range is now '$start:end:step'. - Added an "REST-ish" API to the Plugin to get/set Variables and even send Commands (only understands GET, zero JSON, everything encoded in the URL ). This is mainly intended for Testing and other Edge-Cases, it is not intended as a Replacement for Middleware as FSUIPC or SPAD! - Added Support for X-Plane's WebAPI (12.1.4+) - disabled by default due to an open XP Bug (XPD-16752) 😕 - X-Plane Commands now have an "Command Once" Option (enabled by default) to configure if a Command is send as one Command or different active/release Commands (only relevant when WebAPI is enabled) - The Version Check now also reports if a new Development Build is available - Logging for Errors/Exceptions in Lua-Scripts is bit more detailed now - Updated Libraries / Dependencies - Fixed Event Log Error on Shutdown - Profile Manager - Improved Checking if a Profile was installed during Package Installation. All Profiles in a Package must be either installed or ignored for the Installation to continue! - Now offers to start the StreamDeck Software again if it was closed by the Profile Mapping View - New 'Create Package' View to assist with creating & updating Packages for Distribution - Installer - Rewrite of the Installer to have a shared Code-Base across all Tools - The Installer now shows the current installed Versions (on future Installs / Updates) - The Installer now offers Options for Install & Update (i.e. if FSUIPC7 is used as secondary Connector or if the vJoy-Driver should be checked) - Improved Logging for the Installer

You can start MSFS via steam or however you like. The default auto-start is via the EXE.xml file, although you can select to auto-start via the bat file. By default, the desktop icon(s) installed by the installer just show a splash crean and call steam to start MSFS. If you are using the EXE.xml auto-start and dont want to use the installed desktop icon to start MSFS, you can opt not to have this installed by unchecking the checkbox at the end of the installation process. John

Hi @John Dowson, thanks for the help, I used the LVAR command and it worked.

John, thank you. I modified the FSUIPC.ini file to add the CONNECTED (Spad.next) and READY (Vpilot) on the RUN instructions, and to adjust the DetectToConnectDelayAuto as per the link you provided (the value now set for me is 86). Now everything is working well. Thanks a lot for your help Ezio

Version 3.3.16 of FSUIPCClientDLL is now on NuGet. When using FSUIPC7: Connection will now fail with FSUIPCError.FSUIPC_FS_NOT_READY if the flight sim (MSFS2020 or MSFS2024) is not running or is not ready Version 1.1.4 of the WebSocketServer is now on the website: http://fsuipcwebsockets.paulhenty.com Fixed problem of not detecting the Flight Sim version when using FSUIPC7 and the sim is still starting up. Paul

Hi John, As I mentioned, I wouldn’t call myself a "coder," so I often rely on ChatGPT for help. But when I get stuck, I turn to the forum for deeper insights. Thanks to your hints and guidance, I now have a working script again. I really appreciate your help—thank you so much! Best regards, Isak Here is the working lua script: dev = com.open("COM6", 115200, 0) -- Open COM port with baud rate 115200 ipc.display("Lua script is running...", 3) function processInput() local datastring, length = com.read(dev, 256) if length then ipc.log("Raw data received: '" .. datastring .. "' [" .. length .. "]") if datastring:match("^NAV1SB") then local frequencyStr = datastring:match("NAV1SB%s*(%d+%.%d+)") -- Extracts the frequency if frequencyStr then ipc.log("Extracted frequency: " .. frequencyStr) -- Debug log local bcdValue = convertToBCD(frequencyStr) ipc.log("BCD Converted: " .. string.format("0x%X", bcdValue)) -- Debug log ipc.writeUD(0x311E, bcdValue) -- Send to FSUIPC ipc.display("NAV1 standby set: " .. frequencyStr, 3) ipc.log("NAV1 standby frequency set to BCD: " .. string.format("0x%X", bcdValue)) else ipc.log("Error: Failed to extract frequency!") end end end end -- Convert frequency to BCD (e.g., "113.45" → 0x1345) function convertToBCD(freq) local cleanFreq = freq:gsub("%.", "") -- Remove decimal (e.g., "109.2" → "0920") local decimalNumber = tonumber(cleanFreq) -- Convert to number if not decimalNumber then return 0 end -- Return 0 if conversion fails local bcd = 0 local shift = 0 -- Convert each decimal digit to BCD format while decimalNumber > 0 do local digit = decimalNumber % 10 bcd = bcd + (digit * (16 ^ shift)) -- Use base 16 shift instead of bitwise left shift decimalNumber = math.floor(decimalNumber / 10) shift = shift + 1 end return bcd end while true do processInput() ipc.sleep(100) end

Ok, I will leave it as is in the version I posted above.

I think I solved the problem. I followed this guide: https://flightsimulator.zendesk.com/hc/en-us/articles/360015893879-Checklist-How-to-troubleshoot-crashing-CTDs-issues and did the following. #1 SYNCHRONIZE TIME SETTINGS My time was set to "Adjust automatic daylight saving time" I turned this off. #2 Then “Set time zone automatically” to ON #3 Then "Synchronize your clock" Then this section. "LAUNCH MICROSOFT FLIGHT SIMULATOR AND TRY AGAIN" I bought msfs via Microsoft store, so now I did this. #1 install the Xbox app to my computer. #2 launch Microsoft Flight Simulator from the Xbox App. I was able to create a shortcut from the Xbox app that I was using. For now, this seems to have solved my problem, and I'm happy. 😊👍. Hope it might help others too. Kind regards Per, from Denmark.

I did look at it. I didn't know "Path of Flight Simulator installation" == "InstalledPackegesPath". I meant look at the value in the offset, i.e. log its value. I will update the offset status document to make this clear. Cheers, John

Trim wheels usually work on buttons, not an axis. Some have two buttons in each direction (one for fast movements and one for slow), others just one. For those using just one button, you can use the Rotaries.lua script to convert this to use two virtual buttons instead, to enable fast/slow trim in each direction. The Bravo trim wheel has one button in each direction. I showed how to configure the Bravo for basic operation, including the trim wheel, in the following post: That should work for quite a few aircraft, but it won't work for all aircraft, especially many add-ons, as those assignments use the default FS controls. For such aircraft, you should use a profile and override these with the specific controls for that aircraft, whatever they may be - usually using presets, input events or lvars. There are also many other ways yo assign trim, and it is up to you to decide what works best for the aircraft you are using. For example, see the following post: John

This is an MSFS issue and nothing to do with FSUIPC. You should use the MSFS/Asobo forums for this issue, not this FSUIPC forum. Sorry, but I can only help with FSUIPC issues, not MSFS issues. I will leave this post in case anyone else has any suggestions, but you are better off using the Asobo forums for such issues. I have also moved your post to the FSUIPC7 / MSFS forum as you posted in the main support forum. John

You should use FSUIPC's logging facilities to work out what is happening. Set logging for Buttons & keys, open the logging console and see what is logged when you press the buttons - this should tell you what is happening. But if button 0 is already pressed when you press button 1, line 34 will NOT be triggered as that assignment is on button 0. Assignments are only triggered when the main/assigned button is pressed/released, not when the compound condition is changed. So, assignment 34 should be on button 1 with the compound condition on button 0 being pressed, i.e. 34=CR(+0,0)0,1,K190,8 -{Key press: .>key}-

Sorry but can you please five your topics a more appropriate title... I will update it... 7.4.18 attached below - save and remove the .7418 extension... John FSUIPC7.exe.7418

Would have been helpful, can't replicate that: - Created a Simple Button Action (Control, 65798, no Toggle) on 0.7.12 - Installed 0.8.4 - Checked Action: Toggle still disabled So for the Moment I can just assume you had actually set a Toggle Switch unintentionally. And that a Setup of Toggle Switch enabled +no Alternate Command+ no Monitor Address + no Monitor Value/Comparison just behaved differently with a on pre-0.8.0 Versions 🤔

Strange question...depends on the device, but generally yes (for HID joystick type devices - other devices may need additional drivers or lua), in a licensed/registered version. Device / controller handling in FSUIPC7 is exactly the same in MSFS2024 as for MSFS2020.

Presume you mean 7.4.18, no? If not, please update. If using 7.4.18, please check the first line of your FSUIPC7.log file. If it has a build date of 1st November, i.e.: then please download and re-install. it should say 3rd November: The initial release was accidentally built using the SDK from MSFS2024, and I corrected this the following day, If that is not the issue, please show me / attach your FSUIPC7.log file. Ah...just seen your updates... Yes, that is definitely the issue - please update. John

While people in the MSFS forum are complaining about having to spend all that time setting up their controllers, once I got MSFS2024 running, I fired up CLS2Sim (for the Brunner yoke) and FSUIPC, acknowledged the "CrashIO" dialog (haven't seen that for a while), disabled the default layouts MSFS had picked for the devices it recognized, and went flying. I'm sure I'll find problems in time, but having working controls within a minute, that was, for me, the highlight of this launch day. ❤️ FSUIPC ❤️

*Version-Bump* Plugin updated to Version 0.8.0 Major Plugin Overhaul - it is basically a new Plugin under the Hood! Please make an Export/Backup of your Profiles your created with PilotsDeck! The Intention is that existing Profiles just continue to run (with a bit smaller Fonts), but it is better to be safe than sorry Installer Improved UI Check & Installs all Requirements (either automatically or by starting the Setup for you) Check for the vJoy Driver now tests for the Brunner Version/Fork - which should work on both Win 10 & 11 Ability to remove the Plugin (including all Customizations!) New Profile Manager Application Enables easier Profile Installation in a few Clicks - extracts & copies the Files for you, assists with adding the Profiles to the StreamDeck, automatically removes old Profiles on Updates Own Package Format to distribute Profile Files, Images and (Plugin) Scripts as one File Allows much easier Profile Mapping to switch Profiles automatically depending on the Aircraft (or Sim) Profile Switching now only can switch back to specific Profiles when the Simulator exits These Profile Mappings will automatically be transferred to new Profiles on (Profile) Updates Plugin Property Inspector is now tabbed to allow easier Navigation Option to add a Guard (Image & Command) to an Action (Guard Images can also use Image Mappings) Added Image Mapping to more Actions Top and Bottom Image for the Korry Action can independently enabled/disabled Most Actions can now be used on an SD+ Encoder (except Simple Button and Gauge Dual) B-Var Support added - per default handled as Command-only but can also be used as a Variable Added dedicated Command Type for K-Var (allows to define a Sequence) HVAR Command supports passing a Value to the H-Var New Calculator ("C:") Variable to read the Result of Calculator/RPN Code (read only) Added Internal (X:) Variable to share Data within the Plugin Added Copy and Paste Buttons to all Actions to share single Actions between Users (or to copy between a Keypad and Encoder) Added a new "Composite Action" that gives you much Freedom to design your own Action (Display and Command wise) - most Feature Requests should be now possible with that Action (and can even replace Actions that would only be possible with Lua Scripts) This new Action is configured through its own dedicated "Action Designer" UI (opened via the Property Inspector) The Script now has its own Engine to run Lua Scripts (does not need external Engines like FSUIPC or FlyWithLua anymore) The Functions of these Lua Scripts can be directly addressed as a Variable or Command - like all other Variable/Command Types Multiple Script Types available to be run on-demand (Variable, Command) or constantly when the Session runs The Scripts can read all Variables and send all Commands the Plugin supports FSUIPC7 is now only the secondary Connector for MSFS - it is possible to use it without FSUIPC7 installed if needed! Remote X-Plane Setups are now supported Images can now be stored in Sub-Directories to better Organisation of different Packs and easier Navigation Image Drawing overhauled - Images are now drawed on top of each other (i.e. on the Dynamic Button) Added an Icon in the System Tray / Notification Area to restart the Plugin or show the Developer UI The Developer UI offers Links to some Reference Source to look up Variables or Commands and to access the Plugin's Folders easier The Developer UI has also a Monitor View to look up the current Aircraft-String/-Path or the Plugin's State, Ressources & Statistics Changed vJoy Driver Library to the Brunner Fork Plugin Configuration is now persistent between Updates and allows much more Tweaking Removed Error Image (and Error State) Sim Connection, State Handling Variable Handling completely overhauled Moved to .NET 8 (LTS) and upped minimum OS to Window 10

I experienced the exactly same problem when I had a new programmable keyboard that has rotary encoder, where inputs were very unreliable probably due to the too short interval between keydown and keyup events. After I added " UseKeyboardHook=Yes" to the ini file, FSUIPC works like a charm to capture the encoder input. Thanks!

There is a developer named Oudoum working on a solution to allow FDS (and some other) hardware to work with FSUIPC and with PMDG 737 (and 777). It is called Device Interface Manager. It is available here: https://github.com/Oudoum/DeviceInterfaceManager and there is a live Discord channel for latest discussion and feedback. https://discord.com/channels/1024920961939669052/1236087452637204571 Cheers!

Sky Demon is a navigation system designed for real world General Aviation pilots. However, it is possible to fool the program into believing that the GPS output it is receiving from FSX-SE is coming from a real aircraft. I am posting this workplan as an aid to those who would like to try it out. It may not work for you in which case I apologise. Both Sky Demon and a Virtual Serial Port Device have two week trial periods. I gratefully acknowledge the advice of John Dowson in helping me get this up and flying. Preliminaries You will need the latest subscribed version of FSUIPC4 for FSX-SE. https://www.fsuipc.com/ If you plan to run SkyDemon on a LAN you will also need WideFS7; this includes WideClient for installation on your non-flying client PC/laptop. Details in para.5 and end of para.6. Read the FSUIPC and WideFS User Guides carefully. Workgroup If you are planning to run Sky Demon on a LAN, Make sure that both server (FSX-SE flying PC) and client (non-flying laptop/PC) have the same workgroup name. This is essential. There are several versions of the Windows 10 operating system e,g, Home, Pro, Enterprise. If you are using a newly installed Pro or Enterprise version you will probably find that the default workgroup name is WORKGROUP. If you need to change this, be aware that your change may not ‘stick’ after re-booting. To address this problem, login with a local account, not an MS account like: xxx@hotmail, xxx@outlook etc. Also, check in Settings-System that your computer is set up for private use and not business. 1. In the FSUIPC4.ini file (in the Modules folder of the FSX-SE folder) scroll down and check: [GPSout] GPSoutEnabled=Yes Port=WideFS Speed=19200 Leave the rest unchanged. If not there add: Sentences=RMC,GGA,GSA (no spaces) Next, find [Wide Server] and check: WideFSenabled=Yes AdvertiseService=1 Port=8002 Port2=9002 Save 2. Download the two week trial version of Eltima Virtual Serial Port Driver for Windows 10. Launch. Pair COM8 and COM9. Check in Device Manager – WinKey + X. Payware option after two weeks. Freeware VSPDs are available but I cannot vouch for these. 3. Sky Demon is designed for real world General Aviation navigation. It is payware but there is a trial version. Download and install the latest version for Windows 10. In Setup, Third Party Devices, leave boxes unchecked. Under RS232 GPS Devices set Port to COM8; Baud to 19200 Also in Setup, scroll down to Navigation Options. At the bottom of the page click on the link to Legacy Device Connectivity Options and chose ‘I have a Garmin handheld device’. You can play around with the other Navigation Options. 4. Read this only If you wish to run Sky Demon on a LAN i.e. on a non-FSX client PC or laptop. Skip otherwise. Download WidesFS7 from: https://www.fsuipc.com/ to your non-FSX (client) machine. Make sure you have registered WideFS7 – the code will have been sent to you when you purchased FSUIPC4. Extract and copy WideClient.exe and WideClient.ini to a separate folder on your client machine. I use my home folder and call this folder WideClient. Make a desktop shortcut for WideClient.exe. Edit the Port entries in WideClient.ini configuration. [Config] Port=8002 Port2=9002 Add these to [Config] ServerName=enter your flying PC’s name – whoamI - in Command Prompt Protocol=TCP Add this after the [Sounds] entries, [GPSout] Port=COM8 Speed=19200 Save 5. Running FSX-SE. Login to Steam. Run FSX.exe from your main installation. Launch the Virtual Serial Port Device and check that COM8 amd COM9 are paired. In a LAN Launch WideClient.exe on the client. In my LAN I installed the VSPD device on my client. 6. Run SkyDemon – click on Go Flying and Connect to RS232 GPS Hardware. ‘Keep the shiny side up and the greasy side down!’

Many thanks John, I'll pass details to the other (P3D) user who was having problems.

Ah, yes, sorry - I can certainly do that...

Sorry, I should have been clearer - would you be able to put the same 'ground altitude' fix into FSUIPC6?

Ok, although i don't know why you previously said 'The Workgroups are the same'! Once that is corrected, try again. If you still have issues, try setting the ServerName (or ServerIPAddr) and the Protocol - see the WideFS User guide, and also the WideFS Technical guide for troubleshooting network issues. Ok, but you need to sort this out - I can;t help with this... John

Merci Paul, c'est exactement ça, ça marche, je suis heureux . ça fonctionne !!!! Thanks Paul, that's exactly it, it works, I'm happy. it works !!!!

Thank you again, Paul, I know nothing about programming and your help has really been a lifesaver. I've been at it for quite a long time, 3 or 4 weeks, and now it's working. Here is my code which works and is surely improvable, but it has the merit of functioning. // Accès aux données des réservoirs PayloadServices = FSUIPCConnection.PayloadServices //**************************** Mise à jour des données****************************** FSUIPCConnection.PayloadServices:RefreshData() oFuelTanks est un FsFuelTanksCollection oFuelTanks <- FSUIPCConnection.PayloadServices:FuelTanks SI oFuelTanks = Null ALORS Erreur("Impossible d'accéder aux données des réservoirs") RETOUR FIN //***************** Vérification de la taille de la collection***************** nTaille est un entier = oFuelTanks:Count SI nTaille = 0 ALORS Erreur("La collection de réservoirs est vide") //RETOUR FIN nPourcentageCentral est un entier sur 4 octets nPourcentageGauche est un entier sur 4 octets nPourcentageDroit est un entier sur 4 octets nPourcentageCentral = oFuelTanks:get_Item(FSFuelTanks::Centre_Main):get_LevelPercentage() nPourcentageGauche = oFuelTanks:get_Item(FSFuelTanks::Left_Main):get_LevelPercentage() nPourcentageDroit = oFuelTanks:get_Item(FSFuelTanks::Right_Main):get_LevelPercentage() Info("Pourcentage de carburant dans le réservoir central : " + nPourcentageCentral + "%") Info("Pourcentage de carburant dans le réservoir gauche : " + nPourcentageGauche + "%") Info("Pourcentage de carburant dans le réservoir droit : " + nPourcentageDroit + "%")

Just Install Fsuipc7 and works with your .ini my pc12 simworks. Thanks a lot John!

Just wanted to come back and report everything has been working flawlessly since the adjustments you recommended.

Background PMDG Aircraft for FSX and P3D do not typically use the normal controls provided by the flight sim. This means that many of the aircraft's switches cannot be assigned to buttons and keys using the list of controls in the FSUIPC dropdown boxes. Assigning a standard control in FSUIPC will likely do nothing in the PMDG aircraft when the button or key is pressed. Solution Instead of using the standard list of controls shown in the FSUIPC dropdown box, users must use a different set of controls provided by PMDG for the specific aircraft. These are known as custom controls (or custom events). The custom controls vary for each aircraft and are listed in the SDK that is installed alongside the aircraft. This guide will show you, step-by-step: How to find the SDK files How to calculate the custom control numbers How to work out the parameter value How to assign the control to buttons/keys in FSUIPC The specific examples shown will be taken from the PMDG 737NGX, but the same method works for any PMDG aircraft with an SDK and custom controls (e.g. 777, 747). 1. Locating the SDK From your main Flight Sim install folder, or your MSFS Community folder, and open the PMDG aircraft folder Then select the folder belonging to the aircraft you want to use. e.g. PMDG 737 NG3 or pmdg-aircraft-737 Then select the SDK folder or Documentation\SDK folder for MSFS2020 Locate the file with the .h extension. For the 737 it's called PMDG_NG3_SDK.h (or maybe PMDG_NGX_SDK.h, depending on the sim and variant you are using) You can open this file with Notepad or your favourite text editor. As an example, the document you need for the 737 in MSFS2020 will be: [Community]\pmdg-aircraft-737\Documentation\SDK\PMDG_NG3_SDK.h 2. Calculating the control numbers 2.1. Find THIRD_PARTY_EVENT_ID_MIN The first thing to find is the definition of THIRD_PARTY_EVENT_ID_MIN. Search for the following text: #define THIRD_PARTY_EVENT_ID_MIN You will find a line like this (from the 737 file): #define THIRD_PARTY_EVENT_ID_MIN 0x00011000 // equals to 69632 Note the decimal value at the end. In the case above it's 69632. You will need this value to calculate the control number in the next step. 2.2. Find the control you want to use. Search for the control by name, or look through the listed controls to find the one you want. They are helpfully grouped together by panel. The controls are listed under a comment: // Control Events You can search for this to find where the list of control numbers starts. As an example we'll use the Autopilot CMD A swtich on the MCP. This is the relevant line in the 737 SDK: #define EVT_MCP_CMD_A_SWITCH (THIRD_PARTY_EVENT_ID_MIN + 402) To calculate the control number for this switch we just add 402 to the value of THIRD_PARTY_EVENT_ID_MIN we found earlier. 69632 + 402 = 70034 We have now calculated the control number. We will use this in step 4 to program the button/key. 3. Finding the parameter value PMDG controls need a parameter value. These can one of type types: 3.1. Mouse Click Codes (Shown in the example) You can use these to simulate a mouse click on the particular switch. Mainly it will be the left mouse button, but other clicks types are available (e.g. Right button, left double click etc). To find the codes for each type of click, search for MOUSE_FLAG You'll find a block of #define statements for each type of mouse click. Here are a couple of examples from the 737 sdk: #define MOUSE_FLAG_RIGHTSINGLE 0x80000000 #define MOUSE_FLAG_LEFTSINGLE 0x20000000 Find the click that you want to simulate and get the code. For example, we'll have our key assignment simulate the left mouse button clicking on the CMD A autopilot button. So we'll need 0x20000000 as the parameter value for the control. 3.2. Direct Values (Not shown in the example) Alternatively, some controls can accept a direct value to set the switch to a specific position. To find the direct values you need to look at the top part of the .h file to find the switch definition. These are named differently than the events so you need to search. Taking the battery selector switch as an example, we find the control: #define EVT_OH_ELEC_BATTERY_SWITCH (THIRD_PARTY_EVENT_ID_MIN + 1) For the parameter value we can find the same switch in the top part of the .h file: unsigned char ELEC_BatSelector; // 0: OFF 1: BAT 2: ON This tells us that in addition to mouse clicks, we can also send direct values. In this case: 0 for the OFF position, 1 for the BAT position and 2 for the ON position. It's possible to make a key or button set the Battery Selector directly to the ON position by setting the parameter value to 2 instead of a mouse click code. Simple ON/OFF switches will not have values listed (and will be declared as 'bool'). For these types of switches you can just pass the value 0 for OFF and 1 for ON. 4. Assigning the control to a button or key in FSUIPC Select the [buttons + swtiches] or [key presses] tab in FSUIPC and select the button or key to program. From the "control sent..." dropdown select <custom control> (it's near the top of the list) A popup window appears asking for the control number. Type in the control number you calculated in step 2. For our 'autopilot CMD A' example, we enter 70034 and click OK. The controls dropdown box will now show the control number in angled brackets. In the "parameter" box (below the controls dropdown), enter the parameter value from step 3. This can be a mouse click code or a direct value. Mouse Click Codes: Do not include the first 0 from the number listed in the PMDG SDK. Start with the x. With our example, we would enter x20000000 for the left-button single-click. Note that this code is in hexadecimal. FSUIPC will convert it to the equivalent decimal value. This is nothing to worry about. It's the same number. Entering the value in Hex is more convenient. Direct Values: Just enter the value as a number. Do not add the x at the start like mouse codes. If you're programming a key press, remember to press the [confirm] button. Here is our example control assigned to a button in FSUIPC: Your button or key press should now operate the switch in your PMDG aircraft.