Erratic communication between FSUIPC7 v7.3.17 and FsRadioPanel

[Kklosterman]

I am not totally sure which version of the msfs2020 started having this issue but wanted to see if you have any ideas why the program FsRadioPanel would stop recognizing inputs to set ALT NAV and HEADING. I have contacted there support but have not gotten anything except make sure I have the latest version.

Since there software refers to your program has to be loaded also. And you have better things like logs to reference. I wanted to see if there is anywhere I could look to verify any miscommunication from your program and theirs.

Most of their panels show the correct information during the flight but as mentioned above, Entering a new altitude specifically or turning on the AP with NAV instead of Heading it is just not responding the same anymore.

I tried updating to the 7.3.17 version and that is not helping either.

I have attached a youtube video showing the issue.   

 

As always thanks for any help,

Ken

 

[John Dowson]

I don't know how FsRadioPanel is using FSUIPC, so it is difficult to advise. You can try activating logging for Events as well as Buttons & Keys, open the logging console window (Log -> Open Console) and see what events/controls are being sent. You can also attach your FSUIPC7.log (generated with that logging enabled) and FSUIPC7.ini files here and I can take a look.

Have you tried with various aircraft? Does this apply to all aircraft or only with specific ones?

John

[Kklosterman]

John,

Thanks for the reply. I did turn on the events buttons and keys and then also turned on the console logging. That is very helpful.

My issue is that it is flying by my eyes so quickly LOL     First thing I need to do, it remove all of the 3'd party apps from the community to verify that nothing else is effecting this issue.

What I can tell so far, is that I can see the button pushes on the FSPanel screen in the log. The alt is not staying at the exect  same setting example set for 5000 it might stay at 4600 ft on the display but at least it is working. the odd one is the NAV v/s heading. The heading is working ok, but the nav is all over the place. I went into the dashboard of the plane, and changed from nav to direct to KIND and it tends to fly to the correct direction. After removing the 3'd party extra stuff. I will reinstall the FSPANEL program and re-download the following with out the subscription {Navigraph Data: This products comes with an AIRAC cycle 1513 V2 Navigraph database which has all the information you need to create a flight plan. But if you want to keep your database up to date you will need a subscription from Navigraph. (http://www.navigraph.com/FmsDataManualInstall.aspx) To install the data for the first time, you must press the right button (SLK 6) with the title UPGRADE in the STATUS Screen. The process could take up to 40 minutes, please be patient.}

I will get back to you after checking things after that. I was going to send you the LOG file but have to find a way to coordinate when pushing a button EX: NAV to see what events get generated with a time stamp.

BTW tried 2 planes both with MSFS basic package Diamond craft DA62 , and Textron Avation Cessna Citation CJ4 both have the issues described.

 

Some of what is in the current log is the following: Note the NAV is being seen in the log.

