Yes, please do this if you have the means. If nothing else it might help to diagnose an issue to thwart further instances of this issue.
Also, got some replacement chips in last night, going to try to program and test them out, if they seem OK I’ll send one out to each of you having this problem.
Going to move to DS thread again… http://shoryuken.com/f177/dual-strike-pcb-http-www-arcadeforge-de-219484/index23.html#post9812843
Is there any way to ensure that it’s the chip and not the board with voltage/continuity testing? I don’t want to put a new chip in the board and have the board eat it… than that’s two destroyed chips and I still need a replacement board.
@tonedef
PM me your address, corrosive I’ve got your still I believe. I’ll ship you guys out a new chip when I get a chance to fully program/test the ones I’ve got.
Sorry if this question has been answered already, I read the last 7 pages of the thread looking for it but I don’t have any more time before work to scan the rest.
My stick is no longer working on ps3; it says “an unrecognized usb device has been plugged in”, or words to that effect. It’s worked fine for the last 2-3 months, and it still works on xbox. Any ideas?
Had this same thing with my chimp.believe it loose solder somewhere…mine was below the large chip.so I assume is lost connection somewhere on ur ps2 board. Loose wires I would look at first.
Does it work on PC still? Updated your FW recently?
If it’s working on the xbox still that means that the code is successfully running and the passthrough is working as intended. If it works on PC, update the FW to the latest (3.2) and see what happens. You can snag the updates from the link in the dual strike thread.
edit:
read the top of the chip first, make sure if it’s the atmega8 or the atmega168 version first. Use the update that corresponds with the chip you have.
I don’t have xbox 360 access readily available. Would testing the dual setup on a PC validate the 360 works esp if it registers in device manager as xbox 360 controller?
By the way, thanks PHREAK, received the package, wish me luck.
Yes, test on PC before anything.
plug in without holding anything down, should come up as the dual strike, then unplug and plug back in holding MP, should come up as the 360TE
Edit:
For you and anyone else, before doing anything after sitting down, touch something grounded in case you’ve built any static electricity from walking around.
I’m sorry to bother, but I just ordered an SE stick in the mail, and I couldn’t find information on applying the TEasy to it. All the video guides were for the actual TE.
Is the board for the SE stick the same as the TE? and does the TEasy mod apply solderless to it the same that it does for the TE?
My computer detects it, although it doesn’t list 360 as part of the name in the devices. However when I try to install the update it says “error opening HIDBoot device: The specific device was not found”. My chip is the atmega168 version, so it was the corresponding .bat I was trying to install. I had start held down while trying to install it.
Ok, let me make sure I understand:
You plug it into the PC and it detects it as the Dual Strike?
You plug it into the PC with MP held down and it comes up as the 360TE?
But when you try to plug it into your PC with start held down, there’s no connection sound or there is a connection sound?
Oh, I was just misunderstanding the process; I was trying to just hold down start once the stick was already plugged in, not realizing I had to hold it down while plugging the stick in. Updating the firmware fixed the problem with the ps3 (although I wasn’t able to run the config editor afterward because it was saying java “javaw” isn’t installed, although it is). An additional problem persists though; if you think it could have any relevancy to the config editor then I’d continue trying to get it to work… One of the directions (right) doesn’t work - the down-right and up-right corners work, as do the other directions.
Also thanks for the help so far!
edit: here are some pictures of the PCB
Someone mentioned a fix about that javaw error before (corrosivefrost I believe). I would definitely recommend attempting to get that to work, if nothing else then to allow you to access the features that might be added in the future.
Which FW did you update to, 3.2 beta 2? If not, definitely snag that one.
Directional issue:
Does this happen on 360/PS3? Both, or just PS3?
If it happens on PS3 only, reflash the FW just in case (if you haven’t done so already by updating to 3.2 beta). On your PC, force PS3 Mode by holding LK before plugging it in. Tell me if the directionals are still giving you weird stuff, are you set to DP?
No, press HK to get it into PC mode as the PS3 mode isn’t working on PC since firmware version 3.1…
I don’t understand, when I’m testing things out and I hold LK, it brings a device that shows (PC) but the look of it is much different than the PC version, as in when I force it with LK I see the Z axis and other things that aren’t on the force PC side of things.
Yes, it fits into the SE PCB, however the thing I found out is that I can’t seem to fit the Teasy1.2 + DS2 into my SE stick casing. If anyone can help me with this perdicament with a photo or something, much thanks.
Just want to do a quick status check here. Did you get the DS yet? If so any news so far? So far as the ribbon cable goes, I have not checked that yet since I don’t have a multimeter at the moment.
Honestly haven’t the foggiest on that one, I tested this measurement wise on the TE since I figured the SE had way more room to work with. When you get your DS mounted and everything together please post up a shot so I can see how things went.
The TEasy Mod + the TE PCB fit correctly inside the case though right? the bottom plate doesn’t hit the top of the TE PCB with all the ribbon cables attached right? One point of note is that you might not require the flanged spacers for an SE install.
Yup, got it, tested it, works flawlessly for auto-detection of 360 and forced modes 
I think that the ribbon cable might have just given out or something, but atm I’m using your DS PCB to do testing on some chips I got in the mail, I’ll get it back to you + a new ribbon cable asap.
In the mean time, for sure check the continuity of that cable.
I got the FW updated to 3.2 beta 2 and I installed it more than once. I got the configuration editor to run on another computer and applied defaults through there.
The directional problem happens to both consoles, but it is not something I understand. I am set to DP. It registers the right direction because the corners (up-right and down-right) work 100%, however right by itself does not work. I’ve had this same problem with a single direction not working previously, but it was with a corner as opposed to right, and it seemed to fix itself randomly… until now.
Whenever I flashed it I had it set to 360 mode (holding mp) because neither PC fully interacts with it in ps3 mode. It says drivers do not correctly install and I can’t enter the button check. I think something may be wrong with it?
WOW. So i got this thing working in my first try. Took me 3 hours though.
The green and white USB wires are a BITCH.
Anyway, i just have one weird issue with the start button. In DS mode it only registers on release. Thank goodness it’s only the start button, but could this propagate to the other buttons eventually? Everything is 100% in 360TE mode.