Guide: Advanced Controller Mappings

jrmymllr

I'm getting close. I want to map the D-pad to arrow keys, but it's not working. Just for testing, if I run this (how do you display text as code???):

/opt/retropie/supplementary/xboxdrv/bin/xboxdrv
--evdev /dev/input/by-id/usb-0079_USB_Gamepad-event-joystick
--silent
--detach-kernel-driver
--force-feedback
--deadzone-trigger 15%
--deadzone 4000
--mimic-xpad
--evdev-absmap ABS_X=dpad_x,ABS_Y=dpad_y
--evdev-keymap BTN_THUMB=a,BTN_THUMB2=b,BTN_BASE3=back,BTN_BASE4=start
--dpad-only
--ui-axismap lt=void,rt=void
--ui-buttonmap tl=void,tr=void,guide=void,x=void,y=void,lb=void,rb=void,back=KEY_ESC,a=KEY_1,b=KEY_2 &

Then run "evtest", the D-pad responds as ABS_X and ABS_Y with values -1 to 1. But if I add this to --ui-axismap:

dpad_x=KEY_LEFT:KEY_RIGHT,dpad_y=KEY_UP:KEY_DOWN

it runs with no errors, but now in "evtest" the D-pad causes no response at all. If instead I use:

X1=KEY_LEFT:KEY_RIGHT,Y1=KEY_UP:KEY_DOWN

The D-pad in "evtest" responds not with arrow keys, but the same ABS_X and ABS_Y. Any ideas?

mediamogul

@jrmymllr said in Guide: Advanced Controller Mappings:

how do you display text as code?

https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet#code-and-syntax-highlighting

Everything looks to be correct. You say you're running evtest a second time, but which controller event are you testing at that point? Is it the original physical controller event, or the new virtual controller event? If it's the prior, that event is rendered inert while xboxdrv is running to avoid conflicts. If it's the latter, xboxdrv creates both a new virtualized joystick event, along with a virtualized keyboard event. If your looking to see if the keyboard is being activated with button presses, you'll want to look at the new keyboard event. However, if it's running without errors as you say, it's probably fine. You may just want to fire up an emulator that supports arrow keys and see what shakes loose.

Rion

@mediamogul said in Guide: Advanced Controller Mappings:

@meleu

I originally thought it might be a bit too long and involved for a wiki entry, but maybe it should go there.

Yes please :)

And while where on the topic. This should be built in to the retropie setup. With a gui.

Edit:

Something like this.

Configuration / Tools / Advanced Controller Configuration.

From here you can choose device using
cat /proc/bus/input/devices from a list.

Event Location

ls /dev/input/by-id/

Event codes for each button

And so on all in the gui.

jrmymllr

@mediamogul

I am definitely testing the new virtual Xbox event with evtest. With no xboxdrv running here's the response direct from the controller (USB NES type controller):

Event: time 1475321474.481703, type 3 (EV_ABS), code 1 (ABS_Y), value 255
Event: time 1475321474.481703, -------------- EV_SYN ------------
Event: time 1475321474.593717, type 3 (EV_ABS), code 1 (ABS_Y), value 127
Event: time 1475321474.593717, -------------- EV_SYN ------------
Event: time 1475321475.369820, type 3 (EV_ABS), code 1 (ABS_Y), value 0
Event: time 1475321475.369820, -------------- EV_SYN ------------
Event: time 1475321475.473841, type 3 (EV_ABS), code 1 (ABS_Y), value 127
Event: time 1475321475.473841, -------------- EV_SYN ------------
Event: time 1475321476.417955, type 3 (EV_ABS), code 0 (ABS_X), value 255
Event: time 1475321476.417955, -------------- EV_SYN ------------
Event: time 1475321476.481967, type 3 (EV_ABS), code 0 (ABS_X), value 127
Event: time 1475321476.481967, -------------- EV_SYN ------------
Event: time 1475321477.058044, type 3 (EV_ABS), code 0 (ABS_X), value 0
Event: time 1475321477.058044, -------------- EV_SYN ------------
Event: time 1475321477.122050, type 3 (EV_ABS), code 0 (ABS_X), value 127
Event: time 1475321477.122050, -------------- EV_SYN ------------

