John Dowson

Can you please show me/attach your FSUIPC4.log file generated after a crash. Also, please check the windows event viewer for the crash report and save and attach that. John

It is the parameter/value that is sent with the control. Some controls take a parameter, others not. The parameter should be pretty obvious many/most controls, but if you do not if an FS control/event tales a parmeter, or what that is, then you will need to look up the event in the Asobo documentation (e.g. see https://docs.flightsimulator.com/flighting/html/Programming_Tools/Event_IDs/Aircraft_Autopilot_Flight_Assist_Events.htm). For presets, the parameter is used to substitute the parameter placeholder (the '@' symbol or $Param) before sending the preset calculator code and applying it in the FS, Some Input Events also take parameters (always 64bit floats at the moment) others not - you will need to use logging to determine if a parameter is needed and what the value range of the parameter is. You also posted in a topic that has nothing to do with your question. Please don't hijack unrelated topics/posts - create a new one, with an appropriate title, if you have a question unrelated to other posts. John (I also thought i had already responded to this question in a fresh post but can no longer find/see that...)

Or maybe try looking at the provided documentation....

All three components (Name, Address/email & key) must match. If they all match and the key still doesn't validate, this is usually because the VC++ reditributables need updating. Download and install the latest combined redistristributables (both x64 and x86) from https://docs.microsoft.com/en-US/cpp/windows/latest-supported-vc-redist and try again. If you still get the same issue, please let me know your order number (do NOT post your key details!). John

Sounds like you have checked the Control to repeat while held checkbox. Uncheck that and try again.

You need to use the lvars, not the standard FS controls. The easiest way to do this is to use the available presets. Check the Select for Preset box, click the Find Preset... button, and navigate to the Black Box->AnalogBaron presets, and under Electrical you will see the following presets: LEFT_ALTERNATOR_OFF LEFT_ALTERNATOR_ON RIGHT_ALTERNATOR_OFF RIGHT_ALTERNATOR_ON Try assigning to those. However, looking at the calculator code for those presets, it looks like the *_ON ones are toggles (but not the *_OFF ones) for some reason. You can either use those or define your own presets. Alternatively, you can add the lvars BKSQ_alternatorSwitch_R and BKSQ_alternatorSwitch_L to free/spare FSUIPC offsets and assign to the provided offset controls to set/clear the lvars via the offsets. John

First you have to be aware that the flight load/save/auto-save functionality provided by FSUIPC completely rely on the functions provided by the MSFS SDK, namely the SimConnect functions SimConnect_FlightLoad and SimConnect_FlightSave (as well as SimConnect_FlightPlanLoad). Although the SimConnect_FlightLoad function is documented as working, the SimConnect_FlightSave function (as well as the SimConnect_FlightPlanLoad function) is still documented as 'NOTE: The current status of this function is NO ERROR, NO RESPONSE.', which is Asobo's way of saying that this function is still not 100% working/reliable, It has been this way since release. Therefore the saving and loading of flights is still not 100% reliable, although some users have reported more success with this than others (maybe aircraft dependent). If it is not working, I cannot do much about this - you can try raising a bug request with Asobo, but they may reject this if the flight file is generated by the SimConnect_FlightSave function as they are already aware of issues with this. Flight files generated by MSFS2020 itself and those generated by external apps (using SimConnect_FlightSave) should be compatible/the same, but this may not actually be the case at the moment. You could try loading the flight file via FSUIPC7 (File -> Load Flight) to see if that makes a difference. You can do this either when in the World Map, or when you already have an aircraft loaded and ready-to-fly. John

Yes. Up to you. There are hundreds of add-ons that use FSUIPC, some the freeware version and some the registered/paid version. I cannot comment on any such software - you need yo contact the developer. John

👍

But as I keep telling you, FSUIPC and the PFC driver have nothing to do with your RSG equipment, and I cannot help with this as these devices are not supported by FSUIPC. No problem. John

Can you please try the attached version which has been reported to have fixed this issue. Please let me know if it works for you. John FSUIPC7.exe

That is nothing to do with FSUIPC - I hope that is not in the FSUIPC Launch.Addon section... This is because they are mot written - you add them only if/when needed. There are two new ini parameters that you can add to the [General] section which control the delay between sim detection and trying to connect: DetectToConnectDelay - defaults to 5 seconds, used when FSUIPC7 is started manually DetectToConnectDelayAuto - defaults to 60 seconds, used when MSFS starts FSUIPC7 (i.e. when the '-auto' command-line argument is present No problem - thanks for testing this for me. The issue seems to be that MSFS does not send the required events when you try to connect obtain a connection too early during its initial loading period. I don't understand why I cannot reproduce this here though, very strange... John

Then read that! As it says in that post, I don't know what NMEA/GPS sentences Foreflight is expecting - you need to ask them. It is a facility provided by FSUIPC to send out GPS data to the network for use by 3rd-party programs. If Foreflight is using this feature, they should let you know how to configure this in FSUIPC. This feature is configurable in the AutoSave/GPSOut tab of FSUIPC4 and is described in the FSUIPC4 User guide starting on page 10. But i do not support Foreflight, only FSUIPC, I do not know how to configure FSUIPC for use with Foreflight, you need support form them, not me. John

Your original EXE.xml was corrupt - it was missing an opening SimBase.Document directive. You have two other add-ons using this file - AFCBridge and Logitech MSFS plugin. One of these must have corrupted this file, I have added these back in the attached EXE.xml, so please use this to replace the one you are using: EXE.xml And again, what happens when you try to start manually, i.e. when you double-click the FSUIPC7.exe in windows Explorer? Do you see the FSUIPC7 splash-screen? Is an FSUIPC7.log file created, if so please show it to me (i.e. attach it). Also, please right-click on the FSUIPC7.exe and look at the properties, security tab. Is it blocked from running there? if so allow it to be ran. John

Can you please try the attached. I have increased the delay between detection and trying to connect from 30 seconds to 60 seconds. There is also a new ini parameter where this can be adjusted if needed. John FSUIPC7.exe

I know nothing about Foreflight or even if it uses FSUIPC - as the problem is with this software, I suggest you try their support first. John

The FSUIPC PFC device drivers were written by Pete Dowson, my father. I support these to the best of my ability, but as I don't have any PFC devices my knowledge on these is not much more than what is provided in the documentation and available in existing support requests. These drivers have been stable for many years and are closed for further development, No, not for your issue with the RSG500. It is not, It only runs when FSUIPC is running (it is an embedded dll) and will have no affect on the RSG500. Not really - you need support from RSG for this device. John

Definitely an issue with the latest version of FSUIPC7 - looks like the AircraftLoaded event is received with an empty aircraft name for some reason, so the PMDG threads are not being started. Probably a timing issue somewhere... It should be ok if you exit and then restart FSUIPC7. This problem also applies to the current release of MSFS. I have also added a fix in the attached version if you would like to try. I am also on SU15 now but looks like the beta switcher program isn't working as expected - it has overwritten my released version...hmmm I see there is also a new SDK (0.24.1.0). I will take a look at this and update ready for the release. John FSUIPC7.exe

Can you try the attached please - and add back the '-auto' command line flag in the exe. Show me the FSUIPC7.log regardless of all is working or not please and I will take a look tomorrow (finishing now, orders from the wife!). John FSUIPC7.exe

That is interesting....however, I suspect that it was reconnecting a lot at start-up as that will just reduce the initial stall time from 45s to 5s. Can you show me a FSUIPC7.log file please. I suspect that this is a timing issue between establishing a simconnect connection and requesting the data. I think I will remove this and add the delay between detecting the sim and connecting when auto-started, I will provide an updated version for you to test, probably tomorrow. John

This may be an issue with the latest version. If you exit FSUIPC7 and re-start it, do you then see the CDU data?

Ah, ok - this issue has already been reported and I am investigating under this topic: The problem seems to be that FSUIPC7 is not receiving key presses/releases when auto-started - for some people, its fine here! I am investigating and will update when I have found anything. John

Auto-start is not enabled as there seems to be an issue with your EXE.xml file - from your installation log: This usually occurs due to another 3rd-party app corrupting this file. Please follow those instructions (i.e. rename that file then re-install FSUIPC7), then when done, show me/attach your renamed EXE.xml as well as the new/current one, and also attach your new InstallFSUIPC7.log file. I can then make any necessary changes and provide you a new one. What happens when you try to start manually, i.e. when you double-click the FSUIPC7.exe in windows Explorer? Do you see the FSUIPC7 splash-screen? Is an FSUIPC7.log file created, if so please show it to me (i.e. attach it). If you cannot run FSUIPC7, this is usually due to one of two reasons: 1, Your VC++ redistributables are not up-to-date. Download both the x64 and x86 packages from https://docs.microsoft.com/en-US/cpp/windows/latest-supported-vc-redist, install them and try again. 2. You have some anti-virus software that is blocking FSUIPC7. Check any anti-virus software to see if it has blocked or removed FSUIPC7, and if so configure to allow.

Ok, that is interesting as it implies that this issue only (and always) happens when FSUIPC7 is auto-started by the sim - and only for you as far as I can tell... There will be, but all timings start once the FS is detected, and it works ok for you when you start FSUIPC7 manually before the FS. And all threads are started ok, it is just that simconnect does not seem to be sending/forwarding key presses/releases. As one last test, could you find your EXE.xml file (location will be logged in your InstallFSUIPC7.exe file), find the FSUIPC7 entry and remove this: or maybe change to this: i.e. remove the '-auto' flag. This will change some timings, John Later: someone else has now reported the same issue:

Sorry but I don't know what could cause this issue as I am not using SU15 at the moment. Is there a PMDG update available for SU15? Could you add the following to the [General] section of your FSUIPC7.ini file: TestOptions=x400 and generate a short log file (load the PMDG737, sit on the runway with engines running for a minute or so, then exit) and show me/attach that please. I am still on 3.0.87 of the PMDG737 - I will update to the latest version (3.0.91) and check with this. John