Jump to content

Recommended Posts

Posted

Hello,

 

I just received my first X52 and the all axes work but the X (roll) axis. I operate win 7 64bit, and I downloaded the drivers. On the config screen, everything works but the X axis, is there a fix? Just got it now:mad:

AWAITING ED NEW DAMAGE MODEL IMPLEMENTATION FOR WW2 BIRDS

 

Fat T is above, thin T is below. Long T is faster, Short T is slower. Open triangle is AWACS, closed triangle is your own sensors. Double dash is friendly, Single dash is enemy. Circle is friendly. Strobe is jammer. Strobe to dash is under 35 km. HDD is 7 times range key. Radar to 160 km, IRST to 10 km. Stay low, but never slow.

Posted
I presume you've done a re-install already. Try a different USB connector.

 

Check out the Saitek forums: http://www.saitekforum.com/index.php

 

I cant believe this. This thing will do all moves but ROLL. I didnt open it up, I reinstalled 64/32 Xp/7/Vista. Rebooted. Nothing.. I guess I'll have to return it, but I'll post a few negatives to the amazon retailer asshole. He has to pay the price.

AWAITING ED NEW DAMAGE MODEL IMPLEMENTATION FOR WW2 BIRDS

 

Fat T is above, thin T is below. Long T is faster, Short T is slower. Open triangle is AWACS, closed triangle is your own sensors. Double dash is friendly, Single dash is enemy. Circle is friendly. Strobe is jammer. Strobe to dash is under 35 km. HDD is 7 times range key. Radar to 160 km, IRST to 10 km. Stay low, but never slow.

Posted

AWAITING ED NEW DAMAGE MODEL IMPLEMENTATION FOR WW2 BIRDS

 

Fat T is above, thin T is below. Long T is faster, Short T is slower. Open triangle is AWACS, closed triangle is your own sensors. Double dash is friendly, Single dash is enemy. Circle is friendly. Strobe is jammer. Strobe to dash is under 35 km. HDD is 7 times range key. Radar to 160 km, IRST to 10 km. Stay low, but never slow.

Posted

That's your third topic on the same issue, there no need for that, it will only make it harder for people to help.

 

I will give you some ideas for you to try in case noone else with more experince with this model appears, but with a disclaimer that i don't own a X52 and never fixed one( Just a X65F that come broke on arrival too).

 

First i will try swapping the connector for the X and Y axis to identify if what is broken is the physical sensor or if is something in the board. Judging from pictures i found on this site, looks like they are the two 3-wire connector in the upper-right corner of this picture, i can't be sure from the picture so before changing them look to make sure they really are identical.

 

image090.jpg

 

After swapping them, now test on the ControlPanel and see if now when you move the stick X axis you get a Y axis answer on the screen and no response on the stick Y axis. This could mean a problem further down the board, but mean the sensor is ok.

BUT if you move the stick X axis and don't get any response and now the stick Y axis moves the X axis on the CP then the sensor/cable itself got something wrong.

 

It won't fix anything but at least you can narrow down where is the problem.

AMD Athlon II X2 240 2.8@3360 MHz | MB Asus M4A78-EM | 4GB DDR2-800 Kingston | XFX HD 5770 @850-900/1200-1300 | 500G Samsung HD502HI | Case CM 335 | CM-EPP 460W | Windows 7 Ultimate (64bit) | Saitek X65F | Freetrack(Wii Remote) | LG 23' W2353V

Posted (edited)
That's your third topic on the same issue, there no need for that, it will only make it harder for people to help.

 

I will give you some ideas for you to try in case noone else with more experince with this model appears, but with a disclaimer that i don't own a X52 and never fixed one( Just a X65F that come broke on arrival too).

 

First i will try swapping the connector for the X and Y axis to identify if what is broken is the physical sensor or if is something in the board. Judging from pictures i found on this site, looks like they are the two 3-wire connector in the upper-right corner of this picture, i can't be sure from the picture so before changing them look to make sure they really are identical.

 

image090.jpg

 

After swapping them, now test on the ControlPanel and see if now when you move the stick X axis you get a Y axis answer on the screen and no response on the stick Y axis. This could mean a problem further down the board, but mean the sensor is ok.

 

 

Just as you said and only the Y axis registered in place of X axis. X axis still didnt register in place of Y axis. Sensor problem maybe? Now I'm guessing something wrong with the X physical sensor. Please update on next step.

 

And thank you for taking the liberty.

Edited by WildBillKelsoe

AWAITING ED NEW DAMAGE MODEL IMPLEMENTATION FOR WW2 BIRDS

 

Fat T is above, thin T is below. Long T is faster, Short T is slower. Open triangle is AWACS, closed triangle is your own sensors. Double dash is friendly, Single dash is enemy. Circle is friendly. Strobe is jammer. Strobe to dash is under 35 km. HDD is 7 times range key. Radar to 160 km, IRST to 10 km. Stay low, but never slow.

Posted
170120111465.jpg

AWAITING ED NEW DAMAGE MODEL IMPLEMENTATION FOR WW2 BIRDS

 

Fat T is above, thin T is below. Long T is faster, Short T is slower. Open triangle is AWACS, closed triangle is your own sensors. Double dash is friendly, Single dash is enemy. Circle is friendly. Strobe is jammer. Strobe to dash is under 35 km. HDD is 7 times range key. Radar to 160 km, IRST to 10 km. Stay low, but never slow.

Posted

Now you need to find if the sensor is really completely dead.

 

-First try unscrewing the sensor card from the base, then get one of the magnets(the circular silver-like metal attached to the plastic, picture-1) and move it around the sensor while the stick is plugged on the PC and see if there any movement at all.

image100.jpg

 

-Second, with the sensor unplugged from stick you need to test if current can pass correctly from the sensor legs to the connector on the other end of the cable. Do it for the three wires. Ideally you will use a multimeter for that. If there too much resistance then it could be just a bad solder.

 

 

 

If you get no response on the first test and the second went ok for the three wires, then i will say the sensor is probably dead. I don't know any other tests that can be one on a hall sensor itself.

  • Like 1

AMD Athlon II X2 240 2.8@3360 MHz | MB Asus M4A78-EM | 4GB DDR2-800 Kingston | XFX HD 5770 @850-900/1200-1300 | 500G Samsung HD502HI | Case CM 335 | CM-EPP 460W | Windows 7 Ultimate (64bit) | Saitek X65F | Freetrack(Wii Remote) | LG 23' W2353V

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...