[m42i]

For anyone who has problems with following this guide to update their bluez installation:

Using the latest bluez for PS3 bluetooth (how-to)

the easiest way would be to use my two experimental scripts:
https://raw.githubusercontent.com/m42i/RetroPie-Setup/release/scriptmodules/supplementary/bluez.sh
https://raw.githubusercontent.com/m42i/RetroPie-Setup/release/scriptmodules/supplementary/bluezps3.sh

To get them into your RetroPie-Setup menu use these commands:

cd ~/RetroPie-Setup/scriptmodules/supplementary
sudo wget https://raw.githubusercontent.com/m42i/RetroPie-Setup/release/scriptmodules/supplementary/bluezps3.sh
sudo wget https://raw.githubusercontent.com/m42i/RetroPie-Setup/release/scriptmodules/supplementary/bluez.sh

(I’m not sure you need sudo, but just in case you do)

Now go back to the RetroPi-Setup directory and start the setup as usual

cd ~/RetroPie-Setup
sudo ./retropie-setup.sh

Now you can find two new items under “Experimental packages”. First choose “bluez – Install (PS3) bluetooth controller driver (BLUEZ)”
and then
“bluezps3 – Pair PS3 bluetooth controller (BLUEZ)”

Hopefully this helps.

[m42i]

I’m currently running the latest source and I could get it working editing the file /opt/retropie/configs/all/retroarch.cfg and changing line 387 to

input_libretro_device_p2 = 257

At least for SNES games, for NES games I have yet to find a way.

[m42i]

Thank you for this detailed how-to. I changed the following:

Used /etc/init.d/bluetooth and /etc/defaults/bluetooth from the Debian jessie package:
https://packages.debian.org/jessie/bluez (the .tar.xz file on the right)

With DAEMON= in /etc/init.d/bluetooth pointing to /usr/libexec/bluetooth/bluetoothd.

Added this line to /etc/rc.local:
hciconfig hci0 up pscan

When running bluetoothctl I could trust each controller after plugging it into USB without actually pairing it. Though I had to remove all devices at some point and start over. I think it’s important to disconnect one controller before trusting the next one.

To have the controllers disconnect after 15 minutes of idling I created /etc/bluetooth/input.conf from the Debian package above. But since the axis always send some data it seems it won’t disconnect after all.

[m42i]

In the end I successfully got it working using bluez 5.29 following these instructions:

Using the latest bluez for PS3 bluetooth (how-to)

[m42i]

I did a fresh install of the v2.6 image without updating anything and paired three controllers with sixpair and still only get two connected simultaneously.

Using hcidump I found something interesting. Pairing the first two controllers I get the following:

pi@retropie ~ $ hcidump -r ps3controllerpairing.raw
HCI sniffer - Bluetooth packet analyzer ver 2.4
btsnoop version: 1 datalink type: 1002
> HCI Event: Connect Request (0x04) plen 10
    bdaddr 00:19:C1:D8:79:26 class 0x000508 type ACL
> HCI Event: Command Status (0x0f) plen 4
    Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1
> HCI Event: Connect Complete (0x03) plen 11
    status 0x00 handle 71 bdaddr 00:19:C1:D8:79:26 type ACL encrypt 0x00
> HCI Event: Command Status (0x0f) plen 4
    Read Remote Supported Features (0x01|0x001b) status 0x00 ncmd 0
> HCI Event: Command Status (0x0f) plen 4
    Unknown (0x00|0x0000) status 0x00 ncmd 1
> HCI Event: Read Remote Supported Features (0x0b) plen 11
    status 0x00 handle 71
    Features: 0xfc 0x07 0x82 0x7e 0x08 0x18 0x00 0x80
> HCI Event: Command Status (0x0f) plen 4
    Remote Name Request (0x01|0x0019) status 0x00 ncmd 1
> HCI Event: Remote Name Req Complete (0x07) plen 255
    status 0x00 bdaddr 00:19:C1:D8:79:26 name 'PLAYSTATION(R)3 Controller'
> HCI Event: Connect Request (0x04) plen 10
    bdaddr 00:19:C1:D2:B6:C6 class 0x000508 type ACL
> HCI Event: Command Status (0x0f) plen 4
    Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1
> HCI Event: Connect Complete (0x03) plen 11
    status 0x00 handle 64 bdaddr 00:19:C1:D2:B6:C6 type ACL encrypt 0x00
> HCI Event: Command Status (0x0f) plen 4
    Read Remote Supported Features (0x01|0x001b) status 0x00 ncmd 0
> HCI Event: Command Status (0x0f) plen 4
    Unknown (0x00|0x0000) status 0x00 ncmd 1
