The latest evidence shows that you have a bricked DD2 (Don't care how it happened) as the Fan at 100% with Motor and Base FW versions being totally incompatible for a working DD2 as Motor firmware should be updated first then base.
Latest should be for Fanatec Driver v463:
• Podium DD1 / DD2 Base : 3.1.0.7
• Podium DD1 / DD2 Motor : 3.0.0.2
This will complicate matters as you will have to go to a earlier version of Fanatec driver to correct the issue.
Oldest compatible would be Fanatec Driver v336, v400, or v415:
• Podium DD1 / DD2 Base : 686
• Podium DD1 Motor : 40
To get your base working again, uninstall current driver 455, download and install Driver v336, V400 or V415, power-off the base, then hold the power button pressed for 10 seconds while the base is off to start the base in bootloader mode, click flash firmware, done.
Now uninstall driver v336 or v400 or v415, install latest driver v450 (The only one that works for you) or v463 and run the automatic update process by pressing the green update button in the firmware Manager and then you are updated and good to go.
My current driver is 450, where would I find to Download v336, v400 or v415 I have not saved back as far of these? I will not use Revo uninstaller for now if its that program that caused this, I'll never use again! Thank you for your help :)
So, if you're saying my base is now bricked, should I contact support? How on earth do I fix this Windows thing of not installing the Fanatec driver so it won't happen again and brick another base? Maybe I just don't know enough, never thought I would a degree in computing to sort things out 🤨. At least I have an extra hour in bed 😴😁
i not know why he say that. you need install the 415 driver and then install old base firmware, after that you need install new drivers again for update the firmware
you are not first one that some reason firmware update get messed up
Don't know how this has all happened, all of your issues are quite unique, Fanatec drivers are also quite unique and can quite easily cause issues under specific conditions.
The updating of the Wheel base FW for Motor and Base can be done in the wrong order even by the firmware manager in auto mode (Regardless of Fanatec putting in safe guards to stop it from happening).
Wheels bases have been known to initiate bootloader updates without user intervention in the middle of playing a game, software update locking up or for other strange reasons an Revo Unistaller could cause in software in someway with windows registry, I used Revo years ago and had issues with it so stopped using it, infact nearly all registry cleaners cause more problems than they solve).
The solution to bricking DD1 / DD2 is exactly as I specified earlier, it is a specific sequence specified by Fanatec themselves.
Bricking is a general term that means to me un-usuable, some might say totally unfixable, however with DD1 and DD2 in this state is fixable, barring hardware failures else where in Wheel base.
i have a double button assignment for some time now where the 2 upper button right upper side of the button module( see image) both trigger the (o) button so my PlayStation 🔺triangle button is not available I have the latest 463 driver installed.
strange thing is that whenever there are new driver updates and I connect the wheel to install the new updates using my pc all firmware always says up to date. I do manually update it and updates are always successful but I wander why I can’t see firmware updates between drivers and have to blindly manually force them with no indication of my hardware being I the latest firmware ?
Thank you Maurice for the quick reply that’s great news.
any insights why does my hardware always show its up to date even when new driver is out ?
this started since installing the 457 beta driver if I recall since then I have updated the driver to 462 and now 463 but firmware manager shows all up to date always as mentioned I do it manually and flash it with the new driver.
Maybe because everything actually is up-to-date?! There were no new FIrmwares included for your devices from 457 to 462 and 463... So nothing to update and therefore no info that a new firmware is available because, well, it isnt...
So I´ve been trying to update my formula v2.5 wheel since i got it back in May, but till this day i sadly never recieved any feedback by fanatec support yet (yes i know they have a ot of inquiries but may is half a year ago), therefore i now hope you guys can help me out.
The Formula Wheel is stuck in a firmware loop, I tried installing every driver since then to see if that will fix my issue but none of them sadly did, not even the 463 one.
When I start the the FW Manager it tells me to update as seen below and it also phantomly does that, runs all the way through without obvious issues and restarts the wheelbase and then again it tells me to update, that keeps going forever.
Firmwareversions are seen below as well (Wheel is on FW 33, so its super old).
I tried older Drivers, complety reinstalling, conencted it without any extension cables or hubs, tried a different pc which never had any fanatec software installed, but nothing with success.
Edit: Forgot to attach Logs (Screenshots are the same for 463 as for 462, Logs are already from the new driver version):
I wouldnt mind it if the firmware would be like somewhere close to 47 but its 33 and I´d also like to have the better rumble which got implemented with the latest firmware.
It says successful yeah but it obviously sadly wasnt and I´ve no clue why.
Sometimes it even reports itself as Firmware V 0.0.0.0
I have been using 455 (or 457?) since it was stable on PS5. So I haven‘t followed all the firmware and driver updates as they haven‘t been fully stable.
About a year ago I reported that the Podium Button Module Rally does not work with sequential shifting on PS5.
I still have 450 I have not uninstalled it yet, so can I update the motor FW with 450? I appreciate all the help, sometimes though it gets a little overwhelming if I have too much and different answers, it's like being in a car at a crossway junction and all the signs say "Go this way" But thank you to all that's posted :)
Comments
Your in a real mess here.
The latest evidence shows that you have a bricked DD2 (Don't care how it happened) as the Fan at 100% with Motor and Base FW versions being totally incompatible for a working DD2 as Motor firmware should be updated first then base.
Latest should be for Fanatec Driver v463:
• Podium DD1 / DD2 Base : 3.1.0.7
• Podium DD1 / DD2 Motor : 3.0.0.2
This will complicate matters as you will have to go to a earlier version of Fanatec driver to correct the issue.
Oldest compatible would be Fanatec Driver v336, v400, or v415:
• Podium DD1 / DD2 Base : 686
• Podium DD1 Motor : 40
To get your base working again, uninstall current driver 455, download and install Driver v336, V400 or V415, power-off the base, then hold the power button pressed for 10 seconds while the base is off to start the base in bootloader mode, click flash firmware, done.
Now uninstall driver v336 or v400 or v415, install latest driver v450 (The only one that works for you) or v463 and run the automatic update process by pressing the green update button in the firmware Manager and then you are updated and good to go.
Also recommend to not use Revo uninstaller during all of the above procedure, just windows uninstaller for programs.
My current driver is 450, where would I find to Download v336, v400 or v415 I have not saved back as far of these? I will not use Revo uninstaller for now if its that program that caused this, I'll never use again! Thank you for your help :)
I dont know how this has come about, I had 455 I missed 457...and went to 462, how come my base gone to all the old stuff?
415, you can get here https://forum.fanatec.com/discussion/23824/fanatec-driver-415-for-csl-csw-and-podium-wb-all-wheels/p1
you don't need 336, 400
So, if you're saying my base is now bricked, should I contact support? How on earth do I fix this Windows thing of not installing the Fanatec driver so it won't happen again and brick another base? Maybe I just don't know enough, never thought I would a degree in computing to sort things out 🤨. At least I have an extra hour in bed 😴😁
i not know why he say that. you need install the 415 driver and then install old base firmware, after that you need install new drivers again for update the firmware
you are not first one that some reason firmware update get messed up
Don't know how this has all happened, all of your issues are quite unique, Fanatec drivers are also quite unique and can quite easily cause issues under specific conditions.
The updating of the Wheel base FW for Motor and Base can be done in the wrong order even by the firmware manager in auto mode (Regardless of Fanatec putting in safe guards to stop it from happening).
Wheels bases have been known to initiate bootloader updates without user intervention in the middle of playing a game, software update locking up or for other strange reasons an Revo Unistaller could cause in software in someway with windows registry, I used Revo years ago and had issues with it so stopped using it, infact nearly all registry cleaners cause more problems than they solve).
The solution to bricking DD1 / DD2 is exactly as I specified earlier, it is a specific sequence specified by Fanatec themselves.
Bricking is a general term that means to me un-usuable, some might say totally unfixable, however with DD1 and DD2 in this state is fixable, barring hardware failures else where in Wheel base.
yes, that what i used when my WQR some unknown reason was not able install correctly.
but sometimes even those simple things can be complicated
some people are just not IT minded, so they not know what todo
he been mess this stuff since October 20, even tho by default it should take less than one day.
and its not his fault because software developers are those who needs prevent this kind problems
Hi Maurice
GT DD Pro
Podium hub
Endurance button module
Qr2
PS5
i have a double button assignment for some time now where the 2 upper button right upper side of the button module( see image) both trigger the (o) button so my PlayStation 🔺triangle button is not available I have the latest 463 driver installed.
strange thing is that whenever there are new driver updates and I connect the wheel to install the new updates using my pc all firmware always says up to date. I do manually update it and updates are always successful but I wander why I can’t see firmware updates between drivers and have to blindly manually force them with no indication of my hardware being I the latest firmware ?
Appreciate your help.
Broken button mapping of the BME on PS is known and will be fixed in a new firmware update in the future.
Thank you Maurice for the quick reply that’s great news.
any insights why does my hardware always show its up to date even when new driver is out ?
this started since installing the 457 beta driver if I recall since then I have updated the driver to 462 and now 463 but firmware manager shows all up to date always as mentioned I do it manually and flash it with the new driver.
Maybe because everything actually is up-to-date?! There were no new FIrmwares included for your devices from 457 to 462 and 463... So nothing to update and therefore no info that a new firmware is available because, well, it isnt...
So I´ve been trying to update my formula v2.5 wheel since i got it back in May, but till this day i sadly never recieved any feedback by fanatec support yet (yes i know they have a ot of inquiries but may is half a year ago), therefore i now hope you guys can help me out.
The Formula Wheel is stuck in a firmware loop, I tried installing every driver since then to see if that will fix my issue but none of them sadly did, not even the 463 one.
When I start the the FW Manager it tells me to update as seen below and it also phantomly does that, runs all the way through without obvious issues and restarts the wheelbase and then again it tells me to update, that keeps going forever.
Firmwareversions are seen below as well (Wheel is on FW 33, so its super old).
I tried older Drivers, complety reinstalling, conencted it without any extension cables or hubs, tried a different pc which never had any fanatec software installed, but nothing with success.
Edit: Forgot to attach Logs (Screenshots are the same for 463 as for 462, Logs are already from the new driver version):
Thanks I guess I’ll see when the new update with fix for the BME is released.
Have a great day.
you log says that Frimware update was successful,
could be some other problem like it can't read version number correctly for some reason
bugs like this been happened before
I wouldnt mind it if the firmware would be like somewhere close to 47 but its 33 and I´d also like to have the better rumble which got implemented with the latest firmware.
It says successful yeah but it obviously sadly wasnt and I´ve no clue why.
Sometimes it even reports itself as Firmware V 0.0.0.0
Hello everyone,
checking the recent updates I would highly appreciate your feedback. I have the:
CS DD+ racing wheel F1 with the APM
Podium hub
PBMR
CSL Elite pedals V2
All at the 455 version and without any issues until now. Is it recommended or a must to upgrade to 463?
Also can I go directly from 455 to 463?
Thanks for your help!
Hi,
I have been using 455 (or 457?) since it was stable on PS5. So I haven‘t followed all the firmware and driver updates as they haven‘t been fully stable.
About a year ago I reported that the Podium Button Module Rally does not work with sequential shifting on PS5.
Is that being fixed by now?
No.
Thank you! I have downloaded 415+336...I'll install later and I hope that one of them will install (note to self, keep positive Stephen 🤐 )
No because new driver have upshift issue
deleted - missed some later posts
he motor for unknown reason is 40 not a 3.0.0.2
one thing is what i not understand at all, if motor was not able update, then why base was possible update
in manual there clearly typed that it would not work with wrong motor firmware
Not sure if he tried to update motor and failed or just can’t install drivers. Since correct motor FW is in 450, does that update it?
he started complain since 462 drivers, so beginning is at there
He’s got 450 installed (unless he deleted again) - it has the right motor FW, so just upgrade there?
I still have 450 I have not uninstalled it yet, so can I update the motor FW with 450? I appreciate all the help, sometimes though it gets a little overwhelming if I have too much and different answers, it's like being in a car at a crossway junction and all the signs say "Go this way" But thank you to all that's posted :)
no. if you want that your hardware would start run in 450. you first need downgrade the firmware for the correct order
your current firmware order is messed up