T80 input recognized in certain modes by evtest, but no functionality in application. #181
Comments
|
My T80 doesn't seem to generate any sequence in evtest for wheel rotation nor for the pedals. |
Try running evtest as root. I can add this wheel if somebody provides me the vendor/product ids. What's the rotation range of the wheel side to side? Also, please, list the events for the pedals, wheel and buttons specifying each. |
|
I will provide the event ID's and other information soon, please expect them in 2-3 hours |
|
The device ID shown in lsusb is 044f:b667. The wheel (ABS_X) seems to range from 0-255 with 128 being the middle position. The left pedal returns code (BTN_TL), and the right pedal returns code (BTN_TR). The value seems to be 1 when down and 0 when up for each. For the input buttons, the input scheme seems to be inconsistent, so I believe that is some kind of poor configuration on my part. In general, they seem to be (BTN_NORTH), (BTN_SOUTH) etc. but for some reason the pedal is (BTN_WEST) and the R3 button is labeled (BTN_START), so I'm hesitant to provide those codes as what the wheel uses universally. I hope this helps! (also, it shouldn't make a difference, but I am using arch and the AUR version of the package.) |
|
The naming of the button events may not match their use. There's nothing wrong. Which pedal is BTN_WEST? I will need the complete list. |
|
Okay, I will provide all of them soon.
…On Mon, Mar 11, 2024 at 4:15 AM Bernat ***@***.***> wrote:
The naming of the button events may not match their use. There's nothing
wrong.
Which pedal is BTN_WEST? I will need the complete list.
—
Reply to this email directly, view it on GitHub
<#181 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AUZNOUD43NXFVOQPXHCR73TYXVRZVAVCNFSM6AAAAABCRPGMC2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBXHA2DEMRZHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
HI All, /dev/input/event6: Thrustmaster Thrustmaster T80 How can I help to make the wheel and the pedals generate something? |
I see some axes in the output: RX, RY and HAT0X. It seems these are two different devices with ids b667 and b668. |
|
Can someone help which way to go in order to elicit something from T80 device on pedal and wheel rotation? |
|
Try to switch to PS3 mode, and if you can’t see it in evtest, try xev.
…On Thu, Mar 21, 2024 at 6:32 PM TorokLev ***@***.***> wrote:
Can someone help which way to go in order to elicit something from T80
device on pedal and wheel rotation?
—
Reply to this email directly, view it on GitHub
<#181 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AUZNOUHLPWU5CAS5DPBVG33YZNNWVAVCNFSM6AAAAABCRPGMC2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJTHE3DIOBYGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
xev doesn't show anything. Completely silent. |
|
Try to find a switch on the left side of the wheel housing. It should be labeled to let you switch between PS3 and PS4 mode. Once in PS3 mode, I believe my USB device ID changed and and allowed me to detect wheel movement with evtest. The pedals also should support more than on and off, but I cannot detect those currently. I've been very busy but I should be able to provide the missing values soon. |
|
OK. I have found a video of another T80. |
|
T80 PS3Mode Neutral to leftNeutral to rightPedals, sadly just on and offAccelerator Brake |
berarma
added
good first issue
|
Hello, I have an update with some exciting news. Edit: The USB address is also new, being changed to 044f:b66a. Edit 2: Additionally, after attempting to change the USB ID in my local copy, oversteer fails to recognize the device for some reason. I changed the ID in all places and even did the input axis remapping. Any help would be appreciated |
|
Wheel turn axis (0-255): type 3 (EV_ABS), code 0 (ABS_X), value 128 (either this or 127 is dead center) Event: time 1720639647.396541, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90008 I'm not sure why these values are here, but I'm including them anyway Left pedal axis (0-255): type 3 (EV_ABS), code 3 (ABS_RX), value 1 (similar 0 story) upon lifting all the way: Event: time 1720639854.716187, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90007 All other inputs seem to match TorokLev's previous comment so I'll omit those. I hope this all helps! |
|
I'm already confused by the number of T80 variants. There are two T80 variants already recognized by Overteer, the F458 with pid 24c6:5b00 and another T80 which I don't know the full model name with pid 044f:b668. Now there seems to be another variant with pid 044f:b667 and a switchable mode with pid 044f:b66a. Is this correct? So you're saying your T80 starts in gamepad mode and you have to keep the PS button pressed at switch on to change it to wheel mode? I think it would help having the official names of these wheels and using different issues for each one. Please could you complete this chart?
|
|
I can really only speak for my own wheel, as it's the only one I have access to. The two pid's mine can use are 044f:b66a (The setting that works) and what I assume is the default mode, 044f:b668. I agree that this is quite confusing. Despite TorokLev's wheel having the same pid, it is a newer model, absent of a switch (from ps3-ps4 mode). I would be surprised if it also did not have the alternate mode that allows full functionality. There also seems to a Ferrari version, but I am unaware of the pid of that, or if it's different at all. I mean, some of the T80's have 3 pedals, while mine only has two. In any case, mine has those two modes (044f:b668, 044f:b66a). Actually, something really bizarre has happened! I checked my old post, looking for the person with the b667 pid, but low and behold, it was me! This is to weird. It must be related to my rampant distrohopping, but it's really weird that the pid changed at all. My old arch linux install seems to have recognized it differently somehow. I in any case, I can't find any other examples of the b667 pid. This is all the information I have access to now. It's too bad all the pid's are such a mess. I hope there's some kind of clarity in future. |
|
additionally, a minor issue seems to be that there is no distinction between the top buttons (labeled L2 and R2) and pushing the pedals down entirely in evtest (both producing the: |
|
In the meantime, how do you feel about adding a note in program describing the issue and how to change the wheel to plug and play mode? |
OK. Let's just check the facts and I can add a note and hopefully support this wheel. So you have the T80 Racing Wheel model, not the Ferrari 488 GTB Edition, right? Product id b668 would correspond to the Racing Wheel mode and b66a to the Gamepad mode, right? I've added both ids in the last master commit. Should we better remove b668 so users don't complain the wheel is detected but doesn't work correctly or do we leave both modes in? |
|
Yes, I have the non ferrari model. the product ID's look correct. Would it be possible to add a notification when the b668 ID is detected, stating that the wheel is detected, but in an unsupported mode? This way future issues can be resolved via the help page I linked earlier and not reported as a missing wheel. |
Yes, I thought about that too. Later. Can you test that it works in the latest commit? |
|
Been testing for a bit. Oversteer detects the wheel in gamepad emulation mode. Additionally, with some added configuration in device.py, I was able to get throttle, brakes, and steering working correctly. Unfortunately, none of the buttons register, I assume this is because oversteer does not handle all T80 BTN ecodes? |
I'd need the event codes shown by |
|
okay, I'll do my best to organize these These are the events after clicking and releasing X, O, Square and Triangle in that order (A, B, X, and Y on other controllers). This is the output of pressing the left and right paddles in that order Share and options buttons, in that order The Playstation button buttons labeled L3 and R3 in that order And finally the bizarre behavior when pressing the L2 and R2 buttons, in that order (sends the same input as pressing each pedal down all the way) Hope this isn't too confusing. |
|
Just wanted to follow up on this issue, and make sure the evtest codes have been seen. Thanks again! |
Sorry for initially posting on an old issue, I am brand new to github. Running evtest I see my wheel and get the following output:
The values seem to range from 0-255, and I've been trying to work with the code to make it detect this, but I'm new (both to github & programming) and struggling. In oversteer, everything other than HAT functionality seems to be broken. Since there's input from evtest, could it be used by oversteer?
The text was updated successfully, but these errors were encountered: