renderking
Posts: 3
Joined: Thu Jun 27, 2013 4:10 pm

Re: PS3 Controller and the PI

Thu Jun 27, 2013 4:18 pm

Same problem here... genuine PS3 controller w/gbu521 bluetooth dongle connected directly to pi's usb port.

Any thoughts/updates to this?

[email protected] ~ $ sudo sixad --stop
[email protected] ~ $ sudo sixad --start
sixad-bin[2675]: started
sixad-bin[2675]: sixad started, press the PS button now
sixad-bin[2675]: unable to connect to sdp session
sixad-bin[2675]: Connected Sony Computer Entertainment Wireless Controller (00:19:C1:CF:21:C4)

and there she hangs, matey

jstest runs and interrupts joystick commands no problem.

funkbuqet
Posts: 6
Joined: Mon Aug 12, 2013 2:15 am

Re: PS3 Controller and the PI

Mon Aug 12, 2013 2:33 am

Sorry to resurrect this older post, but has anyone found a solution for this?

I get the same messages as above and it is connecting as a joystick, but for some reason advancemame will not recognize the cross, circle, or triangle buttons when i try to assign them. When running jstest or hidraw-dump all of the buttons certainly seem to be providing input.

I created a default config file & a mac address specific config file, as detailed in the sixad manual, that tells it not to use joystick mode and maps the button presses to standard keyboard input. But sixad does not seem to be interested in using them. I tried a few different ownerships/permissions on the files to no avail. Has anyone successfully implemented a custom sixad config file?

hismajesty
Posts: 1
Joined: Fri Sep 20, 2013 5:19 pm

Re: PS3 Controller and the PI

Fri Sep 20, 2013 5:22 pm

Have tried lots of things to avoid this bug but the only thing I found is to switch to Arch. Works like a charm there.
Even the most recent Raspbian version fails.

Had the same problem, but with a non-original controller (snakebyte).

Russ_T
Posts: 8
Joined: Fri Sep 20, 2013 8:28 pm

Re: PS3 Controller and the PI

Sat Sep 21, 2013 12:07 am

Anyone solve this yet please? Trying to get my controller working with pimame.

Thanks

brian9640
Posts: 1
Joined: Sat Sep 28, 2013 12:48 pm

Re: PS3 Controller and the PI

Sat Sep 28, 2013 1:05 pm

The error message "unable to connect to sdp session" is because the newer version of bluetoothd is not running the sdp socket in udev mode. Running the bluetoothd daemon without '--udev' will not allow the PS3 controller to connect. I believe it has to do with the protocol Sony is using. The sdp session is used by sixad to determine which controller type is connected over bluetooth. If anyone wants to research how to get the sdp running in udev mode please do.

For myself I modified the source code to ignore the controller type. Since I'm only using a PS3 controller I don't care about the others. Here is how to modify the code. Assuming you already have the source code installed.

In directory 'QtSixA-1.5.1/sixad' edit the file 'bluetooth.cpp'. Change line #218 in the 'l2cap_accept' function.

