Jump to content
Sign in to follow this  
airlinetycoon

SimConnect problem - no 1sec system event

Recommended Posts

16 minutes ago, kiek said:

Please read the PSXT Manual ..

You can find it in the PSXseeconTraffic folder. You are using a special PSXT exe with trace info. That info is stored in the Log.txt.

FSUIPC AI Manager is running according to your SimConnect log...

Lol, you just said log.txt, I didn’t know you were talking about psxt log, confuses..I know where psxt log.txt is....

Computer off so it’ll have to be later when I turn it on again..

 

I’ll check my fsuipc, never used any fsuipc AI manager.

Share this post


Link to post
Share on other sites
13 hours ago, AIRIFR said:

Here the Simconnect0.Log. I noticed it says SimConnect version 3.4.0.0, but I installed Flight Simulator SimConnect Client v10.0.61259.0 from the redist FSX-SP2-XPACK folder inside main Prepar3D, so not sure if normal?

From this log:

> 1101.49017 [78, 1]Open: Version=0x00000004  Name="PSXseeconTraffic"
...
1409.29112 [78] Receive Packet Too Large! (1, 80004004)
 

I don't know if this means that the server received a too large packed (sent by PSXT) or vice versa that the client received a too large packed from the server (the sim).

But you could try to increase as well MaxReceiveSize in SimConnect.cfg as MaxRecvSize in SimConnect.xml to 16384  and see what happens.

 

EDIT: Just to give you an idea how many programs use SimConnect, here yours:

> 122.19241 [64, 1]Open: Version=0x00000004  Name="Addon Manager 64"
> 122.19277 [65, 1]Open: Version=0x00000004  Name="SimObjectAnimationModule"
> 122.19360 [66, 1]Open: Version=0x00000004  Name="NavigraphChartsSimlinkFS"
> 122.19375 [67, 1]Open: Version=0x00000004  Name="Couatl"
> 122.19376 [ 0, 1]Open: Version=0x00000017  Name="FSUIPC4"
> 122.19378 [ 1, 1]Open: Version=0x00000017  Name="FSUIPC4_AItraffic"
> 122.19385 [68, 1]Open: Version=0x00000004  Name="PMDG Interface"
> 122.19388 [69, 1]Open: Version=0x00000004  Name="RAAS Professional"
> 122.19439 [70, 1]Open: Version=0x00000004  Name="pilot_core_fsxp3d"
> 122.19617 [71, 1]Open: Version=0x00000004  Name="ASConnect"
> 122.19636 [72, 1]Open: Version=0x00000004  Name="ChasePlane"
> 122.19960 [73, 1]Open: Version=0x00000004  Name="SimObject Display Engine SODE"
> 588.13471 [74, 1]Open: Version=0x00000004  Name="AS16_FSX Managed Data Request"
> 995.82698 [75, 1]Open: Version=0x00000004  Name="747QOTSII"
> 996.49814 [447, 1]Open: Version=0x00000007  Name="ObjectFlow_P3D.dll"
> 1014.76300 [ 2, 1]Open: Version=0x00000017  Name="VIRTUALI p3dProxy"
> 1020.99358 [76, 1]Open: Version=0x00000004  Name="SODEClient"
> 1021.25000 [ 3, 1]Open: Version=0x00000017  Name="FSUIPC4_PMDG_737CDU_DATA"
> 1021.25004 [ 4, 1]Open: Version=0x00000017  Name="FSUIPC4 PMDG 777Xdata"
> 1021.25017 [ 6, 1]Open: Version=0x00000017  Name="FSUIPC4 PMDG 747CDUdata"
> 1021.25018 [ 5, 1]Open: Version=0x00000017  Name="FSUIPC4 PMDG 747data"
> 1066.01372 [77, 1]Open: Version=0x00000004  Name="VE_SC_WPF"
> 1101.49017 [78, 1]Open: Version=0x00000004  Name="PSXseeconTraffic"
> 1872.80559 [79, 1]Open: Version=0x00000004  Name="ENV"
 

