Official 'Kitty' class boards thread

Tech Talk
1741

It is all doom and gloom in gahrling land :frowning:

Trouble with a Kitty TE. It suddenly stopped working while playing BlazBlue CS2 on PS3 and no longer recognises any console.

Set up: TE Round 2, Kitty TE, short ethernet, Neutrik NE8FDP, modified console cables.

When plugging into a PC player LED 4 is lit and is being recognised in Windows as “4 axis 13 button gamepad with hat switch”. No buttons or joystick working. Forcing 360 mode only brings up “4 axis” message. Sometimes when plugged into the PC it is going into 360 mode without pressing any buttons or switches, when in 360 mode the buttons and joystick are working.

I thought it may be due to a faulty part somewhere, but swapping in new ethernet cables, jacks, and RJ45->USB cables causes the same problem. Investigated a possible continuity problem with the 4 USB wires running between the TE motherboard and Kitty but came up clean.

All harnesses are firmly in place.

Trying to update the firmware - LED lights up 1 & 4 (as it should) but then get the following error message:

[details=Spoiler]************** Exception Text **************
System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
at Kitty.Form1.button3_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.269 (RTMGDR.030319-2600)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll

Kitty
Assembly Version: 1.0.4121.3082
Win32 Version:
CodeBase: file:///C:/Users/cex/AppData/Local/Temp/$$_B7E6/Kitty.exe

System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.269 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.276 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.269 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging=“true” />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.[/details]

erm… help?

I should have enough free time to carry out any tests needed (along with the IMPv2 tests) in the next 10 hours.

1742

Redownload the Kitty firmware and extract the zip file to a new directory that doesn’t have spaces in it and try again to reflash.

1743

It works! Thank you.

For future reference, any idea what would have caused the Kitty to stop working mid-game like that?

1744

No Im afraid I dont.

1745

Ok, at least it seems to be working for now. Whatever corrupted the firmware I can only hope it won’t be a common occurrence.

1746

Will this work on the new SFxT sticks ??? if not any ETA on new model ??

1747

FAQs, first posts.

1748

Do you have a price on the SparkCE and can I order it now or do I need to wait till they come in to order?
Thanks

1749

I abhor the idea of preorders, so you’ll have to wait until they’re in hand and ready to ship before I’ll sell them. I expect the SparkCE to be the same price as the current Sparks, and discount the Sparks until they’re gone.

1750

Hey I know you might not want to answer, but does anyone know the life span of a TE? As I said I bought the stick in December 2009, and don’t want to spend $68 shipping a Kitty TE to the UK, just for my stick to stop working…

I’ve tried other sticks like the quanba, and prefer my original TE. If it is nearing the end of its life, is there anyway to save it? :stuck_out_tongue:

1751

Depends on what you mean by end of its life.
The TE is a very modular piece of hardware, if the stick goes, replace it, if the button goes, replace it, the pcbs only have one known problem (the triggers going) and IIRC Toodles has actually cooked up a solution that worked for that.

1752

Yeah my triggers have already gone! aha. Yeah that’s what I thought, it was mainly the PCB I was worried about, because that’s harder to replace. I’ll prob just get the Kitty, and just hope if anything does go wrong its easy to fix. I would just get a quanba, but thats more expensive and the original TE is just the best! :smiley:

1753

Yeah, as PaperTigre said, the PCB is about the only thing on the TE that will go out before anything else. But short of you purposefully trying to fry it, the thing will last a long, long time. If the lack of trigger buttons is troublesome, check out Toodles’ fix for it here:

shoryuken.com/forum/index.php?threads/madcatz-360-te-se-triggers-problem.149353/

1754

Is this a bad time to mention that the next revision of the TE Kitty would include the parts for the trigger fix on it? :slight_smile:

1755

Wow for real? Toodles, your website’s name is about as accurate as can be. So godlike! :lovin:

1756

Damn, really? I may seriously order another set and do away with the current Kitties. The whole point of my TEs is that they’ll be futureproof to a high degree.

1757

Nice work.

Also: I still haven’t figured out the issues I’m having with getting the Kitty in my Ryu TE-S to work on PS/PS2 systems and adapters. I’m going to try swapping it out with one I just ordered from you that is confirmed working in yet another TE-S stick I have kicking around. See if it’s the Kitty itself, or the TE PCB.

1758

Hurm…

I think I remember you mentioned a while back that for the next revision you were looking to implement the same punch down terminals as found on a TEasy Strike. Is this still the case? It would make the devices even more noob friendly by eliminating the need to wire strip for USB connections.

1759

Is a revision to the VLX Kitty planned? Because, I pan on getting another one.

1760

I decided against those again because those connectors are way expensive.

No, I dont have any pcb changes for it planned, and I have plenty on hand, but the headset power issue was bugging me, so I had all of the diodes removed from the VLX Kitties I have; VLX Kitties I sell from here out wont have the ‘disconnect when you plug in a headset’ problem.