Then if I run this:

        --evdev /dev/input/by-id/usb-0079_USB_Gamepad-event-joystick \
        --silent \
        --detach-kernel-driver \
        --force-feedback \
        --deadzone-trigger 15% \
        --deadzone 4000 \
        --mimic-xpad \
        --evdev-absmap ABS_X=dpad_x,ABS_Y=dpad_y \
        --evdev-keymap BTN_THUMB=a,BTN_THUMB2=b,BTN_BASE3=back,BTN_BASE4=start \
        --dpad-only \
        --ui-axismap lt=void,rt=void,X1=KEY_LEFT:KEY_RIGHT,Y1=KEY_UP:KEY_DOWN \
        --ui-buttonmap tl=void,tr=void,guide=void,x=void,y=void,lb=void,rb=void,back=KEY_ESC,a=KEY_1,b=KEY_2 &

the response from evtest from the Dpad through the virtual xboxdrv device is:

Event: time 1475321774.129436, type 3 (EV_ABS), code 1 (ABS_Y), value -1
Event: time 1475321774.129436, -------------- EV_SYN ------------
Event: time 1475321774.265388, type 3 (EV_ABS), code 1 (ABS_Y), value 0
Event: time 1475321774.265388, -------------- EV_SYN ------------
Event: time 1475321775.169519, type 3 (EV_ABS), code 1 (ABS_Y), value 1
Event: time 1475321775.169519, -------------- EV_SYN ------------
Event: time 1475321775.297536, type 3 (EV_ABS), code 1 (ABS_Y), value 0
Event: time 1475321775.297536, -------------- EV_SYN ------------
Event: time 1475321775.889574, type 3 (EV_ABS), code 0 (ABS_X), value -1
Event: time 1475321775.889574, -------------- EV_SYN ------------
Event: time 1475321775.953608, type 3 (EV_ABS), code 0 (ABS_X), value 0
Event: time 1475321775.953608, -------------- EV_SYN ------------
Event: time 1475321776.401679, type 3 (EV_ABS), code 0 (ABS_X), value 1
Event: time 1475321776.401679, -------------- EV_SYN ------------
Event: time 1475321776.489683, type 3 (EV_ABS), code 0 (ABS_X), value 0
Event: time 1475321776.489683, -------------- EV_SYN ------------

However if I press the other buttons during evtest they appear as KEY_ESC,KEY_1, etc. as they should. And, those buttons really behave like I'm pressing the associated keyboard buttons in an emulator.

I've ensured no other xboxdrv processes are running, and tried rebooting. So, no problem emulating the keyboard with controller buttons. The problem is emulating keyboard presses with the Dpad. Should be simple but I must be missing something!

mediamogul

@jrmymllr

Try adding --dpad-as-button and configuring each direction separately in a --ui-buttonmap line using du=KEY_*,dd=KEY_*,dl=KEY_*,dr=KEY_* entries to see if that makes a difference.

jrmymllr

@mediamogul

Success! I previously tried the --dpad-as-button but must not have figured out du,dd,etc.

Thanks a million!

mediamogul

I have now added this guide to the wiki along with @MadHorse's additions. It can be found here. As it doesn't make sense to maintain the same information in two places, I'll leave the first post as is, adding only a notation at the beginning. Of course, anyone can continue to ask questions and trade configurations here if need be.

Thanks guys!

jrmymllr

@MadHorse said in Guide: Advanced Controller Mappings:

This is awesome. This is a great way to run xboxdrv with different commands depending on emulator or ROM. I finally have everything working the way I want.

adafruitfly

Hello I am having trouble with my USB arcade sticks not being recognized by my new PI Zero. I plug them in and emulation station doesn't show any gamepad attached.

I built these arcades sticks myself using a PS3/PC ZERO DELAY USB ENCODER PCB as the input device and all of these arcade sticks work with my PI 2 for the last year.

All of my regular gamepad (Microsoft sidewinder and Logitech controllers) seem to work. Is it perhaps an issue with the retro pie image file for the zero not supporting these arcade stick devices? Or is it that this little device doesn't produce enough juice to power these larger controllers?

Is there a possible fix?

mediamogul

@adafruitfly

You can try running evtest to see if your arcade stick is registering as an input event. If it does, you can use this guide to map you controller using xboxdrv. At that point the system will just think you're using an XBox 360 controller.

My best advice is that you start a new thread detailing your situation separately. This will likely attract a wider array of viewers and may produce a solution more tailored to your specific problem.

adafruitfly

@mediamogul

I've been trying to create a new thread but this forum is badly broken. No matter what I do the forum keeps telling me my post title is too short and refuses to let my post.

