Jump to content
The simFlight Network Forums
Scotfleiger

FSUIPC5 - LINDA Interface Changes

Recommended Posts

3 minutes ago, Scotfleiger said:

I have my throttle, prop and mixture and rudder axes assigned but not calibrated in FSUIPC5.

Assigned "direct" or via FS axis controls?

Does the problem still occur if you remove the Axis assignments (temporarily) from the INI file?

Pete

 

Share this post


Link to post
Share on other sites

Morning Pete. I know I wasn't real clear and may have mis spoke about the axis stuff. I have the axies assigned in p3d. Then I only calibrated in fsuipc checking filter on every axis I calibrated. I will in check the filter option and try again. Then I will try the updated 5101e

Share this post


Link to post
Share on other sites

here is my ini file you requested. I tried a couple things. I unplugged my Saitek throttle quadrant and cleared the spoiler and flap calibration in fsuipc just to see if the spoiler axis was causing the issue. Still errors. Then I plugged the Saitek quadrant back in recalibrated in fsuipc and unchecking all filter boxes in the profile specific calibration tab in fsuipc. still errors. Now going to try 5101e

FSUIPC5.ini

FSUIPC5.log

Share this post


Link to post
Share on other sites

Hi Pete

As promised please find linked below the test plugin you wanted. Unzip and place the 2 files (ipcready.lua and fsuipc5_test.lua) in the \modules folder. The plugin displays a message and an ALT count. Monitoring the AP display you will see the ALT/SPD/HDG/VS/CRS change (as selected) and the buttons flash. The plugin triggers the fault within 20 secs.

FSCUIP5_test_plugin

Share this post


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

Assigned "direct" or via FS axis controls?

Does the problem still occur if you remove the Axis assignments (temporarily) from the INI file?

Hi Pete, sorry I missed your question while working on the test plugin. My axes are 'send direct to FSUIPC calibration'.

Also only one of my Saitek Throttle Quadrants is being recognised by FSUIPC5 - today the throttle detected has changed. You may have thought you had fixed this. Unfortunately not.

Share this post


Link to post
Share on other sites
12 minutes ago, Scotfleiger said:

Also only one of my Saitek Throttle Quadrants is being recognised by FSUIPC5 - today the throttle detected has changed. You may have thought you had fixed this. Unfortunately not.

With which versdion of FSUIPC5? ALL of the feedback on the recent updates confirm it is fixed. If something is still wrong with 5.101d or 5.101e I most certainly need a log and other details from you, most urgently as I've crossed that problem off  --  it also affected 4.967 which uses the same code, and I was about to release 4.968 as a fix for FSX/P3D3!.

Make sure you have FSUIPC5101e_TEST.zip installed, and then add these lines to the [General] section of the FSUIPC5.INI file:

Debug=Please
LogExtras=x200000

and please show me the Log file after plus your FSIPC5.INI and the FSUIPC.JoyScan.csv file.

I'm afraid this is more important than the offset writing problems at present.

Pete

 

Share this post


Link to post
Share on other sites
6 minutes ago, Scotfleiger said:

I ran FSUIPC5 5101e and it found both throttle quadrants

So you were using an older version earlier, before the fix, mainly in 5.101a?

I judt tried to induce the offset writing problem with oyur plug-in. I'm afraid it STILL won't go wring here. I initially started with ipcWrites and Even logging enabled. I have this at the start:

   342001 LUA.1: FSUIPC5_test - started...
   342064 WRITElua 0C4E,   2 bytes: 54 01                                            T.
   342126 *** EVENT: Cntrl= 65716 (0x000100b4), Param= 340 (0x00000154) VOR1_SET
   342142 LUA.1: FSUIPC5_Test :: CRS = 340
   342157 WRITElua 07CC,   2 bytes: 00 00                                            ..
   342157 LUA.1: FSUIPC5_Test :: HDG = 0
   342189 WRITElua 07D4,   4 bytes: 00 00 00 00                                      ....
   342189 LUA.1: FSUIPC5_Test :: ALT = 0
   342220 WRITElua 07E2,   2 bytes: 00 00                                            ..
   342220 LUA.1: FSUIPC5_Test :: SPD = 0
   342220 *** EVENT: Cntrl= 66037 (0x000101f5), Param= 0 (0x00000000) AP_SPD_VAR_SET
   342220 WRITElua 07F2,   2 bytes: 00 00                                            ..
   342220 LUA.1: FSUIPC5_Test :: VS  = 0
   342251 WRITElua 0C4E,   2 bytes: 55 01                                            U.
   342251 *** EVENT: Cntrl= 65716 (0x000100b4), Param= 341 (0x00000155) VOR1_SET
   342267 WRITElua 07CC,   2 bytes: B6 00                                            ..
   342267 *** EVENT: Cntrl= 66042 (0x000101fa), Param= 1 (0x00000001) HEADING_BUG_SET
   342267 WRITElua 07D4,   4 bytes: 70 3D 0F 00                                      p=..
   342267 *** EVENT: Cntrl= 66124 (0x0001024c), Param= 49 (0x00000031) AP_ALT_VAR_SET_ENGLISH
   342298 WRITElua 07E2,   2 bytes: 01 00                                            ..
   342298 *** EVENT: Cntrl= 66037 (0x000101f5), Param= 1 (0x00000001) AP_SPD_VAR_SET