1322937 Starting WAPI...
  1322937   [INFO]: **** Starting FSUIPC7 WASM Interface (WAPI) version 1.0.0 (WASM version 1.0.0) using connection -1
  1322937   [INFO]: Connected to MSFS
  1323469 Stopping WAPI (as MSFS in main menu)...
  1323578   [INFO]: SimConnect_Close done
  1324437 Maximum number of custom events available is 1024 (defined by ini parameter MaxNumberOfCustomEvents)
  1324437 Aircraft="DA62 Asobo"
  1325109 Planned flight from KCVG to KIND
  1325109 C:\USERS\KKLOS\APPDATA\LOCAL\PACKAGES\MICROSOFT.FLIGHTSIMULATOR_8WEKYB3D8BBWE\LOCALSTATE\MISSIONS\CUSTOM\CUSTOMFLIGHT\CUSTOMFLIGHT.PLN
  1325656 *** EVENT: Cntrl= 67412 (0x00010754), Param= 0 (0x00000000) SET_DECISION_HEIGHT
  1325656 *** EVENT: Cntrl= 67413 (0x00010755), Param= 0 (0x00000000) SET_DECISION_ALTITUDE_MSL
  1325656 *** EVENT: Cntrl= 67419 (0x0001075b), Param= 0 (0x00000000) MASTER_CAUTION_SET
  1325656 *** EVENT: Cntrl= 67414 (0x00010756), Param= 0 (0x00000000) MASTER_WARNING_SET
  1327484 Starting WAPI...
  1327484   [INFO]: **** Starting FSUIPC7 WASM Interface (WAPI) version 1.0.0 (WASM version 1.0.0) using connection -1
  1327484   [INFO]: Connected to MSFS
  1328750 *** EVENT: Cntrl= 67419 (0x0001075b), Param= 0 (0x00000000) MASTER_CAUTION_SET
  1328750 *** EVENT: Cntrl= 67414 (0x00010756), Param= 0 (0x00000000) MASTER_WARNING_SET
  1328797 *** EVENT: Cntrl= 67412 (0x00010754), Param= 0 (0x00000000) SET_DECISION_HEIGHT
  1328797 *** EVENT: Cntrl= 67413 (0x00010755), Param= 0 (0x00000000) SET_DECISION_ALTITUDE_MSL
  1331875 #### ERROR: No SimConnect data seen for more than set stall time - will attempt to reconnect...
  1331875 **** SimConnect Data Stalled! Re-connecting now ... ****
  1332187 SimConnect_Open succeeded
  1332203 Running in "KittyHawk", Version: 11.0.282174.999 (SimConnect: 11.0.62651.3)
  1332203 MSFS version = 11.0.282174.999
  1332203 Initialising SimConnect data requests now
  1332203 Mapping custom control numbers 69632 - 84232
  1332203 Maximum number of custom events available is 1024 (defined by ini parameter MaxNumberOfCustomEvents)
  1332203 User Aircraft ID 1 supplied, now being used
  1332234 C:\USERS\KKLOS\APPDATA\LOCAL\PACKAGES\MICROSOFT.FLIGHTSIMULATOR_8WEKYB3D8BBWE\LOCALSTATE\MISSIONS\CUSTOM\CUSTOMFLIGHT\CUSTOMFLIGHT.PLN
  1332234 SimObjects\Airplanes\Asobo_DA62\aircraft.CFG
  1332297 User Aircraft ID 1 supplied, now being used
  1332297 C:\USERS\KKLOS\APPDATA\LOCAL\PACKAGES\MICROSOFT.FLIGHTSIMULATOR_8WEKYB3D8BBWE\LOCALSTATE\MISSIONS\CUSTOM\CUSTOMFLIGHT\CUSTOMFLIGHT.PLN
  1332437 *** EVENT: Cntrl= 65568 (0x00010020), Param= 0 (0x00000000) HEADING_GYRO_SET
  1332437 *** EVENT: Cntrl= 67419 (0x0001075b), Param= 1 (0x00000001) MASTER_CAUTION_SET
  1332437 *** EVENT: Cntrl= 67419 (0x0001075b), Param= 1 (0x00000001) MASTER_CAUTION_SET
  1332437 *** EVENT: Cntrl= 67315 (0x000106f3), Param= 0 (0x00000000) XPNDR_IDENT_OFF
  1332500 *** EVENT: Cntrl= 67315 (0x000106f3), Param= 0 (0x00000000) XPNDR_IDENT_OFF
  1332703 *** EVENT: Cntrl= 67315 (0x000106f3), Param= 0 (0x00000000) XPNDR_IDENT_OFF
  1332812 System time = 01/03/2023 10:28:21, Simulator time = 10:28:13 (15:28Z)

1898109 *** EVENT: Cntrl= 65814 (0x00010116), Param= 0 (0x00000000) AP_APR_HOLD_OFF
  1898109 *** EVENT: Cntrl= 65813 (0x00010115), Param= 0 (0x00000000) AP_LOC_HOLD_OFF
  1898109 *** EVENT: Cntrl= 65811 (0x00010113), Param= 0 (0x00000000) AP_NAV1_HOLD_ON
  1898109 *** EVENT: Cntrl= 65814 (0x00010116), Param= 0 (0x00000000) AP_APR_HOLD_OFF
  1898109 *** EVENT: Cntrl= 65813 (0x00010115), Param= 0 (0x00000000) AP_LOC_HOLD_OFF
  1898109 *** EVENT: Cntrl= 65811 (0x00010113), Param= 0 (0x00000000) AP_NAV1_HOLD_ON
  1898109 *** EVENT: Cntrl= 65814 (0x00010116), Param= 0 (0x00000000) AP_APR_HOLD_OFF
  1898109 *** EVENT: Cntrl= 65813 (0x00010115), Param= 0 (0x00000000) AP_LOC_HOLD_OFF
  1898109 *** EVENT: Cntrl= 65811 (0x00010113), Param= 0 (0x00000000) AP_NAV1_HOLD_ON
  1898109 *** EVENT: Cntrl= 65814 (0x00010116), Param= 0 (0x00000000) AP_APR_HOLD_OFF
  1898109 *** EVENT: Cntrl= 65813 (0x00010115), Param= 0 (0x00000000) AP_LOC_HOLD_OFF
  1898109 *** EVENT: Cntrl= 65811 (0x00010113), Param= 0 (0x00000000) AP_NAV1_HOLD_ON
  1898109 *** EVENT: Cntrl= 66103 (0x00010237), Param= 0 (0x00000000) AP_PANEL_ALTITUDE_ON
  1899031 *** EVENT: Cntrl= 65568 (0x00010020), Param= 0 (0x00000000) HEADING_GYRO_SET
  1902062 *** EVENT: Cntrl= 65568 (0x00010020), Param= 0 (0x00000000) HEADING_GYRO_SET
  1902062 WRITE0[14808]  07E8,   4 bytes: 00 00 00 00                                      ....

 

 

[Kklosterman]

Reinstalled the FSRADIOPLANEL with updated navigation download. Ran this time with the plane listed in log took off from KCVG to KIND with nav turned on but the controls with NAV didn't keep the plane in that direction.

The ALT was set and that was not maintaining the correct ALT.

Went back into the cockpit mode and changed from FLT PLAN to Direct to KIND and it allowed the plane to head to indy. but the alt was still way off.

