DD2 Podium base not detected
![Yves Reber](https://forum.fanatec.com/applications/dashboard/design/images/defaulticon.png)
Hi guys
Around 4 years now, my DD2 with BMW GT2 rim works without any issuies. After i installed a new game and had problems with the game/steering wheel, i decidet to update the drivers (i run old ones , about 328).
But after the update - while updating the base, a Error occured "Failed to detect Fanatec Wheel Base or has been disconnected from PC!...."
I tried several times to deinstall and reinstall the drivers - also with older ones. In the Fanatec Control Panel it shows always "No Wheel Base detected".
Therefore my wheel seems also not connected - i can't get in the Tuning Menü. I then looked a video from Fanatec, where they show how to delete the controller in the device manager. I deleted the controller of the wheelbase.
But that's it. What steps should i do to try to fix that?
Comments
7) Update the FW for devices as per normal, Base (v3.0.0.6) first, then Motor (v3.0.0.2), with Wheels and Pedals last.
https://forum.fanatec.com/discussion/17499/podium-dd2-can-not-update-firmware-brand-new
If the Base is not shown in the control panel, he could not update the FW.
What you can try is to push and hold the power button from off state approx. 12 sec. This should bring up the boot loader menu where you maybe can update the FW. If this will not function, I think you have to open RMA at support. Base seems to be bricked. There are many probs with all direct drive bases and actuel FW (during / after update).
I had simular experience with my DD+. Meanwhile they changed my base.
Duration of RMA Process approx. 4-5 weeks if they change and new one will be on stock. For repair times I have no information.
Bloody crap site lost my original highly detailed report on bootloader mode and how to aproach the fix.
Thank god for Windows clipboard History, recovered it and now reposted.
You have not given a lot of info to go off, but sounds like you have bricked the DD2 motor / base FW which could be done by Fanatecs own update process by doing them in the wrong order, this was fixed in later Fanatec Driver releases:
1) Read all of the below two PDF for full instructions.
2) Remove all Fanatec Drivers from PC, Reboot, then reload your the old v336 Fanatec Drivers and reboot again, all with the DD2 off.
3) Once the old v336 drivers are loaded and your DD2 is plugged into a USB port of the PC, Turn on the DD2 into boot-loader mode by holding its power button for 8-10 seconds, when prompted to flash the FW (Base v656), accept the default and follow the on screen instructions.
4) If unsuccessful then there is probably a fault with the DD2 itself, that Fanatec tech may have to repair.
5) If Fanatec Config / Driver now shows a DD2 device and full working, you can try up upgrading again in a specific order as to avoid known problems with other Fanatec versions Driver packages.
6) Turn off DD2, Un-Install Fanatec Driver and reboot, Install Fanatec Driver v447 and reboot computer, then turn on DD2.
7) Update the FW for devices as per normal, Base (v3.0.0.6) first, then Motor (v3.0.0.2), with Wheels and Pedals last.
8) If all has gone smoothly you could push your luck and go full upgrade by repeating steps 6-7 with the Fanatec driver v457.
https://forum.fanatec.com/discussion/778/fanatec-beta-driver-v336-for-csl-csw-and-podium-bases-all-wheels/p1
https://forum.fanatec.com/discussion/26510/fanatec-driver-447-prev-official-release-prev-445-446-for-csl-csw-and-podium-wb-all-wheels/p1
https://forum.fanatec.com/discussion/30856/fanatec-driver-457-release-candidate-for-csl-clubsport-and-podium-all-wheels/p1
Bootloader mode doc: See page 27 onwards.
https://drive.google.com/open?id=1L6XBk0vhF101Yk2S6im7aEHodcAHO_PU&usp=drive_fs
Fanatec driver and FW updating: See page 11 onwards.
https://drive.google.com/open?id=1LKBx0wSJX3MUqPUCmn7byvAT2KlNq7Qs&usp=drive_fs
That's it. 😉
Thanks guys for your support and tipps!
Push the power button for 10s helped me. After that the base was connected again and then i could (after several attemps) update the Firmware of the Base. Now everything is up to date and works again :-)