Thanks for the responses, PaperTigre and gahrling. I’ll definitely be doing that.
Thanks for getting those replacement ribbons to me quickly Toodles. Now I have another problem with my stick. When I plug it in to my computer to check if the stick is working, the top row of the turbo LEDs flash and the guide button lights up and turns off, when i press buttons on the stick, the correct LEDs light up. The device manager, the stick shows up as Unknown Device and when trying to flash the firmware, it closes and says it cannot find the device. Ill try to upload pictures of my kitty board/Te board later today if you need them. Thanks
Hey guys, I did a TEKitty mod on one of my clients Round 1 TE a couple of months ago and his Guide button the 360 side doesn’t work anymore. Everything else, like the stick and buttons, works just fine and the PS3 side works flawlessly even the guide button. I took a look inside and didn’t anything wrong at all so I decide to (re)flash the TEKitty firmware. That didn’t help the current issue. I remember that Microsoft did an update that disable/disrupts third party controllers. Could it be that? Thoughts?
The most important thing with the new spring terminal Kittys is that the VS harness ends that plug into the Kitty are on the OUTSIDE connectors of the Kitty near the edge of the board. You will run into problems if they’re plugged into the inside because of the resistors that were added for the Rnd1 trigger fix. Verify they’re plugged into the outside connector on the Kitty and we’ll go from there.
Yep. But in a non-Pro model TE, you’re better off with the TE Kitty, but either one can do 360 or PS3 and everything else all through the RJ45 jack if you want.
Sure, trim it as short as you would like.
If this is in normal Kitty mode, then it’s a problem with the outgoing USB connection. Check the USB wires from the cord to the Kitty.
Nah, it doesnt have anything to do with that update, that was all wireless stuff anyways.
Most likely fault is the ribbon in the H section going from Kitty to main 360 board. Test the voltage on the XGUILD point on the TE pcb when the button is pressed and unpressed. If the voltage is low when the Guide button is pressed, then it’s something with the 360 board; other than just reseating the cables I dont think anything could be done. If the voltage doesn’t go low when it’s pressed, then there is a connection problem most likely in that H ribbon going from the TE board to the Kitty.
Edit: Fixed my problem.
New problem came out though. I’m using a BlazBlue TE (and have the TE-S kit). When I press LT/RT/RB in Kitty Mode, the corresponding lights don’t light up. In the controller set up in Windows, LT/RT won’t have a number light up but RB will (no light on the Turbo panel though).
In TE mode, they work though.
I’m rather confused by that; on a PC in Kitty mode, there is a numbered button for all three of those.Can you please describe again in a bit more detail?
-Do the turbo panel LEDs for those buttons light up in PS3/Kitty mode? 360 mode?
-Do the button presses get seen by the console in PS3/Kitty mode? 360 mode?
In the properties, this is what I have for the Kitty mode.
X = 1
A = 2
B = 3
Y = 4
LB = 5
RB = 6
RT = No Number Activates
LT = No Number Activates
Start = 10
Back/Turbo = 9
Guide = 13
When I force 360 mode, the properties show:
A = 1
B = 2
X = 3
Y = 4
LB = 5
RB = 6
Back = 7
Start = 9
LT = 9
RT = 10
When playing in Kitty mode/360 mode, the A, X, B, Y, LB all light up on the Turbo panel. RB, LT, RT don’t light up on the Turbo panel.
When playing in Kitty mode, the LT/RT don’t work.
When playing in 360 mode, the LT/RT do work.
Sorry I confused you about this (my head is playing tricks with both of us!), but that’s what I’m getting right now. Thank you for taking the time out to help me with this too, Toodles. Greatly appreciated.
Check that the ribbon cables that start at the button distro board are plugged into the Kitty on the outside connectors, near the edge of the board.
I think I may have discovered the problem. One of the wires in the CN2 ribbon came out of the connector. Don’t know how it could have happened as I was real careful. Bummer. I’ll patch that up and see if it fixes my problem. Should be fun. :\
Edit: Both weren’t on the outside connectors. Forgot to answer your question! Double d’oh!
Edit: They weren’t on the outside. Bad time to have a typo. With the exception of one (RB), they all light up now. Gotta fix that wire and I should be good.
Toodles, you truly are godlike. 
Edit: Fixed the ribbon cable (temporarily right now) and RB doesn’t want to light up on the Turbo panel. It works in the Properties menu though.
Final Edit: All patched up and everything is working except that RB Turbo light. That really doesn’t bother me though, so I’ll be closing my stick up and enjoying all of the TE Kitty goodness. Said it once already, but I’ll repeat it because it’s that true. Toodles = 100% Godlike
Are these turbo buttons failing to light up also doing this in the latest board revision?
Madcatz VS, TE Kitty with VS Harness
I have a similar problem to joedub3 except that in my case, it is LB that does not work at all (no LED, no Control panel recognition). I have verified a short in the long button-distro section of the CN1 (#5) ribbon cable on the LB pin, but the wire seems to be solidly in place. Any chance of getting a replacement cable? Also, I am installing a Remora w/ArcEye3s on top of the multi-mod. I assume it’s ok to proceed and everything will be fine except LB won’t light?
Nothing has changed on the turbo lights section; the diodes can still pop off if mishandled.
You said you found a short, but are you describing a disconnect? If we have certain reason to believe its a problem with that ribbon cable, sure, replacements are easy to send but I do like to know how it failed when I can.
Sorry, wrong term. Yes, disconnect. When I saw a button wasn’t registering I multi-meter’d everything and found LB wasn’t connecting from the distro-board to the main TE board. So I unplugged that cable and tested the pins. LB wire on the long side had no signal, but all the pins seemed snug.
Edit: Also, the Remora/ArcEye add-on went smooth. God, it’s pretty.
hey all, i’m completely stumped here and just don’t know how to proceed with my kitty install. my original post is here
and this one has updates as to what i could determine is happening given my lack of knowledge on the subject.
anyhow, if anyone can help it would be greatly appreciated.
thanks.
I’m having an issue with my install. I’m all the way at the test stage. got to where I flash the firmware and got it to flash. Now when I plug the usb holding turbo on the computer, the device shown just shows “Unspecified G”. The top left and bottom right home lights anytime its plugged in are green. I tested out on an xbox360 and ps3 and same results and the inputs on the turbo leds are showing the correct buttons are being pressed but nothing happens on screen. I’m not sure if I did the new punch terminals correctly. Never did those before. I’ve done a few kitties before but they were the screw terminals.
Hi,
Just installed a TE Kitty in my mvc2 TE stick. X360 works perfectly, but when I play UMvC3 on PS3, it looks like the R2 and L2 buttons get ‘stuck’ when there’s any other input. I confirmed this on the PC side. When I’m holding down a button or two, PC buttons 7 or 8 get stuck (light up) until there is more input or I let go of the buttons i’m pressing. Doesn’t happen to any other buttons.
I tried to avoid the R2 and L2 buttons by doing the Turbo/Guide remapping, but whatever is assigned to the TE-Kitty 6 and 8 buttons start getting stuck with multiple button inputs. So weird. it makes me think that it has to do with the fact that the mvc2 TE default button layout is different from the normal TE button layout.
Hope you can help me out. Thanks.
i can’t help but i can at least let you know i have a stock round 1 and it’s got the same issue, just with my r2. although i’m just clueless as to what to do, my best guest is no it got nothing todo with your UMvC3 stick and more to do with something else.
I hope Toodles didn’t get a bad batch then. Try to reassign a button to L2 in PS3 mode. Should be happening with that button too if it’s the same as my problem.
I am still having problems with my computer recognizing my stick, I have tried to reconnect the wires to the kitty multiple times and nothing is working. I’m sending you a few pictures of the kitty and madcatz board with my wiring. Let me know if you need any additional pictures if you think it might be a wiring issue.
I think I might be having same problem. I just pulled out another vs stick I had used a previous screw terminal kitty and matched up everything exact on my vs stick having the problem(two ribbons were wrong, oops, now correct) and I’m still not getting recognized on pc or Xbox and ps3. Correct buttons light up and on mine the top left and bottom right player led just stay on.