ACARS stops because of FSUIPC error

[PilotTe]

Good morning,

I have been trying for the last three weeks to log flights using ACARS and part way through the flight it stops logging the flight. I bought FSUIPC about three weeks ago. The error I get is the following;

2020/04/02 10:38: ERROR:    Unable to retreive flight simulator date and time - Closing FSUIPC connection
2020/04/02 10:38: WARNING:  Stopping all timers

This has happened many times. I am at my wits end as I have spent hours and hours each day trying to figure out the problem and reflying the flights to have the same things happen. Please help!!

I have uninstalled and reinstalled ACARS, FSUIPC, and Simconnect. I also did a full FSX - SE delete and reinstall about a month ago.

Everything is being run as an administrator.

Trevor Teakle

Edited April 2, 2020 by PilotTe
Addition to original post

[John Dowson]

19 minutes ago, PilotTe said:

I bought FSUIPC about three weeks ago

You don't need a registered version of FSUIPC to to use the 3rd party interface (to allow 3rd party applications to communicate to the sim via the FSUIPC API/offsets).

21 minutes ago, PilotTe said:

2020/04/02 10:38: ERROR:    Unable to retreive flight simulator date and time - Closing FSUIPC connection
2020/04/02 10:38: WARNING:  Stopping all timers

Is this from the ACARS log? Sounds like its at least connecting to FSUIPC. Are there any errors in the FSUIPC4 log file? Are you running ACARS at the same privilege level as FSX-SE? i.e. if you run your sim with admin privileges, you also need to run programs that connect via FSUIPC with admin privileges.

Sorry, but I know nothing about ACARS. Have you tried their support?

John

 

[PilotTe]

The log is from the ACARS. This usually happens about part way into a flight or about 10 minutes before landing. It works fine until there is a blip (almost like it's refreshing something). Both ACARS and FSX-SE are run in administrator mode. 

I've attached the log as I'm now flying without ACARS running but it happened someplace in here I would imagine.

 4622734 System time = 02/04/2020 10:38:57, Simulator time = 09:38:16 (14:38Z)
  5035453 **** No SimConnect events or states being received! Re-connecting now ... ****
  5035562 SimConnect_Open succeeded: waiting to check version okay
  5035562 Opened separate AI Traffic client okay
  5035656 Running in "Microsoft Flight Simulator X", Version: 10.0.62615.0 (SimConnect: 10.0.62615.0)
  5035656 Initialising SimConnect data requests now
  5035656 FSUIPC Menu entry added
  5035687 User Aircraft ID 1 supplied, now being used
  5036703 System time = 02/04/2020 10:45:51, Simulator time = 09:45:31 (14:45Z)
  5800672 **** No SimConnect events or states being received! Re-connecting now ... ****
  5800765 SimConnect_Open succeeded: waiting to check version okay
  5800765 Opened separate AI Traffic client okay
  5800781 Running in "Microsoft Flight Simulator X", Version: 10.0.62615.0 (SimConnect: 10.0.62615.0)
  5800781 Initialising SimConnect data requests now
  5800781 FSUIPC Menu entry added
  5800812 User Aircraft ID 1 supplied, now being used
  5801625 System time = 02/04/2020 10:58:36, Simulator time = 09:58:51 (14:58Z)
  5815750 **** No SimConnect events or states being received! Re-connecting now ... ****
  5815843 SimConnect_Open succeeded: waiting to check version okay
  5815843 Opened separate AI Traffic client okay
  5815859 Running in "Microsoft Flight Simulator X", Version: 10.0.62615.0 (SimConnect: 10.0.62615.0)
  5815859 Initialising SimConnect data requests now
  5815859 FSUIPC Menu entry added
  5815890 User Aircraft ID 1 supplied, now being used
  5816015 System time = 02/04/2020 10:58:50, Simulator time = 09:58:55 (14:58Z)
  6223593 **** No SimConnect events or states being received! Re-connecting now ... ****
  6223703 SimConnect_Open succeeded: waiting to check version okay
  6223703 Opened separate AI Traffic client okay
  6223703 Running in "Microsoft Flight Simulator X", Version: 10.0.62615.0 (SimConnect: 10.0.62615.0)
  6223703 Initialising SimConnect data requests now
  6223703 FSUIPC Menu entry added

FSUIPC4.log

[PilotTe]

It happened around 10:38 so it looks like I may have pulled out the wrong part of the log.

[John Dowson]

17 minutes ago, PilotTe said:

5815750 **** No SimConnect events or states being received! Re-connecting now ... ****

You have quite a few of these messages logged, which is not a good sign. This is usually a sign that the system is overloaded and not giving enough time to FS or SimConnect. Is your system heavily loaded?

I see that you are also using a PMDG aircraft. Do you get the same error when using other (default) aircraft? Are you using the auto-save facility?

 

[Pete Dowson]

2 hours ago, PilotTe said:

It happened around 10:38 so it looks like I may have pulled out the wrong part of the log.

I don't think that matters. Lookng at the part you supplied these interruptions are occurring at intervals:

**** No SimConnect events or states being received! Re-connecting now ... ****

That occurred 4 times in the short log segment you provided. That is terrible. Each time SimConnect stops sending data to FSUIPC for a while, FSUIPC has to decide that the connection is gone and it reconnects. That involves a complete re-initialisation, so itself takes some time.

There is a parameter in the FSUIPC4.INI file which determines how long it waits before deciding things are wrong, but whilst you could try increasing that, i think first you should work out why it is that your setup cannot cope. FSUIPC needs continuous data being updated by SimConnect in order to carry out many of its operations.

Generally these particular SimConnect problems occur because the system is massively overloaded, so perhaps you could list the AddOns you are using too?  You may be using an advanced cockpit like those from PMDG or Aerosoft, and have the Autosave option enabled -- either in FSUIPC or in another program. Most such aircraft also save a few files detailing the state of the cockpit, so a simple FSX-SE flight save turns out to be several seconds of disk operations. Sometimes an increase in FSUIPC timeouts will help with that.

Finally, your ACARS program needs to allow for more of a delay in receiving data, to overcome periods like that described. It does sound like it is in need of a bit of improvement.

Pete