CPflight MCP does not find FSUIPC7

[fischkarl]

Hi, I would like to use the PMDG 737 with my CPflight 737 USB MCP. If I want to connect this, then the error message comes

up that  FSUIPC7 is not found and I should install it. However, I have a registered FSUIPC7 version. Can the error be because there is no .evt file from the PMDG in the FSUIPC folder? And if so, where can I get such a file from? Thank you, Michael

[John Dowson]

14 minutes ago, fischkarl said:

If I want to connect this, then the error message comes up that  FSUIPC7 is not found and I should install it.

Did you check that FSUIPC7 is running? Where/what software is this error message from?

14 minutes ago, fischkarl said:

Can the error be because there is no .evt file from the PMDG in the FSUIPC folder?

There is no *.evt file for the PMDG 737. Event files only provide access to custom events that are handled by either the aircraft or a WASM module. The event files that come with FSUIPC7 are mainly for use with the MobiFlight event module, although there is also one for the FBW A320. However, you do not really need use event files any more as they have been replaced by presets. A preset is a name attached to a calculator code string, which when used is applied by the FSUIPC WASM module. Event files are events that are mapped to similar calculator code strings but this is done in the handling module, usually the MF event module.

The PMDG 737 seems to have implemented its custom controls using parameters for the Rotor Brake control. You can assign to this control directly, if you know the parameter values to use (I believe someone posted a spreadsheet containing these...somewhere...) - otherwise you can use (or at least take a look at) the preset calculator code, or see what is being used by a preset. For a searchable list of available presets, please see the MG HubHop resource: https://hubhop.mobiflight.com/presets/

John

P.S. You seem to have raised the same question twice - I will delete the other one

[fischkarl]

Yes, FSUIPC was started. The error message came from the CPflight software FS_Com. There it was written, among other things:
Copy the file flybywire-aircraft-a320neo.evt from EventFile of fsuipc7 folder directly in the main folder of fsuipc7

Open your fsuipc7.ini file and verify that the line flybywire_a320-neo in the first position of the {EventFiles} section with 0 prefix. Verify also in your fsuipc7.ini file that Wapi is enabled, in case add the command like in the example below...

I had hoped that there would also be such an .evt file for the PMDG.
I'm afraid that I can no longer connect my MCP

Yes, sorry, I accidentally posted this twice

[John Dowson]

23 minutes ago, fischkarl said:

I had hoped that there would also be such an .evt file for the PMDG.

There is no event file for the PMDG. However, you can create one if you wish, using the MobiFlight cip file. You would then also need the MobiFlight WASM module installed to handle those events. As event files have basically now been superseded by presets, I am no longer providing event files. There are no custom events provided and handled by the PMDG 737 as far as O a, aware - the custom events for this aircraft use the Rotor Brake control, with the parameter indicating the purpose/control.

BUT, this will have nothing to do with your MCP not being able to connect. I don't know what your issue is with this and cannot really help you either. You need to contact whoever provides the software for this.

 

[ppatys]

Hello,
I have the same problem. After installing FSUIPC 7.3.4 CPflight MCP  stopped working. It says it can't find FSUIPC. All the others elements of throttle where working properly. ALT+P started FSUIPC control window. After uninstalling FSUIPC 7.3.4 and installing the previous version 7.3.3 CPflight works correctly.

[John Dowson]

14 hours ago, ppatys said:

After uninstalling FSUIPC 7.3.4 and installing the previous version 7.3.3 CPflight works correctly.

Ok, that is interesting....but I can't see any changes between these versions that would cause this...
Could you show me an FSUIPC7.log file from both versions please.

John

[ppatys]

So, now I reinstalled FSUIP to 7.3.4 version and it works 😀

Sorry for confusion.

[Ron Vogel]

Hello,

After loading msfs and starting FSUIPC latest version with auto startup , prosimv3, 2 sioc instances, etc, all starts up exept CP flight MCP, it lights up for a few moments then dies. I removed auto start from .ini, manualy starting programs all works fine until start FSUIPC7, same result. Using Simconnect in Prosim does the same.

Any suggestions, 

Ron

[John Dowson]

Please show me/attach your FSUIPC7.log and FSUIPC7.ini files.

[Ron Vogel]

 

Hi John,

Herewith files as requested.

Thanks,

Ron

FSUIPC7.ini FSUIPC7.log

[John Dowson]

The FSUIPC7.log file shows that you started FSUIPC7 manually, it didn't detect MSFS, and you exited 4 minutes later.
Was MSFS running when you started FSUIPC7, or did you start MSFS after FSUIPC7 was running? If MSFS was running at some stage, then this was not detected by FSUIPC7.
If this is the case, please try adding
    DisableMSFSMonitor=Enum
