Solved problème de configuration Xin-mo

[acris]

bonjour @picon
Penses tu que nous sommes 24h/24h scotché au forum et notamment le weekend ?

Test ton cablage avec evtest oi sdl jstest
https://github.com/recalbox/recalbox-os/wiki/Testez-votre-joystick-avec-sdl2-jstest-(FR)

Ou encore mieux fournir l archive demandèe dans le post it on aurait gagner du temps....

[picon]

bonjour,
je te remercie de me répondre,
(je suis une bille en informatique il a fallut que je lise un tuto pour ouvrir une session ssh via putty. )
j'espère que c'est cela que tu ma demander

oystick Name: 'Xin-Mo Xin-Mo Dual Arcade'
Joystick Path: '/dev/input/event0'
Joystick GUID: 03000000c0160000e105000001010000
Joystick Number: 0
Number of Axes: 2
Number of Buttons: 10
Number of Hats: 0
Number of B***s: 0
GameController:
not a gamepad
Axis code 0: 0
Axis code 1: 1
Button code 0: 288
Button code 1: 289
Button code 2: 290
Button code 3: 291
Button code 4: 292
Button code 5: 293
Button code 6: 294
Button code 7: 295
Button code 8: 296
Button code 9: 297

Joystick Name: 'Xin-Mo Xin-Mo Dual Arcade'
Joystick Path: '/dev/input/event1'
Joystick GUID: 03000000c0160000e105000001010000
Joystick Number: 1
Number of Axes: 2
Number of Buttons: 12
Number of Hats: 0
Number of B***s: 0
GameController:
not a gamepad
Axis code 0: 0
Axis code 1: 1
Button code 0: 288
Button code 1: 289
Button code 2: 290
Button code 3: 291
Button code 4: 292
Button code 5: 293
Button code 6: 294
Button code 7: 295
Button code 8: 296
Button code 9: 297
Button code 10: 298
Button code 11: 299

Joystick Name: 'Xin-Mo Xin-Mo Dual Arcade'
Joystick Number: 1