and then in case it was affecting the timing, I turned off those logging options, here, nearly 3 minutes later (172 seconds):

   494633 LUA.1: FSUIPC5_test -- AP buttons 0
   494633 *** EVENT: Cntrl= 65580 (0x0001002c), Param= 0 (0x00000000) AP_MASTER
   494633 *** EVENT: Cntrl= 66107 (0x0001023b), Param= 0 (0x00000000) AP_PANEL_HEADING_OFF
   494633 *** EVENT: Cntrl= 65819 (0x0001011b), Param= 0 (0x00000000) AP_NAV1_HOLD_OFF
   494633 *** EVENT: Cntrl= 66113 (0x00010241), Param= 0 (0x00000000) AP_PANEL_SPEED_OFF
   494633 *** EVENT: Cntrl= 66104 (0x00010238), Param= 0 (0x00000000) AP_PANEL_ALTITUDE_OFF
   494633 *** EVENT: Cntrl= 66116 (0x00010244), Param= 0 (0x00000000) AP_PANEL_VS_OFF
   494633 *** EVENT: Cntrl= 65814 (0x00010116), Param= 0 (0x00000000) AP_APR_HOLD_OFF
   494633 *** EVENT: Cntrl= 65813 (0x00010115), Param= 0 (0x00000000) AP_LOC_HOLD_OFF
   494633 *** EVENT: Cntrl= 65818 (0x0001011a), Param= 0 (0x00000000) AP_BC_HOLD_OFF
   494648 *** EVENT: Cntrl= 65716 (0x000100b4), Param= 150 (0x00000096) VOR1_SET
   494648 LUA.1: FSUIPC5_Test :: CRS = 150
   494648 LUA.1: FSUIPC5_Test :: HDG = 170
   494648 LUA.1: FSUIPC5_Test :: ALT = 3050
   494648 *** EVENT: Cntrl= 66037 (0x000101f5), Param= 28 (0x0000001c) AP_SPD_VAR_SET
   494648 LUA.1: FSUIPC5_Test :: SPD = 28
   494648 LUA.1: FSUIPC5_Test :: VS  = -50
   494664 LUA.1: FSUIPC5_test -- AP buttons 1
   494664 LUA.1: FSUIPC5_test -- AP buttons 0
   494680 LUA.1: FSUIPC5_Test :: CRS = 151
   494680 LUA.1: FSUIPC5_Test :: HDG = 171
   494680 LUA.1: FSUIPC5_Test :: ALT = 3100
   494680 LUA.1: FSUIPC5_Test :: SPD = 29
   494680 LUA.1: FSUIPC5_Test :: VS  = -40
   494695 LUA.1: FSUIPC5_test -- AP buttons 1
   494695 LUA.1: FSUIPC5_test -- AP buttons 0

I let this carry on till here:

   592757 LUA.1: FSUIPC5_test -- AP buttons 1
   592867 LUA.1: FSUIPC5_test -- AP buttons 0
   593085 LUA.1: FSUIPC5_Test :: CRS = 164
   593116 LUA.1: FSUIPC5_Test :: HDG = 184
   593147 LUA.1: FSUIPC5_Test :: ALT = 9300
   593147 LUA.1: FSUIPC5_Test :: SPD = 151
   593179 LUA.1: FSUIPC5_Test :: VS  = 900
   593272 LUA.1: FSUIPC5_test -- AP buttons 1
   593397 LUA.1: FSUIPC5_test -- AP buttons 0
   593600 LUA.1: FSUIPC5_Test :: CRS = 165
   593631 LUA.1: FSUIPC5_Test :: HDG = 185
   593678 LUA.1: FSUIPC5_Test :: ALT = 9400
   593709 LUA.1: FSUIPC5_Test :: SPD = 152
   593740 LUA.1: FSUIPC5_Test :: VS  = -900

So, it was running fine, no errors, for a full 251 seconds with no problems. Over 4 minutes. Do I need to run it for longer?