to the [General] section of your FSUIPC7.ini file. This is usually only needed with Windows 11, but maybe there has been a windows 10 update which now requires this for Windows 10 (I will check this later).

Otherwise, please show me/attach a log showing your issue.

John
    

 

[John Dowson]

It is also strange that some basic start-up parameters seem to be missing from your ini file. When you start MSFS, wait for FSUIPC7 start and then wait for MSFS to get to the main menu.
Once this is done, the start-up ini parameters will be written to your ini file. Then exit MSFS and start it again and your FSUIPC start=up parameters will be tuned.

[Ron Vogel]

Hi John,

I tried yourt suggestion, no luck there.

WhenI start MSFS and wait, FSUIPC will not autostart, however in the menu it say start auto connect to FS.

So I start FSUIPC manualy, all starts up also my CP flight MCP, it lights up as it normally does and then the displays change tothe standard start sighs and the it dies.

I coped and paste part of the Prosim Log, complete log too big, and as you can see Com5, For MCP, does not connect.

Running with P3Dv5 and FSUIPC6 ther is no problem at all. If you need more info please let me know.

Best regards,

Ron

7/23/2024 7:55:49 PM * genericCOMport:Opening COM5 at 115200,N,8,One
7/23/2024 7:55:49 PM ! genericCOMport:Error opening port: Access to the port 'COM5' is denied.
7/23/2024 7:55:54 PM * genericCOMport:Opening COM5 at 115200,N,8,One
7/23/2024 7:55:54 PM ! genericCOMport:Error opening port: Access to the port 'COM5' is denied.
7/23/2024 7:55:59 PM * genericCOMport:Opening COM5 at 115200,N,8,One
7/23/2024 7:55:59 PM ! genericCOMport:Error opening port: Access to the port 'COM5' is denied.
7/23/2024 7:56:04 PM * genericCOMport:Opening COM5 at 115200,N,8,One
7/23/2024 7:56:04 PM ! genericCOMport:Error opening port: Access to the port 'COM5' is denied.
7/23/2024 7:56:09 PM * genericCOMport:Opening COM5 at 115200,N,8,One
7/23/2024 7:56:09 PM ! genericCOMport:Error opening port: Access to the port 'COM5' is denied.
7/23/2024 7:56:14 PM * genericCOMport:Opening COM5 at 115200,N,8,One
7/23/2024 7:56:14 PM ! genericCOMport:Error opening port: Access to the port 'COM5' is denied.
7/23/2024 7:56:19 PM * genericCOMport:Opening COM5 at 115200,N,8,One
7/23/2024 7:56:19 PM ! genericCOMport:Error opening port: Access to the port 'COM5' is denied.
7/23/2024 7:56:24 PM * genericCOMport:Opening COM5 at 115200,N,8,One
7/23/2024 7:56:24 PM ! genericCOMport:Error opening port: Access to the port 'COM5' is denied.
7/23/2024 7:56:29 PM * genericCOMport:Opening COM5 at 115200,N,8,One
7/23/2024 7:56:29 PM ! genericCOMport:Error opening port: Access to the port 'COM5' is denied.
7/23/2024 7:56:34 PM * genericCOMport:Opening COM5 at 115200,N,8,One
7/23/2024 7:56:34 PM ! genericCOMport:Error opening port: Access to the port 'COM5' is denied.
7/23/2024 7:56:39 PM * genericCOMport:Opening COM5 at 115200,N,8,One
7/23/2024 7:56:39 PM ! genericCOMport:Error opening port: Access to the port 'COM5' is denied.
7/23/2024 7:56:42 PM * hoppie:Sending http://www.hoppie.nl/acars/system/connect.html?logon=yxt6TWhGyABvbsqa from=1947 to=SERVER type=poll :  
7/23/2024 7:56:44 PM * genericCOMport:Opening COM5 at 115200,N,8,One
7/23/2024 7:56:44 PM ! genericCOMport:Error opening port: Access to the port 'COM5' is denied.
7/23/2024 7:56:49 PM * genericCOMport:Opening COM5 at 115200,N,8,One
7/23/2024 7:56:49 PM ! genericCOMport:Error opening port: Access to the port 'COM5' is denied.
 

FSUIPC7.log FSUIPC7.ini

[John Dowson]

16 hours ago, Ron Vogel said:

WhenI start MSFS and wait, FSUIPC will not autostart,

For all auto-start issues, see 

The log file you attached shows no issues, but also shows that you either attached it when FSUIPC7 was still running, or FSUIPC7 had crashed. Please always exit FSUIPC7 before attaching files.

16 hours ago, Ron Vogel said:

