John Dowson

After the FSUIPC splash screen is shown, FSUIPC iconizes itself and sits in your system tray. Are you sure it is not there? Have you tried pressing Alt + F (the default hot key) to open the FSUIPC7 main window? It is not possible for FSUIPC7 to delete itself. If its no longer there (but please check), I can only assume that it is some sort of anti-virus program gas detected it and quarantined it for some reason. Check your anti-virus program.

Those offset use the indexed simvar GENERAL ENG FUEL PUMP SWITCH. This is actually documented as unsettable, so they are not writeable - I will update the offset spreadsheet document to make this clear. Not sure why they are not reflecting the correct value though - maybe those aircraft don't use this simvar... Have you tried using the controls: FUELSYSTEM_PUMP_TOGGLE FUELSYSTEM_PUMP_SET FUELSYSTEM_PUMP_OFF FUELSYSTEM_PUMP_ON ? The offsets may be working (i.e. for reading the current setting) for some aircraft, but not all. For complex aircraft, best to check what to use in the MobiFlight preset app (https://hubhop.mobiflight.com/). However, I can't see much there for the 747 or the 787. Maybe try seeing if there are any lvars available for those aircraft. For the A320 (FBW version), there are toggle presets for the left/right/center pumps - here's the calculator code to toggle the center fuel pump: That looks like its using the control Fuelsystem Pump Toggle to toggle the fuel pump (with the parameter specifying which pump) and also toggling an lvar, presumable to flip the switch in the UI. I can also see there are some new simvars for this, although they are defined as read-only: I can maybe add these to some FSUIPC offsets - possibly the same ones if its an either/or situation. I could possibly also make them writeable by triggering the Fuel System Pump Toggle event when written to. I will put this on my list to investigate, hopefully later this week. John

Sorry but I cannot advise on this. It looks like many of the Virtual Avionics devices are support via FSUIPC (e.g. for default aircraft, PMDG737, ProSim737) but I don't know the AeroSystems 737. Maybe try support from Virtual Avionics and/or Aerosystems. John

As Reinhard says, we need to know what FS, which version of FSUIPC, and which aircraft you are using. For MSFS, most of the G1000 controls are accessed through either hvars or lvars (or MobiFlight events). A G1000.hvar file is included in the FSUIPC7 HvarFiles sub-folder. to use this, you need to copy to the FSUIPC WASM folder (or the WASM permanent storage area) and rename it to a substring match of the aircraft for which you want to use it. Instructions are provided in the Advanced User guide. John

Sorry, but I no nothing about teensy. Not sure I understand... You say 'only the buttons on the encoders are detected', so why don't you assign to those? Rotary encoders come in various types. Some use potentiometers in which case they are assigned to an axis, but many use either one or two buttons in each direction. For these types of rotaries, you assign the buttons to the corresponding inc/dec control. If there are two buttons in each direction, one will be for fast inc/dec, the other for slow inc/dec. If there is only one button in each direction, you can use a lua script to emulate fast/slow turning - such a script is provided in the lua examples: If its a two-phase type rotary, the ones where turning the spindle one way gives pulses on two lines phase shifted one way, and turning the spindle the other way gives the opposite phase relationship, then please see the Advanced User guide (P21). John

There is only one version of FSUIPC that supports MSFS, and that is FSUIPC7. FSUIPC7 does have auto-save, but some issues have been reported when using with some Bush trips. You can download and try it - a trial license is available in a sticky-post at the top of this sub-forum. John P.S. You posted in the FAQ sub-forum where it states NOT for support requests. I have moved your post for you.

