Seemingly unnecessary events quandry...

[n116dh]

This post may be better intended for Carenado, but I thought I'd start here where the really informed folks are.

For the Carenado Phenom 300, I'm seeing that the events logs is showing a lot of events that either don't seem relevant or are constantly repeating (and conceivably wasting resources). The 300 doesn't have "Mixture" setting.  And the AP_PANEL_SPEED shouldn't be changing constantly  Wondering if anyone has any insight for this.  Thanks so much in advance.  Here is a segment of the logs:

 

********* FSUIPC5, Version 5.15 (27th November 2018) by Pete Dowson *********
User Name="David Howell"
User Addr="xxxxx@xx.com"
FSUIPC5 Key is provided
WIDEFS7 not user registered, or expired
  5962406 System time = 23/07/2021 10:24:31, Simulator time = 10:15:40 (14:15Z)
  5962406 FLT path = "C:\Users\David\Documents\Prepar3D v4 Files\"
[Continuation log requested by user]
Running inside Prepar3D v4 on Windows 10
Module base=7FFA7A1D0000
  5962609 *** EVENT: Cntrl= 66113 (0x00010241), Param= 0 (0x00000000) AP_PANEL_SPEED_OFF
  5962734 *** EVENT: Cntrl= 66113 (0x00010241), Param= 0 (0x00000000) AP_PANEL_SPEED_OFF
  5962765 *** EVENT: Cntrl= 66113 (0x00010241), Param= 0 (0x00000000) AP_PANEL_SPEED_OFF
  5962796 *** EVENT: Cntrl= 66113 (0x00010241), Param= 0 (0x00000000) AP_PANEL_SPEED_OFF
  5962843 *** EVENT: Cntrl= 66113 (0x00010241), Param= 0 (0x00000000) AP_PANEL_SPEED_OFF
  5962906 *** EVENT: Cntrl= 66113 (0x00010241), Param= 0 (0x00000000) AP_PANEL_SPEED_OFF
  5962984 *** EVENT: Cntrl= 65983 (0x000101bf), Param= 0 (0x00000000) MIXTURE1_RICH
  5962984 *** EVENT: Cntrl= 65988 (0x000101c4), Param= 0 (0x00000000) MIXTURE2_RICH
  5962984 *** EVENT: Cntrl= 66113 (0x00010241), Param= 0 (0x00000000) AP_PANEL_SPEED_OFF
  5963140 *** EVENT: Cntrl= 66072 (0x00010218), Param= 0 (0x00000000) PITOT_HEAT_ON
  5963140 *** EVENT: Cntrl= 66113 (0x00010241), Param= 0 (0x00000000) AP_PANEL_SPEED_OFF
  5963203 *** EVENT: Cntrl= 66113 (0x00010241), Param= 0 (0x00000000) AP_PANEL_SPEED_OFF
  5963265 *** EVENT: Cntrl= 66113 (0x00010241), Param= 0 (0x00000000) AP_PANEL_SPEED_OFF
  5963296 *** EVENT: Cntrl= 66113 (0x00010241), Param= 0 (0x00000000) AP_PANEL_SPEED_OFF
  5963390 *** EVENT: Cntrl= 66113 (0x00010241), Param= 0 (0x00000000) AP_PANEL_SPEED_OFF
  5963421 *** EVENT: Cntrl= 66113 (0x00010241), Param= 0 (0x00000000) AP_PANEL_SPEED_OFF
  5963484 *** EVENT: Cntrl= 66113 (0x00010241), Param= 0 (0x00000000) AP_PANEL_SPEED_OFF
  5963531 *** EVENT: Cntrl= 66113 (0x00010241), Param= 0 (0x00000000) AP_PANEL_SPEED_OFF
  5963578 *** EVENT: Cntrl= 66113 (0x00010241), Param= 0 (0x00000000) AP_PANEL_SPEED_OFF
  5963640 *** EVENT: Cntrl= 66113 (0x00010241), Param= 0 (0x00000000) AP_PANEL_SPEED_OFF
  5963703 *** EVENT: Cntrl= 66113 (0x00010241), Param= 0 (0x00000000) AP_PANEL_SPEED_OFF
  5963750 *** EVENT: Cntrl= 66113 (0x00010241), Param= 0 (0x00000000) AP_PANEL_SPEED_OFF
  5963812 *** EVENT: Cntrl= 66113 (0x00010241), Param= 0 (0x00000000) AP_PANEL_SPEED_OFF
  5963875 *** EVENT: Cntrl= 66113 (0x00010241), Param= 0 (0x00000000) AP_PANEL_SPEED_OFF
  5963937 *** EVENT: Cntrl= 66113 (0x00010241), Param= 0 (0x00000000) AP_PANEL_SPEED_OFF
  5963968 *** EVENT: Cntrl= 66113 (0x00010241), Param= 0 (0x00000000) AP_PANEL_SPEED_OFF
  5964015 *** EVENT: Cntrl= 66113 (0x00010241), Param= 0 (0x00000000) AP_PANEL_SPEED_OFF
  5964078 *** EVENT: Cntrl= 65983 (0x000101bf), Param= 0 (0x00000000) MIXTURE1_RICH
  5964078 *** EVENT: Cntrl= 65988 (0x000101c4), Param= 0 (0x00000000) MIXTURE2_RICH
  5964078 *** EVENT: Cntrl= 66113 (0x00010241), Param= 0 (0x00000000) AP_PANEL_SPEED_OFF
  5964125 *** EVENT: Cntrl= 66072 (0x00010218), Param= 0 (0x00000000) PITOT_HEAT_ON
  5964125 *** EVENT: Cntrl= 66113 (0x00010241), Param= 0 (0x00000000) AP_PANEL_SPEED_OFF
  5964203 *** EVENT: Cntrl= 66113 (0x00010241), Param= 0 (0x00000000) AP_PANEL_SPEED_OFF
  5964265 *** EVENT: Cntrl= 66113 (0x00010241), Param= 0 (0x00000000) AP_PANEL_SPEED_OFF
  5964328 *** EVENT: Cntrl= 66113 (0x00010241), Param= 0 (0x00000000) AP_PANEL_SPEED_OFF
  5964343 *** EVENT: Cntrl= 66113 (0x00010241), Param= 0 (0x00000000) AP_PANEL_SPEED_OFF
  5964437 *** EVENT: Cntrl= 66113 (0x00010241), Param= 0 (0x00000000) AP_PANEL_SPEED_OFF
  5964484 *** EVENT: Cntrl= 66113 (0x00010241), Param= 0 (0x00000000) AP_PANEL_SPEED_OFF
  5964515 *** EVENT: Cntrl= 66113 (0x00010241), Param= 0 (0x00000000) AP_PANEL_SPEED_OFF
  5964578 *** EVENT: Cntrl= 66113 (0x00010241), Param= 0 (0x00000000) AP_PANEL_SPEED_OFF
  5964640 *** EVENT: Cntrl= 66113 (0x00010241), Param= 0 (0x00000000) AP_PANEL_SPEED_OFF

