John Dowson

Here's the analysis from Microsoft: John

The on-line submission to Microsoft also detected no malware - you probably won't be able to access this but here's the link: https://www.microsoft.com/en-us/wdsi/submission/4df57e58-4a1e-4d81-ac6f-ad28e26e1fdf Hopefully this will be fixed in a virus definition update shortly. Cheers, John

It was reported on the exe I believe. And I have had it stopped at run-time and removed from the installation folder by Windows Defender. As you are using windows defender, you should look at the threat removal/quaranteen and restore it from there. That exe is the previous version, 7.4.3.

I think it may be your anti-virus blocking and quarantining the FSUIPC7.exe. I have also experienced this on occasion with this release, but not always. It is very strange - I have reported this as a false-positive to Microsoft so hopefully should be fixed with a virus definition update. Check your anti-virus - if you are using anything other than Windows Defender you should report this o your anti-virus definition provider. John

Also, what happens if you manually start FSUIPC7 once MSFS2024 is already running? You don't need to re-install to test this - just double click the FSUIPC7.exe (for your MSFS2020 installation) and it should run ok (although you won't have access to the WASM facilities if this is not installed in MSFS2024).

Please use the FSUIPC7 sub-forum for all issue/questions on FSUIPC7 / MSFS2020 / MSFS2024. I have moved your post. Thanks, There is no fix. This was also reported in the MSFS2024 SU16 beta a while ago, but was later fixed see If MSFS2024 is crashing, then it is an issue for Asobo and you should check the CTD reports there - there is nothing I can do to investigate crashed in MSFS2020/MSFS2024. And if it is crashing, it will be something that needs to be addressed/fixed by Asobo. I also just fired up MSFS2024 here to check and everything seems fine here. John

I am now getting this again in Windows Defender - I will report to Microsoft.... John

Such connection issues are usually due to FSUIPC7 running at a different privilege level to APL. If you had previously changed FSUIPC7 to be ran as admin, this will have been lost when you re-install. So maybe try running the latest version with admin privileges, to see if it then connects.

Can you show me / attach your FSUIPC7.log file please. The previous version is attached below. Rename your current FSUIPC7.exe (e.g. FSUIPC7.exe.754) and save the attached to your FSUIPC7 installation folder and see if that still works. Please send me the log for the current version before you do this. Thanks, John FSUIPC7.exe

That will be a false positive - please report to the ant-virus provider you are using. I have also had this issue with Windows Defender. I reported this and it seems to be ok now, although I did get one download attempt blocked due to a threat, but subsequent downloads and installs seemed to be ok. If I get further false=positives from Windows Defender, I will report, but if you are using other anti-virus software you will need to report this yourself, or allow the threat/rstore the file, as there is not much I can do. There is no virus in FSUIPC7. John P.S. This is for FSUIPC7 so I have moved your post to the FSUIPC7 sub-forum.

👍 Thanks for the update. John

You will have to do this manually. First remove all the [LuaFiles] entries that you are no longer using, and move the corresponding lua scripts out of your FSUIPC7 installation folder. Then, for each lua script remaining, you can renumber it and also change the assignment reference. So, for example, if you changed: 16=Elevator_Trim to 1=Elevator_Trim You would need to replace all occurrences of 'CL16:' with 'CL1:', i.e. change the lua reference numbers in the assignments to the new index number of the lua script. If you are re-organising your luas, you should also consider moving them all to a subdirectory and using the LuaPath ini parameter under the [LuaFiles] section. John

No idea. FSUIPC7 does not generate that file on its own - there must be something else running that is generating those files, probably a lua script. Check your assignments and lua files in your FSUIPC7.ini file.

Better to keep the terminate function - always a good idea to close com connections. Cheers, John

As the offset event handling function is only called when the offsets change, you don't need to store and compare to the old value, so this can be simplified to function sendComFrequencies(offset, value) if offset == 0x05C4 then com.write(dev, "COM1:" .. formatComFreq(value) .. "\n") else if offset == 0x05CC then com.write(dev, "COM1SB:" .. formatComFreq(value) .. "\n") end end end John

First, can you please attach your lua scripts rather than pasting the contents. It would make this thread far easier to read. As I said, you should update the sendComFrequencies fumction, e.g. function sendComFrequencies(offset, value) if offset == 0x05C4 then local strCom1 = formatComFreq(value) if strCom1 ~= lastCom1 then com.write(dev, "COM1:" .. strCom1 .. "\n") lastCom1 = strCom1 end else if offset == 0x05CC then local strCom1sb = formatComFreq(value) if strCom1sb ~= lastCom1sb then com.write(dev, "COM1SB:" .. strCom1sb .. "\n") lastCom1sb = strCom1sb end end end But if its not running, try debugging it. Check the FSUIPC log file for errors, add further ipc.log to determine what is happening, and you can also set Lua Plugin logging to trace what is happening in the lua script. John

No idea. Where/what is that image from? What has this got to do with FSUIPC? You really need to provide more information....

Change to function processInput(dev, datastring, length) -- Parsing the received string to set COM1 standby frequency ... and wait for the data event using event.com(dev, 256, "processInput") For the sendComFrequencies function, you can use event.Offset on offsets 0x05C4 and 0x5CC, and refactor the function to use the value passed in with a conditional on the offset (or use two functions, one for each offset. John

No, obviously not. They should work in most aircraft, but not in all - as I said, they don't work correctly with the FBW A320neo that implements its own pushback system via the flypad. No, As the offset document states, both offsets 0x31FC and 0x31F8 are write-only, you cannot read the current value of the speed/heading from these offsets. I don't think there is anything available that holds the tug speed, although the tug heading is available in the simvar PUSHBACK ANGLE (in Radians).

Like most add-on aircraft then! Many (most) add-on aircraft in MSFS2020/2024 seem to implement their behavior in non-standard ways and not use the standard events or simvars.

Ok, interesting. With P3Dv4, it is always advised to start with a default aircraft, and then switch, especially if using complex add-ons, but probably a good idea to do this when using any add-on aircraft. Thanks for the update.

Electronic Flight Bag, also called a flypad (looks like an ipad), usually attached to the door below the pilots window. Used by many complex add-ons (airliners and airbuses) to configure the aircraft (fuel, weights/passengers, even throttle set-up and calibration, brakes etc) and control ground services amongst other things.

Ok, thats interesting - and I also don't understand why this would fix your issue - maybe there was an option you set that disabled this for some reason. But glad its now fixed! Maybe try comparing the old prepar3d.cfg (if you saved it) to the new one, to see what has changed that could affect this.

Tested in the FBW A320. You need to switch the pushback system on in the EFB, and then you can only attach the tug via the offsets. Looks like you need to set the direction in the EFB and control from there really.

The idea with the logs was to compare the working v5 log with the non-working v6 log, to see if any additional controls were being sent in v5. But as now v5 isn't working, this is not possible. And I don't know this aircraft. For most aircraft that I know, you would manually switch fuel tanks. Is this not the case in this aircraft? There's not much else I can do at the moment, until I have re-installed P3Dv4, installed this aircraft and taken a look.