Clubsport DD+ stuck in Update Mode
My DD+ is stuck in Update Mode. The update then always fails. The device is shown as unknown device in the device manager. I tried different USB-C cables (including the original one) and every possible Software. I also uninstalled all Fanatec drivers in between trying the different software versions.
The update always fails at Waiting SteParameterRequest response (just stays at this message), so I guess the software is broken. Probably the needed parameters the base needs to tell the software in order to update are corrupted in memory, but it could be anything else aswell.
Does anybody have another idea what to try?
Fanatec RMA times are crazy right now. Already waiting for 2.5 weeks for an answer and I know it can take another 2.5 weeks. Would be happy if I didnt need to ship it to Fanatec and if I could just play.
Comments
Uninstall 457, install 454, upgrade the base firmware. I solved it this way.
I tried this before and did try it once again but the problem remains exactly the same.
Did you have the exact same problem or a slightly different one?
I had this problem when trying to roll back from 457 to 455 because i couldn't get the Qr update to run. Eventually reinstalled 457 and tried a few times and it got over the loop, competed 457 and completed the QR.
Reading through the 457 discussion, it arises when trying 457 to 455, going to 456 first appears to have worked for some also, but I haven't tried as I'm it date and working now.
GL
I had the exact same one.
Okay I tried it with every Software Version that is out for at least 10-12 times now and the error persists. It just wont come past the SetParameterRequest response stage. I guess I will sunddenly need to wait for RMA then.
The problem is that I dont know what exactly happened to that base to cause this error. I am the second owner of it and bought it as is.
The seller told me the error just randomly appeared one day but I dont know if thats actually true.
Okay thanks for the information, but suddenly no software Version seems to be working for my base.
@ Dominique
As you're not the original purchaser, I don't believe you are going to be able to rma it.
From Fanatec's site (Information/Fanatec Consumer Guarantee).
"The guarantee is bound to the person of the first buyer (hereinafter: warrantee) and is not transferable."
Yes it says that there but if you have the original receipt they normally do it.
I also have contact to previous owner and he could do it for me also.
@ Dominique
Sounds like you have it covered. Good luck!
Hello good morning, i am in the exact same situation.
how did you solve it?
any update?
thanks
Anyone with this issue try removing the steering wheel to install the update then backdate the firmware to 454. That should solve the update loop and you can update to where you want to be, for example 457
I did it without the steering wheel and it stucks at this
Yes it was the same for me. My base is now at Fanatec for RMA. I suddenly did not find a way to fix it by myself.
I am since july waiting a reply from them… sent a video on 2nd of august and nothing. How long did you wait?
Did you guys get it fixed somehow? So frustrating, happened to my wheelbase out of the blue yesterday. I played iRacing 2 days ago, like usual. Then yesterday, turned the computer on to play and boom, went to this mode. I did not even open the Fanatec application, I was not trying to update it or anything.
If this is it and the only way to fix is RMA, this is the type of thing that makes me want to sell all my Fanatec gear, never come back and tell everyone I can possible tell to never buy Fanatec. I don't live in Europe, will be extremely costly and will take a lot of time, if I ever get it back fixed.
Not even 6 months of use and no misuse, unbelievable.
BTW I already tried everything, different computers, cables, drivers versions. After reading all comments in this post and other ones I am quite hopeless that is a software problem, seems hardware, but I want to be wrong.
did you fix it? mine is stuck on the please wait message adter updating.
did you find a fix for it?