GPIO inputs spinnen total rum

[funkybunch]

@Substring Hi! Thanks, i'll give it a try. Not translated exactly but with new insights.
I've testet several ways to control the games, but the only nearly perfect method is using a gamepad. At the moment i reconnectet the buttons back to the USB encoders. The Encoders are dual strikes by Jochen Zurborg. The reason for using especially this encoders is, that i got a real ps3 in my cabinet too for playing newer games.
The only Problem is, that every keystroke will recognize 2 times. When i press a button, sometimes the menu opens and close again. Same problem with the Joystick. A click to the right equals a jump 2 systems... but only sometimes. It's difficult to describe, but i've found a similar post.

https://forum.recalbox.com/topic/2933/reporting-test-of-my-controllers-available-to-help-adding-support-for-new-pcb

I've tried the encoder running in PS3 and PC mode. Same problem.

What's the „The xarcade2joystick trick described in the wiki seems to work.“?

[Substring]

@funkybunch when each input is remeated twice, it's most of'times because it's triggering 2 events : one as a keyboard, the other as a pad.

Xarcade2jstick is a small tool that converts a "keyboard" as 2 pads and locks the keyboard events.

[Substring]

please provide a link to that encoder, i'd like to check some stuff

[funkybunch]

@Substring is it possible to deactivate this tool? i can set the dualstrike in different modes. but in ps3 mode (which i prefer cause of switching between pi and ps3) it is probably the problem you described.

here are the links:
device
documentation

[Substring]

@funkybunch sure you can disable xarcade2jstick, but i don't think it's the origin of your problem as it just works for very particuliar devices. Anyway you can disable it in recalbox.conf

[Substring]

Could you run /recalbox/scripts/recalbos-support.sh and upload the resulting archve so that i can take a look at your setup ?

[funkybunch]

@Substring https://file.ac/dAEa2U-BtUU/
Thanks in advance

[Substring]

@funkybunch I don't see any joystick or encoder plugged. Could you retry with your encoder(s) plugged ?

[funkybunch]

@Substring Sorry... forget to connect the Joystick. Here's the new one. Link
But unfortunately one of the PCB's seems to be broken

[Substring]

@funkybunch I see nothing wrong. Can you try running evtest and see if you still have that double input problem ? should be easy to notice in the output of the command

[funkybunch]

@Substring with evtest i see that sometimes a button triggered 2 times. i testet 2 buttons alternately and marked the lines when it triggered 2 times.

the other problem i have is, that the encoders don't detect at starting the system. i have to disconnect and plug in again.

[Substring]

@funkybunch This looks pretty much more complicated than I thought ...

You have some kind of ghost rebound on your controller, but is it a hardware problem or a a software problem ? I definitely can't tell ...

[Substring]

Does it happen in any mode you set your controller ? PS3/Xbox/Mame or whichever ?

[funkybunch]

@Substring Now i checked all modes separately.

The xbox mode is the only one which works 100% correctly, but then i have to switch the mode everytime i play a game on the ps3.

Even the mame mode which emulates only keystrikes makes this problem but regular usb keyboard works fine.

[funkybunch]

@Substring Where can i deactivate the xarcade2jstick tool? can't find the entry in the Recalbox.conf

[funkybunch]

@Substring ok... found, deactivated but same problem as before

[Substring]

@funkybunch so you want it as a PS3 pad ? And in such case you have double inputs, right ?

[funkybunch]

@Substring Yes. I definitly want to use it as a PS3 controller for sharing with the original console.

I tested a regular PS3 Gamepad with recalbox. The regular gamepad works fine.

[Substring]

@funkybunch It's hard to tell whether it's a linux problem or a controller problem. Anyway, hardly anything i can fix

[funkybunch]

@Substring Thanks for your help. If i find a solution for the problem, i'll let you know.