Edited by kiek

Share this post


Link to post
Share on other sites
14 hours ago, kiek said:

Please post your Log.txt too. What flightsim are you using? If P3D you do not need to install a SimConnect Client if you are using PSXT 64 bit. I have P3D v5 and it says SimConnect version 5.0.0.0

EDIT: in the SimConnect0.log I see that you have several programs running via SimConnect. One is FSUIPC4. Do not that you should not use the AI managerr of FSUIPC... The last event in the Log is not from PSXT but from FSUIPC....

P3D itself doesn't need simconnect client if ran alone, but the addons that run with it some do, including Active Sky etc..so needed install them, hence the name SIMconnect, you probably know that already.

There is no AI manager with FSUIPC, never heard of it, the only thing I can think of is the traffic limiter option within FSUIPC, it lets you if you wish set a max number of aircraft around, I never touched those traffic limiter settings left them at default, which is no traffic limit, 

meaning the sim can run any number of aircraft accordingly.

Share this post


Link to post
Share on other sites
2 hours ago, kiek said:

EDIT: Just to give you an idea how many programs use SimConnect, here yours:

> 122.19241 [64, 1]Open: Version=0x00000004  Name="Addon Manager 64"
> 122.19277 [65, 1]Open: Version=0x00000004  Name="SimObjectAnimationModule"
> 122.19360 [66, 1]Open: Version=0x00000004  Name="NavigraphChartsSimlinkFS"
> 122.19375 [67, 1]Open: Version=0x00000004  Name="Couatl"
> 122.19376 [ 0, 1]Open: Version=0x00000017  Name="FSUIPC4"
> 122.19378 [ 1, 1]Open: Version=0x00000017  Name="FSUIPC4_AItraffic"
> 122.19385 [68, 1]Open: Version=0x00000004  Name="PMDG Interface"
> 122.19388 [69, 1]Open: Version=0x00000004  Name="RAAS Professional"
> 122.19439 [70, 1]Open: Version=0x00000004  Name="pilot_core_fsxp3d"
> 122.19617 [71, 1]Open: Version=0x00000004  Name="ASConnect"
> 122.19636 [72, 1]Open: Version=0x00000004  Name="ChasePlane"
> 122.19960 [73, 1]Open: Version=0x00000004  Name="SimObject Display Engine SODE"
> 588.13471 [74, 1]Open: Version=0x00000004  Name="AS16_FSX Managed Data Request"
> 995.82698 [75, 1]Open: Version=0x00000004  Name="747QOTSII"
> 996.49814 [447, 1]Open: Version=0x00000007  Name="ObjectFlow_P3D.dll"
> 1014.76300 [ 2, 1]Open: Version=0x00000017  Name="VIRTUALI p3dProxy"
> 1020.99358 [76, 1]Open: Version=0x00000004  Name="SODEClient"
> 1021.25000 [ 3, 1]Open: Version=0x00000017  Name="FSUIPC4_PMDG_737CDU_DATA"
> 1021.25004 [ 4, 1]Open: Version=0x00000017  Name="FSUIPC4 PMDG 777Xdata"
> 1021.25017 [ 6, 1]Open: Version=0x00000017  Name="FSUIPC4 PMDG 747CDUdata"
> 1021.25018 [ 5, 1]Open: Version=0x00000017  Name="FSUIPC4 PMDG 747data"
> 1066.01372 [77, 1]Open: Version=0x00000004  Name="VE_SC_WPF"
> 1101.49017 [78, 1]Open: Version=0x00000004  Name="PSXseeconTraffic"
> 1872.80559 [79, 1]Open: Version=0x00000004  Name="ENV"
 

Yes, and? 

Edited by kiek

Share this post


Link to post
Share on other sites
18 minutes ago, AIRIFR said:

Yes, and?

It was just for information. Try a bigger size 

Please post your Log.txt...

Edited by kiek

Share this post


