..:: PCSX2 Forums ::..

(09-28-2013, 06:36 AM)Huesoman Wrote: [ -> ]After reading posts: #726, #972, #987, #989, #994, #1004, #1070, #1143 and this one (#1014):
@Contrite: your BTH Dongle is a very early REV of the CSR chipset (USB\VID_0A12&PID_0001&REV_0134) and doesn't fully support EDR.
I came to the conclusion that my BT dongle doesn't support EDR, I mean it is Bluetooth V2.0 but not Bluetooth V2.0+EDR, and the dongle needs to support EDR in order to read the PS3 controller (DS3) inputs. So, even when the hardware id is listed as a supported dongle (USB\VID_0A12&PID_0001), not all revisions are supported, at least not this: USB\VID_0A12&PID_0001&REV_0134, and I think neither this: USB\VID_0A12&PID_0001&REV_0100 (I even think is not bluetooth V2.0 but V1.2). So there I go. I will look for a bluetooth with EDR. Just hope its hardware is supported.

Somebody knows if some of these Bluetooth dongles (see below) are supported?
Trendnet TBW-107UB (Version 1.0R)
TOSHIBA (PN PA3710U-1BTM)

The thing is, I'm not using a BT dongle. I'm just trying to get my controller to work via USB port so that I can play my games without BSOD from Motioninjoy's drivers (Which, until I get this working I have to deal with)

My issue is that SCP DS3 Service just simply won't install onto my system as a Windows Service. I have no doubt that the drivers themselves are installed but without the service, I'd might as well have nothing.

Every time I plug my Bluetooth adapter into a different slot, it installs the BTH DS3 Device thing onto each port. I have 2 different USB 2.0 Bluetooth adapters, different brands too and it does this for both. Any way to prevent this, because I want to connect Wiimotes to my PC as well

(09-28-2013, 06:14 PM)existingdark Wrote: [ -> ]The thing is, I'm not using a BT dongle. I'm just trying to get my controller to work via USB port so that I can play my games without BSOD from Motioninjoy's drivers (Which, until I get this working I have to deal with)

My issue is that SCP DS3 Service just simply won't install onto my system as a Windows Service. I have no doubt that the drivers themselves are installed but without the service, I'd might as well have nothing.

Oh, I know, I was talking to myself (I guess) . I think I'm not the person that can help you with your issue, but here are some new advices:
1. Unistall all what you have installed from this thread.
2. Use "restore system" on your computer, choose a date prior to all the installs from this thread.
3. Install again, but leave the box "Bluetooth driver" unchecked (as you said you will not use BT, and maybe there is a conflict with those drivers), but check "Force intall" box.
4. Pray to the gods.

You know, I had to read almost all the 158 pages of this thread to know what could be my issue (I'm now on page 120), maybe you should do the same because I doubt old users (that can help you) are checking this thread anymore. BTW,

Somebody knows if some of these Bluetooth dongles (see below) are supported?
Trendnet TBW-107UB (Version 1.0R)
TOSHIBA (PN PA3710U-1BTM)

(01-14-2013, 08:07 AM)Scarlet.Crush Wrote: [ -> ]@rama: unfortunately your dongle is BT 1.2. The first digit only of the HCI Version specifies the BT version and is coded (the rest is encoding formats). See here for the Bluetooth SIG numbering assignments.

I typo'd the version requirement for DS3s, it should be BT 2.0 + EDR. So you would need a dongle with HCI Version 3.xxxx or above.

Your dongle is doing all the connection setup correctly, it just doesn't understand the stream of reports coming from the DS3.

Not need to answer anything but I quote you just to say that my prior dongle HCI Version (according to ScpMonitor) was 3.3164 with hardware id: USB\VID_0A12&PID_0001&REV_0134. According to the link it should be 2.0+EDR, but I think it doesn't support EDR (because this issue: BTH 0000000 None) and I think it is Bluetooth v2.0 (because I read it in the box and the advertisement, and never read +EDR btw. ). Furthermore, my new dongle HCI version (according to ScpMonitor) reads 6.8891 with hardware id USB\VID_0A12&PID_0001&REV_8891 (same hardware as before but new revision) and according to the link it should be Bluetooth 4.0...Buuuuuuuut, I don't think it is Bluetooth 4.0, I read the box, the advertisement and check the manufacturer website and it says this: "Class II Bluetooth v2.0 and v2.1 + EDR", so, unless they are crazy and advertise their product as v2.0 when in fact it is v4.0, we have 3 possible answers:
1. The link about HCI numbers has some errors
2. ScpMonitor has some errors, or...
3. My dongle, driver, etc has (have) some errors.

Well, in fact I quote you just to tell you that the hardware id: USB\VID_0A12&PID_0001
is in fact supported, but not all revisions (specially REV 0134, ) and that it is possible that the HCI number displayed by ScpMonitor isn't telling us correct information about our dongles. Annnnnnnnd, I also wnat to thank you very much for such great work, I wanted to use my ps3 controller with the PC because good controller are very expensive in my country (there are cheaper controllers but I know by experience they don't last but just a few months) and I didn't want (nor have enough money) to buy a new controller. I read in a previous post that you didn't give a link to donations because you do this for fun and to learn new things in the way and I think that speaks a lot of you, it isn't that common to find that kind of people, I'm glad one decided to create an application to use a ps3 controller with a PC, . Thanks again and good luck with your next projects.
...I have no more issues by the way, the controller works great

