I see. sounds like it’s gonna be a while. The longer the better really because this will be perfect when it comes out. so awesome!
I’m changing my release version to support PS3/360 instead of PS3/PC. The reason for the initial exclusion of PC controller support is because I’ve found that there are a variety of data layouts and I’d rather not waste my time organizing all that when there are more pressing details that need tending to. I will re-visit universal PC controller support at a later date. PS3/360 support should meet the needs of most tournament settings.
-ud
I’ve modified the x360 driver in linux, so I have some understanding of it. PM me if you still need to debug/print-info-about this driver.
(I wanted to use a 360 stick in ubuntu and get the L-R analog triggers working as buttons )
Will input lag be sub-1 frame? Love the idea but would suck if notoriously picky ST heads don’t accept it for that reason.
It better be! Once I’ve got all the firmware functionality in place that I want, I’ll get back to latency testing. I respect and agree with such lag pickiness, so I will certainly do all within my power to be sub-1 frame. That would be a lot of lost development time 
I suppose the PS2 or DB15 option would become viable, at that point, but let’s not think about that just yet.
-ud
Played some XvSF, last night. P1 X360, P2 PS3 
There have been a lot of changes to my code since since I last did latency testing, so I ran 50 samples with an MC Cthulhu (measurements in milliseconds):
Spoiler
11.6
14.0
18.8
17.8
15.4
17.6
17.2
17.6
17.8
10.5
18.1
15.8
14.0
14.6
20.0
19.0
13.0
18.6
12.2
10.2
17.0
15.8
15.0
17.0
19.6
11.8
17.8
10.2
14.6
19.2
16.2
16.6
12.2
15.2
19.0
14.8
19.6
17.6
16.0
18.0
16.6
12.4
10.8
19.8
17.4
18.4
17.2
13.8
16.4
10.8
Best response: 10.2
Worst response: 20.0
Average response: 15.8
This is probably acceptable for a general purpose converter, but for this application, I really need to be under 16.7 consistently. There’s probably some more optimization to be done, I’m just hoping it’s in my code and not the USB stack, as that could get dirty. I’m also curious how much lag is inherent in other controllers.
-ud
any other updates?
Yeah, I tested some other controllers and latency was significantly less than the MC Cthulhu. For example, MadCatz X360 pad was 7-11ms range. Toodles and I tossed some ideas around and he recommended updating the firmware in my MC Cthulhu to his 1ms version. 2ms or less response times: yee-freaking-ha! So, in short pretty much everything I have on hand to test on this is safely under 1 frame lag. I’ll just recommend to people that they update their MCC to the 1ms FW. I’m sure some controller out there is super laggy (esp. some of those converters), but I’ll take no responsibility for that 
As you can see by my avatar, I’m planning on being @ EVO and I intend to bring a couple of these things to demo. I’ll likely bring my programming stuff so if I run into any nasty oversights, I can tweak things while I’m there. Still have some final tweaks to do to pretty much everything, but even if I had to take what I have today, I believe the majority of controllers would work on it and with less than 1 frame of controller lag.
-ud
I’m assuming this will also be compatible with any other system that connects via Jamma?
The opposite: it’s a supergun built into a CPS2.
You’d provide a means to update the firmware post launch too, right? I can’t wait to see some Youtube vids of this in action.
I need to look into this, but presently I don’t have a USB bootloader set up.
Yeah, I imagine after EVO there should be some footage
Toodles recommended I pursue the latency issue for the controllers that are spec.ed @ 10ms, and I am in agreement. My USB Host board seems to be taking 2x the time it actually needs to transfer the button data to the CPS2, which although acceptable for speedy controllers, can violate sub 1 frame timing for slower controllers. I will try and make time to investigate this before EVO.
-ud
How optimal is your code at this point? Is that still part of the design process or is it more of a hardware limitation at this point?
Not hardware limitation, it’s a FW thing. 90% of my code I will probably never need to touch again, so there’s about 10% that will likely get some massaging in the next few months as it gets more testing by folks. Changes before EVO, changes after EVO, beta tester feedback, etc.
-ud
I meant the signal processing code and not the project as a whole.
Thanks for the update!
Mmm, no more compatible than you are willing to wire up Common ground and is happy w/ 5V logic. As is stated in the OP, I will be offering USB Host boards and my power supply board @ some point. Will make supergun folks quite happy, I reckon
-ud
Anywhere I can put some money down for the DB to USB converter?
Not yet. I’ll be using most of my free time getting stuff ready for the full CPS2 system for EVO, but after that, I’ll be whipping up some modder/hobbiest friendly boards for people to try out. I’ll post here when stuff is available Cool part is you can use them for anything. Control your toaster! Control your toilet paper roll with a TE and a motorized gearbox!
-ud
I WANT IT NOW!
LOL! Seriously though, Cps2 enthusiasts are anxiously awaiting the final product, I am definitely trying to get one of these asap!
Good stuff!