mediamogul

This post is deleted!

mediamogul

Added instruction for changing the joystick mouse speed.

This particular example works well for mapping a controller's left analog stick to mouse support using the --ui-axismap variable and can be changed to the right stick by simply altering the line to --ui-axismap x2=REL_X:10,y2=REL_Y:10. To change the speed of the mouse, just change the REL_*:* integer of the X and Y axis higher or lower than 10.

Rion

@mediamogul

I have been trying to get this to work with my 8bitdo NES 30 Pro Controller for some days now and i am stuck.

This is what i have done so far.

Connected the Gamepad using the 8bitdo guide on the wiki Setting up an 8bitdo Bluetooth controller

cat /proc/bus/input/devices

I: Bus=0005 Vendor=3820 Product=0009 Version=0100
N: Name="8Bitdo NES30 Pro"
P: Phys=b8:27:eb:5b:f5:53
S: Sysfs=/devices/platform/soc/3f201000.uart/tty/ttyAMA0/hci0/hci0:12/0005:3820:0009.0003/input/input2
U: Uniq=e4:17:d8:db:66:6b
H: Handlers=event2 js0
B: PROP=0
B: EV=1b
B: KEY=ffff0000 0 0 0 0 0 0 0 0 0
B: ABS=30627
B: MSC=10

So the Gamepad event number is 2.

ls /dev/input/by-id/

usb-NOVATEK_USB_Keyboard-event-if01  usb-NOVATEK_USB_Keyboard-event-kbd

No input id found.

evtest /dev/input/event2

Input driver version is 1.0.1
Input device ID: bus 0x5 vendor 0x3820 product 0x9 version 0x100
Input device name: "8Bitdo NES30 Pro"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 304 (BTN_SOUTH)
    Event code 305 (BTN_EAST)
    Event code 306 (BTN_C)
    Event code 307 (BTN_NORTH)
    Event code 308 (BTN_WEST)
    Event code 309 (BTN_Z)
    Event code 310 (BTN_TL)
    Event code 311 (BTN_TR)
    Event code 312 (BTN_TL2)
    Event code 313 (BTN_TR2)
    Event code 314 (BTN_SELECT)
    Event code 315 (BTN_START)
    Event code 316 (BTN_MODE)
    Event code 317 (BTN_THUMBL)
    Event code 318 (BTN_THUMBR)
    Event code 319 (?)
  Event type 3 (EV_ABS)
    Event code 0 (ABS_X)
      Value    128
      Min        0
      Max      255
      Flat      15
    Event code 1 (ABS_Y)
      Value    127
      Min        0
      Max      255
      Flat      15
    Event code 2 (ABS_Z)
      Value    128
      Min        0
      Max      255
      Flat      15
    Event code 5 (ABS_RZ)
      Value    127
      Min        0
      Max      255
      Flat      15
      Resolution      46
    Event code 9 (ABS_GAS)
      Value      0
      Min        0
      Max      255
      Flat      15
    Event code 10 (ABS_BRAKE)
      Value      0
      Min        0
      Max      255
      Flat      15
    Event code 16 (ABS_HAT0X)
      Value      0
      Min       -1
      Max        1
    Event code 17 (ABS_HAT0Y)
      Value      0
      Min       -1
      Max        1
  Event type 4 (EV_MSC)
    Event code 4 (MSC_SCAN)
Properties:
Testing ... (interrupt to exit)

After testing all the buttons i figured out the Key Code and name for every button

A=  (EV_KEY), code 304 (BTN_SOUTH)	 	= Corresponds to Xbox360 button = a
B=  (EV_KEY), code 305 (BTN_EAST)	 	= Corresponds to Xbox360 button = b
X=  (EV_KEY), code 307 (BTN_NORTH)	 	= Corresponds to Xbox360 button = x
Y=  (EV_KEY), code 308 (BTN_WEST)	 	= Corresponds to Xbox360 button = y

L1= (EV_KEY), code 310 (BTN_TL)	 	= Corresponds to Xbox360 button = lb
L2= (EV_KEY), code 312 (BTN_TL2) KEY_#312	= Corresponds to Xbox360 button = lt
R1= (EV_KEY), code 311 (BTN_TR)	 	= Corresponds to Xbox360 button = rb
R2= (EV_KEY), code 313 (BTN_TR2) KEY_#313	= Corresponds to Xbox360 button = rt