Anyway to make the PS button behave like a regular button? Makes a great "exit" for hyperspin

So, I picked up another DS3 and this one is just giving me headaches.
This DS3 controller works fine when connected to the ps3 either through an USB cable or wirelessly. However, there's absolutely no way to get it work on my computer.
Everytime I connect it to my pc that runs windows 7 home premium 64 bit, I get a message telling me that it was not possible to install driver for this peripheral and, if I try to unplug it and plug it back in, I get an "USB Device not recognized message".

Usually, windows should pick it up the controller as Dual shock 3, but in my case it is not happening, as windows is flat out refusing to see the controller. Anyone experienced a similar problem and got it to work?

Hiya! Great work on your program here! I've been looking for an alternative to MotioninJoy for a while now, and this seems to be a viable answer!

Problem is, that it won't recognize my PS3 Dualshock controller when I connect via USB. (It installs successfully, but I don't see the service running at all. o.o I do not have bluetooth, so that's out of the question for me.) I am currently running Windows 7.

I have also tried this, as it seems to be the norm that you usually ask when troubleshooting:

1. Unplug your DS3 from USB.
2. Restart the Service (or reboot your PC).
3. Plugin your DS3 to USB.
4. Wait 30 seconds.
5. Unplug your DS3 from USB.
6. Wait 30 seconds.
7. Plugin your DS3 to USB.
8. Wait 30 seconds.
9. Unplug your DS3 from USB.
10. Wait 30 seconds.

Aside from that, I have also tried unplugging and replugging, then reinstalling.

My logs are as attached. [attachment=45786]

Thanks for your time!

(09-30-2013, 02:02 AM)Beep Beep Wrote: [ -> ]Hiya! Great work on your program here! I've been looking for an alternative to MotioninJoy for a while now, and this seems to be a viable answer!

Problem is, that it won't recognize my PS3 Dualshock controller when I connect via USB. (It installs successfully, but I don't see the service running at all. o.o I do not have bluetooth, so that's out of the question for me.) I am currently running Windows 7.

I have also tried this, as it seems to be the norm that you usually ask when troubleshooting:

1. Unplug your DS3 from USB.
2. Restart the Service (or reboot your PC).
3. Plugin your DS3 to USB.
4. Wait 30 seconds.
5. Unplug your DS3 from USB.
6. Wait 30 seconds.
7. Plugin your DS3 to USB.
8. Wait 30 seconds.
9. Unplug your DS3 from USB.
10. Wait 30 seconds.

Aside from that, I have also tried unplugging and replugging, then reinstalling.

My logs are as attached.

Thanks for your time!

If the "SCP DS3 Service" service doesn't start when starting your PC, right click the task bar and open the task manager, then go to the "Services" tab and click the "Services..." button, you should see the "SCP DS3 Service" listed, right click it and choose start. After that you should be able to use your PS3 controller without issues.

hello, can anyone help me identify what the problem is?
i'm using windows 8.1 x86

when i install the driver everything seem fine, all the button works fine



and then i unplugged the usb cable and press ps button, but nothing happen (it wont connect to bluetooth)


when i plug the cable again, it detected as another pad


scp services is running

(09-30-2013, 07:30 AM)Huesoman Wrote: [ -> ]If the "SCP DS3 Service" service doesn't start when starting your PC, right click the task bar and open the task manager, then go to the "Services" tab and click the "Services..." button, you should see the "SCP DS3 Service" listed, right click it and choose start. After that you should be able to use your PS3 controller without issues.

That's the thing, I don't see it at all. Hence I'm unable to "turn it on".