I think something else it doing on here. I'm testing on Win7 as all my debugging tools are here, but I'll now conduct a similar test on Win10.

Pete

 

 

Share this post


Link to post
Share on other sites
11 minutes ago, pcssundahl said:

I tried 5101e and still issue remains. here is the log file with the 3 logging options on.

Odd that I cannot make it happen here, with both your apps nor with the plug-in from Scotfleiger.

Pete

 

Share this post


Link to post
Share on other sites
3 minutes ago, pcssundahl said:

hmmmm. im on windows 8.1 no idea if that helps

I can't test on that, never had it.

Pete

 

Share this post


Link to post
Share on other sites

Hi Pete

That would suggest that is an interaction between FSUIPC5 and LINDA (and other Addons) combined with the offset writes that is causing the problem. I will do a 'bare' installation test.

You may like to try my latest beta build 633 (see link). Installation is to drill down to the modules folder and copy the folder contents into your modules folder. I have modified the ipcReady.lua file to start LINDA and the FSUIPC5_test.lua plugin.

LINDA 3.0.0 beta build 633 - For testing purposes only.

Share this post


Link to post
Share on other sites
8 minutes ago, pcssundahl said:

I tried 5101e and still issue remains. here is the log file with the 3 logging options on.

I see from the log that it was okay for 194 seconds -- over 3 minutes. Maybe I aborted the previous test I was doing too early.

I notice from your log that there are lots and lots of axis movements before it started going wrong. Rudder and Elevator. Does it need this happening to make it go wrong? 

2 minutes ago, Scotfleiger said:

You may like to try my latest beta build 633 (see link). Installation is to drill down to the modules folder and copy the folder contents into your modules folder. I have modified the ipcReady.lua file to start LINDA and the FSUIPC5_test.lua plugin.

Okay, will try that first on Win7.

Pete

 

Share this post


Link to post
Share on other sites

The axis movements were me moving the yoke out of view so I could see various switches on the instrument panel. I also probably had my feet on the rudder pedals - my footrests.

Share this post


Link to post
Share on other sites
17 minutes ago, Scotfleiger said:

You may like to try my latest beta build 633 (see link). Installation is to drill down to the modules folder and copy the folder contents into your modules folder. I have modified the ipcReady.lua file to start LINDA and the FSUIPC5_test.lua plugin.

How long do I need to let it run? It's been going 750 seconds now (over 12 minutes) with no sign of any errors! :-(

Win10 next ...

Pete

 

Share this post


Link to post
Share on other sites
23 minutes ago, Pete Dowson said:

I see from the log that it was okay for 194 seconds -- over 3 minutes. Maybe I aborted the previous test I was doing too early.

I notice from your log that there are lots and lots of axis movements before it started going wrong. Rudder and Elevator. Does it need this happening to make it go wrong? 

Pete

 

To answer about the axis movements- maybe I believe that is from my axis being a few years old and maybe a bit dirty (One of thr reasons FSUIPC is GREAT it smooths out most of that)

 

PS - even though I downloaded your 5101e zip the log still says 5101d. I double checked

Share this post


Link to post
Share on other sites
7 minutes ago, pcssundahl said:

even though I downloaded your 5101e zip the log still says 5101d. I double checked

Yes, my error. Don't worry. The difference is only in the JoyLetters assignments, a minor change.

Pete

 

Share this post


Link to post
Share on other sites
15 minutes ago, Scotfleiger said:

Strange. With Win10 and no LINDA running or present the error exception appears in less than a minute.

Strange indeed!

BUT I think I now have a clue about that.

I've managed to repro it, but ONLY WITH A RELEASE VERSION! Of course, for testing I need to use a Debug version, because that way I can set breakpoints and do tracing and so on.  So I never tried with the compiled test version!!!

Now it gets difficult. I have to work out what actual code difference is doing it!

Pete

 

 

Share this post


Link to post
Share on other sites

Reproduction of a fault is the essential starting point. I was having the same problem over the weekend with I first reported I could not connect to FSUIPC5 on my working system as P3Dv4 won't run on my development system (no DirectX11). Good luck.

Share this post


Link to post
Share on other sites
5 hours ago, Scotfleiger said:

Reproduction of a fault is the essential starting point.

Well , I could reproduce it with a release-compiled version, but not the debug-compiled version, which is worrying. And because I had little access to proper debugging facilities then it took a while to narrow down, mainly using logging in narrower and narrower areas.

I found that a flag I was testing was somehow being set. I though this must be because it was being trampled on by something, so I moved it somewhere else completely, to no avail.

I reprogrammed what the flag was being used for, and now it all works okay. But I am a little worried that I've simply hidden another problem by doing this.

More checks tomorrow.

Pete

 

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

×

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.