Start= (EV_KEY), code 315 (BTN_START)	 = Corresponds to Xbox360 button = start
Select= (EV_KEY), code 314 (BTN_SELECT)	 = Corresponds to Xbox360 button = back

Digital Up= (EV_ABS), code 17 (ABS_HAT0Y)	 = Corresponds to Xbox360 button = dpad_y
Digital Down= (EV_ABS), code 17 (ABS_HAT0Y)	 = Corresponds to Xbox360 button = dpad_y
Digital Left= (EV_ABS), code 16 (ABS_HAT0X)	 = Corresponds to Xbox360 button = dpad_x
Digital Right= (EV_ABS), code 16 (ABS_HAT0X)	 = Corresponds to Xbox360 button = dpad_x

Left Analog Up= (EV_ABS), code 1 (ABS_Y)	 	= Corresponds to Xbox360 button = y1
Left Analog Down= (EV_ABS), code 1 (ABS_Y)	 	= Corresponds to Xbox360 button = y1
Left Analog Left= (EV_ABS), code 0 (ABS_X)	 	= Corresponds to Xbox360 button = x1
Left Analog Right= (EV_ABS), code 0 (ABS_X)	 	= Corresponds to Xbox360 button = x1
Left Analog Button= (EV_KEY), code 317 (BTN_THUMBL)	= Corresponds to Xbox360 button = tl

Right Analog Up= (EV_ABS), code 5 (ABS_RZ)	 	 = Corresponds to Xbox360 button = y2
Right Analog Down= (EV_ABS), code 5 (ABS_RZ)	 	 = Corresponds to Xbox360 button = y2
Right Analog Left= (EV_ABS), code 2 (ABS_Z)	 	 = Corresponds to Xbox360 button = x2
Right Analog Right= (EV_ABS), code 2 (ABS_Z)	 	 = Corresponds to Xbox360 button = x2
Right Analog Button= (EV_KEY), code 318 (BTN_THUMBR)	 = Corresponds to Xbox360 button = tr

Next i started to map the Virtual Xbox 360 GamePad

sudo /opt/retropie/supplementary/xboxdrv/bin/xboxdrv \
        --evdev /dev/input/event2 \
	--silent \
	--detach-kernel-driver \
	--force-feedback \
	--deadzone-trigger 15% \
	--deadzone 4000 \
	--trigger-as-button \	
	--device-name "NES30 PRO Advanced Controller Configuration" \
	--evdev-absmap ABS_X=x1,ABS_Y=y1,ABS_X=x2,ABS_Y=y2,ABS_HAT0X=dpad_x,ABS_HAT0Y=dpad_y \
	--evdev-keymap BTN_SOUTH=a,BTN_EAST=b,BTN_NORTH=x,BTN_WEST=y,KEY_#312=lt,KEY_#313=rt,BTN_TL=lb,BTN_TR=rb,BTN_THUMBL=tl,BTN_THUMBR=tr,BTN_SELECT=back,BTN_START=start \
	--ui-buttonmap guide=void \
	&

xboxdrv 0.8.8 - http://pingus.seul.org/~grumbel/xboxdrv/
Copyright © 2008-2011 Ingo Ruhnke <grumbel@gmail.com>
Licensed under GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details.


Your Xbox/Xbox360 controller should now be available as:
  /dev/input/js1
  /dev/input/event3

Press Ctrl-C to quit

sudo nano /etc/rc.local

#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.

# Print the IP address
_IP=$(hostname -I) || true
if [ "$_IP" ]; then
  printf "My IP address is %s\n" "$_IP"
fi

#!/bin/bash
echo "Hi, I'm sleeping for 5 seconds..."
sleep 10
echo "all Done."

sudo /opt/retropie/supplementary/xboxdrv/bin/xboxdrv \
        --evdev /dev/input/event2 \
        --silent \
        --detach-kernel-driver \
        --force-feedback \
        --deadzone-trigger 15% \
        --deadzone 4000 \
        --trigger-as-button \
        --device-name "NES30 PRO Advanced Controller Configuration" \
        --evdev-absmap ABS_X=x1,ABS_Y=y1,ABS_X=x2,ABS_Y=y2,ABS_HAT0X=dpad_x,ABS_HAT0Y=dpad_y \
        --evdev-keymap BTN_SOUTH=a,BTN_EAST=b,BTN_NORTH=x,BTN_WEST=y,KEY_#312=lt,KEY_#313=rt,BTN_TL=lb,BTN_TR=rb,BTN_THUMBL=tl,BTN_THUMBR=tr,BTN_SELECT=back,BTN_START=start \
        --ui-buttonmap guide=void \
        &