OLD:
if (!legacy && req.vendor == 0x054c && req.product == 0x0268) {
NEW:
if (!legacy) {

Next run the 'make' command. Followed by the 'sudo make install' command.

Remember to restart the service or reboot the RPi.

renderking
Posts: 3
Joined: Thu Jun 27, 2013 4:10 pm

Re: PS3 Controller and the PI

Fri Oct 04, 2013 5:50 am

[email protected] ~/.emulationstation $ sudo sixad --start
sixad-bin[2506]: started
sixad-bin[2506]: sixad started, press the PS button now
sixad-bin[2506]: unable to connect to sdp session
sixad-sixaxis[2511]: started
sixad-sixaxis[2511]: Connected 'PLAYSTATION(R)3 Controller (00:19:C1:CF:21:C4)' [Battery 05]


Pi connects to the ps3 controller via bluetooth, but then hangs at above. The only way to get back to prompt is to send ctrl break. Not sure if I missed something within instructions, so I'll further review, maybe tomorrow.

renderking
Posts: 3
Joined: Thu Jun 27, 2013 4:10 pm

Re: PS3 Controller and the PI

Fri Oct 04, 2013 4:09 pm

@ brian9640 SUCCESS!! My config files were so tweaked from other attempts, that I started with a fresh install this morning, and brian9640 solution worked for me. PS3 connects with my bluetooth adapter without issue. Thanks brian9640 for sharing!

Russ_T
Posts: 8
Joined: Fri Sep 20, 2013 8:28 pm

Re: PS3 Controller and the PI

Mon Oct 07, 2013 9:17 pm

Thank you very much Brian! I would never have thought to solve it that way.

Now all I need to do is get the PS3 controller working in PiSNES stop my sound hissing when I exit it and I'm there :)

Aergan
Posts: 1
Joined: Sun Dec 08, 2013 5:34 pm

Re: PS3 Controller and the PI

Sun Dec 08, 2013 6:24 pm

brian9640 wrote:The error message "unable to connect to sdp session" is because the newer version of bluetoothd is not running the sdp socket in udev mode. Running the bluetoothd daemon without '--udev' will not allow the PS3 controller to connect. I believe it has to do with the protocol Sony is using. The sdp session is used by sixad to determine which controller type is connected over bluetooth. If anyone wants to research how to get the sdp running in udev mode please do.

For myself I modified the source code to ignore the controller type. Since I'm only using a PS3 controller I don't care about the others. Here is how to modify the code. Assuming you already have the source code installed.

In directory 'QtSixA-1.5.1/sixad' edit the file 'bluetooth.cpp'. Change line #218 in the 'l2cap_accept' function.

OLD:
if (!legacy && req.vendor == 0x054c && req.product == 0x0268) {
NEW:
if (!legacy) {

Next run the 'make' command. Followed by the 'sudo make install' command.

Remember to restart the service or reboot the RPi.
That's worked for me, many thanks!

itsmedoofer
Posts: 362
Joined: Wed Sep 25, 2013 8:43 am

Re: PS3 Controller and the PI

Tue Jan 07, 2014 1:52 pm

Hi,

I've previously tried to get the PS3 controller to work and failed miserably, being as it was a curiosity project I gave up. However I now need it to work for an actual project so will try again with brian9640's suggestion......

However I did come across this and thought it would be worth a pop before hand, any suggestions ?

http://ubuntuforums.org/showthread.php? ... st10953009

Old topic I know but still valid I feel....

itsmedoofer
Posts: 362
Joined: Wed Sep 25, 2013 8:43 am

Re: PS3 Controller and the PI

Sun Jan 12, 2014 4:19 pm

Bit of feedback.

Tried the above and it didn't work, worth a pop.

Piwel
Posts: 1
Joined: Wed Jan 29, 2014 7:41 pm

Re: PS3 Controller and the PI

Wed Jan 29, 2014 7:44 pm

Hi!
I'm having trouble to get my ps3 controllers (2 controllers) to work in emulationstation....
both controllers are paired with rpi and i see the response of the keys in jstest.
i followed the tutorials step by step but still it won't work in emulationstation....

could anyone please help me to get this to work.... :?

thx

wonx
Posts: 22
Joined: Tue Aug 07, 2012 11:00 am
Location: Barcelona

Re: PS3 Controller and the PI

Sat Feb 01, 2014 5:52 pm

Hello,

I am having trouble configuring my generic PS3 controller via bluetooth. At first I tried with the regular method until I got the "unable to connect to sdp session" error. I edited the bluetooth.cpp file according to brian9640's instructions and now the controller seems to pair, because the leds stop blinking and just the 1st one is lit, although the controller starts vibrating and it doesn't stop. It literally can vibrate for minutes, or until I kill the sixad process.

I am sorry if it's a long post, but I want to provide as much information as possible.

When I run sixad --start (in verbose mode), this is what I get.

Code: Select all

[email protected] ~ $ sudo /usr/bin/sixad --start
sixad-bin[2863]: started
sixad-bin[2863]: sixad started, press the PS button now
sixad-bin[2863]: Server mode active, will start search now
sixad-bin[2863]: One event received
sixad-bin[2863]: unable to connect to sdp session
sixad-bin[2863]: Will initiate Sixaxis now
sixad-bin[2863]: One event proccessed
sixad-sixaxis[2869]: started
And I wait a few minutes without doing anything, the controller stops vibrating (and all the leds turn off) and this is what appears in the console screen:

Code: Select all

sixad-sixaxis[3428]: Connected 'PLAYSTATION(R)3 Controller (00:1E:3D:DE:41:02)' [Battery 00]
sixad-sixaxis[3428]: Read loop was broken on the Sixaxis process
sixad-sixaxis[3428]: Closing uinput...
sixad-sixaxis[3428]: uinput_close()::ioctl(UI_DEV_DESTROY) - success!
sixad-sixaxis[3428]: uinput_close()::close(fd) - success!
sixad-sixaxis[3428]: Done

Simultaneously, I run hcidump to monitor the bluetooth traffic. Note how the controller pairs and at the end of the code I can see the hexadecimal values of each button, which change when pressed, meaning that the keystrokes are being sent by bluetooth. During all this time, my controller keeps vibrating:

Code: Select all

[email protected] ~ $ sudo hcidump -t -x

HCI sniffer - Bluetooth packet analyzer ver 2.4
device: hci0 snap_len: 1028 filter: 0xffffffff

2014-02-01 17:23:53.923443 > HCI Event: Connect Request (0x04) plen 10
    bdaddr 00:1E:3D:DE:41:02 class 0x001f00 type ACL
2014-02-01 17:23:53.923554 < HCI Command: Accept Connection Request (0x01|0x0009) plen 7
    bdaddr 00:1E:3D:DE:41:02 role 0x00
    Role: Master
2014-02-01 17:23:53.927545 > HCI Event: Command Status (0x0f) plen 4
    Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1
2014-02-01 17:23:54.112463 > HCI Event: Role Change (0x12) plen 8
    status 0x00 bdaddr 00:1E:3D:DE:41:02 role 0x00
    Role: Master
2014-02-01 17:23:54.125450 > HCI Event: Connect Complete (0x03) plen 11
    status 0x00 handle 42 bdaddr 00:1E:3D:DE:41:02 type ACL encrypt 0x00
2014-02-01 17:23:54.125698 < HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
    handle 42
2014-02-01 17:23:54.126471 > HCI Event: Page Scan Repetition Mode Change (0x20) plen 7
    bdaddr 00:1E:3D:DE:41:02 mode 1
2014-02-01 17:23:54.137480 > HCI Event: Command Status (0x0f) plen 4
    Read Remote Supported Features (0x01|0x001b) status 0x00 ncmd 1
2014-02-01 17:23:54.140482 > ACL data: handle 42 flags 0x02 dlen 12
    L2CAP(s): Connect req: psm 17 scid 0x00ee
2014-02-01 17:23:54.141133 < ACL data: handle 42 flags 0x02 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0040 scid 0x00ee result 1 status 0
      Connection pending - No futher information available
2014-02-01 17:23:54.141160 < ACL data: handle 42 flags 0x02 dlen 10
    L2CAP(s): Info req: type 2
2014-02-01 17:23:54.144484 > HCI Event: Number of Completed Packets (0x13) plen 5
    handle 42 packets 1
2014-02-01 17:23:54.146576 > HCI Event: Number of Completed Packets (0x13) plen 5
    handle 42 packets 1
2014-02-01 17:23:54.148477 > HCI Event: Read Remote Supported Features (0x0b) plen 11
    status 0x00 handle 42
    Features: 0xfc 0x07 0x82 0x7a 0x08 0x18 0x00 0x80
2014-02-01 17:23:54.148574 < HCI Command: Remote Name Request (0x01|0x0019) plen 10
    bdaddr 00:1E:3D:DE:41:02 mode 2 clkoffset 0x0000
2014-02-01 17:23:54.154478 > HCI Event: Command Status (0x0f) plen 4
    Remote Name Request (0x01|0x0019) status 0x00 ncmd 1
2014-02-01 17:23:54.191481 > HCI Event: Remote Name Req Complete (0x07) plen 255
    status 0x00 bdaddr 00:1E:3D:DE:41:02 name 'PLAYSTATION(R)3Conteroller-ghic'
2014-02-01 17:23:58.153045 < ACL data: handle 42 flags 0x02 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0040 scid 0x00ee result 0 status 0
      Connection successful
2014-02-01 17:23:58.153418 < ACL data: handle 42 flags 0x02 dlen 16
    L2CAP(s): Config req: dcid 0x00ee flags 0x00 clen 4
      MTU 64 
2014-02-01 17:23:58.156872 > HCI Event: Number of Completed Packets (0x13) plen 5
    handle 42 packets 1
2014-02-01 17:23:58.158880 > HCI Event: Number of Completed Packets (0x13) plen 5
    handle 42 packets 1
2014-02-01 17:23:58.181886 > ACL data: handle 42 flags 0x02 dlen 12
    L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 0
2014-02-01 17:23:58.181999 < ACL data: handle 42 flags 0x02 dlen 18
    L2CAP(s): Config rsp: scid 0x00ee flags 0x00 result 0 clen 4
      MTU 672 
2014-02-01 17:23:58.186904 > HCI Event: Number of Completed Packets (0x13) plen 5
    handle 42 packets 1
2014-02-01 17:23:58.195894 > ACL data: handle 42 flags 0x02 dlen 14
    L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
      Success
2014-02-01 17:23:58.198884 > ACL data: handle 42 flags 0x02 dlen 12
    L2CAP(s): Connect req: psm 19 scid 0x00ef
2014-02-01 17:23:58.199058 < ACL data: handle 42 flags 0x02 dlen 16
    L2CAP(s): Connect rsp: dcid 0x0041 scid 0x00ef result 0 status 0
      Connection successful
2014-02-01 17:23:58.199080 < ACL data: handle 42 flags 0x02 dlen 16
    L2CAP(s): Config req: dcid 0x00ef flags 0x00 clen 4
      MTU 64 
2014-02-01 17:23:58.204886 > HCI Event: Number of Completed Packets (0x13) plen 5
    handle 42 packets 1
2014-02-01 17:23:58.205878 > HCI Event: Number of Completed Packets (0x13) plen 5
    handle 42 packets 1
2014-02-01 17:23:58.224915 > ACL data: handle 42 flags 0x02 dlen 36
    L2CAP(s): Config req: dcid 0x0041 flags 0x00 clen 24
      QoS 0x02 (Guaranteed) 
2014-02-01 17:23:58.225056 < ACL data: handle 42 flags 0x02 dlen 18
    L2CAP(s): Config rsp: scid 0x00ef flags 0x00 result 0 clen 4
      MTU 672 
2014-02-01 17:23:58.229912 > HCI Event: Number of Completed Packets (0x13) plen 5
    handle 42 packets 1
2014-02-01 17:23:58.237898 > ACL data: handle 42 flags 0x02 dlen 14
    L2CAP(s): Config rsp: scid 0x0041 flags 0x00 result 0 clen 0
      Success
2014-02-01 17:23:59.261119 < ACL data: handle 42 flags 0x02 dlen 10
    L2CAP(d): cid 0x00ee len 6 [psm 17]
      HIDP: Set report: Feature report
      F4 42 03 00 00 
2014-02-01 17:23:59.266060 > HCI Event: Number of Completed Packets (0x13) plen 5
    handle 42 packets 1
2014-02-01 17:23:59.289061 > ACL data: handle 42 flags 0x02 dlen 5
    L2CAP(d): cid 0x0040 len 1 [psm 17]
      HIDP: Handshake: Successful
2014-02-01 17:23:59.290549 < ACL data: handle 42 flags 0x02 dlen 41
    L2CAP(d): cid 0x00ee len 37 [psm 17]
      HIDP: Set report: Output report
      01 00 FE FF FE FF 00 00 00 00 02 FF 27 10 00 32 FF 27 10 00 
      32 FF 27 10 00 32 FF 27 10 00 32 00 00 00 00 00 
2014-02-01 17:23:59.296139 > HCI Event: Number of Completed Packets (0x13) plen 5
    handle 42 packets 1
However, even if jstest seems to show that some kind of controller exists, it doesn't register any of the keystrokes on the controller:

Code: Select all

[email protected] ~ sudo jstest /dev/input/js0

Driver version is 2.1.0.
Joystick (PLAYSTATION(R)3 Controller (00:1E:3D:DE:41:02)) has 29 axes (X, Y, Z, Rx, Ry, Rz, Throttle, Rudder, Wheel, Gas, Brake, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, (null), (null), (null), (null), (null), (null), (null), (null))
and 17 buttons (Trigger, ThumbBtn, ThumbBtn2, TopBtn, TopBtn2, PinkieBtn, BaseBtn, BaseBtn2, BaseBtn3, BaseBtn4, BaseBtn5, BaseBtn6, BtnDead, BtnA, BtnB, BtnC, BtnX).
Testing ... (interrupt to exit)

Axes:  0:     0  1:     0  2:     0  3:     0  4:-32767  5: 32767  6: 32767  7:     0  8:     0  9:     0 10:     0 11:     0 12:     0 13:     0 14:     0 15:     0 16:     0 17:     0 18:     0 19:     0 20:     0 21:     0 22:     0 23:     0 24:     0 25:     0 26:     0 27:     0 28:     0 Buttons:  0:off  1:off  2:off  3:off  4:off  5:off  6:off  7:off  8:off  9:off 10:off 11:off 12:off 13:off 14:off 15:off 16:off 
By the way, I forgot to mention that plugging the controller via USB seems to work. Also, I tried to pair it with my Ubuntu laptop with similar results (unable to connect to sdp session, etc.). As I said before, I do not own a genuine ps3 controller but a cheap one I got on ebay. It gets recognised as SHENGHIC 2009/0708ZXW-V1Inc. PLAYSTATION(R)3Conteroller.

So, is there a problem with my controller, QtSixA-1.5.1 or both? Since I can see the keystrokes in hcidump, I know the controller is working, but needs to be configured someway.

Any information that could help me troubleshoot the problem will be greatly appreciated!

arentz
Posts: 1
Joined: Sat Feb 15, 2014 12:03 pm

Re: PS3 Controller and the PI

Sat Feb 15, 2014 12:19 pm

Hi,

I am experiencing almost exactly the same problems with my China-PS3 controllers. However, it was possible to get rid of the vibration, by adding "enable_rumble 0" to the /var/lib/sixad/profiles/default.

I also noticed with hcidump that the controller is connecting properly. The data is flowing across and the hex-values change as I push different buttons.

The connection is not dropping either, so the big question is how do I get the bluetooth data out on a hid device file. For some reason the driver (sixad-bin) is not passing the bluetooth data on to /dev/uinput so there is no data for sixad-sixaxis to pass on to /dev/input/js0 (if I understood the source code correctly)

Any idea of how to move forward with troubleshooting this would be greatly appreciated.

debauchery1st
Posts: 1
Joined: Mon Feb 17, 2014 12:31 am

Re: PS3 Controller and the PI

Mon Feb 17, 2014 12:49 am

by arentz » Sat Feb 15, 2014 12:19 pm
Hi,

I am experiencing almost exactly the same problems with my China-PS3 controllers. However, it was possible to get rid of the vibration, by adding "enable_rumble 0" to the /var/lib/sixad/profiles/default.

I also noticed with hcidump that the controller is connecting properly. The data is flowing across and the hex-values change as I push different buttons.

The connection is not dropping either, so the big question is how do I get the bluetooth data out on a hid device file. For some reason the driver (sixad-bin) is not passing the bluetooth data on to /dev/uinput so there is no data for sixad-sixaxis to pass on to /dev/input/js0 (if I understood the source code correctly)

Any idea of how to move forward with troubleshooting this would be greatly appreciated.

Seems I'm stuck in the same exact situation as arentz.
bought some cheap PS3 from China, the hardware name shows up as PLAYSTATION(R)3Conteroller-ghic

I think some code modifications may be the only way to get these "conterollers" to register correctly as a peripheral device. I was looking through uinput.cpp last night, but didn't make much progress. I did find this page http://apple.stackexchange.com/question ... -bluetooth where someone is having a similar problem in OSX.

thoughts?

insertvodkahere
Posts: 1
Joined: Tue May 13, 2014 11:49 am

Re: PS3 Controller and the PI

Tue May 13, 2014 12:07 pm

Sorry for reviving the thread but... No one got a fix for this? :( I mean, my controller pair but just vibrates, cant get a single input from it :(

wonx
Posts: 22
Joined: Tue Aug 07, 2012 11:00 am
Location: Barcelona

Re: PS3 Controller and the PI

Thu Jun 19, 2014 10:50 pm

Bump.

Any news on this issue? I'm still trying to pair my knock-off controller without the USB cable...

inlinechan
Posts: 1
Joined: Sun Sep 14, 2014 2:09 am

Re: PS3 Controller and the PI

Sun Sep 14, 2014 2:35 am

I'm using Model B+ and updated firmware by rpi-update.
For me, PS3 controller(genuine) was not correctly paired while keeping blinking LEDs.
I found the solution, so I like to share.

As QtSixA's document says, it is not paired with sixad's one but with default linux's one. http://qtsixa.sourceforge.net/manual.pdf
The Sixaxis in Linux
The sixaxis works out-of-the box in Linux; just get yourself an USB cable, connect the sixaxis to the computer, and
press the 'PS' button on the sixaxis to activate it.
You won't get all sixaxis features this way though – leds will keep blinking, accelerometers and rumble won't work.
Note: when connected over USB the sixaxis leds will stop blinking when the internal battery is fully charged.
The 3in1 KeyMote also works by default. Just connect the dock over usb, hold the PS button on the keymote.
You can use 'sixad-3in1' to get extra functionality.
There is already work in progress to make the leds and rumble work by default in Linux, it's just a matter of time now.
Same thing applies to bluetooth too (through BlueZ).
QtSixA solves this by implementing a custom driver (based on linux uinput) that supports leds, accelerometers and
rumble. The default way to handle sixaxis in QtSixA is bluetooth, but it can be used for USBas well (no leds or rumble
support though).
I installed sixad by the one from retropie-setup.sh which build sixad with CC=g++-4.6 but failed.
So I followed instructions in https://github.com/petrockblog/RetroPie ... controller and it stops blinking LEDs and finally paired correctly.

The only difference is overriding CC and include <unistd.h>, I have no idea why this happen.

1. It's worth to read the documentation of QtSixA
2. Blinking LEDs means that it was not paired sixad but with linux's default one.
3. Try https://github.com/petrockblog/RetroPie ... controller

Thanks.

rberg
Posts: 5
Joined: Sun Jan 04, 2015 9:42 pm

Re: PS3 Controller and the PI

Sun Jan 04, 2015 9:51 pm

Brian9640's patch worked like a charm, thanks Brian :)

I will assemble a guide how to setup limelight (remote streaming of games running on your PC on the PI) and the PS3 dual shock controller on my private Wiki: http://embedded-software-architecture.c ... spberry_Pi Probably I will add a .patch-file for brian9640's fix and the wget-patch-commands for installing it.

(For beginners: Don't forget to call make and sudo make-install again after the patch ;) ... )

Regards,
Roelof

rberg
Posts: 5
Joined: Sun Jan 04, 2015 9:42 pm

Re: PS3 Controller and the PI

Wed Jan 14, 2015 10:46 pm

I gave up installing the PS3 controller and use an xbox (USB for PC) controller instead.

My guide for the PS3 controller (unfinished): http://embedded-software-architecture.c ... _limelight
My guide for an xbox controller: http://embedded-software-architecture.c ... spberry_Pi (Chapter 'Connect an xbox controller')

eytan
Posts: 13
Joined: Mon Jan 26, 2015 1:01 am
Location: Ottawa Canada

Re: PS3 Controller and the PI

Sat Jan 31, 2015 1:39 am

Brian 9640 fix worked perfectly. My controller is now connected and working according to jstest.
My question may be silly ( and not in the right place ) but I can't find anything online, Now that I have the PS3 controller connected, how do I use it as an input in my python program ???
-edit-
OK, as soon as i posted, I found link to pygame to interface joystick into python environment. Works like a charm.

User avatar
cyryllo
Posts: 5
Joined: Thu May 17, 2012 6:38 am
Location: Gdansk/Poland
Contact: Website

Re: PS3 Controller and the PI

Wed Mar 04, 2015 8:28 am

I have

Code: Select all

sixad started, press the PS button now
sixad-bin[2107]: unable to connect to sdp session
sixad-sixaxis[2111]: started
And I can't connect my pad.

I use Brian9640 fix and still not work

edit:
Pad pair only when i push PS button. When the lights are flashing I have connection. When go out flashing after a while also lose the connection to Pad.

Dynamicduck
Posts: 1
Joined: Wed Jul 01, 2015 12:31 pm

Re: PS3 Controller and the PI

Wed Jul 01, 2015 12:35 pm

I think you have to attach the controller via USB the first time and run "sixpair". Try watching this video https://www.youtube.com/watch?v=C2yKiMx ... el=quidsup.

ryangro5h5
Posts: 2
Joined: Wed Sep 21, 2016 3:22 pm

Re: PS3 Controller and the PI

Wed Sep 21, 2016 3:27 pm

For the sake of google searchers everywhere. I picked up a "FiveStar" PS3 clone controller pair for $20 on Amazon. They recognize as gaisa controllers on an RP3. I could not get the native bluetooth stack to recognize the controller OR the retropie default sixaxis driver to recognize the controller. A combination of luetzel's bluetooth build and supertypo's qtsixa github repo were the trick. A couple of notes though-- I removed bluez native which removes bluetooth-pi3, you have to install the luetzel bluez package from "make install", then reinstall package bluetooth-pi3. Remove any old sixaxis and install sypertypo's version sixaxis and utils. You do this by going into the sixaxis directory and utils directory and doing a make/make install. Finally add a 5 second delay to sixaxis start in /etc/init.d/sixaxis because the pi3 bluetooth detection is slow and sixaxis won't find the bluetooth adapter on startup if you don't.

ryangro5h5
Posts: 2
Joined: Wed Sep 21, 2016 3:22 pm

Re: PS3 Controller and the PI

Thu Sep 22, 2016 12:40 am

I might have said this...but it worked well for the cheapest controlers I could get online.

I picked up a "FiveStar" PS3 clone controller pair for $20 on Amazon. They recognize as gaisa controllers on an RP3. I could not get the native bluetooth stack to recognize the controller OR the retropie default sixaxis driver to recognize the controller. A combination of luetzel's bluetooth build and supertypo's qtsixa github repo were the trick. A couple of notes though-- I removed bluez native which removes bluetooth-pi3, you have to install THIS bluez package from "make install", then reinstall package bluetooth-pi3. Remove any old sixaxis and install sypertypo's version sixaxis and utils. You do this by going into the sixaxis directory and utils directory and doing a make/make install. Finally add a 5 second delay to sixaxis start in /etc/init.d/sixaxis because the pi3 bluetooth detection is slow and sixaxis won't find the bluetooth adapter on startup if you don't.

Return to “Gaming”