Dual Strike PCB now with EX Strike PCB - http://www.arcadeforge.de

oh :frowning: okay then. i didnt know the imp board also toggled where the 5v power goes to as well, i was just under the impression it just switched the D+ and D- signals like a DPDT switch oh well i guess i cant do this mod

The imp board doesnt toggle the 5v between the controllers (both controllers are connected to the 5v at the same time anyway). The leds would be wired to the 4066 chip on the imp (so the same thing can be done on the chimp board too). Basically the PIC on the imp and chimp tell the 4066 chip which usb d- and d+ lines it should be switched to, via two of the pins. One pin will be logic high while the other one will be a logic low. If you have the led’s hooked up to those pins, you can have one lit up while the other one is off.

ohh okay. i get it now, sorry if that was annoying…

I’ve been sitting on this SMD Dual Strike for almost 2 months now trying to figure out what to put it in. Meanwhile, I have this mayflash case that I gutted for the PCB for one of my other projects. Why I didn’t think to put it in there is beyond me, but nobody ever said I was smart. Anyway, quick question that I should know the answer to. If I hacked one of the madcatz controllers (4715? whatever the hot modding one is that isn’t the SFIV pad), do I have to do the trigger hack with the inverter and diodes, or just wire everything up to the Dual Strike? May as well start working on this one soon…

No trigger hack is needed. Just remove the pots from the madcatz pcb and wire the spot the middle pins were at to the lt and rt spot on the dual strike smd. You’ll want to update to the newest firmware and then enable the trigger inversion via the fw’s config mode.

No trigger common to fuss with like the wireless stick? sweet…

Hey,

I`ve made here an partlist for V1 for the kit users.

Partlist V1

Hope this helps somebody…

IĀ“m loving DS pcb but the last who I bought from Bencao doesnĀ“t reconize the direccions, but reconizne the rest, the 2 grounds, the HP etc… I try to make inputs at pc and itĀ“s turns out funcionalaty, but when I conect to PS3 donĀ“t reconize again.
I“m waiting for an answer from Bencao, and I don“t want spend more money with shiping, I hope this was a simple thing to resolve, if anyone got a clue I“m be happy:pray:

Might need to configure the joystick mode it is in. Try holding select before plugging it in (let go after plugged in) and then press down on the joystick. Press start to save the config. This should save the joystick config mode to act as the dpad.

seqo just told me that this was the solution. :slight_smile: fixed

I think there needs to be a fix in the code because I’ve noticed this problem when I assemebled my dual strike smd boards with the 1.7 fw.

Plus holding strong won’t switch to passthrough. I checked the code and notice its checking for fierce when it should be strong, so I’ll see about making a 1.71 fw to fix these two issues.

probably there is something with the eeprom config. After udpating to fw 1.7 Ivlephisto told that the eeprom must be set to the default setting. perhaps there is a more simple way to do this.

For the strong button there must be an issue in the source. Might be IvlePhisto reserved this button for activation of upcoming Wii support…

btw new version of dual strike PCB arrived yesterday :slight_smile: Now I`m waiting on the remaining parts. @Gummowned : Do you want one to test?

I think its just no stick setting is set for default when its reset. Simple fix.
EDIT: My suspicions were right. The default config setting doesn’t set the stick mode to any setting.

For the other issue i think it was just a strong/fierce button mixup.

Sure I wouldn’t mind testing one. I might have someone who would want to buy some of those custom etched button caps too.

EDIT: I have the fixes done, I just need to upload them.

ql!! You still have your SVN access

just pm me… :wink: I`ve ordered some and they should arrive this week.

glad to hear that

Just a slight addition, I noticed in the one you gave me that I needed to switch the configuration so that the joystick was recognized. It was a simple configuration switch, but it struck me as odd.

Also, glad to hear your new boards are coming. Mine should be in my hands today or tomorrow. DHL says it’s ā€œwith delivery courierā€ :pray:

With the new additions, if everything on my end works out great, we need to work out a deal for when I go to EVO. I think the idea of selling a ā€œbolt onā€ dual mod ā€œkitā€ that you can install with a screw driver would be awesome. :pray:

Jep, you`re right! Need the fix here. @Gummo : just post me the fix, then can I check it in…

EVO is in about 3-4 weeks, nor? time is running :slight_smile:

Hey guys!
Sorry for this configuration problem :S
I integrated a fix into the Trunk (changed one 0 to a 1), but I would suggest to release a new version when I’ve finished EEPROM programming support - if no major problems occur this might be today…

Hey **IvIePhisto ; **

this EEPROM programming support will be a really great feature :wink: take the time you need… :wink:
[URL=ā€œhttp://shoryuken…/members/112085-IvIePhistoā€]

Firmware Version 1.7.1

As it takes me some more time to implement EEPROM programming (and now even EEPROM readout) I created a 1.7.1 version fixing the ā€œno joystick mode in default configā€ bug. It’s available through the usual URLs and in the SVN repository.

Rock on :rock: