Yet More PS3 Bluetooth Woes......

Wolfman100

The controller is paired and Emulation Station detects the Gamepad.

I have done a test to see if the controls are being detected as I learnt from @Floob video.This was achieved by the following:

osmc@Blackbox:~$ ls /dev/input
by-id by-path event0 event1 event2 event3 js0 mice
osmc@Blackbox:~$ jstest /dev/input/js0
Driver version is 2.1.0.
Joystick (PLAYSTATION(R)3 Controller) has 27 axes (X, Y, Z, Rz, (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null))
and 19 buttons (Trigger, ThumbBtn, ThumbBtn2, TopBtn, TopBtn2, PinkieBtn, BaseBtn, BaseBtn2, BaseBtn3, BaseBtn4, BaseBtn5, BaseBtn6, BtnDead, BtnA, BtnB, BtnC, (null), (null), (null)).
Testing ... (interrupt to exit)

As you can see the controller is recognised as a Playstation 3 controller and all it's buttons etc are seen.

The catch however is that when I push any of the buttons on the controller they do not show up in the JsTest.This I'm assuming is why Emulation Station is not registering the button presses....

Anyone got any idea what might be causing this issue?

BuZz

you might need to add a udev rule for it

create a file /etc/udev/rules.d/99-local.rules

containing

SUBSYSTEM=="input", ATTRS{name}=="YOUR DEVICE NAME", MODE="0666", ENV{ID_INPUT_JOYSTICK}="1"

the name should show up when doing

for dev in $(find /dev/input -name "event*" | sort); do path=$(udevadm info --name=$dev | grep DEVPATH | cut -d= -f2); name=$(</$(dirname sys$path)/name); echo $name; ((i++)); done

Wolfman100

Thanks @BuZz .Will try that now :)

Wolfman100

@BuZz I've tried that.I get the following response:

Apple, Inc Apple Keyboard
Apple, Inc Apple Keyboard
lircd
PLAYSTATION(R)3 Controller

Upon doing jstest again,I still get no response to the buttons being pushed though....

BuZz

the second command just lists all your input devices to get the right name. You need to take PLAYSTATION(R)3 Controller and put it where it says YOUR DEVICE NAME in the udev file. Did you do that, and reboot ?

Wolfman100

@BuZz I just created a Udev rule from inside the RetroPie>configure bluetooth options and assigned it to the Playstation 3 Controller...

Lets see what happens

Wolfman100

@BuZz No joy.Holding the button on controller but nothing happens.It says '1 Gamepad detected' and the controller is solidly paired.Puzzled

BuZz

It might just be incompatible.

mediamogul

@Wolfman100

Do you get any feedback using evtest?

Wolfman100

@BuZz Could that really be the case??

This is craaaaazy.

Wolfman100

@mediamogul what is evtest?

mediamogul

Your controller should register as an event at /dev/input/event*. From the command line, run evtest /dev/input/event*on each numbered event until you find the one belonging to your controller. You'll know it's the correct event when you receive input feedback when pressing one of the controller's buttons. If none of them register feedback, then I'd say it's a lost cause. If one does, you can map that feedback to a virtual controller device that should allow everything to function properly. I'll elaborate on that process further if you can find a functioning event*.

Wolfman100

@mediamogul said in Yet More PS3 Bluetooth Woes......:

evetest /dev/input/event*

Under '/dev/input' I get the following:

'by-id by-path event0 event1 event2 event4 js0 mice'

js0 is the Playstation3 controller

I have done 'jstest /dev/input/js0', which gives me the following:

Driver version is 2.1.0.
Joystick (PLAYSTATION(R)3 Controller) has 27 axes (X, Y, Z, Rz, (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null))
and 19 buttons (Trigger, ThumbBtn, ThumbBtn2, TopBtn, TopBtn2, PinkieBtn, BaseBtn, BaseBtn2, BaseBtn3, BaseBtn4, BaseBtn5, BaseBtn6, BtnDead, BtnA, BtnB, BtnC, (null), (null), (null)).
Testing ... (interrupt to exit)

followed by all the controls,axis,buttons etc etc

I am no sure what you mean by doing evetest /dev/input/event.If I enter 'evetest /dev/input/event1' for example,it says no command found.

mediamogul

@Wolfman100 said in Yet More PS3 Bluetooth Woes......:

I enter 'evetest /dev/input/event1' for example,it says no command found.

I meant to type evtest, sorry. Hectic day so far. I corrected it above as well.

Wolfman100

@mediamogul No probs...but it must be even more hectic than you think yourself,because command still not found!

mediamogul

@Wolfman100

I would try it again to be sure. evtest is part of a larger package of device testing components included by default in RetroPie.

Wolfman100

@mediamogul My RteroPie is installed under OSMC,maybe that's got something to do with it?

BuZz

using RetroSMC ? Or manually ? Did you exit Kodi ? RetroSMC have their own support thread on the OSMC forum. You should mention details like this when posting as mentioned on https://retropie.org.uk/forum/topic/3/read-this-first

Wolfman100

@BuZz Yes,apolagies.....it is RetrOSMC.

I am connected via SSH and after everychange I am rebooting RetroPi

BuZz

Not sure I can advise, but you need to make sure Kodi isn't running when you launch ES, or it won't be able to read any input devices AFAIR. have you asked for help on the RetroSMC OSMC thread ?