edited first post and the newest features.
SNES pad mod is done too now 
i’ll charge you 5 bucks for giving you the idea >=(
competition pro mod is possible, too. Anyone wants this idea? 
whats a competition pro?
btw, finished 6 button genesis mod w/ turbo last night. Now I got 3 different classic controllers all ready to play on ps3 or emus on pc
A joystick for Atari VCS, C64, Amiga and such, see here. A DS firmware supporting those joysticks is planned.
Rephrase:
Tried upgrading to fw 3.1.0.
Game controller on PC still reads “Dual Strike V3.0.0 (PS3)”.
In properties, button 10 shows as constantly pressed. The rest of the controller seems to be fine.
Autodetect seems to be confused… when I go from configuration mode (hold select) to normal autodetect by pressing start, it uses the madcatz driver and shows 10 buttons (1-4p/k and start/select). Joystick works fine.
When I plug in the stick to my pc with no buttons held, it shows the “Dual Strike V3.0.0 (PS3)” as the game controller and I assume that to mean that it’s trying to use Dual Strike in PC mode. This is where I see 12 buttons, 9 is never used, 10 is constantly pressed, 1-8 work fine as 1-4p/k, and start and select work fine as 11 and 12.
Phreakazoid187 is trying to help me over in the TEasy thread but nothing seems to change anything.
I can get in the configuration editor – I have xbox support off and MAME keyboard support off.
Autodetection is on. Default Joystick mode is Digital Pad.
On the next tab (HW), I have meta as select, home button and 4k/4p emulation disabled and s3/s4 function as “nothing”.
Something seems really off here, as for whatever reason, the firmware version doesn’t seem to change in the game controller window.
Strangely, autodetect seems to work fine with all buttons on both xbox 360 and ps3 consoles.
Any help would be much appreciated.
Thanks.
Edit: Tried the fightstick on another laptop – the dualstrike shows up as “Dual Strike V3.1.0 (PS3)” on that computer, but the Dual Strike PCB in PC mode still shows button 10 as constantly pressed.
hmm, seems that reset fuse is not disabled on the MCU. This has no really issues for game play. If you want to use inverted triggers or such stuff then you need a mcu with other fuse settings. Send me a PM if you want to exchange the MCU.
known issue, will be solved in bug fix release. Dual Strike V3.1.0 is installed but shows on some systems sill 3.0.0. No impact here about functionality.
bencao74, your PM box is full.
Does changing out an MCU involve soldering?
If it does, I’d need to do a full board swap because I have 0 soldering skill.
At that point would it make more sense to work with Phreakazoid187 since he’s located in the US and sold me the DS board originally?
It figures… i finally get around to getting the parts and trying this myself and there’s something wrong with my board. 
ups… it`s empty again.
No. Just swapping
hmmm, what do you mean exactly… I thougth youve an activation of button 10. This is no issue for game play, coz youre not using inverted triggers I suppose.
again, the dual strike info in the game controller setting is ok. You`ve reported that auto-detect works and all buttons are registered…
Do you have a joystick switch or something else connected to the S4 pin? Otherwise it really should be an open reset fuse.
It’s a problem of Windows which can’t be fixed. When you first plug in a game controller Windows uses this name for ever in the game controller applet. To have a look at the right value open the device manager and find the “USB Input Device” under “Humen Interface Devices” of the Dual Strike. In the properties on the “Details” tab the value “Bus reported device description” shows the real version.
|v|ephisto:
usb connected to screw terminals on dual strike.
ribbon cable connected from header to header on TEasy.
so there should be nothing connected to the S4 pin unless it’s something done between header of DS and TEasy board.
also, thanks for info on the versioning – makes sense.
As far as the button 10 activation goes, while it may not affect anything at this point, I still know that something is technically wrong and my OCD personality traits fixate on it.
It’s hard to explain, it just bothers me that when I plug in and it autodetects on PC that the button is constantly registering – some day I may be playing something on PC and that could come back to bite me in the ass. Reminds me of how the SNES game Inindo: Way of the Ninja would not work if you had the Super Scope 6 sensor plugged into controller port 2. Took FOREVER to figure out what was wrong there. Returned game cartridges and lost saves… ugh. I’d rather be safe and KNOW everything is working at 100% than know something is off, even if it’s not currently affecting me, because it might in the future.
Anyway, Phreakazoid is going to help me out, so no worries, just some extra hassle.
Question: Which mode is the correct mode for “autodetect” on PC? Dual Strike PC mode or Pass-thru?
It will go in PC mode. If you want to get it to go in pass-thru mode on the pc you need to hold triangle/Y/Punch2 (w/e you want to call it) while you plug it in.
On other dual strike SMD news, I now have the MS wireless 360 pad dual modded and sega saturn pad dual modded.
I would just like to say that dual modding the MS wireless 360 pad is a major pain in the butt and I encountered a strange lil problem. When all wired up and plugged in, the ds board was always in bootloader mode. When I tried again with the start button not wired, the ds board was going into config mode. When I tried again with the select button not wired, the ds board was going into one of the pass-thru modes. What I think was happening is all the buttons were being registered as being pressed on initial power up. When I checked out the button inputs on pc, nothing was being held down. I also tested the board when not hooked up to the pad and it acted like normal. So I ended up having to make a custom firmware to prevent those weird things from happening when hooked up to the wireless 360 pad.
sounds reasonable. perhaps add this stuff in the next release?
I think it was only a special case with the wireless 360 pcb. I actually used a modified version of the 2.0.2 firmware. So no need to investigate further.
Whats funny is that this isn’t the first time I tried dual modding the wireless MS pad with a dual strike smd. I actually dual modded one before a while back with one of my initial batches of smd boards. I was using a different button combo to go into bootloader mode, start+select or home, but you had to hold them down the entire time or else you exit bootloader mode. So this whole issue never appeared because the bootloader mode required the buttons to remain held unlike what it is now.
Hey, some news here. You can buy now your Dual Strike at ArcadeShop.DE
A usb cable for free is included in this offer. Go for it
Just wanted so say sorry to everyone who was trying to access the svn today, I had to move it to another server so it was down for a few minutes - I know someone must have tried to access it at this time as the logfile was spammed with requests during the time I was trying to figure out some misconfigurations I had made
Everything should be back to normal now :>
thanks a lot for supporting us with SVN!!!
K. Here is a dumb question. I installed the 3.1 version to my DS V2 board. The autodetect works flawlessly. Except in PC mode my TE stick buttons are all wacky and missing some inputs. I assume I have to go to configuration mode to set the button keys to the corresponding 3xPunches and 3xKicks.
However, I get an error message for the configuration editor. Tried numerous times to the java and batch command line to execute. What to do? I get the can’t find “javaw” error message. Even though I am positive java was installed.
Any ideas what I’m doing wrong?
Open a command prompt and type “javaw”. If you get something like “command not found”, javaw isn’t in your PATH environment variable. Add the directory path containing javaw to your PATH environment variable and try launching the configuration batch file again.
You could probably also edit the bat file to use the full path to the javaw.exe.