Author Topic: Joystick issues and occasional AH error (Read 950 times)

Dragon · « **on:** October 05, 2011, 09:27:34 PM »

My X-52 occasionally just decides to turn left. I've had issues in the past but replacing the cord and checking connections helped.
I've calibrated in winblows and AH and all looks good.
If pushing right fixed it I think I could live with it, but it doesn't help and the stick stays turned left till it wants to behave.
Mode 1 and mode 2 both do the same thing. I know I should get a powered USB hub so shush.
Tonight ended with me running from a 14k fight with Deke in a KI and after initial merge, I left tuned and plummeted to @2k before regaining control, ran to base, landed, upped a wirble, got in turret and as it started left turning, AH folded. UGH!

DX in case it helps:

------------------
System Information
------------------
Time of this report: 10/5/2011, 21:49:56
   Machine name: DRAGON-PC
   Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.110622-1506)
   Language: English (Regional Setting: English)
System Manufacturer: System manufacturer
   System Model: System Product Name
   BIOS: Phoenix - AwardBIOS v6.00PG
   Processor: Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz (2 CPUs), ~2.7GHz
   Memory: 2048MB RAM
Available OS Memory: 2046MB RAM
   Page File: 1215MB used, 2877MB available
   Windows Dir: C:\Windows
   DirectX Version: DirectX 11
DX Setup Parameters: Not found
   User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
   DWM DPI Scaling: Disabled
   DxDiag Version: 6.01.7601.17514 64bit Unicode

------------
DxDiag Notes
------------
   Display Tab 1: No problems found.
   Sound Tab 1: No problems found.
   Sound Tab 2: No problems found.
   Sound Tab 3: No problems found.
   Input Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D: 0/4 (retail)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)

---------------
Display Devices
---------------
   Card name: NVIDIA GeForce 9800 GTX/9800 GTX+
   Manufacturer: NVIDIA
   Chip type: GeForce 9800 GTX/9800 GTX+
   DAC type: Integrated RAMDAC
   Device Key: Enum\PCI\VEN_10DE&DEV_0612&SUBSYS_0BB719F1&REV_A2
   Display Memory: 1776 MB
   Dedicated Memory: 1009 MB
   Shared Memory: 767 MB
   Current Mode: 1680 x 1050 (32 bit) (60Hz)
   Monitor Name: SyncMaster 226BW(Digital)
   Monitor Model: SyncMaster
   Monitor Id: SAM027F
   Native Mode: 1680 x 1050(p) (59.883Hz)
   Output Type: DVI
   Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Driver File Version: 8.17.0012.6658 (English)
   Driver Version: 8.17.12.6658
   DDI Version: 10
   Driver Model: WDDM 1.1
  Driver Attributes: Final Retail
   Driver Date/Size: 1/7/2011 23:27:00, 12859496 bytes
   WHQL Logo'd: Yes
   WHQL Date Stamp:
  Device Identifier: {D7B71E3E-4552-11CF-4360-BB2B1CC2C535}
   Vendor ID: 0x10DE
   Device ID: 0x0612
   SubSys ID: 0x0BB719F1
   Revision ID: 0x00A2