[John Dowson]

43 minutes ago, n116dh said:

For the Carenado Phenom 300, I'm seeing that the events logs is showing a lot of events that either don't seem relevant or are constantly repeating (and conceivably wasting resources). The 300 doesn't have "Mixture" setting.  And the AP_PANEL_SPEED shouldn't be changing constantly  Wondering if anyone has any insight for this.  Thanks so much in advance.  Here is a segment of the logs:

FSUIPC just logs all events seen by SimConnect. Many aircraft (more in MSFS2020) and especially add-on aircraft can continually log events. Also, some controllers (notably the new Honeycomb bravo and alpha) have always on buttons, which, if assigned in the FS (FSUIPC assignments don't have this problem) can also continually be activated and send such events.

So, if the controls are something that is actually being sent by one of you assignments, then you need to look into which button/assignment is sending those and check that assignment. If it is just something that the a/c model is using internally, then you can ignore such events using the DontLogThese ini parameter. Check the Advanced User guide for details. It goes in the [General] section, and for some versions of FSUIPC it can also be used in the [Profile.xxx] sections, but I can't remember off-hand if I added that in FSUIPC5 (for sure in FSUIPC6 and FSUIPC7).

John

[spokes2112]

It isn't just Carenado, many other reputable designers have the same thing - constant control firing.
2 reasons why this may happen :
1) Unavoidable, the logic behind the system requires constant updating, an example. Many years ago I programmed a terrain following radar tied to the AP. In order for it to work correctly I needed to send vertical speed & altitude commands to the AP as fast as possible.
2) Poor programming. Many many times this is the cause.

In the case of the Phenom, I can see the MIXTURE#_RICH being used. Yes in jets it can be (and is) used, in the core of the sim it is basically the same as fuel valves.
The firing of AP_PANEL_SPEED_OFF, whoah! That really looks like bad programming, in this case it should be something like : 
(A:AUTOPILOT AIRSPEED HOLD, bool) 0 != if{ (>K:AP_PANEL_SPEED_OFF) } 
Basically, if the AP speed should be off, and it isn't, well then, turn it off! In the case above it just isn't checking if already off.

When it comes to constant firing it really isn't that bad (wasting resources) as long as it doesn't constant fire dozens (>36) of different commands.
There is 1 command, the exits, (shift-E + #) that will always be affected by constant firing. When the exits command is used (other than #1) it will not work because the second part of the command, the number, is interrupted by the background constant firing of commands. A good sign that the aircraft programming is guilty of constant firing without actually checking for it.

I see John has replied also. DontLogThese, that is one .ini entry that I just cannot live without, specially when it comes time for logging, be it lua programming or button/key/hardware checking. If interested, you could look here, I provided proof of constant firing for other reputable designers. (A2A, PMDG, Leonardo, Iris)

Roman

[n116dh]

Hey Guys, copy on the responses.  Thanks a lot for the insight.  I will give the DontLogThese a try.