I coped and paste part of the Prosim Log, complete log too big, and as you can see Com5, For MCP, does not connect.

Does not connect to what? If the MCP doesn't connect to Prosim, this is nothing to do with FSUIPC. There are no com ports configured in your FSUIPC7.ini file.

On 7/19/2024 at 10:49 AM, Ron Vogel said:

After loading msfs and starting FSUIPC latest version with auto startup

Can you switch back to the previous version and see if it works with that please. If not, it is not an FSUIPC issue. The previous version, if you don't have it, is available here.

John

P.S. If access is denied on a port, then it could be a permissions issue or something else could be using / blocking the port. Make sure toy are running everything at the same privilege level, and reboot your PC.

Edited July 24 by John Dowson
PS added

[John Dowson]

Also, are you running the CPFlight MCP driver (and if not, why not?)? I believe this uses the FSUIPC WASM module. Check that this is still running (via the devmode debug console window), or show me the FSUIPC_WASM.log file, but attach only AFTER exiting MSFS. There is an issue where the WASM sometimes can crash - if this is the case, there are some config. parameters you can set that will make this crash less likely. But best to confirm if this is an issue or not first.

John

[Ron Vogel]

Hi John,

Tried with the previous versien, same result. FSUIPC starts MSFS, when ready to fly pressed twice nothing happens and I have to start the FSUIPC7 exe manualy.  All starts up but MCp dies as before. As I use Prosimv3, CP flight runs direct with prosim, When exit FSUIPC and restart Prosim MCP works OK. I don not understand the WASM tried with 

Can not find FSUIPC_WASM log file.

 

[John Dowson]

14 hours ago, Ron Vogel said:

FSUIPC starts MSFS

FSUIPC does not necessarily start MSFS. The desktop icon, installed by the FSUIPC installer, starts MSFS. In the default configuration, with auto-start using the EXE.xml, it is MSFS that starts FSUIPC7. As I said, for ALL issues with auto-start, please see that FAQ entry I referenced.

14 hours ago, Ron Vogel said:

Can not find FSUIPC_WASM log file.

This is located in your WASM persistence area, which is:

Quote

In the WASM persistent storage area, which is:
    For Steam installs, in the following folder under your user account:
        AppData\Roaming\Microsoft Flight Simulator\Packages\fsuipc-lvar-module\work
    For MS Store installs, in the following folder under your user account:
        AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\fsuipc-lvarmodule\work

The FSUIPC WASM log file (FSUIPC_WASM.log) can also be found in this location.

I don't think it will show much but worth checking. Make sue toy attach it after you have shutdown MSFS.

14 hours ago, Ron Vogel said:

All starts up but MCp dies as before. As I use Prosimv3, CP flight runs direct with prosim, When exit FSUIPC and restart Prosim MCP works OK.

I don't understand this as FSUIPC is doing nothing with your MCP as far as I can tell. I can only think that it must be one of the programs that is started/stopped with FSUIPC:

Quote

Run1=READY,CLOSE,"D:\Prosim v3\ProSimB738\ProSimB738\ProSimB738.exe"
Run2=READY,CLOSE,"C:\SIOC\SIOC - OH Server New\sioc OH Server new.exe"
Run3=READY,CLOSE,"C:\Program Files\AivlaSoft\EFB2\Server\AivlaSoft.Efb.Server.exe"
Run4=READY,CLOSE,"C:\SIOC\SIOC - OH DIRECT\sioc OH Direct.exe"
Run5=READY,CLOSE,"D:\Prosim v3\ProSimAudio2\ProSimAudio2\ProsimAudio.v2.exe"

Maybe try removing them (temporarily - comment them out), and start each one manually to see if one of them is causing this issue.

[John Dowson]

Also I see you are running FSUIPC with elevated privileges:

Quote

FSUIPC is running with elevated privileges

Make sure you are also running MSFS and all other programs with elevated privileges, otherwise they won't connect. Always better to run with standard privileges unless you have a good reason not to.

John

[Ron Vogel]

Hi JOHN,

I disabled autostart of programms and started MSFS as administrator, Fsuipc also started with it, started all programms manualy did the same as before MCP started and died. when exit FSUIPC and restarted Prosim MCP started up again. I waited a few moments and started FSUIPC again and MCP did not die .If this is the routine I have to follow, so be it, but it should not be so.

I attached WASM log and again the FSUIPC log.

Ron

 

FSUIPC_WASM.log FSUIPC7.log

[John Dowson]

If you are running MSFS with admin privileges, are all your other programs also set to be ran with admin privileges?

On 7/26/2024 at 11:19 PM, Ron Vogel said:

Fsuipc also started with it, started all programms manualy did the same as before MCP started and died.