Axes 2:
0: 0 [ # ]
1: 0 [ # ]

Buttons 12:
0: 0 [ ]
1: 0 [ ]
2: 0 [ ]
3: 0 [ ]
4: 0 [ ]
5: 0 [ ]
6: 0 [ ]
7: 0 [ ]
8: 0 [ ]
9: 0 [ ]
10: 0 [ ]
11: 0 [ ]

Hats 0:

B***s 0:

Press Ctrl-c to exit

sdl2-jstest

Usage: sdl2-jstest [OPTION]
List available joysticks or test a joystick.
This programm uses SDL for doing its test instead of using the raw
/dev/input/jsX interface

[Substring]

@picon il faut que tu les testes avec evtest puis tu choisis un xinmo, tu essaies TOUT, CTRL+C, re la commande et tu testes pareil l'autre xinmo. S'il y a un probleme d'un bouton qui ne répond pas, problème de cablage.

[picon]

bonjour,
je te remercie de t'occuper de mon cas.
normalement je dois avoir cela:

No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0: CHICONY USB Keyboard
/dev/input/event1: Xin-Mo Xin-Mo Dual Arcade
/dev/input/event2: Xin-Mo Xin-Mo Dual Arcade
/dev/input/event3: CHICONY USB Keyboard
Select the device event number [0-3]: 1
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x16c0 product 0x5e1 version 0x101
Input device name: "Xin-Mo Xin-Mo Dual Arcade"
Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
Event code 288 (BTN_TRIGGER)
Event code 289 (BTN_THUMB)
Event code 290 (BTN_THUMB2)
Event code 291 (BTN_TOP)
Event code 292 (BTN_TOP2)
Event code 293 (BTN_PINKIE)
Event code 294 (BTN_BASE)
Event code 295 (BTN_BASE2)
Event code 296 (BTN_BASE3)
Event code 297 (BTN_BASE4)
Event type 3 (EV_ABS)
Event code 0 (ABS_X)
Value 0
Min -1
Max 1
Event code 1 (ABS_Y)
Value 0
Min -1
Max 1
Event type 4 (EV_MSC)
Event code 4 (MSC_SCAN)
Properties:
Testing ... (interrupt to exit)
Event: time 1519115418.131917, type 3 (EV_ABS), code 1 (ABS_Y), value -1
Event: time 1519115418.131917, -------------- SYN_REPORT ------------
Event: time 1519115418.387973, type 3 (EV_ABS), code 1 (ABS_Y), value 0
Event: time 1519115418.387973, -------------- SYN_REPORT ------------
Event: time 1519115418.964022, type 3 (EV_ABS), code 1 (ABS_Y), value 1
Event: time 1519115418.964022, -------------- SYN_REPORT ------------
Event: time 1519115419.188070, type 3 (EV_ABS), code 1 (ABS_Y), value 0
Event: time 1519115419.188070, -------------- SYN_REPORT ------------
Event: time 1519115419.812128, type 3 (EV_ABS), code 0 (ABS_X), value -1
Event: time 1519115419.812128, -------------- SYN_REPORT ------------
Event: time 1519115420.052183, type 3 (EV_ABS), code 0 (ABS_X), value 0
Event: time 1519115420.052183, -------------- SYN_REPORT ------------
Event: time 1519115420.644234, type 3 (EV_ABS), code 0 (ABS_X), value 1
Event: time 1519115420.644234, -------------- SYN_REPORT ------------
Event: time 1519115420.948269, type 3 (EV_ABS), code 0 (ABS_X), value 0
Event: time 1519115420.948269, -------------- SYN_REPORT ------------
Event: time 1519115421.956402, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90002
Event: time 1519115421.956402, type 1 (EV_KEY), code 289 (BTN_THUMB), value 0
Event: time 1519115421.956402, -------------- SYN_REPORT ------------
Event: time 1519115422.244432, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90002
Event: time 1519115422.244432, type 1 (EV_KEY), code 289 (BTN_THUMB), value 1
Event: time 1519115422.244432, -------------- SYN_REPORT ------------
Event: time 1519115422.884521, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 1519115422.884521, type 1 (EV_KEY), code 288 (BTN_TRIGGER), value 0
Event: time 1519115422.884521, -------------- SYN_REPORT ------------
Event: time 1519115423.204558, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 1519115423.204558, type 1 (EV_KEY), code 288 (BTN_TRIGGER), value 1
Event: time 1519115423.204558, -------------- SYN_REPORT ------------
Event: time 1519115423.780624, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90003
Event: time 1519115423.780624, type 1 (EV_KEY), code 290 (BTN_THUMB2), value 0
Event: time 1519115423.780624, -------------- SYN_REPORT ------------
Event: time 1519115424.084678, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90003
Event: time 1519115424.084678, type 1 (EV_KEY), code 290 (BTN_THUMB2), value 1
Event: time 1519115424.084678, -------------- SYN_REPORT ------------
Event: time 1519115424.724743, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90004
Event: time 1519115424.724743, type 1 (EV_KEY), code 291 (BTN_TOP), value 0
Event: time 1519115424.724743, -------------- SYN_REPORT ------------
Event: time 1519115425.044784, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90004
Event: time 1519115425.044784, type 1 (EV_KEY), code 291 (BTN_TOP), value 1
Event: time 1519115425.044784, -------------- SYN_REPORT ------------
Event: time 1519115425.604858, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90006
Event: time 1519115425.604858, type 1 (EV_KEY), code 293 (BTN_PINKIE), value 0
Event: time 1519115425.604858, -------------- SYN_REPORT ------------
Event: time 1519115425.940896, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90006
Event: time 1519115425.940896, type 1 (EV_KEY), code 293 (BTN_PINKIE), value 1
Event: time 1519115425.940896, -------------- SYN_REPORT ------------
Event: time 1519115426.500980, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90005
Event: time 1519115426.500980, type 1 (EV_KEY), code 292 (BTN_TOP2), value 0
Event: time 1519115426.500980, -------------- SYN_REPORT ------------
Event: time 1519115426.853015, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90005
Event: time 1519115426.853015, type 1 (EV_KEY), code 292 (BTN_TOP2), value 1
Event: time 1519115426.853015, -------------- SYN_REPORT ------------
Event: time 1519115427.477087, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90009
Event: time 1519115427.477087, type 1 (EV_KEY), code 296 (BTN_BASE3), value 0
Event: time 1519115427.477087, -------------- SYN_REPORT ------------
Event: time 1519115427.877139, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90009
Event: time 1519115427.877139, type 1 (EV_KEY), code 296 (BTN_BASE3), value 1
Event: time 1519115427.877139, -------------- SYN_REPORT ------------
Event: time 1519115428.421222, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9000a
Event: time 1519115428.421222, type 1 (EV_KEY), code 297 (BTN_BASE4), value 0
Event: time 1519115428.421222, -------------- SYN_REPORT ------------
Event: time 1519115428.773250, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9000a
Event: time 1519115428.773250, type 1 (EV_KEY), code 297 (BTN_BASE4), value 1
Event: time 1519115428.773250, -------------- SYN_REPORT ------------

[picon]

et la partie 2

evtest

No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0: CHICONY USB Keyboard
/dev/input/event1: Xin-Mo Xin-Mo Dual Arcade
/dev/input/event2: Xin-Mo Xin-Mo Dual Arcade
/dev/input/event3: CHICONY USB Keyboard
Select the device event number [0-3]: 2
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x16c0 product 0x5e1 version 0x101
Input device name: "Xin-Mo Xin-Mo Dual Arcade"
Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
Event code 288 (BTN_TRIGGER)
Event code 289 (BTN_THUMB)
Event code 290 (BTN_THUMB2)
Event code 291 (BTN_TOP)
Event code 292 (BTN_TOP2)
Event code 293 (BTN_PINKIE)
Event code 294 (BTN_BASE)
Event code 295 (BTN_BASE2)
Event code 296 (BTN_BASE3)
Event code 297 (BTN_BASE4)
Event code 298 (BTN_BASE5)
Event code 299 (BTN_BASE6)
Event type 3 (EV_ABS)
Event code 0 (ABS_X)
Value 0
Min -1
Max 1
Event code 1 (ABS_Y)
Value 0
Min -1
Max 1
Event type 4 (EV_MSC)
Event code 4 (MSC_SCAN)
Properties:
Testing ... (interrupt to exit)
Event: time 1519112956.908420, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9000a
Event: time 1519112956.908420, type 1 (EV_KEY), code 297 (BTN_BASE4), value 0
Event: time 1519112956.908420, -------------- SYN_REPORT ------------
Event: time 1519112957.324494, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9000a
Event: time 1519112957.324494, type 1 (EV_KEY), code 297 (BTN_BASE4), value 1
Event: time 1519112957.324494, -------------- SYN_REPORT ------------
Event: time 1519112958.028553, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90009
Event: time 1519112958.028553, type 1 (EV_KEY), code 296 (BTN_BASE3), value 0
Event: time 1519112958.028553, -------------- SYN_REPORT ------------
Event: time 1519112958.412596, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90009
Event: time 1519112958.412596, type 1 (EV_KEY), code 296 (BTN_BASE3), value 1
Event: time 1519112958.412596, -------------- SYN_REPORT ------------
Event: time 1519112959.260698, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90002
Event: time 1519112959.260698, type 1 (EV_KEY), code 289 (BTN_THUMB), value 0
Event: time 1519112959.260698, -------------- SYN_REPORT ------------
Event: time 1519112959.580735, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90002
Event: time 1519112959.580735, type 1 (EV_KEY), code 289 (BTN_THUMB), value 1
Event: time 1519112959.580735, -------------- SYN_REPORT ------------
Event: time 1519112960.236831, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 1519112960.236831, type 1 (EV_KEY), code 288 (BTN_TRIGGER), value 0
Event: time 1519112960.236831, -------------- SYN_REPORT ------------
Event: time 1519112960.652879, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 1519112960.652879, type 1 (EV_KEY), code 288 (BTN_TRIGGER), value 1
Event: time 1519112960.652879, -------------- SYN_REPORT ------------
Event: time 1519112961.132918, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90003
Event: time 1519112961.132918, type 1 (EV_KEY), code 290 (BTN_THUMB2), value 0
Event: time 1519112961.132918, -------------- SYN_REPORT ------------
Event: time 1519112961.548966, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90003
Event: time 1519112961.548966, type 1 (EV_KEY), code 290 (BTN_THUMB2), value 1
Event: time 1519112961.548966, -------------- SYN_REPORT ------------
Event: time 1519112962.045026, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90004
Event: time 1519112962.045026, type 1 (EV_KEY), code 291 (BTN_TOP), value 0
Event: time 1519112962.045026, -------------- SYN_REPORT ------------
Event: time 1519112962.509079, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90004
Event: time 1519112962.509079, type 1 (EV_KEY), code 291 (BTN_TOP), value 1
Event: time 1519112962.509079, -------------- SYN_REPORT ------------
Event: time 1519112963.069162, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90006
Event: time 1519112963.069162, type 1 (EV_KEY), code 293 (BTN_PINKIE), value 0
Event: time 1519112963.069162, -------------- SYN_REPORT ------------
Event: time 1519112964.141276, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90006
Event: time 1519112964.141276, type 1 (EV_KEY), code 293 (BTN_PINKIE), value 1
Event: time 1519112964.141276, -------------- SYN_REPORT ------------
Event: time 1519112964.621368, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90005
Event: time 1519112964.621368, type 1 (EV_KEY), code 292 (BTN_TOP2), value 0
Event: time 1519112964.621368, -------------- SYN_REPORT ------------
Event: time 1519112965.341441, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90005
Event: time 1519112965.341441, type 1 (EV_KEY), code 292 (BTN_TOP2), value 1
Event: time 1519112965.341441, -------------- SYN_REPORT ------------
Event: time 1519112965.885523, type 3 (EV_ABS), code 1 (ABS_Y), value -1
Event: time 1519112965.885523, -------------- SYN_REPORT ------------
Event: time 1519112966.317573, type 3 (EV_ABS), code 1 (ABS_Y), value 0
Event: time 1519112966.317573, -------------- SYN_REPORT ------------
Event: time 1519112966.445561, type 3 (EV_ABS), code 1 (ABS_Y), value 1
Event: time 1519112966.445561, -------------- SYN_REPORT ------------
Event: time 1519112966.909612, type 3 (EV_ABS), code 1 (ABS_Y), value 0
Event: time 1519112966.909612, -------------- SYN_REPORT ------------
Event: time 1519112967.005657, type 3 (EV_ABS), code 0 (ABS_X), value -1
Event: time 1519112967.005657, -------------- SYN_REPORT ------------
Event: time 1519112967.517713, type 3 (EV_ABS), code 0 (ABS_X), value 0
Event: time 1519112967.517713, -------------- SYN_REPORT ------------
Event: time 1519112967.549709, type 3 (EV_ABS), code 0 (ABS_X), value 1
Event: time 1519112967.549709, -------------- SYN_REPORT ------------
Event: time 1519112968.541791, type 3 (EV_ABS), code 0 (ABS_X), value 0
Event: time 1519112968.541791, -------------- SYN_REPORT ------------

[Substring]

A toi de me.dire si certains boutons n'ont pas reagi, je ne vais pas tout relire et comparer avec ce qui est attendu ... Chaque bouton doit générer un évènement different composé du type d'evenement (EV_BTN ou EV_ABS voire EV_KEY) et du nom du bouton (genre BTN_THUMB). À toi de voir si chaque pression/direction génère bien un évènement unique (genre pas 2 boutons qui ont le même nom)

[picon]

d'accord je vais essayer de voir ca

[picon]

alors apparemment
il y a bien EV_MSC ET MSC_SCAN et EV_KEY et le nom du bouton
et chaque boutons a un nom différent (le numéro du code correspond bien au nom du boutons)droite et gauche même numéro et même nom ?

[picon]

svp personne pour m'aider
j'ai formater la carte et réinstaller plusieurs fois,
cela enregistre bien les axes et un bouton n'importe lequel et après je ne peut plus rien faire après j'ai beau appuyer sur les boutons il ne se passe rien?

[acris]

Il faut archive de support voir post it

[picon]

bonsoir,
merci je m'occupe de ca demain

[picon]

bonsoir,
si j'ai bien compris voila le fichier
http://dl.free.fr/sr7mLSLof
svp tu pourras m'expliquer se que tu a chercher et pourquoi pour résoudre le problème si cela est faisable bien entendu
(même si je suis une bille j'essais de comprendre)
merci
j

[picon]

bonjour,
svp quel qu'un pour m'aider

[picon]

bonjour,
mon problème et'il insoluble?

[Substring]

@picon ton bouton B réagit-il dans sdl2-jstest ? (je te donnerai la ligne de commande is tu ne sais pas comment faire)

[picon]

bonjour,
et merci de me répondre
après plusieurs essai le joystick fonctionne toujours , c'est le premier bouton n'importe le qu'elle des 8 qui fonctionne (fait essai avec tous les boutons)
c'est après que les autre ne réponde pas j'ai beau appuyer 1 fois et attendre ou plusieurs fois rien ne répond sauf par moment il y en 1 qui répond
fait des essai avec clavier numérique branché /débranché /changer carte sd/
par contre je ne comprend pas car sous Windows tous les boutons fonctionnent sans souci
si il faut il me servir de sdl2-jstest il faudrais que tu me donne la ligne de commande merci

[tony37]

@picon salut, tu as resolu ton problème ?
Sinon, de memoire la commande c'est :
sdl2-jstest --test 0

[picon]

bonjour,
non pas toujours pas résolu je vais recevoir une nouvelle carte controlleur a voir si sa vient de cela mais je vais quand même tester ta ligne de commande il faut chercher quoi dessus

[picon]

bonjour quand je fait
sdl2-jstest --test 0 sur putty
j'ai cela

Axes 2:
0: 0 [ # ]
1: 0 [ # ]

Buttons 10:
0: 0 [ ]
1: 0 [ ]
2: 0 [ ]
3: 0 [ ]
4: 0 [ ]
5: 0 [ ]
6: 0 [ ]
7: 0 [ ]
8: 0 [ ]
9: 0 [ ]

[picon]

problème résolu avec changement carte contrôleur