howei
Creatures
Loderunner
Posts: 32
|
Post by howei on Jan 17, 2020 11:36:57 GMT
Hi all I have a old DB9 to USB Joystick adapter with two ports running on the TheC64mini with firmware 1.20 correctly without any problems. Attached to the adapter is an original competition pro joystick. The entry in the gamecontrollerdb.txt is this: 03000000c0160000dc27000001010000,hexagons.de Retro-Joystick,x:b6,y:b7,back:b2,start:b3,b:b4,a:b5,lefttrigger:b0,righttrigger:b1,leftx:a0,lefty:a1,platform:Linux, Recently i decided to upgrade the firmware to 1.32. Upgrade was ok. I copied the new gamecontrollerdb.txt to my Laptop, added the Adaper configuration to it and copied it back to the mini. No Joystick at the adapter works correctly now. On both ports. The fire button works, but no responding on up, down, left, right movement. I read out the C64mini with dmesg. The entry for the adapter seems correct: [ 1.662622] input: hexagons.de Retro-Joystick as /devices/platform/sw-ohci.2/usb5/5-1/5-1:1.0/input/input1 [ 1.663102] generic-usb 0003:16C0:27DC.0001: input: USB HID v1.01 Joystick [hexagons.de Retro-Joystick] on usb-sw-ohci-1/input0 [ 1.674654] input: hexagons.de Retro-Joystick as /devices/platform/sw-ohci.2/usb5/5-1/5-1:1.1/input/input2 [ 1.675140] generic-usb 0003:16C0:27DC.0002: input: USB HID v1.01 Joystick [hexagons.de Retro-Joystick] on usb-sw-ohci-1/input1 Any solution for this problem? I don't want to downgrade to 1.20 (will be the last option)
Greetings, Howei
|
|
|
|
Post by jj0 on Jan 17, 2020 19:03:39 GMT
Hi all I have a old DB9 to USB Joystick adapter with two ports running on the TheC64mini with firmware 1.20 correctly without any problems. Attached to the adapter is an original competition pro joystick. The entry in the gamecontrollerdb.txt is this: 03000000c0160000dc27000001010000,hexagons.de Retro-Joystick,x:b6,y:b7,back:b2,start:b3,b:b4,a:b5,lefttrigger:b0,righttrigger:b1,leftx:a0,lefty:a1,platform:Linux, Recently i decided to upgrade the firmware to 1.32. Upgrade was ok. I copied the new gamecontrollerdb.txt to my Laptop, added the Adaper configuration to it and copied it back to the mini. No Joystick at the adapter works correctly now. On both ports. The fire button works, but no responding on up, down, left, right movement. I read out the C64mini with dmesg. The entry for the adapter seems correct: [ 1.662622] input: hexagons.de Retro-Joystick as /devices/platform/sw-ohci.2/usb5/5-1/5-1:1.0/input/input1 [ 1.663102] generic-usb 0003:16C0:27DC.0001: input: USB HID v1.01 Joystick [hexagons.de Retro-Joystick] on usb-sw-ohci-1/input0 [ 1.674654] input: hexagons.de Retro-Joystick as /devices/platform/sw-ohci.2/usb5/5-1/5-1:1.1/input/input2 [ 1.675140] generic-usb 0003:16C0:27DC.0002: input: USB HID v1.01 Joystick [hexagons.de Retro-Joystick] on usb-sw-ohci-1/input1 Any solution for this problem? I don't want to downgrade to 1.20 (will be the last option) Greetings, Howei
What editor & OS did you edit the file on? If on Windows then the line endings in the file might have been converted to Windows-style line endings instead of Linux-style line endings. This might throw of interpretation of the file. In which case the easiest solution is to on the Mini go to the directory where gamecontrollerdb.txt is and do: dos2unix gamecontrollerdb.txt |
|
howei
Creatures
Loderunner
Posts: 32
|
Post by howei on Jan 18, 2020 15:12:06 GMT
no, i used unix(LF) and UTF-8.
|
|
|
|
Post by jj0 on Jan 18, 2020 20:17:53 GMT
no, i used unix(LF) and UTF-8. Hmmm. Then I'm not sure. Do you still have the v1.20 gamecontrollerdb.txt? You could try if that works. |
|
howei
Creatures
Loderunner
Posts: 32
|
Post by howei on Jan 19, 2020 20:27:11 GMT
I copied the V1.20 gamecontrollerdb.txt to the mini. No success. Same problem
|
|
|
|
Post by jj0 on Jan 20, 2020 11:01:56 GMT
I copied the V1.20 gamecontrollerdb.txt to the mini. No success. Same problem Do you still have the v1.20 'the64' executable? You could try to run that to see if it works. Just as a test of course. And verify whether the adapter works OK on a different device. |
|
howei
Creatures
Loderunner
Posts: 32
|
Post by howei on Jan 21, 2020 11:37:44 GMT
no, i only have the 1.20 firmware.bin file. And i don't know how to edit the fw to extract it.
The adapter works fine on my Windows Laptop.
I checked the mapping with the "SDL2 gamepad tool v1.2" on the Laptop - ok.
|
|
|
|
Post by marione on Jan 21, 2020 12:11:22 GMT
follow
|
|
|
|
Post by jj0 on Jan 21, 2020 20:23:23 GMT
no, i only have the 1.20 firmware.bin file. And i don't know how to edit the fw to extract it. The adapter works fine on my Windows Laptop. I checked the mapping with the "SDL2 gamepad tool v1.2" on the Laptop - ok. You can extract the firmware to get the 'the64' executable. |
|
howei
Creatures
Loderunner
Posts: 32
|
Post by howei on Jan 22, 2020 12:59:47 GMT
ok, i extracted the file "the64" from the fw 1.20.
the64 file (fw 1.20) has a size of 181,8 kb. Is this correct? Because there are two of these files there. One in payload0 and one in payload1. Both have the same size.
I made a backup from the file located in usr/bin directory and then copied the "old" file into this dir.
this was not good. Now i have a black screen on boot.
|
|
|
|
Post by jj0 on Jan 22, 2020 14:08:43 GMT
ok, i extracted the file "the64" from the fw 1.20. the64 file (fw 1.20) has a size of 181,8 kb. Is this correct? Because there are two of these files there. One in payload0 and one in payload1. Both have the same size. I made a backup from the file located in usr/bin directory and then copied the "old" file into this dir. this was not good. Now i have a black screen on boot. I think the one from payload 0 is for European Mini's and the one from payload 1 is for US Mini's. So you have to use the one that corresponds to where your Mini is from. You can start it from the UART shell as well just to see what the output is. Just type: killall the64
killall the64
the64The killall is just to make sure it isn't already running. |
|
howei
Creatures
Loderunner
Posts: 32
|
Post by howei on Jan 22, 2020 15:05:05 GMT
Ok, this ist the output: I used the file from payload0. I have an european mini.
![]()
|
|
|
|
Post by jj0 on Jan 22, 2020 17:35:43 GMT
Ok, this ist the output: I used the file from payload0. I have an european mini.
![]() Most likely the v1.20 program is incompatible with the later firmware. I tried this with a v1.3.0 and a v1.3.1 one and they were swappable. So if you have v1.3.x firmwares you could try those. But mostly I'm out of ideas now :-( |
|
howei
Creatures
Loderunner
Posts: 32
|
Post by howei on Jan 23, 2020 7:32:36 GMT
hmmm. I have a last idea. I will try different entries in the controllerdb.txt. Leftx and lefty don't work. Maybe the other notations for stick movement will do the job. I will report.
so, if this doesn't work, i will downgrade the fw to 1.20. Do you have instructions to do this savely?
|
|
|
|
Post by jj0 on Jan 23, 2020 19:10:17 GMT
hmmm. I have a last idea. I will try different entries in the controllerdb.txt. Leftx and lefty don't work. Maybe the other notations for stick movement will do the job. I will report. so, if this doesn't work, i will downgrade the fw to 1.20. Do you have instructions to do this savely? I've checked the 1.3.0 firmware update and that updated a few libraries. So the safest way to downgrade would be to restore a (v1.2) nandb backup. But then you lose any modifications of course. Another way would be to extract a nandb backup to e.g. an USB drive and copy at least the /lib directory to the Mini and then see if the 1.2 'the64' works. Either way make a '1.3.2' nandb backup first. |
|
howei
Creatures
Loderunner
Posts: 32
|
Post by howei on Jan 29, 2020 13:55:03 GMT
ok, i am back. f#@*ing rl.  I tried some entries for the stick movement: 1. rightx:a0, righty:a1 2. leftx:a0, lefty:a1 3. dpdown:h0.4,dpleft:h0.8,dpright:h0.2,dpup:h0.1 4. dpup:-a1,dpdown:+a1,dpleft:-a0,dpright:+a0, Nothing helped. When i use the factory reset, will the mini go back to the firmware it had at the time i purchased it, or will it only erase all data and stay at the current firmware? |
|
howei
Creatures
Loderunner
Posts: 32
|
Post by howei on Jan 29, 2020 14:06:04 GMT
i forgot to ask:: is it possible to test the joystick input within the putty environment?
|
|
|
|
Post by jj0 on Jan 29, 2020 14:59:19 GMT
ok, i am back. f#@*ing rl. I tried some entries for the stick movement: 1. rightx:a0, righty:a1 2. leftx:a0, lefty:a1 3. dpdown:h0.4,dpleft:h0.8,dpright:h0.2,dpup:h0.1 4. dpup:-a1,dpdown:+a1,dpleft:-a0,dpright:+a0, Nothing helped. When i use the factory reset, will the mini go back to the firmware it had at the time i purchased it, or will it only erase all data and stay at the current firmware? It will only erase all data, it doesn't keep a copy of the old firmware. Do you know what flash chip is in your Mini? I might have an old backup somewhere. |
|
|
|
Post by jj0 on Jan 29, 2020 15:58:31 GMT
ok, i am back. f#@*ing rl. I tried some entries for the stick movement: 1. rightx:a0, righty:a1 2. leftx:a0, lefty:a1 3. dpdown:h0.4,dpleft:h0.8,dpright:h0.2,dpup:h0.1 4. dpup:-a1,dpdown:+a1,dpleft:-a0,dpright:+a0, Nothing helped. When i use the factory reset, will the mini go back to the firmware it had at the time i purchased it, or will it only erase all data and stay at the current firmware? It will only erase all data, it doesn't keep a copy of the old firmware. Do you know what flash chip is in your Mini? I might have an old backup somewhere. The joystick should be one of the devices in /dev/input. For example with only the Maxi joystick attached (to my Mini) I have: # ls -l /dev/input/
total 0
crw-rw---- 1 root root 13, 64 Jan 1 00:00 event0
crw-rw---- 1 root root 13, 65 Jan 1 00:00 event1
crw-rw---- 1 root root 13, 63 Jan 1 00:00 mice
# dmesg | grep input
[ 1.570279] input: axp20-supplyer as /devices/platform/sun7i-i2c.0/i2c-0/0-0034/axp20-supplyer.28/input/input0
[ 3.733744] input: THEC64 Joystick THEC64 Joystick as /devices/platform/sw-ehci.1/usb2/2-1/2-1.2/2-1.2.1/2-1.2.1.1/2-1.2.1.1:1.0/input/input1
[ 3.734193] generic-usb 0003:1C59:0024.0001: input: USB HID v1.10 Joystick [ THEC64 Joystick THEC64 Joystick ] on usb-sw-ehci-1.2.1.1/input0
event0 appears to be the axp209 power managment unit so I take a gamble on the joystick to be event1 and see what happens if I press the left fire button: # cat /dev/input/event1 | hexdump
0000000 01ba 0000 522e 000a 0004 0004 0001 0009
0000010 01ba 0000 5236 000a 0001 0120 0001 0000
0000020 01ba 0000 52cf 000a 0000 0000 0000 0000
0000030 01ba 0000 4818 000c 0004 0004 0001 0009
0000040 01ba 0000 483b 000c 0001 0120 0000 0000
0000050 01ba 0000 4908 000c 0000 0000 0000 0000
You can also use the attached evtest (25.49 KB) program which I got from the A20-OlinuXino-LIME rootfs: # evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0: axp20-supplyer
/dev/input/event1: THEC64 Joystick THEC64 Joystick
Select the device event number [0-1]: 1
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x1c59 product 0x24 version 0x110
Input device name: " THEC64 Joystick THEC64 Joystick "
"
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 127
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 127
Min 0
Max 255
Flat 15
Event code 3 (ABS_RX)
Value 127
Min 0
Max 255
Flat 15
Event code 4 (ABS_RY)
Value 127
Min 0
Max 255
Flat 15
Event type 4 (EV_MSC)
Event code 4 (MSC_SCAN)
Properties:
Testing ... (interrupt to exit)
Event: time 577.812449, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 577.812458, type 1 (EV_KEY), code 288 (BTN_TRIGGER), value 1
Event: time 577.812614, -------------- EV_SYN ------------
Event: time 578.052442, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 578.052453, type 1 (EV_KEY), code 288 (BTN_TRIGGER), value 0
Event: time 578.052608, -------------- EV_SYN ------------
|
|
howei
Creatures
Loderunner
Posts: 32
|
Post by howei on Jan 29, 2020 23:31:07 GMT
I used evtest: Joystick 1: (up,down,left,right,button)
# evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0: axp20-supplyer
/dev/input/event1: hexagons.de Retro-Joystick
/dev/input/event2: hexagons.de Retro-Joystick
Select the device event number [0-2]: 1
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x16c0 product 0x27dc version 0x101
Input device name: "hexagons.de Retro-Joystick"
Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
Event code 288 (BTN_TRIGGER)
Event code 289 (BTN_THUMB)
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 287.155066, type 3 (EV_ABS), code 1 (ABS_Y), value -1
Event: time 287.155094, -------------- EV_SYN ------------
Event: time 287.307076, type 3 (EV_ABS), code 1 (ABS_Y), value 0
Event: time 287.307097, -------------- EV_SYN ------------
Event: time 288.547087, type 3 (EV_ABS), code 1 (ABS_Y), value 1
Event: time 288.547114, -------------- EV_SYN ------------
Event: time 288.723066, type 3 (EV_ABS), code 1 (ABS_Y), value 0
Event: time 288.723086, -------------- EV_SYN ------------
Event: time 290.587090, type 3 (EV_ABS), code 0 (ABS_X), value -1
Event: time 290.587121, -------------- EV_SYN ------------
Event: time 290.803066, type 3 (EV_ABS), code 0 (ABS_X), value 0
Event: time 290.803091, -------------- EV_SYN ------------
Event: time 291.771084, type 3 (EV_ABS), code 0 (ABS_X), value 1
Event: time 291.771112, -------------- EV_SYN ------------
Event: time 291.939063, type 3 (EV_ABS), code 0 (ABS_X), value 0
Event: time 291.939088, -------------- EV_SYN ------------
Event: time 293.243080, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 293.243086, type 1 (EV_KEY), code 288 (BTN_TRIGGER), value 1
Event: time 293.243096, -------------- EV_SYN ------------
Event: time 293.299083, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 293.299088, type 1 (EV_KEY), code 288 (BTN_TRIGGER), value 0
Event: time 293.299097, -------------- EV_SYN ------------
Joystick 2:
# evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0: axp20-supplyer
/dev/input/event1: hexagons.de Retro-Joystick
/dev/input/event2: hexagons.de Retro-Joystick
Select the device event number [0-2]: 2
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x16c0 product 0x27dc version 0x101
Input device name: "hexagons.de Retro-Joystick"
Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
Event code 288 (BTN_TRIGGER)
Event code 289 (BTN_THUMB)
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 414.914114, type 3 (EV_ABS), code 1 (ABS_Y), value -1
Event: time 414.914145, -------------- EV_SYN ------------
Event: time 415.074063, type 3 (EV_ABS), code 1 (ABS_Y), value 0
Event: time 415.074083, -------------- EV_SYN ------------
Event: time 416.410088, type 3 (EV_ABS), code 1 (ABS_Y), value 1
Event: time 416.410113, -------------- EV_SYN ------------
Event: time 416.530069, type 3 (EV_ABS), code 1 (ABS_Y), value 0
Event: time 416.530090, -------------- EV_SYN ------------
Event: time 417.578081, type 3 (EV_ABS), code 0 (ABS_X), value -1
Event: time 417.578110, -------------- EV_SYN ------------
Event: time 417.690061, type 3 (EV_ABS), code 0 (ABS_X), value 0
Event: time 417.690085, -------------- EV_SYN ------------
Event: time 418.754086, type 3 (EV_ABS), code 0 (ABS_X), value 1
Event: time 418.754116, -------------- EV_SYN ------------
Event: time 418.874062, type 3 (EV_ABS), code 0 (ABS_X), value 0
Event: time 418.874087, -------------- EV_SYN ------------
Event: time 419.930095, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 419.930101, type 1 (EV_KEY), code 288 (BTN_TRIGGER), value 1
Event: time 419.930112, -------------- EV_SYN ------------
Event: time 420.010087, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 420.010093, type 1 (EV_KEY), code 288 (BTN_TRIGGER), value 0
Event: time 420.010102, -------------- EV_SYN ------------
seems that the Usb Adapter works correctly. But when i boot the mini normally, only the button of the joysticks works. up, down, left, right no function
|
|
howei
Creatures
Loderunner
Posts: 32
|
Post by howei on Jan 30, 2020 0:02:58 GMT
Downgrade: i have the orignainal files as a backup. I think, it was fw 1.06 and i have also nandb version 1.20.
|
|
|
|
Post by jj0 on Jan 30, 2020 11:03:11 GMT
I used evtest: ...
seems that the Usb Adapter works correctly. But when i boot the mini normally, only the button of the joysticks works. up, down, left, right no function
You could try to map it on Windows or Linux first, an copy those settings to the TheC64. There's a description with some tools here: github.com/gabomdq/SDL_GameControllerDB/blob/master/README.md, and a tool here: generalarcade.com/gamepadtool/ Edit: Don't use the tool on Windows, the stick's identifier will be different from linux. |
|
howei
Creatures
Loderunner
Posts: 32
|
Post by howei on Jan 30, 2020 12:31:52 GMT
I used the tool already to find out the settings of the adapter. This was the base for me to find out what i have to insert in the gamecontroller.txt.
With the 1.2 fw it worked fine. I only have these Problem with fw 1.32.
|
|
|
|
Post by jj0 on Jan 30, 2020 12:54:26 GMT
All I can think of is to remove everything from the gamecontrollerdb.txt except for your single line and see how that works out.
Or contact Retro LTD, but they might not help with a modded TheC64. But then again they seem fairly OK.
|
|
howei
Creatures
Loderunner
Posts: 32
|
Post by howei on Jan 30, 2020 20:41:57 GMT
ok, thank you for your help.  I will downgrade the mini. Since it worked perfectly there's no need for future upgrades. |
|
|
|
Post by jj0 on Jan 31, 2020 6:50:41 GMT
ok, thank you for your help. I will downgrade the mini. Since it worked perfectly there's no need for future upgrades. Don't give up yet!  From the (I think 1.20) source of the64 all the possible options for gamecontrollerdb.txt are: static tsf_input_name_t input_name_map[] = {
{ INPUT_X, 1, "x"},
{ INPUT_Y, 1, "y"},
{ INPUT_A, 1, "a"},
{ INPUT_B, 1, "b"},
{ INPUT_BACK, 4, "back"},
{ INPUT_GUIDE, 5, "guide"},
{ INPUT_START, 5, "start"},
{ INPUT_DIG_LEFT, 6, "dpleft"},
{ INPUT_DIG_RIGHT, 7, "dpright"},
{ INPUT_DIG_UP, 4, "dpup"},
{ INPUT_DIG_DOWN, 6, "dpdown"},
{ INPUT_SHLD_LEFT, 12, "leftshoulder"},
{ INPUT_TRIG_LEFT, 11, "lefttrigger"},
{ INPUT_SHLD_RIGHT, 13, "rightshoulder"},
{ INPUT_TRIG_RIGHT, 12, "righttrigger"},
{ INPUT_STICK_LEFT, 9, "leftstick"},
{ INPUT_STICK_RIGHT, 10, "rightstick"},
{ INPUT_AXIS_LEFT_X, 5, "leftx"},
{ INPUT_AXIS_LEFT_Y, 5, "lefty"},
{ INPUT_AXIS_RIGHT_X, 6, "rightx"},
{ INPUT_AXIS_RIGHT_Y, 6, "righty"}These strings except maybe x,y,b are all also present in the 1.3.2 the64 binary: # hexdump -C -s 0x32048 -n 176 the64
00032048 61 00 00 00 62 61 63 6b 00 00 00 00 67 75 69 64 |a...back....guid|
00032058 65 00 00 00 73 74 61 72 74 00 00 00 64 70 6c 65 |e...start...dple|
00032068 66 74 00 00 64 70 72 69 67 68 74 00 64 70 75 70 |ft..dpright.dpup|
00032078 00 00 00 00 64 70 64 6f 77 6e 00 00 6c 65 66 74 |....dpdown..left|
00032088 73 68 6f 75 6c 64 65 72 00 00 00 00 6c 65 66 74 |shoulder....left|
00032098 74 72 69 67 67 65 72 00 72 69 67 68 74 73 68 6f |trigger.rightsho|
000320a8 75 6c 64 65 72 00 00 00 72 69 67 68 74 74 72 69 |ulder...righttri|
000320b8 67 67 65 72 00 00 00 00 6c 65 66 74 73 74 69 63 |gger....leftstic|
000320c8 6b 00 00 00 72 69 67 68 74 73 74 69 63 6b 00 00 |k...rightstick..|
000320d8 6c 65 66 74 78 00 00 00 6c 65 66 74 79 00 00 00 |leftx...lefty...|
000320e8 72 69 67 68 74 78 00 00 72 69 67 68 74 79 00 00 |rightx..righty..|
But the ones I haven't seen you try are 'leftstick' and 'rightstick', maybe these will work? |
|
howei
Creatures
Loderunner
Posts: 32
|
Post by howei on Feb 1, 2020 9:55:53 GMT
But the ones I haven't seen you try are 'leftstick' and 'rightstick', maybe these will work? These entries are present in the gamecontrollerdb.txt (i.e. Hori real arcade pro4). The thing that make me suspicious is the absence of the x and y axis. But i will try them.
|
|
howei
Creatures
Loderunner
Posts: 32
|
Post by howei on Feb 1, 2020 12:19:49 GMT
Ok, "rightstick" and "leftstick" had no success.
I made an evtest with a competition pro extra attached to the mini:
# evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0: axp20-supplyer
/dev/input/event1: SPEEDLINK COMPETITION PRO Game Controller for Android
Select the device event number [0-1]: 1
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x79 product 0x181c version 0x111
Input device name: "SPEEDLINK COMPETITION PRO Game Controller for Android "
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 type 3 (EV_ABS)
Event code 0 (ABS_X)
Value 128
Min 0
Max 255
Flat 15
Event code 1 (ABS_Y)
Value 128
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 128
Min 0
Max 255
Flat 15
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)
Event: time 946686576.939265, type 3 (EV_ABS), code 1 (ABS_Y), value 0
Event: time 946686576.939298, -------------- EV_SYN ------------
Event: time 946686577.059273, type 3 (EV_ABS), code 1 (ABS_Y), value 128
Event: time 946686577.059306, -------------- EV_SYN ------------
Event: time 946686578.675267, type 3 (EV_ABS), code 1 (ABS_Y), value 255
Event: time 946686578.675299, -------------- EV_SYN ------------
Event: time 946686578.819265, type 3 (EV_ABS), code 1 (ABS_Y), value 128
Event: time 946686578.819293, -------------- EV_SYN ------------
Event: time 946686584.931264, type 3 (EV_ABS), code 0 (ABS_X), value 0
Event: time 946686584.931302, -------------- EV_SYN ------------
Event: time 946686585.075266, type 3 (EV_ABS), code 0 (ABS_X), value 128
Event: time 946686585.075298, -------------- EV_SYN ------------
Event: time 946686586.291268, type 3 (EV_ABS), code 0 (ABS_X), value 255
Event: time 946686586.291303, -------------- EV_SYN ------------
Event: time 946686586.419263, type 3 (EV_ABS), code 0 (ABS_X), value 128
Event: time 946686586.419294, -------------- EV_SYN ------------
Event: time 946686598.891195, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90004
Event: time 946686598.891202, type 1 (EV_KEY), code 307 (BTN_NORTH), value 1
Event: time 946686598.891314, -------------- EV_SYN ------------
Event: time 946686599.011193, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90004
Event: time 946686599.011201, type 1 (EV_KEY), code 307 (BTN_NORTH), value 0
Event: time 946686599.011311, -------------- EV_SYN ------------
The main difference between the adapter and the CP pro extra are the values returned on stick movement
The adapter has -1 , 0 , +1 , 0
the cp pro has 0, 128, 255, 128 the buttons have the same value. What are the values for?
|
|
|
|
Post by jj0 on Feb 1, 2020 15:19:48 GMT
Ok, "rightstick" and "leftstick" had no success. I made an evtest with a competition pro extra attached to the mini:
The main difference between the adapter and the CP pro extra are the values returned on stick movement
The adapter has -1 , 0 , +1 , 0
the cp pro has 0, 128, 255, 128 the buttons have the same value. What are the values for?
I think different adapters report the axis values differently. For the adapter x-axis it is -1 (left), 0 (center) and 1 (right), and for the CP Pro 0 (left), 128 (center) and 255 (right) I guess. But interesting difference all the same. |
|
iCode
Creatures
Posts: 18
|
Post by iCode on Jan 2, 2021 3:19:46 GMT
Did you ever figure this out? i have the same issue. upgraded firmware and now only fire works. same exact steps to troubleshoot and joystick is reporting correct info but I get no movement in games/menus.
|
|
