Forum Replies Created

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • diliegrOS
    Participant

    Hi exonerated, I will not have access to my Raspberry until Monday, so it will be difficult to me to do some tests. Anyway I will try to help. I don’t know if having a PS3 controller synced should be a problem, but it can be.

    What I can see from your commands is that the BT MAC that you are using to delete the PS3 controller is the BT USB dongle MAC, not the controller MAC, that must be the problem. When you run hciconfig you can see the proprieties of the BT USB interface, it is needed to know only the number of the device, in your case it is “hci0”, the MAC that is displayed there is the dongle MAC, not the PS3 controller MAC that you may need to remove.

    If you have your PS3 controller with you, you can get its MAC doing the “hcitools scan” command and by put the controller in paring mode. That’s the MAC you have use in the bluez-simple-agent command.

    If that doesn’t work, it could be better if you try on a clean RetroPie to avoid any sort of problems. ;)

    diliegrOS
    Participant

    Hi exonerated, you are completely right, the correct file to edit is /etc/rc.local, it is already changed in the tutorial.

    About the problem of connection, (and sorry for my English): There is a solution for that. The problem seems to happen when the controller is paired to the BT dongle in the Raspberry, disconnected, paired on another device, and then paired again to the Raspberry. I think it happens because Bluez has some kind of bug.

    Anyway, to fix that you need to delete the controller pair data, you need python-gobject, so:

    sudo apt-get install python-gobject

    And then:

    bluez-simple-agent hciX XX:XX:XX:XX:XX:XX remove

    Where X in hciX is the number of your BT device, usually 0 (hci0), check it with:

    hciconfig

    And XX:XX:XX:XX:XX:XX is the DS4 MAC, that you can get with:

    hcitool scan

    Once you do the bluez-simple-agent command, you can try ds4drv again, it should connect:

    pi@raspberrypi ~ $ ds4drv –led 000008
    [info][controller 1] Created devices /dev/input/js0 (joystick) /dev/input/event0 (evdev)
    [info][bluetooth] Scanning for devices
    [info][bluetooth] Found device A4:15:66:4E:CA:53
    [info][controller 1] Connected to Bluetooth Controller (A4:15:66:4E:CA:53)
    [info][bluetooth] Scanning for devices
    [info][controller 1] Battery: 75%
    [warning][controller 1] Signal strength is low (48 reports/s)

Viewing 2 posts - 1 through 2 (of 2 total)