HELP - Wheel base died after Driver 464

Hi everyone,

I’m reaching out here because I’m completely stuck and could really use some help.

I’ve been using my Podium DD1 wheel without any issues for two years, but everything went downhill after updating to driver 464. Here’s what happened:

  1. After updating to driver 464, everything worked except for my shifter.
  2. To fix it, I downgraded to driver 463. While this brought my shifter back, my wheels (F1 Podium Wheel and ClubSport BMW M3 GT2) stopped being recognized.
  3. Thinking the issue was due to firmware updated on the wheels with driver 464, I reinstalled 464 to confirm. but this caused my wheelbase to stop being recognized altogether.

Now, no matter what driver I install (I’ve tried reverting to 463 and 464 and even older versions), the following issues persist:

  • The wheelbase powers on and its display lights up, but it isn’t recognized on Fanalab or Fanatec Control Panel.
  • The power button only works to power it on but doesn’t respond to power off; I have to unplug the unit to turn it off.
  • The buttons on the wheel are unresponsive, so I can’t follow the Firmware Recovery Instructions or check the motor version.
  • During one of my tests I got an error message pointing me to the log file location (See attached)

I’m out of ideas and feeling pretty desperate. Has anyone experienced something similar or know how to fix this? I’d really appreciate any advice or suggestions.

Thanks in advance!

Comments

  • change to comp mode and look if it comes to alive,

    or uninstall current drivers and then install 451

  • Bonjour , je rebondis sur le sujet. Comment avancer sur la garantie constructeur ? J’ai écrit par mail à Fanatec et aucune réponses en retour.


    Aucune mise à jour n’a été faite. Au bout d’1 an à peine notre base ne s’allume plus.


    Que devons nous faire pour la prise en charge du SAV?

  • Hi, I'm just getting back on the subject. How can I make progress on the manufacturer's warranty? I have written to Fanatec by email and no reply has been received.

    No update has been made. After just 1 year, our base unit no longer lights up.


    What should we do about the after-sales service?

  • Hi all

    Just a quick update. Problem is not sorted but there are some progress.

    After flashing it Using Driver 464, the wheel buttons are back working, but the base still isn't recognized. Now I can see the motor is v41.0.0 but the Main is v3.3.0 (I'm wonderinig if this could be the problem now (?)

    The base is still not recognized

    I tried flashing with driver 463 but no luck either

    Now, when I turn the base on it goes to calibration mode with fans running full speed. I can perform the calibration using the tunning menu on the wheel but after that the fans keep running loud and wheel is still not recognized. Also, if I turn the base off, when I turn it on again the base it goes back to calibration mode.


    Any ideas from here?


  • You flashed the firmwares in the wrong order so now the new Base Firmware can no longer communicate with the old Motor Firmware. You always have to flash the Motor first, only then the Base.

    You now have to uninstall your current driver, install driver 336, power-off the base, press the power button for 8 seconds to start the base in bootloader mode and then flash the base firmware. This Base Firmware now can communicate again with the old Motor Firmware v41. Afterwards uninstall 336, install 464, open Control Panel, open Firmware Manager, click the green update button to run the automatic update process which flashes everything in the correct order automatically.

  • THANK YOU SO SO SO MUCH!


    that worked! I was already going nuts with that. I don't know why Fanatec doesn't make it more user friendly or at least make the process full of warnings so that people don't get confused. It's very easy to mess it up.


    My only questions now to better document this for future people who may find this is Why my Motor now is 3.0.0? (for me it sounds like 41.0.0 was newer)


  • Glad it worked :)

    41.0.0 is not newer. the driver just had read it wrong because the base was screwed. Correct was 41, not 41.0.0 and 41 is older than the new semantic versioning with 3.X.X.X.

    The green new driver available notification is a false positive message which came up last night for whatever reason. Will be fixed tomorrow. Just ignore it ;)

Sign In or Register to comment.