Link to post
Share on other sites
16 minutes ago, AIRIFR said:

, I never touched those traffic limiter settings left them at default, which is no traffic limit, 

meaning the sim can run any number of aircraft accordingly.

Okay  thats according to the PSXT Manual .

Share this post


Link to post
Share on other sites
47 minutes ago, kiek said:

It was just for information. Try a bigger size 

Please post your Log.txt...

Here the log from about 10min ago, in flight at the moment, no simconnect event (yet?)..about another 7h fight until landing. Flight time so far 03:45.

EDIT: using the official 18.4 website update, not this forum links you sent recently.

Edited by AIRIFR

Share this post


Link to post
Share on other sites
55 minutes ago, AIRIFR said:

 

EDIT: using the official 18.4 website update, not this forum links you sent recently.

That's not good... The official version has no trace info. You should have taken the links in this thread ....

And only post the Log of a session that ends with the SimConnect problem and also the corresponding SimConnectx.log please.

Edited by kiek

Share this post


Link to post
Share on other sites
9 minutes ago, kiek said:

That's not good... The official version has no trace info. You should have taken the links in this thread ....

And only post the Log of a session that ends with the SimConnect problem.

Alright, next flight I'll use. I used that website one because didn't have simconnect event on last try, but had it with the thread one.

Yes but I thought I send log anyway just for clarity or anything there or not there etc.

Share this post


Link to post
Share on other sites
 
This is inconclusive yet but I eliminated from my DLL.XML  "traffictoolbox.dll"   which is STK FSX addon, and I never suspected it but when I try without it I had 2 uninterrupted successful flights with 18.4 standard from the website.
Maybe going through one by one and eliminating temporarily addons from  DLL.XML   trace which conflicts with PSXT
 
mike

Sim,PC, monitor,prescription glasses, chair.

Share this post


Link to post
Share on other sites

Hi Nico,

Looking at very specific examples now.

PSXT reports:

Quote

RPA4399*          IND ->CLT  E75L airborne not detected, no ON_GROUND msg received, no objectId.. is hanging ...  

You have previously indicated that this was a fault with the data provider.  Right.

Quote

