Maurice BöschenMember, CSL E RP1 PS4 beta tester, RMcL BT, CS SWFORM V2 Beta test, DD Beta Tester, PHub Beta Tester, P BME beta tester
edited August 2020
That's not necessary, no. In fact, I never detached my wheel in hundreds of base firmware updates.. ^^
Just be aware that the base will restart in Xbox mode when you have a Xbox compatible wheel attached so it's not recognized by Windows anymore until you switch back to pc mode.
I also had this issue with my DD1. I found that once I updated the Wireless Quick Release Firmware I was able to successfully update the motor firmware.
After doing all the firmware updates (wheel base, motor, wheel), I then ran the motor calibration and there was a very big jolt as the motor started the first rotation.
Did anything else change? I am on the new driver and notice the FFB has improved quite a bit. It seems quicker and more responsive and with less oscillations.
I had no issues with updating my DD1 for PS4 at all.
I think it's very important to remove all drivers, reboot before installing the new one, and reboot again.
Follow the message as well to calibrate the motor by removing the wheel.
I've followed these steps and had zero issues, I put back my settings and on F1 2020 everything feels quite nice ( it was a bit too warm to drive though ).
Thats the proper way to uninstall and re-install an update though.
Its always bad to install over an exisiting installation, always remove the old stuff first to avoid strange issues which can happen with leftovers of previous version if you dont update properly.
Your issue might be speciial to your hardware configuration.
"much more"? that's not information or a reason, that's useless, any reason for this driver for a normal csw 2.5 and universal hub? any ffb improvements?
Maurice BöschenMember, CSL E RP1 PS4 beta tester, RMcL BT, CS SWFORM V2 Beta test, DD Beta Tester, PHub Beta Tester, P BME beta tester
Lee, just read the changelog... and if you're still on the aging v328 you might read the changelogs for the last couple of drivers while you are at it^^
Loaded new driver and firmware all ok except on Rfactor 2 and Assetto corsa I get 100% cpu occupancy and run slowly as I did with the previous driver 365, if I leave the new firmware but revert to driver 356 all is ok.So I can use new firmware but not new driver.
Hm, I can't confirm this. What's your CPU? Did you have a look in the task manager, if your CPU usage increases when you start your wheelbase with driver 372?
hi there just downloaded these drivers and wheel works fine but i dont have the speed on my rim showing also my v3 setup page isnt showing now so i cant adjust the pedals all i get is when i click on v3 -properties the wheel settings page comes up i dont have a cable from the wheel too the pedals the pedals are plugged direct into pc. the pedals themselves seem too work fine i just cant adjust them ?
Maurice BöschenMember, CSL E RP1 PS4 beta tester, RMcL BT, CS SWFORM V2 Beta test, DD Beta Tester, PHub Beta Tester, P BME beta tester
Comments
That's not necessary, no. In fact, I never detached my wheel in hundreds of base firmware updates.. ^^
Just be aware that the base will restart in Xbox mode when you have a Xbox compatible wheel attached so it's not recognized by Windows anymore until you switch back to pc mode.
You can leave the rim attached to your wheelbase while flashing the firmware of your base.
Great, thank you.
Anyone? Can't find any info about this
I also had this issue with my DD1. I found that once I updated the Wireless Quick Release Firmware I was able to successfully update the motor firmware.
Podium DD2 with formula V2 wheel.
Updated from V365 with all associated firmware.
After doing all the firmware updates (wheel base, motor, wheel), I then ran the motor calibration and there was a very big jolt as the motor started the first rotation.
Ran it a 2nd time and it worked as normal.
Everything else is good so far.
Did anything else change? I am on the new driver and notice the FFB has improved quite a bit. It seems quicker and more responsive and with less oscillations.
That would not be unrealistic due to the many improvements under the hood ;-) Thanks for the positive feedback!
Is the correct install procedure the following
Install new driver leaving existing in place
Install new Fanalab leaving existing in place
or
Remove existing driver
Install New Driver
Install new Fanalab over old one?
Any help appreciated, I read the full first post and the pdf manual but it doesnt mention if old driver should be removed first.
Cheers
Remove old driver and FanaLab, reboot the pc, install new driver, restart the pc again, install new FanaLab version - enjoy.
I had no issues with updating my DD1 for PS4 at all.
I think it's very important to remove all drivers, reboot before installing the new one, and reboot again.
Follow the message as well to calibrate the motor by removing the wheel.
I've followed these steps and had zero issues, I put back my settings and on F1 2020 everything feels quite nice ( it was a bit too warm to drive though ).
NO! THIS IS NOT IN THE INSTRUCTIONS.
Read my earlier posts. On CSL-E 1.1 this caused major issues. Updating the driver should be done in-situ.
If removing the old driver first was required, it should be in the instructions!
Not gonna comment on Fanalab because I did not have the older version installed.
Thats the proper way to uninstall and re-install an update though.
Its always bad to install over an exisiting installation, always remove the old stuff first to avoid strange issues which can happen with leftovers of previous version if you dont update properly.
Your issue might be speciial to your hardware configuration.
any reason to use this driver over the 328 driver offially listed on the website? for a csw 2.5
Yes, read the Changelog... BME compatibility, Drift Mode fixes and much more.
"much more"? that's not information or a reason, that's useless, any reason for this driver for a normal csw 2.5 and universal hub? any ffb improvements?
Some report there is a ffb improvement, yes.
Well I can't quote the whole Changelog since 328 so you have to read all the Changelogs yourself and judge if it's worth for you to update.
Lee, just read the changelog... and if you're still on the aging v328 you might read the changelogs for the last couple of drivers while you are at it^^
Loaded new driver and firmware all ok except on Rfactor 2 and Assetto corsa I get 100% cpu occupancy and run slowly as I did with the previous driver 365, if I leave the new firmware but revert to driver 356 all is ok.So I can use new firmware but not new driver.
Podium wheelbase dd1 ps4
Clubsport PBME
W/B firmware v674
Motor firmware v40
WQR firmware v6
PBME firmware v13
Fanalab v147
Hm, I can't confirm this. What's your CPU? Did you have a look in the task manager, if your CPU usage increases when you start your wheelbase with driver 372?
CPU is I5 7600 k only get high occupancy in rfactor 2 and assetto corsa all other games appear to be ok i will check in task manager
+4 and +5 where removed because they were impractical, rest is still as it should
Can you please send me the logs which are located in C:\Users\Public\Fanatec Logs
Thanks Maurice, one last question, export existing profiles from 1.24 Fanalab and import to 1.47 will convert them to new version correctly?
Thanks for any info
hi there just downloaded these drivers and wheel works fine but i dont have the speed on my rim showing also my v3 setup page isnt showing now so i cant adjust the pedals all i get is when i click on v3 -properties the wheel settings page comes up i dont have a cable from the wheel too the pedals the pedals are plugged direct into pc. the pedals themselves seem too work fine i just cant adjust them ?
you can only open the property page of the pedals when the base is powered off. This is a long time issue since forever.. ^^
1.42 was not an available version but yes, should convert properly.
thanks maurice also is v3 firmware version still 1.30 ?
Yes understand, I was using as I have the PBME on a Porsche Podium Wheel and was included in the
Button-Module-Endurance-Software-Package-v1-2.zip
Only have a few profiles so can easily recreate them if conversion doesn't work. Thank you again for the information.
Cheers
yes, it always was 1.30 since they were released 5 years ago and its unlikely that there will ever be a new one.^^