> HCI Event: Read Remote Supported Features (0x0b) plen 11
    status 0x00 handle 64
    Features: 0xfc 0x07 0x82 0x7e 0x08 0x18 0x00 0x80
> HCI Event: Command Status (0x0f) plen 4
    Remote Name Request (0x01|0x0019) status 0x00 ncmd 1
> HCI Event: Remote Name Req Complete (0x07) plen 255
    status 0x00 bdaddr 00:19:C1:D2:B6:C6 name 'PLAYSTATION(R)3 Controller'

After that hcidump doesn’t show anything. Even when trying to connect my iPad using PISCAN mode hcidump is still silent.

Disconnecting one controller and trying to pair the iPad again I get:

pi@retropie ~ $ hcidump
HCI sniffer - Bluetooth packet analyzer ver 2.4
device: hci0 snap_len: 1028 filter: 0xffffffff
> HCI Event: Disconn Complete (0x05) plen 4
    status 0x00 handle 71 reason 0x13
    Reason: Remote User Terminated Connection
> HCI Event: Connect Request (0x04) plen 10
    bdaddr B4:F0:AB:XX:XX:XX class 0x6a0110 type ACL
> HCI Event: Command Status (0x0f) plen 4
    Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1
> HCI Event: Connect Complete (0x03) plen 11
    status 0x00 handle 70 bdaddr B4:F0:AB:XX:XX:XX type ACL encrypt 0x00
> HCI Event: Command Status (0x0f) plen 4
    Read Remote Supported Features (0x01|0x001b) status 0x00 ncmd 0
> HCI Event: Command Status (0x0f) plen 4
    Unknown (0x00|0x0000) status 0x00 ncmd 1
> HCI Event: Read Remote Supported Features (0x0b) plen 11
    status 0x00 handle 70
    Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
> HCI Event: Command Status (0x0f) plen 4
    Read Remote Extended Features (0x01|0x001c) status 0x00 ncmd 1
> HCI Event: Read Remote Extended Features (0x23) plen 13
    status 0x00 handle 70 page 1 max 1
    Features: 0x07 0x00 0x00 0x00 0x00 0x00 0x00 0x00
> HCI Event: Command Status (0x0f) plen 4
    Remote Name Request (0x01|0x0019) status 0x00 ncmd 1
> HCI Event: Remote Name Req Complete (0x07) plen 255
    status 0x00 bdaddr B4:F0:AB:XX:XX:XX name 'iPad'
> HCI Event: Disconn Complete (0x05) plen 4
    status 0x00 handle 70 reason 0x13

Could it be that my dongle isn’t capable of more than two connections? I have:
Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

[m42i]

[quote=87755]All of you controllers are paired? meaning you can get all of them to connect to retropie one at a time? You can get two at the same time at the most?[/quote]

This is my exact problem currently. For the first and second controller I’m pairing via sixad over bluetooth I get this in the logs:

Mar 31 15:12:40 tarantula kernel: [   54.318800] input: PLAYSTATION(R)3 Controller (00:19:C1:D8:79:26) as /devices/virtual/input/input0
Mar 31 15:12:50 tarantula kernel: [   64.225794] input: PLAYSTATION(R)3 Controller (00:06:F7:59:E0:AE) as /devices/virtual/input/input1

And I get js0 and js1 in /dev/input/. After I disconnect one controller (holding PS button >12 sec) and pair a third one I get:

Mar 31 15:14:04 tarantula kernel: [  138.389150] input: PLAYSTATION(R)3 Controller (04:76:6E:EF:33:09) as /devices/virtual/input/input2

But inside /dev/input I still only have js0 and js1.

[quote]
Have you ran an updated retropie_setup.sh and installed ps3 controller (from the setup script)?[/quote]
Yes, I’m using commit #4f210c3909.

Though when I go through the dialogs, the setup doesn’t recognize my PS3 pad being plugged into USB. But lsusb shows it as
[code]Bus 001 Device 005: ID 054c:0268 Sony Corp. Batoh Device / PlayStation 3 Controller"[/code]

[quote]
after pairing 2 controllers when you run hciconfig what does it return?
[/quote]

pi@tarantula ~/RetroPie-Setup $ hciconfig
hci0:   Type: BR/EDR  Bus: USB
        BD Address: 00:1A:7D:DA:71:0C  ACL MTU: 310:10  SCO MTU: 64:8
        UP RUNNING PSCAN
        RX bytes:9013087 acl:155439 sco:0 events:263 errors:0
        TX bytes:6677 acl:166 sco:0 commands:72 errors:0

[Author]

Posts