Hi Leo, You don't/shouldn't call ipc.exit() in the terminate event function, as the thread is already terminating. Remove that, and also the sleep. Try that first, but if it continues to crash in the same place, try commenting out your event.terminate statement completely (so that the termination event isn't called) and let the thread be forcibly killed, when needed, instead. John

Right-click the link and select Save link as... John

Hi Leo, Not heard much from you recently - is this a good sign? John

Title of topic updated to reflect this issue is with Pilot2ATC and not FS2Crew.

Ok, then I don't know why its not connecting at the moment. I will take a look, maybe over the weekend but more likely next week. I will report back once I have taken a look. John

Have you only just started using the auto-start function then? This has been available for a long time... No, that doesn't help as your issue seems to occur only when FSUIPC7 is auto-started, no? It will only show messages logged AFTER the console window has been opened. If you keep that option set, the console window should open automatically when FSUIPC7 next auto-starts. So, now you have that option set, just run MSFS again, which should auto-start FSUIP7 and show the console. Once you see the 'starting everything now' message, then try and connect Pilot2ATC. I am only trying to verify that you are not trying to connect before FSUIPC7 is ready. John

Thank you. Your log files look ok. Are you sure that you are not just trying to connect too early? You can only connect once the following line has been logged: -------------------- Starting everything now ---------------------- Can you check that this line has been logged BEFORE you try and connect Pilot2ATC. The easiest way of doing this is to open the console window (using the Log -> Open Console menu item) and monitor the messages. Otherwise I have no idea. I will have to download Pilot2ATC and take a look, but before I do this please check the above and let me know. Thanks, John

I was trying to get you to use the latest version that I attached above, but this seems to be confusing you for some reason, so just forget that for the moment. All you need to do is to run MSFS, which will run FSUIPC7, and then try to connect Pilot2ATC. This should fail (which is your issue). When this happens, exit FSUIPC and restart it (the same version, as you always do). Then, try and connect PilotToATC again - it should succeed, according to your description of the issue. Then exit FSUIPC7, and show me the FSUIPC7.log and FSUIPC7_prev.log files. All I need is the two log files from the same version of FSUIPC7, one where the Pilot2ATC connection succeeded and one where it fails. This really isn't that difficult. John

I need to see your FSUIPC7.log files, not your FSUIPC7.ini files. And those files are still from 7.2.12. John

As I said: The log file is written to the same folder as where you ran the FSUIPC7.exe. If you don't know where that is, you can use the FSUIPC7 File -> Open Installation Folder... menu option. Please re-read my previous post. John

Sorry, but I can't help with the hardware/cable connection. Doesn't the device come with a serial cable, or can be optionally be purchased from Garmin? Maybe try asking on www.cockpitbuilders.com, or Garmin support. Once you have the device connected, the following web page can help you configure FSUIPC: https://support.flyelite.com/knowledge-base/what-settings-to-use-with-the-696796-gps-cable-in-fsxprepar3d/ Good luck! Regards, John

By the way, are you sure you are in the cockpit when you first attempt to connect Pilot2ATC? The Pilot2ATC User Guide does say: Do not attempt to connect Pilot2ATC until after you are in the cockpit in MSFS Could it be that you are just trying to connect too early? John

The log file is written to the same folder as where you ran the FSUIPC7.exe. You should use that FSUIPC7.exe to replace your currently installed one. The 'not connecting' log is from that new FSUIPC7.exe I attached above - your log shows this, and that you ran it from your Downloads folder: Whereas your 'connecting' log is from your installed v7.2.12 version: No you didn't, as your 'connecting' log shows you are still using this version. Please replace your FSUIPC7.exe in C:\FSUIPC7\ with the one in D:\Downloads. Then start MSFS/FSUIPC7, load an aircraft and try to connect Pilot2ATC. If it doesn't connect, restart FSUIPC7 and try again. If it then connects, show me your FSUIPC7.log file (which will be the successful one) and your FSUIPC7_prev.log file (which will be the previous one, produced when it failed to connect). Also, the usual reason that 3rd party programs cannot connect is that they are ran at different privilege levels. If Pilot2ATC cannot connect when FSUIPC7 is auto-started with MSFS, maybe try restarting Pilot2ATC, first with standard privileges and then with admin privileges. John

If you get the same issue, can you show me your two FSUIPC7.log files, one from when MSFS is started and Pilot2ATC fails to connect, and the other from when you restart and it connects ok.

Sure, I can add them. Any information on available hvars for any aircraft is always welcome, thanks. Note you can add them yourself (as I'm sure you are aware) but hvar files in the Community fsuipc-lvar-module folder location will get over written when you re-install. If you modify any provided hvar files, best to move them to the WASM persistent storage area (under your AppData folder - see the Advanced User Guide) where they will take precedence. John

I have no idea.... Some things to try: 1. Re-order the items - try starting AFC_Bridge first 2. If that doesn't work, try starting only AFC_Bridge: If that works, add the other items in, one by one. If it doesn't, maybe try uninstalling and re-installing ADC_Bridge. If it works then, try adding in the other entries. Otherwise, I suggest you try support for AFC_Bridge. John

Not that I am aware of. Do you know why Pilot2ATC does not connect to MSFS? Any error message? There weren't that many changes between 7.2.11 and 7.2.12, and none that should affect Pilot2ATC. Or was yout previous version not 7.2.11, and if so what version were you using? Maybe try with the attached version, which will be released shortly: John FSUIPC7.exe

Ok, good to know. Thanks for reporting back. John

Also, please update to the latest version of FSUIPC4, v4.976. Only the latest version is supported. John