Hurm…
I’ll try that out then and post up some results once done.
Hurm…
I’ll try that out then and post up some results once done.
I’m open for formulation improvements, English is my second language…
I will include it when into the next updates, but it’s not worth an update in itself. PM me your email address and you get a specially brewed firmware…
EDIT: OK, Gummowned bet me His proposal is a good one
Hey,
has someone Dual Strike installed and can test out the PS2 emulation compability on PS3?
Bye,
Jochen
Hey ben, what version atmega chip is the new DS using? I’m out of atmega8 chips and am wondering if I should make an order for atmega8a or something different.
go with the 168. All the DS v2 are assembled with this one. Here in eu is difficult to find the ATmega8, btw… We`re working on bigger release and we need the space ;)…
Hi again,
I’ve been poking around with my multimeter and here’s what I’ve found (using my Windows XP laptop, not the Macbook, and with home button emulation enabled. I’m leaving the 360 out of this test as the symptoms are the same on the laptop and it’s better to test with as it recognises both the PS3 and 360 modes):
360 passthrough mode almost always fails now (in the early days it was fine), giving a ‘device not recognised’ error. While in this state (S1=0V, S2=5V), the voltage across the home wire/screw is 5.02V. Pressing select+start drops it to 0V, so interestingly, the DS appears to still be doing the right things.
If it does work (S1=0V, S2=5V), pressing select+start drops the home wire/screw voltage from 4.30V to 0V
In DS/PS3 mode (S1=5V, S2=0V), pressing select+start drops the home wire/screw to 3.75V from 4.30V and Windows recognises that button 13 (home) has been pressed. Holding the buttons down causes the voltage to rest at 3.95V.
I’m not sure it it’s an issue with the DS board or the Mad Catz PCB I’m using, but I was using the Mad Catz pad often on my 360 without any problems.
I really need home button emulation as my stick doesn’t have enough buttons and the fact no one else seems to have come across this problem makes me wonder if my DS board has an issue.
I just downgraded to firmware 1.7.1 to see if the same thing happens (set 360 mode to default and home emulation to enabled). So far, with 1.7.1, going into config mode and quitting out usually gives the device error, but connecting the DS again puts it into 360 mode and so far it only gives the error if I quit config mode, otherwise it seems ok.
Also, if I put the laptop into standby and then resume, the error reappears and I have to reconnect to go into 360 mode. If I hold a button before resuming from standby, the DS goes into PS3 mode and works as normal.
HMMMMmmmMM…
I made some changes in the PT mode from 1.7 to 2.0. You already poked around in the code, didn’t you? Maybe you could play around with the lines 206/207 in “DualStrike.c” of the 2.0.1 source. As it works with 1.7.1 and doesn’t with 2.0.1 I suppose it has to do with this behavior. It works perfectly with my TE PCB, so it might be a special thing of the Fightpad. But then, there are other DS-Fightpad setups that work (but maybe they didn’t update to 2.0.1). Most readings seem OK, but the 4.30V seem small to me. I had a similar problem with the joystick switch emulation and solved it by changing code: instead of pulling high I made the ports float by making them inputs, see here, it will be in the next release. I/you could do something similar for the Home button.
If it helps, I also have some LEDs (with potentiometers) wired up to the 5V out from the DS PCB but they’re switched off. Not sure if they were involved in dropping the voltage to 4.30V. I might try disconnecting them anyway just in case they’re somehow involved. I’ll try looking at the source when I get back from work.
Hey bencao,
just tried playing sfac on the OG 60gb ps3 and the dual strike did not work. Im running on 2.0.1 fw, do you have any plans on supporting ps2 with future updates?
I’ve found a workaround which means I’ve no need for guide button emulation: I replaced the SPDT switch for my LEDs (off, dark, bright) with a DPDT switch to control what my select button does (disabled, select/back, home/guide) with the LED intensity indicating what mode it’s in. Finally the LEDs have an actual purpose other than just looking nice, and I can disable the button to prevent accidental presses (it’s on the right side of the joystick body so prone to random presses).
I’ll probably put fw 2.0.1 on now as I’ll hopefully have no pass-through problems any more.
Hm, difficult to test … @IvlePhisto Do you have a PS3 60GB version?
@ bencao74: I’m borrowing a PS3 from work now, I’ll try it with PS2 games when I get home…
:update:
It doesn’t work for me either. When booting a PS2 game, the controller turns off for a second or so, then back on again. Pressing/holding the PS button does nothing. I tried home button emulation on/off, and also tried changing the directions from dpad to left analogue stick.
I wonder if something about the PS3 switching to PS2 mode makes it ignore the PS button signal? Those PS2-USB converters that have PS buttons are fine, but maybe they emulate an actual PS3 pad instead of just an HID controller?
Hey, thanks for the test. we`re just discussing this issue, hopefully we do find a solution
Updated first post…
Strange issue. Does it work with (M)Cthulu and/or UPCB?
I fear I don’t, I have a PS3 slim…
it works with (M)Cthulu, Toodles has always solutions for that kind of stuff for the upcb I don’t know…
I bought a DS v2 pcb TE, but the computer does not recognize it, when I plug it appears something like “USB device not recognized”, but this works on the PS3, on PC and Dual mod does not work, any help?
check the pinout. Did you use the right order? Is soldering job ok? Check all soldered connections on your TE PCB hack.
Please make clear what is working and what isn’t, I don’t get it :xeye:
Hi, I plug the pcb on the computer(windows Xp) and the computer don´t recognized this, I just wiring the usb data line to check the pcb, the red one on the 5V screw, the black on the ground, the green on the D+ and the withe on the D-, it´s all ok, no?
I have 4 Dual Strike V1 and all of them works well, and when I plug them the pc reconizes, but that last I bought from Bencao isn´t recognized. I dont have a multimeter, I just buy this pcbs because it´s simple to conect.
Edit- The pcb it´s one DS V2 with screws just for the usb data lines, I´ve tryed today in other dual mod I´ve got here and this dont works too, I try 2 diferent usb cables but this remaing the same, but works on the PS3, something is wrong with this, maybe one broken pcb, on the computer the pcb apears like “Unknow dispositiv” on the hardware sistem.
OK, rather strange it works on PS3 but not on PC.
Please try the following things:
[list]
[]Recheck the wires on the screw terminals, pull them a bit to see if they are fastened. If you made adjustments, retry. If the wires are connected fine and it doesn’t work, continue with:
[]Uninstall the device (on english systems in the device manager right click on the device and choose uninstall), disconnect the DS from the PC, reconnect it again. If it doesn’t work, continue with:
[]Start the configuration editor, set your options and upload the configuration to the device. If this doesn’t work, continue with:
[]Execute a firmware update.
[/list]
If it still doesn’t work, you could try the following, but it’s a bit delicate: pop out the big chip of your V2 DS and the chip of one of the working DS V1 (VERY CAREFULLY) and try the V1 chip in the V2 DS. If this works, it might be a bad chip.