Driver Strong Name: oem4.inf:NVIDIA_SetA_Devices.NTamd64.6 .1:Section005:8.17.12.6658:pci\ven_10de&dev_0612
   Rank Of Driver: 00E62001
   Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C
   Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
   {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
   {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0)


   D3D9 Overlay: Supported
   DXVA-HD: Supported
   DDraw Status: Enabled
   D3D Status: Enabled
   AGP Status: Enabled

-------------
Sound Devices
-------------
   Description: Speakers (High Definition Audio Device)
Default Sound Playback: Yes
Default Voice Playback: Yes
   Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0883&SUBSYS_10438249&REV_1000
   Manufacturer ID: 1
   Product ID: 65535
   Type: WDM
   Driver Name: HdAudio.sys
   Driver Version: 6.01.7601.17514 (English)
   Driver Attributes: Final Retail
   WHQL Logo'd: Yes
   Date and Size: 11/20/2010 06:44:23, 350208 bytes
   Other Files:
   Driver Provider: Microsoft
   HW Accel Level: Basic
   Cap Flags: 0xF1F
   Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
Static/Strm HW 3D Bufs: 0, 0
   HW Memory: 0
   Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
   I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No

   Description: Digital Audio (S/PDIF) (High Definition Audio Device)
Default Sound Playback: No
Default Voice Playback: No
   Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0883&SUBSYS_10438249&REV_1000
   Manufacturer ID: 1
   Product ID: 65535
   Type: WDM
   Driver Name: HdAudio.sys
   Driver Version: 6.01.7601.17514 (English)
   Driver Attributes: Final Retail
   WHQL Logo'd: Yes
   Date and Size: 11/20/2010 06:44:23, 350208 bytes
   Other Files:
   Driver Provider: Microsoft
   HW Accel Level: Basic
   Cap Flags: 0xF1F
   Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
Static/Strm HW 3D Bufs: 0, 0
   HW Memory: 0
   Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
   I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No

   Description: Headphones (High Definition Audio Device)
Default Sound Playback: No
Default Voice Playback: No
   Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0883&SUBSYS_10438249&REV_1000
   Manufacturer ID: 1
   Product ID: 65535
   Type: WDM
   Driver Name: HdAudio.sys
   Driver Version: 6.01.7601.17514 (English)
   Driver Attributes: Final Retail
   WHQL Logo'd: Yes
   Date and Size: 11/20/2010 06:44:23, 350208 bytes
   Other Files:
   Driver Provider: Microsoft
   HW Accel Level: Basic
   Cap Flags: 0xF1F
   Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
Static/Strm HW 3D Bufs: 0, 0
   HW Memory: 0
   Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
   I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No

---------------------
Sound Capture Devices
---------------------
   Description: Microphone (High Definition Audio Device)
  Default Sound Capture: Yes
  Default Voice Capture: Yes
   Driver Name: HdAudio.sys
   Driver Version: 6.01.7601.17514 (English)
   Driver Attributes: Final Retail
   Date and Size: 11/20/2010 06:44:23, 350208 bytes
   Cap Flags: 0x1
   Format Flags: 0xFFFFF

   Description: Microphone (High Definition Audio Device)
  Default Sound Capture: No
  Default Voice Capture: No
   Driver Name: HdAudio.sys
   Driver Version: 6.01.7601.17514 (English)
   Driver Attributes: Final Retail
   Date and Size: 11/20/2010 06:44:23, 350208 bytes
   Cap Flags: 0x1
   Format Flags: 0xFFFFF

---

Dragon · « **Reply #1 on:** October 05, 2011, 09:28:55 PM »

----------------
DirectInput Devices
-------------------
Device Name: Mouse
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a

Device Name: Keyboard
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a

Device Name: Micr
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x045E, 0x0745
FF Driver: n/a

Device Name: Micr
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x045E, 0x0745
FF Driver: n/a

Device Name: Micr
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x045E, 0x0745
FF Driver: n/a

Device Name: Micr
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x045E, 0x0745
FF Driver: n/a

Device Name: Micr
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x045E, 0x0745
FF Driver: n/a

Device Name: Saitek X52 Flight Control System
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x06A3, 0x075C
FF Driver: n/a

Device Name: Dell USB Keyboard
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x413C, 0x2010
FF Driver: n/a

Device Name: Dell USB Keyboard
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x413C, 0x2010
FF Driver: n/a

Device Name: Dell USB Keyboard
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x413C, 0x2010
FF Driver: n/a

Poll w/ Interrupt: No

-----------
USB Devices
-----------
+ USB Root Hub
| Vendor/Product ID: 0x10DE, 0x026D
| Matching Device ID: usb\root_hub
| Service: usbhub
| Driver: usbhub.sys, 3/24/2011 23:29:26, 343040 bytes
| Driver: usbd.sys, 3/24/2011 23:28:59, 7936 bytes
|
+-+ Generic USB Hub
| | Vendor/Product ID: 0x413C, 0x1003
| | Location: Port_#0002.Hub_#0001
| | Matching Device ID: usb\class_09
| | Service: usbhub
| | Driver: usbhub.sys, 3/24/2011 23:29:26, 343040 bytes
| |
+-+ Saitek X52 Flight Controller (USB)
| | Vendor/Product ID: 0x06A3, 0x075C
| | Location: Port_#0001.Hub_#0001
| | Matching Device ID: usb\vid_06a3&pid_075c
| | Service: HidUsb
| | OEMData: 00 00 00 00 22 00 00 00
| | Driver: hidusb.sys, 11/20/2010 06:43:49, 30208 bytes
| | Driver: hidclass.sys, 11/20/2010 06:43:49, 76800 bytes
| | Driver: hidparse.sys, 7/13/2009 20:06:17, 32896 bytes
| |
| +-+ Saitek X52 Flight Controller (HID)
| | | Vendor/Product ID: 0x06A3, 0x075C
| | | Matching Device ID: hid\vid_06a3&pid_075c
| | | Service: SaiH075C
| | | OEMData: 00 00 00 00 22 00 00 00
| | | Driver: SaiH075C.sys, 5/1/2007 17:10:50, 171144 bytes
| | | Driver: SaiD075C.pr0, 5/1/2007 17:10:50, 8252 bytes
| | | Driver: SaiC075C.Dll, 5/1/2007 17:10:50, 1046016 bytes
| | | Driver: SaiC075C_07.dll, 5/1/2007 17:10:50, 8192 bytes
| | | Driver: SaiC075C_09.dll, 5/1/2007 17:10:50, 7680 bytes
| | | Driver: SaiC075C_0A.dll, 5/1/2007 17:10:50, 8192 bytes
| | | Driver: SaiC075C_0C.dll, 5/1/2007 17:10:50, 8704 bytes
| | | Driver: SaiC075C_10.dll, 5/1/2007 17:10:50, 8192 bytes
| | | Driver: SaiC075C_11.dll, 5/1/2007 17:10:50, 5632 bytes
| | | Driver: SaiC075C_0402.dll, 5/1/2007 17:10:50, 7168 bytes

ebfd11 · « **Reply #2 on:** October 06, 2011, 12:16:40 AM »

I dont know it is helpful but you might want to try using an externaly powered USB hub and connect your joystick and keyboard to that.

BTW what power supply do you have???

Dragon · « **Reply #3 on:** October 06, 2011, 07:27:43 AM »

Its a CoolerMaster 850w, plenty of power for what I have.

gyrene81 · « **Reply #4 on:** October 06, 2011, 07:30:10 AM »

you're running windows 7 64bit with only 2gb of ram? i hope that paging file usage is not on a fresh boot.

what else do you have plugged into the usb ports besides keyboard, mouse and joystick? are you running any other programs beside ah when the issue(s) occur?

Skuzzy · « **Reply #5 on:** October 06, 2011, 08:50:38 AM »

2GB of system RAM is not a lot for Windows 7. You are easily running out of system RAM. Also noted you do not have the native sound card drivers loaded, but are using the default Microsoft supplied driver, which is really riddled with bugs.

morfiend · « **Reply #6 on:** October 06, 2011, 10:43:32 AM »

Dragon,

when you say turns left do you mean the rudder is deflecting or is the roll causing the issue?

I know the only problem I had with my X52 was with the rudder axis,it's not HID and uses a potentiomitor that have been known to go bad.Saitek has a driver fix,supposedly,but it never solved my sticks issue.

The issue was fixed by getting rudder pedals and eliminating the use of the twist rudder.

cohofly · « **Reply #7 on:** October 06, 2011, 10:57:23 AM »

Hmmmm X-52, Mine, bought in 2010 (early) had issues after only about 10 months of game play. The trigger would always fire when I pulled up. After trying all of the things that you did I finally decided to pull it apart one day. What a POC! What I discovered was a wire that had worn through the insulation at the base of the tube that runs through the entire stick portion. When I pulled back on the stick, The wire for Trigger 1 would ground itself on the metal tube, causing it to fire. The problem that you are having sounds somewhat similar. I decided to retire the stick as I didnt really like the way it handled, instead of return or fixing. (these are tiny aluminum wires) I am now using CH gear and am way happy with their products.

I dont know whether this will help or hinder
Good Luck
<S>
Carver

Dragon · « **Reply #8 on:** October 06, 2011, 12:45:00 PM »

Quote from: gyrene81 on October 06, 2011, 07:30:10 AM

you're running windows 7 64bit with only 2gb of ram? i hope that paging file usage is not on a fresh boot.

what else do you have plugged into the usb ports besides keyboard, mouse and joystick? are you running any other programs beside ah when the issue(s) occur?

Not a fresh boot, it's been on for days. Just keyboard, mouse and stick. Normally run winamp streaming music while flying, but that seems to have no effect as it happens with or without at the same frequency.

Quote from: Skuzzy on October 06, 2011, 08:50:38 AM

2GB of system RAM is not a lot for Windows 7. You are easily running out of system RAM. Also noted you do not have the native sound card drivers loaded, but are using the default Microsoft supplied driver, which is really riddled with bugs.

I'll look into the driver issue and approach SWMBO about some more RAM.

Quote from: morfiend on October 06, 2011, 10:43:32 AM

Dragon,

when you say turns left do you mean the rudder is deflecting or is the roll causing the issue?

It's roll, not rudder. I'll check the wires again, the one connecting the sticks as well as the ones inside the joystick again.

morfiend · « **Reply #9 on:** October 06, 2011, 02:51:56 PM »

Dragon,if it's the roll axis then you might want to look into the magnet upgrade/fix for the X52. I'm sure if you search these forums you'll find the link to this mod for the x52. Since the roll axis is a HID I'd look to see if the magnet placement is right,it may have moved causing you to have continual roll inputs.

hope this helps!

MADe · « **Reply #10 on:** October 07, 2011, 05:06:13 PM »

The aileron axis uses a 3 wire potentiometer. If the middle wire breaks, the pot stops working. If an endpoint wire breaks, the pot loses its self centering capability and settles on a different centering spot. If the bad wire is an intermittant thing, the pot would flip back and forth depending on whether which state the circuit is in.
Pot is just going bad or is dirty.
My rudder was doing this very thing, squeezed the connections, 1 was lose. Building my own flight controllers has learn't me a smidgen.

In AH's advances controller settings, in the two blue vertical boxes with green bar. Do they center at same spot when controller is at rest?
No, try calibrating the axis with the advanced settings GUI. Check and calibrate each axis 1 at a time.

Use DXTweak 2 to see pots input whilest moving controller.
ie: if the pot has a dead spot you will see the movement in the gui. If necessary you could change where you want controller center to be, based on input numbers from controller when at rest.

Establishing if the pots bad is best, then you can decide options.

clerick · « **Reply #11 on:** October 07, 2011, 05:22:15 PM »

Quote from: Dragon on October 06, 2011, 07:27:43 AM

Its a CoolerMaster 850w, plenty of power for what I have.

Don't dismiss the powered hub. It's been discussed over and over. The X52 really likes its power and your power supply don't mean squat if it's not making it to the stick.

ebfd11 · « **Reply #12 on:** October 09, 2011, 11:25:50 AM »

Dragon the reason why I say use a powered USB hub is the X-52 draws alot of power from the USB ports. I had a similar problem too but when I installed the external hub I had no issues after that.

Skuzzy · « **Reply #13 on:** October 10, 2011, 06:13:49 AM »

Dragon, you could have a million gigawatt power supply and USB devices could still not get enough power. The USB chip in the computer can only supply a certain level of power to the USB bus, no matter how big the power supply is.

Tigger29 · « **Reply #14 on:** October 10, 2011, 08:35:54 AM »

Quote from: MADe on October 07, 2011, 05:06:13 PM

The aileron axis uses a 3 wire potentiometer. If the middle wire breaks, the pot stops working. If an endpoint wire breaks, the pot loses its self centering capability and settles on a different centering spot. If the bad wire is an intermittant thing, the pot would flip back and forth depending on whether which state the circuit is in.
Pot is just going bad or is dirty.

That is wrong. This stick uses Hall Effect sensors and not potentiometers for the stick's X/Y axes (which is the elevator and aileron axes). I'm not saying that a bad wire or connection can't be the fault but a defective hall effect sensor is highly unlikely.

Aces High Bulletin Board

Author Topic: Joystick issues and occasional AH error (Read 950 times)

Dragon

Joystick issues and occasional AH error

Dragon

Re: Joystick issues and occasional AH error

ebfd11

Re: Joystick issues and occasional AH error

Dragon

Re: Joystick issues and occasional AH error

gyrene81

Re: Joystick issues and occasional AH error

Skuzzy

Re: Joystick issues and occasional AH error

morfiend

Re: Joystick issues and occasional AH error

cohofly

Re: Joystick issues and occasional AH error

Dragon

Re: Joystick issues and occasional AH error

morfiend

Re: Joystick issues and occasional AH error

MADe

Re: Joystick issues and occasional AH error

clerick

Re: Joystick issues and occasional AH error

ebfd11

Re: Joystick issues and occasional AH error

Skuzzy

Re: Joystick issues and occasional AH error

Tigger29

Re: Joystick issues and occasional AH error