AITFC,624381993,38.750,-85.980,27100,1856,1,119,406,RPA4399*,E75L,,IND,CLT,1597421679
AITFC,624381993,38.730,-85.930,27100,0,1,129,406,RPA4399*,E75L,,IND,CLT,1597421707
AITFC,624381993,38.730,-85.930,27100,0,1,129,406,RPA4399*,E75L,,IND,CLT,1597421707
AITFC,624381993,38.710,-85.910,27100,0,1,129,406,RPA4399*,E75L,,IND,CLT,1597421719
AITFC,624381993,38.710,-85.910,27100,0,1,129,406,RPA4399*,E75L,,IND,CLT,1597421719
AITFC,624381993,38.700,-85.900,27100,0,1,129,406,RPA4399*,E75L,,IND,CLT,1597421731
AITFC,624381993,38.700,-85.900,27100,0,1,129,406,RPA4399*,E75L,,IND,CLT,1597421731
AITFC,624381993,38.690,-85.880,27100,0,1,129,406,RPA4399*,E75L,,IND,CLT,1597421743
AITFC,624381993,38.690,-85.880,27100,0,1,129,406,RPA4399*,E75L,,IND,CLT,1597421743
AITFC,624381993,38.690,-85.880,27100,0,1,129,406,RPA4399*,E75L,,IND,CLT,1597421743
AITFC,624381993,38.680,-85.860,27100,0,1,129,406,RPA4399*,E75L,,IND,CLT,1597421755
AITFC,624381993,38.680,-85.860,27100,0,1,129,406,RPA4399*,E75L,,IND,CLT,1597421755
AITFC,624381993,38.670,-85.840,27100,0,1,129,406,RPA4399*,E75L,,IND,CLT,1597421767
AITFC,624381993,38.670,-85.840,27100,0,1,129,406,RPA4399*,E75L,,IND,CLT,1597421767
AITFC,624381993,38.650,-85.820,27100,0,1,129,406,RPA4399*,E75L,,IND,CLT,1597421779
AITFC,624381993,38.650,-85.820,27100,0,1,129,406,RPA4399*,E75L,,IND,CLT,1597421779
AITFC,624381993,38.660,-85.700,29500,1728,1,115,417,RPA4399*,E75L,,IND,CLT,1597421789
AITFC,624381993,38.660,-85.700,29500,1728,1,115,417,RPA4399*,E75L,,IND,CLT,1597421789
AITFC,624381993,38.660,-85.700,29500,1728,1,115,417,RPA4399*,E75L,,IND,CLT,1597421789
AITFC,624381993,38.660,-85.700,29500,1728,1,115,417,RPA4399*,E75L,,IND,CLT,1597421789
AITFC,624381993,38.660,-85.700,29500,1728,1,115,417,RPA4399*,E75L,,IND,CLT,1597421789
AITFC,624381993,38.630,-85.660,29500,0,1,130,417,RPA4399*,E75L,,IND,CLT,1597421815
AITFC,624381993,38.620,-85.640,29500,0,1,130,417,RPA4399*,E75L,,IND,CLT,1597421827
AITFC,624381993,38.620,-85.640,29500,0,1,130,417,RPA4399*,E75L,,IND,CLT,1597421827
AITFC,624381993,38.620,-85.640,29500,0,1,130,417,RPA4399*,E75L,,IND,CLT,1597421827
AITFC,624381993,38.610,-85.620,29500,0,1,130,417,RPA4399*,E75L,,IND,CLT,1597421839
AITFC,624381993,38.610,-85.620,29500,0,1,130,417,RPA4399*,E75L,,IND,CLT,1597421839
AITFC,624381993,38.590,-85.600,29500,0,1,130,417,RPA4399*,E75L,,IND,CLT,1597421851
AITFC,624381993,38.590,-85.600,29500,0,1,130,417,RPA4399*,E75L,,IND,CLT,1597421851
AITFC,624381993,38.580,-85.580,29500,0,1,130,417,RPA4399*,E75L,,IND,CLT,1597421863
AITFC,624381993,38.610,-85.520,30400,1536,1,115,427,RPA4399*,E75L,,IND,CLT,1597421863
AITFC,624381993,38.610,-85.520,30400,1536,1,115,427,RPA4399*,E75L,,IND,CLT,1597421863
AITFC,624381993,38.610,-85.520,30400,1536,1,115,427,RPA4399*,E75L,,IND,CLT,1597421863

Can you please indicate what is at fault with the data provider for this aircraft?

Trying to understand, WHAT, and WHY these errors are occurring.  If the data provided by the data feed is correct (which it seemingly is as far as I can see), why is PSXT complaining about it?