This sounds like their issue but wanted to find out how to explain to that vendor what is not coming correctly into your log file.

Again Thanks for any assist.

FSUIPC7.log

[John Dowson]

Can you please also attach your FSUIPC7.ini file (although your panel isn't assigned in FSUIPC). Also please disable logging for Axes Controls - you only need Event logging activated, and the axes events are just noise in the log file for this issue. Keep IPC Write logging activated, as it looks like the FsPanelServer is writing to offsets to control things. I will check the offsets that it is using to see if these are writeable and working in MSFS, but a cleaner log file (without axes logging) would help. I will look into this further tomorrow.

John

 

[Kklosterman]

I am referencing a youtube that I did along with this flight to show the different screens and referencing the event on the left of the log.

I ended this flight in the air by ESC and going to main menu and then desktop.

NOTE: for some reason the NAV controlling the direction is working for some reason "this flight" , but the ALT and V/S are a little wonky.

Thank you so much for your feedback. 

Ken

FSUIPC7.ini

FSUIPC7.log

[John Dowson]

Hi Ken,

so it seems that the only thing not working correctly is the AP altitude hold. This is set with the write to offset 07D4, and only occurs in two places in your log:

Quote

...
   488594 WRITE0[10320]  07D4,   4 bytes: 7D 3B 80 02  
   488609 *** EVENT: Cntrl= 66124 (0x0001024c), Param= 2100 (0x00000834) AP_ALT_VAR_SET_ENGLISH
...
   519453 WRITE0[10320]  07D4,   4 bytes: A6 97 55 03
   519453 *** EVENT: Cntrl= 66124 (0x0001024c), Param= 2800 (0x00000af0) AP_ALT_VAR_SET_ENGLISH
 

This is why the altitude is being held at 2800, not at 2000 as the panel shows, so it looks like it is out of sync. Rather than just switching alt hold on/off, maybe try changing the value to see if it then syncs correctly with the FS (turn off, change value, turn on). However, note that the comment on 07D4 (in the FSUIPC7 Offset Status document) says this:
    Autopilot constrained altitude value (limited by Flight Plan and flight profile as in SID), as metres*65536. Also see offset 0x0798 for target altitude value
So maybe this value is being constrained by the flight plan? You can try logging both offsets 07D4 and 0798 using FSUIPC's offset logging facility (Log->Offsets, log as U32 and check Display to - Normal log file) to see what they are holding, although you will need to divide the logged value by 65536 to get the displayed value in meters. This would show you what the target value and constrained value is as held by the FS, and not what the radio panel is displaying - but hopefully at least one should match!

But there certainly doesn't seem to be any issues with FSUIPC. Maybe fsRadioPanel should be using the target altitude offset and not the constrained one, but I am not sure. I am by no means an expert in AP systems - you would be better of asking about this on the avsim forums,  or using the fsRadioPanel support.

For the vertical speed, this is using offset 07F2 which has the following comment:
    Autopilot vertical speed value, as ft/min: Write reported as working but only after sending an AP VS SET control (only once)  

No AP VS SET control is being sent, so maybe this could be why this isn't working, and would (probably) need an update to fsRadioPanel to fix. However, as the target altitude is set at 2800 (and not 2000), which is basically the altitude you are flying at, the VS will be ignored anyway as you are at the target altitude - according to the FS, not the display panel.

John

 

 

[Kklosterman]

John,

Thanks so much for taking the time to look at this. Let me study and chew on this for a while and let you know what I found. 

Your support is Great.

Ken.

[Kklosterman]

Hi John,

Still trying some things to see about narrowing this down.

I downloaded another APP from the windows store called XCockpit. And it has issues also communicating . It allows heading to be entered on the app, and that seems to work. But When entering ALT and or V/S  It operated a little different then the FsPanelServer program. If I enter a new ALT like currently running a real ALT of say 19000 and then entering 15000. It doesn't got to 15000 by itself. But then switching over to the v/s and changing to -1500 in that field and toggling to use v/s, the plane starts declining by -1500 and  then when the plane reaches 15000 in real ALT it toggles back to ALT and the plane stays at that alt. And the entered -1500 in the V/s field goes to 000. So this is different then how the FsPanelServer did the adjustment.   I contacted this programmer and he said his software is relatively new. Doesn't have a manual yet, and He said that it is very difficult to get all the planes to work correctly. But he will get back with me after testing the cessna jet I used for the test.  BTW his software cost was like $1.50 so I am not holding my breath that he will have a lot of answers. But we will see. I was just trying to see if there was any common denominator and all of this.   

I can't believe that the sim software can be so picky. This all used to work so well and then Microsoft (in my opinion) changes something and things go crazy.

So in answer, this can be closed on your end and I will just keep experimenting on my end.  Also note your program is super with all that you have put into it. And with all the diagnostic things it can do. Logs etc. I don't fault your support or anything like that. I am going to save this post on my pc and refer back to it, but to be honest, my lack of aircraft terms and how a regular plane is supposed to work, I am overwhelmed with understanding your explanation yet.  That is why I am still chewing on this LOL   It's hell being 73 years old 🙂