Is the log file attached from the first start, when it failed, or the second start? And how come FSUIPC didn't start the programs - did you disable this in the ini file?

On 7/26/2024 at 11:19 PM, Ron Vogel said:

If this is the routine I have to follow, so be it, but it should not be so.

No, you shouldn't have to do that. And I don't see how FSUIPC can be doing anything as all it is doing is starting programs.
Could it be that some of these programs are already running when you start FSUIPC7 and then two copies are running?
You could change the Run commands to use RunIf, which will prevent the programs from starting if they are already running,
Other than that, I cannot understand why the MCP would die. Do you still get the the com error in the ProSim log when this happens?

 

[Ron Vogel]

Hi John,

Changed Run for RunIf, no startups at all, so manualy again, problem still there. changed Prosim to Simconnect, all is werking, then start FSUIPC.  All works. Do not see com failure anymore.

What would be the right line for startups .ini with RunIf?

Ron

 

[John Dowson]

10 minutes ago, Ron Vogel said:

Changed Run for RunIf, no startups at all,

Please show me your log and ini files. Changing Run to RunIf should noy effect the start-up, just not start the programs if already running.

10 minutes ago, Ron Vogel said:

changed Prosim to Simconnect, all is werking, then start FSUIPC.  All works. Do not see com failure anymore.

So you only get the COM errors when ProSim is set to use FSUIPC? I am not that familiar with ProSim, but I think SimConnect is the recommended setting these days. Pete uses ProSim - I will ask him to take a look...
But earlier you also said 'Using Simconnect in Prosim does the same.' - so what else has changed?

 

10 minutes ago, Ron Vogel said:

What would be the right line for startups .ini with RunIf?

Exactly the same as Run. The only difference is that RunIf programs are not ran if they appear to be already running. So changing from Run to RunIf should have no effect if the programs are not already running. So if no programs were started, then either they were running already or there is an error somewhere (hence the need to see your files).

 

[John Dowson]

18 hours ago, Ron Vogel said:

Changed Run for RunIf, no startups at all, so manualy again, problem still there.

By 'no startups', do you also mean FSUIPC7 or just the programs that FSUIPC7 starts? When you say 'manually started;, do you mean FSUIPC7, or the programs that FSUIPC7 starts, or both?

18 hours ago, Ron Vogel said:

changed Prosim to Simconnect, all is werking, then start FSUIPC.  All works. Do not see com failure anymore.

Did you should down FSUIPC7 and all other programs before doing this, or just FSUIPC7? Was this when using RunIf instead of Run?

I think your problem lies with these additional programs being started, and not with FSUIPC7. It seems that two of your programs are trying to access the same port, or one program that is being ran twice. I suggest you check your ProSim / SIOC configutation.

I also asked Pete about this - this is his reply:

Quote

I think Prosim includes its own SIOC software (though I’m not 100% sure. It does have drivers incorporated for most supported hardware. So I suspect one of the problems he has is caused by this:

    4969 Run: ""C:\SIOC\SIOC - OH Server New\sioc OH Server new.exe""
    4969 Run: ""C:\Program Files\AivlaSoft\EFB2\Server\AivlaSoft.Efb.Server.exe""
    4969 Run: ""C:\SIOC\SIOC - OH DIRECT\sioc OH Direct.exe""

And I see that, later, he appears to have succeeded when these were eliminated / RunIf’d.

 As you said, Prosim should be used directly with all hardware it states as supported, including SIOC-based hardware such as CPFlight. And, indeed, he says: “As I use Prosimv3, CP flight runs direct with prosim, “.

The mode in which Prosim is run (SimConnect / FSUIPC) is purely concerned with how it controls the aircraft – NOT where it gets its inputs from. So I honestly cannot see how that can affect the MCP operation.

The COM5 lockout business can surely only be due to two programs trying to access it – the SIOC programs he was running and the one built into Prosim. USB devices can be “shared” but COM serial ports cannot, even if implemented via a USB socket.

Like you, I cannot see this as an FSUIPC problem, more a case of a confused implementation via INI and CFG files.

John

[Ron Vogel]

Hi John, thanks for your and Pete's reply. I will dig in to the Prosim settings onze more. I will let you know how it progresses.

Ron

[Ron Vogel]

Hi John, after testing and trying several ways of starting my system the only way to get it going without parts of the sytem not working(either CP flight MCP, or SIOC) is the following sequent.

Prosim with Simconnect, SIOC( 1 x Direct, 1 x with script for Flight & Land Alt, fsuipc disabled in setup) then FSUIPC7. 

Next MSFS when at gate all other add ons will start up, including on 2 more computers with FSUIPC and Wide FS.

This way all works ok. I can live with this. 

Kind regards Ron