I am not sure what "no ON_GROUND msg received" means (it's not documented anywhere), and the "airborne not detected" doesn't make sense either as per the PSXT specs, the airborne flag is set, to a value of 1 as per your data spec.

May I even further state, that your own protocol documentation, states that "Header and airborne are not relevant,"  So I am seriously failing to understand where the "airborne not detected, no ON_GROUND msg received" is coming from, seeing that it is apparently a data provider fault?

 

Edited by cknipe

Share this post


Link to post
Share on other sites
1 hour ago, cknipe said:

Hi Nico,

Looking at very specific examples now.

PSXT reports:

You have previously indicated that this was a fault with the data provider.  Right.

Can you please indicate what is at fault with the data provider for this aircraft?

Trying to understand, WHAT, and WHY these errors are occurring.  If the data provided by the data feed is correct (which it seemingly is as far as I can see), why is PSXT complaining about it?

I am not sure what "no ON_GROUND msg received" means (it's not documented anywhere), and the "airborne not detected" doesn't make sense either as per the PSXT specs, the airborne flag is set, to a value of 1 as per your data spec.

May I even further state, that your own protocol documentation, states that "Header and airborne are not relevant,"  So I am seriously failing to understand where the "airborne not detected, no ON_GROUND msg received" is coming from, seeing that it is apparently a data provider fault?

 

This is off topic, could you please start a new thread. We are already at page 10 here...

Share this post


Link to post
Share on other sites
7 hours ago, AIRIFR said:

Here the log from about 10min ago, in flight at the moment, no simconnect event (yet?)..about another 7h fight until landing. Flight time so far 03:45.

EDIT: using the official 18.4 website update, not this forum links you sent recently.

Flight done, 10:42 and NO simconnect event, with website 18.4! Like before.

Looks like my finding about my addon automatic camera feature was what was causing the conflict?

Testing again tomorrow on my next flight. I'll do couple more flight tests and if no simconnect events we'll assume back to normal.

 

By the way, is it possible to reinstate the traffic limit feature within PSXT? It came handy on busy airports, it shows at the moment 142! Live aircrafts here at KSFO! Approaching the airfiled I could feel the performance degradation, stutters, low fps and VAS warning all of the sudden, and was wondering why, and when looking PSXT I saw that, that explained why. As you know, I'm not running a 64bit flight simulator but a 32bit so VAS is always a concern for my P3Dv3. You could just reinstate it to the PSXT 32bit version since 64bit version don't have VAS problems.

Share this post


Link to post
Share on other sites
25 minutes ago, kiek said:

This is off topic, could you please start a new thread. We are already at page 10 here...

sure, of course.

Page 10 and no one still knows what the issue is... One moment everything is 100% fine for 24+ hours in sim, the next moment random errors from PSXT within 10 minutes.

Share this post


Link to post
Share on other sites

@kiek - I believe I can reproduce the issue on demand.  I need to do a few more tests, but I've just deliberately crashed PSXT (no position update received).

It's not a problem in the data feeder, it's not a problem in PSXT, it's a general, very rare, issue that DOES happen and occur in real life as far as MODE-S transponder codes go.  Hint: Whilst they are SUPPOSED to be unique, there IS a chance, that a duplicate can occur.  - that should already point you towards where I am heading with this.

I suspect you are relying on the MODE-S codes to be unique, and I suspect the errors occur when the data feed injects two (or more) aircraft with the same MODE-S.  The AI Object is removed (seems to be generated based on the MODE-S code), but PSXT still tries to update it after it has been removed from the sim (the update occurs from the other aircraft, not the object deleted, but I think SimConnect removes -all- objects with the same ID).

FYI: https://en.wikipedia.org/wiki/Aviation_transponder_interrogation_modes  Mode-S Transponders and how they can be reprogrammed,

FYI: https://www.pprune.org/atc-issues/550950-duplicate-icao-24-bit-aircraft-addresses-ssr.html an interesting forum read about duplicate Mode-S codes in real life at Heathrow.

In a nutshell, inject two duplicate aircraft (MODE-S codes), remove one (i.e. PSXT executes the DeleteObject), then go to another airport which puts you out of range and PSXT will (fail) in attempting to execute the second DeleteObject because it doesn't exist in the sim anymore.

Follow AAY1791* in test.txt (what I inject into PSXT), and watch what happens in PSXT after AAY1791 is removed at KSDF, and after I move to KJFK.  She's dead in the water.  Data feed no longer receiving position updates from PSXT (connects, but receives no data).

Logs at https://filebin.net/tcnw9wic5ldzv0ex - your latest 64bit build with trace logs.

 

This will explain why this is so rare, and it IS this rare in real life as well - but even in real life, it does cause absolute havoc from what I am reading / understanding.

PS: Should be fixable in PSXT, or in the data feeder fairly easily, if I am right about this.
PSS: Please don't shoot me down again when I'm asking for information re data feeds - there's a very valid reason for my questions, you may just not know them.  20+ years in IT my friend, you know as well as I do that rare problems, often has nothing to do with what / where you are looking at for the problem.

Edited by cknipe

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...