There’s a guide to tell which you have based on part numbers, its in the first post of this thread. Comes in handy; the other day I had 3 of the 1.4 boards on my desk and had to recheck which was which.
I checked the first page and I’m not sure which guide you’re speaking of.
That’s exactly it.
from the first post:
I’ve dual modded my 360 TE stick with a chuthulu board. When I play cvs2 on a ps3 backwards compatible with the ps2 chip in the ps3, I notice there’s joystick lag. Would this be tv lag or ps2 lag or some sort of lag. When I play hdr, i don’t notice that much lag… or is this just the nature of the board being dual modded.
PS2 games lag on all PS3s, all modes. If it were the stick or any part of it, you’d see the same lag in HDR and PS3 native games. SInce you don’t, it’s the PS2 BC lag.
Just how much lag are we talking about?
http://forums.shoryuken.com/showthread.php?t=173220
http://forums.shoryuken.com/showthread.php?t=159919
Thanks. I knew about the lag I was just wondering if there were concrete numbers out there. seems people are still saying 2-3 frames.
The only thing I can think of that would cause anything close to that would be if the PS3 thought the controller disconnected, and reconnected it to a different controller port number. The only thing that should cause it to disconnect would be pulling too much current.
Give me the full breakdown of everything in the stick and how its wired up, especially the USB cord, any dual mod stuff, whether you’re doing the Start+Select=Home bit (and how) or if there’s a dedicated Home button. Pictures always help. Then, double check if anything is wired to the VCC screw terminal. We’ll go from there.
The stick is using a 10’ monoprice.com USB cable (I’ve tried an extra I had and it does the same thing), no dual modding, all qd’s, 22 guage wire, nothing wired to the vcc, I’ve tried start+select=home and I’ve tried dedicated (both with the same result). When I did the start+select, I just ran a short wire from the home terminal to the ground terminal right next to it.
Edit: It’s a mess in there right now since I’m not worried about it being tidy until it works. Thanks for the help!
http://i241.photobucket.com/albums/ff32/jinxmitchell/CIMG2317.jpg
The short loose wire is the home button. It’s generally hooked into the ground terminal right next to it.
http://i241.photobucket.com/albums/ff32/jinxmitchell/CIMG2319.jpg
I noticed you had 2 pairs of the black (silicone?) diodes instead of the smaller orange (ceramic?) ones. Is that on all the new assembled ones now?
Alright, I’m assuming you have SF4 so that’s what I’ll use for this. What I’d like you to do is this. Setup the stick so there is a dedicated Home button and no shorting wire between Home and GND.
- Unplug any other USB devices from the PS3.
- Turn on the PS3 via the button on the PS3 itself; we don’t want to have any SIXAXIS or any other controllers involved or on. If any of them are on, use their PSX button to bring up the menu to turn them off.
- Use the cthulhu to verify it maneuvers with the directions through the XMB. Dont select anything or press any buttons.
- Insert the SF4 disc if it isn’t already. If it doesn’t auto play, use the cthulhu to select and start the game.
- Use the cthulhu’s Start to get to the menu. Go into training mode for a quick spell just to verify the buttons and stick work. Use Start to exit back to the main menu, and then B to take you back to the ‘Press Start’ screen with the SF4 logo.
- Press and HOLD the home button. It should bring up the XMB menu with the ‘Turn off System’ and ‘Turn off Controller’ options. Release home when that comes up. Use the stick up and down to see if you can move in this menu. Let me know if you can.
- Tap the Home button to go back to the SF4 logo screen. Press start to see if you get to the main menu of the game. If you can, go into training mode and check everything else.
- Assuming you can’t get to the main SF4 menu, unplug the controller, and plug it back in. Press Start to get to the SF4 menu and test out the stick in training mode. If it won’t go to the SF4 menu, press and hold Home to bring the in game menu back up.
Let me know how that goes. Also, I need to know if you’ve upgraded the firmware on the MC or if its the original one it came with, and I also need to know if there are any other console cord connected to the MC (PSX, GC, and/or Xbox) and whether or not they are connected to anything like adapters or other consoles.
EDIT: I didnt see the picture before; I guess that answers the second question 
Yes. All of the Cthulhu (MC and PS3) now being sold are the preassembled 1.4 versions which use the better, more expensive black diodes. The oragish ones were made of glass (n4148), which are cheap, but are rated for about 100mA and 0.7v voltage drop. THe black ones (aww, crap, n5817’s I think they are) are rated for 1A and about 0.3v voltage drop. They’re more expensive, but handle more current much better than the glass ones do.
This is being used for Marvel vs Capcom 2 PSN download so that’s what it’s been tested on. It was also tested on HD Remix.
Everything works fine until this point. After the home button is pressed everything stops working except the home button.
This one isn’t a MC (atleast, that’s not what I ordered), and it has original firmware.
Something interested though: I tried things out during a BD movie and it all seemed to work fine. As soon as I tried a game though, it was back to the same problem.
Does the stick and/or buttons work IN the XMB window that comes up, that’s the question. And if it does, do they still work when you go into the XMB the second time? And does replugging fix it?
No, once the XMB is brought up, everything on the stick stops working except the home button, even when in the XMB. Unplugging and plugging back in doesn’t fix it. Also, I just tried it on SFIV and it’s the same result. Something to note though: When it is first plugged in, the system registers the stick as pressing buttons, so it will sort my games, bring up the “Turn off system” option and sometimes start a game if the cursor is on one.
Thank you for your reply…
We actually tried cvs2 on a ps3 bc using hdmi on a crt tv and the lag was barely noticeable. So I guess it’s just how it is.
A-HA!
HAHAHAHAHAHAHA!
Jinx, look at where the QD’s connect to the microswitches on the stick.
And then look where they connect on the pushbuttons.
You have the ground line connected to the oddball ‘top’ prong, which is the COM tab, and perfectly fine. On the stick, you have the signal line for the stick directions going to the tab closest to the COM tab. That’s cool. On the buttons, you have the signal line going to the ‘NC’ tab, the ‘normally closed’ tab. That’s bad. Move them so they go to the other tab, the ‘NO’ (normally open) tab. It doesn’t really matter which is which, but the important thing is that you only use the two tabs farthest from the little red doohickey that gets pressed on the white microswitch.
Try it, and inform us that everythings working peachy. Because, sigh, its a wiring problem.
its always a wiring problem…
It looks like the ChImp code is ready for testing. I’ve tested out the functionality as best I can, and everything appears to be working as expected. There are two things though that I’m throwing out for input in case anyone wants to throw in.
-
The board by itself does the whole “Start+Select=Home/Guide” thing, both internally when on PS3/PC, and by forcing the line low, pretending to ‘press’ the Guide, when in 360 mode. It will continue to do this until the first time the actual Guide button is pressed, if one exists. So, if you don’t have a dedicate home/guide button, no worries, it will always work no questions asked. If you do have a dedicated home/guide button, then once you press it for the first time after you plugged it in, it’ll work no questions asked. I’m curious if anyone would expect that Start+Select activating the Home/Guide button before the first time you press the real button would be a problem? I’m pretty damned confident that it won’t, but I could be wrong. I could have the chip save a flag in the EEPROM, something to tell the board, “I’ve never seen a Home button, so let’s go ahead and keep doing the start+select=home thing” or “Yes, I have seen a Home button, so no pretending.” But then I’d also have to put in a button press combination to clear that flag in case the board got moved over to a different stick and I’m really not thinking the added coding time and headache will actually help anything. Pro’s, con’s, opinions?
-
If the chimp+ 360 pad are plugged into a 360 when the 360 is off, you won’t be able to turn on the 360 via the guide/home button (or start+select combination. see above). Once the 360 is turned on, then the chimp sees the 360, and goes into full 360 mode no problem. In fact, if the 360 is then turned off with the stick still plugged in, you CAN turn on the 360 via the guide/home button just peachy, as much as you like until you unplug the stick. The chimp can’t currently detect a 360 console if the console is off, and I really feel that trying to force the issue so it detects a powered off 360 console would cause some problems with some PC’s. Does anyone really think this is a deal breaker or even something to worry about?