Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Encoders, Joysticks, and LED support #12

Open
Airnautique opened this issue Jun 9, 2020 · 8 comments
Open

Encoders, Joysticks, and LED support #12

Airnautique opened this issue Jun 9, 2020 · 8 comments

Comments

@Airnautique
Copy link

I am currently working on making a DIY wheel for my Fanatec base. Looking through the current code and documentation, it appears that there is support for mapping all of the existing buttons from the Fanatec wheels. However, I don't see any mention of the encoders, joysticks, or led rev lights. Most Fanatec wheels have a "funkyswitch" which is a 4-directional d-pad/joystick that also has an encoder built in. Is it possible to add support for that input?

Also, I am currently working on 3d modeling a DIY electrical connector that uses inexpensive header pins so there isn't a need to do the molding using an existing connector,

@lshachar
Copy link
Owner

Hi there,
You are correct, there's no support for LEDS / encoders / joysticks in the code. however, I feel like all the heavy lifting is already done in the code, so it should be very straightforward to implement these quite easily, if you have Arduino programming experience. good luck!

@andrewkerr5
Copy link

I am currently working on making a DIY wheel for my Fanatec base. Looking through the current code and documentation, it appears that there is support for mapping all of the existing buttons from the Fanatec wheels. However, I don't see any mention of the encoders, joysticks, or led rev lights. Most Fanatec wheels have a "funkyswitch" which is a 4-directional d-pad/joystick that also has an encoder built in. Is it possible to add support for that input?

Also, I am currently working on 3d modeling a DIY electrical connector that uses inexpensive header pins so there isn't a need to do the molding using an existing connector,

how did you get on with the model of the connector, im thinking of doing something similar, did you find any suitable pins?

@EtienneGameSeed
Copy link

EtienneGameSeed commented Oct 29, 2020

Hi,
If you're interested I'm selling a board based on Teensy LC, with which can manage buttons, encoder, joystick, RGB leds, 7 segment display and rumble motors. There's an 8 pin jst 2.0 connector so the connection to a Fanatec QR is easy
But it is not based on Ishachar code and not open source :
https://www.electroseed.fr/shop/product_info.php?products_id=351

@Fish2
Copy link

Fish2 commented Nov 7, 2020

@EtienneGameSeed out of interest do the inputs and outputs go throw the Fanatec wheel base ? so my main question is will I be able to configure the leds in Fanalab ?

@lshachar
Copy link
Owner

lshachar commented Nov 7, 2020

they do, and you will.

@EtienneGameSeed
Copy link

Yes I confirm, it wheel behave exactly like a Fanatec wheel, and you'll even be able to configure FFB from the wheel as with a Fanatec wheel

@Shane87F3Ng
Copy link

Shane87F3Ng commented Mar 7, 2022

Hello @lshachar,

first of all, thx very much for your work, that is just awesome!
I have one question about how to add additional buttons / encoders..
Do i need to change to another wheel than the Porsche RSR? or just modify the button matrix and bytes?
Because as far as i know, i can only use buttons that are originally supported by the wheel? it is like that with thrustmaster

Actually i build sth similar for my previous thrustmaster base and was reading the wheelstates with an arduino sketch by https://rr-m.org/blog/ to implement it into my sketch and simulate the right wheel..

my plan is to use:

3 encoders + push button
8 buttons

so in total i would need to have 19 buttons (wheel states)

any help on where to start?

@EtienneGameSeed As is saw you do not sell the teensy anymore, maybe you can help with some thoughts here without getting too much info away on your own project.

@thomaswang04
Copy link

I know this is an old thread but I did some poking in the code and figured out how the joystick code works for at least the porche 918 rsr in the base code. returnData[5] is for the x axis and returnData[6] is for the Y axis. 0x00 and 0xff are center position. 0x00 to 0x7f is negative x/y where 0x7f is the farthest the joystick goes. Then 0x80 is the opposite side of the x/y axis which goes all the way back to 0xff which returns to center.

I spent like an hour trying manually adjusting values before trying to cycle through each value and discovering how it works.

hopefully this helps @Airnautique if he is still working on this or anyone else who reads this thread.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants