-
Notifications
You must be signed in to change notification settings - Fork 2
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
Cubsport DD+ compatibility #18
Comments
Hi, have you uploaded sketch as 918 rsr? |
I am not sure I understand your question. In my outgoing Fanatec messages the header is 0xA5, and the id is 0x03 |
Try 0x0C (is the podium hub) and check in fanatec interface tab in the arduino ide if the hex correspond to podium hub, i can't remember now and let me know if it work |
Have you solved? It is working on DD+ now emulating the podium hub? |
As I said, I don't have a DD+ base. One of my friends ordered it, but it will arrive only in January. :( |
Had a similar issue using code designed for the older belt drive fanatec bases on a dd1. Turned out that the newer bases expected spi communication to start-up faster than the arduino could boot. Options were to use faster arduino/Mcu or remove arduino bootloader which speeds up boot process. DD+ could be expecting even faster spi startup. See here: lshachar/Arduino_Fanatec_Wheel#14 (comment) |
Hi everyone! |
Hi!
Thank you for your awesome work! I’ve made a few wheels using this project with slight modifications for friends, and everyone is thrilled with the results! :) I decided to emulate the Porsche 918 RSR wheel because it has the most buttons.
One of my friends sold his wheel to someone with a new Fanatec DD+ wheelbase, but it didn’t work! When the wheelbase starts, it begins the initialization process but stops after 1-2 seconds. That’s it. The Fanatec app on Windows shows no wheel is attached. However, the wheel still works perfectly on other wheelbases.
Has anyone else experienced issues with the DD+? I don’t have access to this wheelbase, so I’m not sure what to check.
The text was updated successfully, but these errors were encountered: