Jump to content
The simFlight Network Forums
oldpop

loss of X55 throttle

Recommended Posts

I've checked, and in fact the logging I need is already in place. It logs the results from the actual polling of the joysticks, at first and then whenever they change. It will make a BIG log, especially with your working device in place, so please, not only keep the session short (though not so short you don't get to operate buttons or move levers when the sim is ready to fly), then ZIP it up and send it to me at petedowson@btconnect.com.

To get this logging as well as the earlier stuff, change the LogExtras line n the INI to

LogExtras=x201000

Please don't forget to remove the extra copies of the two added lines.

Oh, and to keep the log size down, it might be best to temporarily disconnect the working devices. Otherwise I'll have to add an INI parameter to select which devices to log.

[LATER]

Another thing I now realise: you have no assignments to the axes or buttons in question. I sort of assumed you were carrying over an INI file from an earlier install. 

FSUIPC does NOT scan devices where there's no need because no assignments, so the new logging I'm asking for will ONLY occur whilst in the Axis or Button assignments dialog. So you can keep the session and log shorter by keeping those visits short.

Thanks,
Pete

 

Share this post


Link to post
Share on other sites

Did you send me a log by email, from someone called "Ron" (you NEVER seem to sign your posts here so I've no idea who you are or where the email is from)?

Pete

 

 

Share this post


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

yes that's me! Ron or Pop

Okay. In that case, here's what your log clearly shows:

Your stick is working, and as you have two button assignments to that it is being scanned all of the time, even when you are not in the FSUIPC Options for Axes or Buttons. That fills up most of the log. The rudder isn't assigned so that doesn't appear except when you enter the options.

After you entered the Buttons assignment dialogue, all possible joystick numbers were scanned (I must fix that -- it should only scan those detected before hand -- i.e. in your case 0, 1, and 2, the Stick, Throttle and Rudder.  Oddly, 3 gave a valid response too, but I think that must be a fluke. it gave an error later. Here's an extract showing valid responses for 0-3:

   153218 *** Entered Buttons option page ***
   153218 Read joy 0, Buttons=x00000000, POV=-1
   153218     Axes: X=33444,Y=32524,Z=0,R=0,U=0,V=32751
   153218           S=0,T=0,P=-1,Q=-1,M=-1,N=-1
   153218 Read joy 1, Buttons=x00000000, POV=-1
   153218     Axes: X=0,Y=0,Z=0,R=0,U=0,V=0
   153218           S=0,T=0,P=-1,Q=-1,M=-1,N=-1
   153218 Read joy 2, Buttons=x00000000, POV=-1
   153218     Axes: X=0,Y=0,Z=0,R=0,U=0,V=32383
   153218           S=0,T=0,P=-1,Q=-1,M=-1,N=-1
   153218 Read joy 3, Buttons=x00000000, POV=-1
   153218     Axes: X=0,Y=0,Z=0,R=0,U=0,V=0
   153218           S=0,T=0,P=-1,Q=-1,M=-1,N=-1

You see the X, Y values for the Stick (Joy 0), near max. Those values wobble a bit, typical jitter probably ignored by FSUIPC with the default Delta value left set.

The readout for Joy 1 is basically a default. But it is most certainly coming from the device (or rather from DirectInput and the device's driver). 

Here, Joy 2, the rudder, has an interesting non-default value for the V axis (probably not used), but otherwise the input from that seems stable at zero. 

Oddly, though you were supposed to be checking the buttons on the Throttle, you pressed buttons on the Stick instead:

   159640 FirstButtonChange res=00000008 (0.0, 8)
   159656 Read joy 0, Buttons=x00000100, POV=-1
   159656     Axes: X=31852,Y=32206,Z=0,R=0,U=0,V=32751
   159656           S=0,T=0,P=-1,Q=-1,M=-1,N=-1

Later the same again for buttons 8, 6, 7, 8, 12, 10, 13, 11, 4, 12, in that order. Surely you saw these coming up in the dialogue, for your stick? Did you actually press any buttons on the throttle? 

Then, at about 235 seconds (3m 55s) into the session, something wierd started happening. Your X-55 devices were disconnecting themselves (unless you did it), or losing power. This happened with both Stick and Throttle. maybe this is when you pressed buttons on the Throttle, precipitating the problems?

   235156 *** JOY ERROR: GetDeviceState for Joy #0 returned 'Input Lost'
   235156 *** JOY ERROR: GetDeviceState for Joy #1 returned 'Input Lost'
   235156 Read joy 2, Buttons=x00000000, POV=-1
   235156     Axes: X=0,Y=0,Z=0,R=0,U=0,V=32383
   235156           S=0,T=0,P=-1,Q=-1,M=-1,N=-1
   235156 Read joy 3, Buttons=x00000000, POV=-1
   235156     Axes: X=0,Y=0,Z=0,R=0,U=0,V=0
   235156           S=0,T=0,P=-1,Q=-1,M=-1,N=-1
   235156 *** JOY ERROR: Poll for Joy #0 returned 'Input Lost'
   235156 *** JOY ERROR: GetDeviceState for Joy #0 returned 'Input Lost'
   235156 *** JOY ERROR: Poll for Joy #1 returned 'Input Lost'
   235156 *** JOY ERROR: GetDeviceState for Joy #1 returned 'Input Lost'

Interestingly the Rudder and the mysterious Joy 3 continued okay.

This went on for a great portion of the log until 238 seconds (only 3 seconds, but a lot of log!) when another USB device was added!

   238093 ***** A device has been attached!
   238093 ***** HID USB device reconnected: re-initialising FSUIPC connections
   238093 #### Initialising Dlrectinput Axis Scanning ...
   238093 EnumDevices: 0.GUID={B15E4040-937C-11E5-8002-444553540000}
   238093 EnumDevices: 1.GUID={B160B140-937C-11E5-8006-444553540000}
   238109 EnumDevices: 2.GUID={B15E4040-937C-11E5-8001-444553540000}
   238109 EnumDevices: 3.GUID={3C3B5D00-9DAB-11E5-8001-444553540000}

A "real" device 3 after all! Not the ghost scanned earlier. And see what this turned out to be:

   238125    Joy#3: Finding name in "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_068E&PID_C010\"
   238125    Joy#3: OEMName = "CH Control Manager Device 1"
   238125    Joy#3: GUID = {3C3B5D00-9DAB-11E5-8001-444553540000}

Now what is that for? Why are you running the CH control Manager at all? Maybe this is the cause of all the problems?

It not only did this, but appeared to reconnect the device many more times (over 6, I lost count), and in the process also got the Stick moved to device 4!

Not only that, but subsequently Joy 3 stopped returning any values, even though as a "ghost" device it did!

So, conclusions:

1. Uninstall CH Control manager and re-test.
2. It looks possible that the USB port for your X-55's, and especially the Throttle, is playing up. Try moving them. If using a hub try plugging them direct into the PC.

As far as I can see, apart from the excessive scanning (all 16 initially), FSUIPC is doing everything right.

Pete


 


 

 

Share this post


Link to post
Share on other sites

I've been analysing the Registry exports you sent and trying to relate them to the last FSUIPC log I got from you, the only with the Extra logging.

They don't match. There is no way that log is from the same machine, or in the same situation (i.e. no removals or reinstalls of the X-55 between) as the registry exports.

Background

If you refer to the top (pinned) thread in this Forum, you will see that I now have this sort of information from Paul Henty, one of the many successfully running an X-55 system with FSUIPC 4.966c. Comparing his registry with yours I was hoping to find the problem, assuming it it registry rather than hardware or connections.

First off, oddly, for both Throttle and Stick, there are two entries each. On Paul's system the Stick pair both have the same GUIDs -- which should be impossible! However, only one has a Joystick ID, and that, the first, is the one FSUIPC chooses.  For the Throttle the two have different GUIDs, and again onl the first has a Joystick ID. FSUIPC chooses that.

When FSUIPC knows that there are 2 devices it will be looking for the details for the second. but in these cases there's only one, and FSUIPC therefore assumes there's only one entry and chooses the first. I suspect that through some error during installation the Throttle using on your system is actually using the second.

However, without further analysis on your setup I can't progress that further and work out what to do.

Action Please

So, please can you do this:

1. Make sure you still have
Debug=Please
LogExtras=x200000 

in the [General] section of the FSUIPC4.INI

2. Run the Sim till ready to fly, then close it.

3. Repeat the Registry export process to get two .reg files and rename them to .txt.

4. ZIP the 3 files together and send to me again.

This will make sure everything tallies.

Thanks,
Pete

 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...

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.