I wasn’t quite sure where to put this. I thought about the padhacking thread since I had it in a dual mod, but the problem exists in the pad by itself. I asked on TTToL, but didn’t get an answer.
Anyway, here’s the issue. A month or two ago I dual-modded a PS3 SE for a client using a 360 Madcatz SF Fightpad. Recently we’ve had a lot of storms in the area, and the client’s power was on for three days. When the power came back on, he said the stick no longer worked properly in 360 mode.
This is what I noticed after running some tests:
– When plugged into PC, PS3 mode works perfectly.
– In 360 mode the Fightpad registers registers 5 (LB) and Up as constantly activated. Pressing Left triggers Up-Left, Right gets Up-Right, Down gets neutral (no directions pressed). Every other button works, including guide.
– Disconnected 360 pad completely and connected a spare USB cable from another fightpad. It does this on its own, so I know the problem is with the pad itself.
– Cleaned off all contact pads where I soldered. Still does it.
– Tested for continuity, neither LB or Up are grounded. Shorting both has no results.
I’m thinking it’s a fried resistor, but I have no idea where to start looking, and I’m out of pads so I can’t replace it.
I took two 10k resistors and soldered them together, connected one to Up and the other to LB, then attached the end of one of them to VCC. Voltage for both is 1. I’ll hook it all back up and see what happens. Give me 20 mins.
I have a 10k on each signal separately on one end, but they both connect together at the point where they meet at VCC.
Anyway, it works fine on PC, but it won’t even register on 360. I wonder if the security chip isn’t fried on this pad.
edit:
Upon gathering more information, it turns out the original problem is that the pad stopped being recognized by the 360. This is odd because guide will turn the system on. However, when I plug the pad into a PC, it works just fine after adding those two 10k resistors.