exit 0

sudo reboot

But EmulationStation still cant find it. Still Says 8bitdo Nes 30 Pro

Tried with and without adding the controller to the udev rules like the Setting up an 8bitdo Bluetooth controller Guide says

/etc/udev/rules.d/99-bluetooth.rules

SUBSYSTEM=="input", ATTRS{name}=="8Bitdo NES30 Pro", MODE="0666", ENV{ID_INPUT_JOYSTICK}="1"

Testet all the option in the Guide using Configure bluetooth connect mode from default, boot & background.
No change.

So what am i doing wrong?

bfenty

Looking through here, this seems to work great for mapping a controller of any type, but would it work in mapping a keyboard input? I have the GPIO pins emulating key presses for the buttons on my portable pi, I've got them up and running for pretty much all games with a few wonky outliers, would I benefit from going through this trouble or should I just leave it as-is?

mediamogul

@Rion said in Guide: Advanced Controller Mappings:

So what am i doing wrong?

It looks like everything is right on your end. It's very helpful to see that your command launches directly from the command line without error. That should mean that it's also launching from rc.local and is just being ignored. I've never had that happen, but it could be that the original controller event is taking precedent and when you go to map in ES it reads the original event first. This isn't supposed to happen because xboxdrv is designed to render the original event inert to avoid these types of situations. It could be that it's unable to do this because of something unique to the NES30 setup.

Try deleting the original NES30 mapping from es_input.cfg, reboot and see if it can then read the xboxdrv virtual event. Just make sure you have something else mapped to control ES as a backup if it doesn't work. If it does work and the original NES30 event is conflicting, that conflict will of course still show up in other software as well.

mediamogul

@bfenty

I've never tried mapping a keyboard, but it should work, as you'd just be taking an event code from the keyboard and mapping it to a virtual controller event. Give it a shot. I'd be very interested to see how it goes.

weirdocollector

Hi!

I'm following the wiki in order to try to use my Xbox One wired controller with the Retropie emulators that normally support keyboard only.

I've discovered the events generated by the pad, and I've noticed that the two triggers are registered as button events, nominally BTN_TL2 and BTN_TR2, and not as ABS events.

Should the command that launches xboxdrv look like this ?

sudo /opt/retropie/supplementary/xboxdrv/bin/xboxdrv \
    --evdev /dev/input/by-id/usb-Microsoft_Controller_7EED8E7D89A9-event-joystick \
    --silent \
    --detach-kernel-driver \
    --force-feedback \
    --deadzone-trigger 15% \
    --deadzone 4000 \
    --mimic-xpad \
    --trigger-as-button \
    --evdev-absmap ABS_X=x1,ABS_Y=y1,ABS_RX=x2,ABS_RY=y2,ABS_HAT0X=dpad_x,ABS_HAT0Y=dpad_y \
    --evdev-keymap BTN_SOUTH=a,BTN_EAST=b,BTN_NORTH=x,BTN_WEST=y,BTN_TL=lb,BTN_TR=rb,BTN_TL2=lt,BTN_TR2=rt,BTN_THUMBL=tl,BTN_THUMBR=tr,BTN_MODE=guide,BTN_SELECT=back,BTN_START=start \
    &

Notice that I've used the --trigger-as-button option, and that the BTN_TL2=lt,BTN_TR2=rt button events are mapped in the --evdev-keymap option .

mediamogul

@weirdocollector said in Guide: Advanced Controller Mappings:

Should the command that launches xboxdrv look like this ?

It looks fine to me. Have you tried using it yet?

weirdocollector

@mediamogul said in Guide: Advanced Controller Mappings:

@weirdocollector said in Guide: Advanced Controller Mappings:

Should the command that launches xboxdrv look like this ?

It looks fine to me. Have you tried using it yet?

Yess !

I works, but at first it didn't work because both Emulationstation and Retroarch detected both the Xbox One and the Xbox 360 controllers, giving priority to the former.

To make it functioning I had to do the following:

erase ~/.emulationstation/es_input.cfg
reconfigure Retroarch setting, making the Xbox 360 controller the first to be used by all emulators

I'm now going to try to configure the driver in order to use the controller with the Atari800 Emulator.

Thanks a lot !