PiHut controller button mapping problem

[ralphhughes]

Good morning,

I've bought the PiHut 2.4Ghz wireless controller from here . I'm connecting this to a Raspberry Pi Zero W mounted on my robot.

$ dmesg detects it as a "ShanWan PC/PS3/Android" controller:

[ 4496.194008] usb 1-1: New USB device found, idVendor=2563, idProduct=0575, bcdDevice= 2.00
[ 4496.194036] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 4496.194049] usb 1-1: Product: PC/PS3/Android
[ 4496.194060] usb 1-1: Manufacturer: ShanWan
[ 4496.217141] input: ShanWan PC/PS3/Android as /devices/platform/soc/20980000.usb/usb1/1-1/1-1:1.0/0003:2563:0575.0001/input/input0
[ 4496.218858] hid-generic 0003:2563:0575.0001: input,hidraw0: USB HID v1.10 Gamepad [ShanWan PC/PS3/Android] on usb-20980000.usb-1/input0

I've installed your excellent python library, and then attempted to write a python script to control the BrickPi3 hat on my robot using the wireless controller. I eventually concluded that the button mappings are all wrong, none of the circle, square, cross, triangle buttons map correctly. The left trigger maps to select, select maps to l2, l1 maps to triangle etc. In addition both analogue sticks seem to have large dead\hot zones covering over 50% of the analogue sticks range, although I don't know if this is a hardware quality issue.

To exclude my code, I've cloned your repo and run python3 scripts/show_controls.py and it shows the same incorrect mappings for my controller. I'm willing to try and debug\write code\submit a pull request, however I'm primarily a Java programmer and my python code is at beginner level! Could you point me in the right direction as to how to start debugging this?

Many thanks!

[tomoinn]

Hi,

Firstly thanks for an excellent issue description! I've just released version 2.6.0 which takes a somewhat different approach to adding controllers. You should hopefully be able to create a profile for your particular controller by updating the library, then using https://approxeng.github.io/approxeng.input/profiling.html to build a profile for it, if you chuck me the resultant profile file I can add it into the library for the next release, and you can use it directly in the meantime.

Tom

[ralphhughes]

Thanks for releasing 2.6.0 and the very clear documentation to go with it :-)

Using your approxeng_input_profile program I discovered something with my controller. It has a small button labelled "ANALOG" in the middle which seems to toggle the behaviour of the controller. I have generated two different yaml files for me to use depending which mode its in. Note that in "analog" mode L2, R2 and the buttons from pushing in the left and right thumbsticks don't seem to do anything. In the other mode, those work but instead I can't detect the right stick or the D-pad.

shanwan_pcps3android_v9571_p1397.yaml-analog-mode.txt
shanwan_pcps3android_v9571_p1397.yaml-other-mode.txt

To anyone else who has one of these controllers, the "analog" mode seems more useful.

Regards,
Ralph

[windy54]

interesting, I have just been trying to get my "identical" controller working on a PI4 using 64 bit OS.

I have had mine a few years and it is detected as an Xbox360 Controller.
when i connect the dongle dmesg outputs

[ 1225.369289] usb 1-1.1: New USB device found, idVendor=045e, idProduct=028e, bcdDevice= 1.10
[ 1225.369319] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1225.369336] usb 1-1.1: Product: XBOX 360 For Windows
[ 1225.369350] usb 1-1.1: Manufacturer: ShanWan
[ 1225.374718] input: Microsoft X-Box 360 pad as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1/1-1.1:1.0/input/input7
the analog button does not seem to change anything.

It looks like these controllers may look identical but interface wise they are not.

regards
Steve