Getting user feedback early and often is entirely consistent with modern software development practices. However, at some point, you have to be able to deploy a production release that isn't experimental. That hasn't happened in at least six months (since v335).
What happens is, when you don't keep a release branch in a ready-to-ship state, then you can't respond with a targeted fix when a bug is found in your current production release (as in the aforementioned v335). You end up having to fix the bug and then ship whatever else is in your development branch alongside the fix, regardless of whether those other commits are ready.
I'm seroius about the fact the Fanatec wheel bases don't reboot to PC mode after a firmware update. Reading through this forum here and several other simracing forums I find, that one out of three complaints regarding this new firmware is related to the base rebooting to something else than PC mode after updateing the firmware. Please put that on your buglist with high priority and have it fixed asap (sorry for the harsh word).
Gives people more confidence and saves you a lot of time and probably some grey hair ;-)
I have tested this update and my USB froze when I tried to go to game controllers after doing all FW updates, it actually froze all USB devices and I had to restart (via RDP from a laptop, PC still worked fine).
Also when idle in Windows or driving, my rim is getting a weird tingling/trickling, maybe a FFB noise? I always had this even with 335 but very very low, with this update it became uncomfortable and noticeable. I tried FEI and INT but none of the changes fixed it, tried erasing and calibrating motor couple times.
This update seems to have bricked my Podim base. I can't get it to work with any driver now. My PC doesn't seem to even know its connected. Any idea on how to solve this?
Yes it always has it, exact from the moment when i install the new firmware and also i have the exact same issue like the other guy, when im trying to click on update motor firmware the software freezes.
I haven't upgraded to v352 yet, given that some CSW 2.5 users have reported issued with it I held off. I do still have the notchy feeling on 347 with motor FW 20 - but based on the testing a few of us did in a previous FW update thread, that combination seemed to be the best balance of notcy feeling and coil whine. This combination still has both the notchy feel and coil whine for me, but not to the extreme that other combinations did.
For me, it is easy to reproduce though, as it begins happening as soon as the wheel base is powered on.
This seems to have worked a bit and now Fanalab again detects my base. THANK YOU!!!! So simple!
However, in game it cannot detect any steering angle. The shifters and everything else work but there's no response to steering when setting up my inputs. Furthermore, the settings seem unresponsive to the maximum steering anlge. I assume this is the SEN bug people are mentioning????
Int 4 is also possible , tested it a minute ago :D
But even with 80 FEI some of the random FFB spikes are still noticeable, so 70 FEI is the setting if you want them to be completely gone. Raceroom and ACC , DD1.
Are you using the latest Fanalab version? In 1.23 the SEN issue is fixed. Try using 1080° instead of AUTO ingame and in the tuning menu, this might help.
When the base is upgraded to 669, I can't flash the motor firmware anymore (firmware updater doesn't appear and leds are blinking like in this video: https://streamable.com/8niko). I have to downgrade the firmware before.
Yes I've got 1.23 runnning at the moment and the 352 driver but the steering angle detection and sensitivity doesn't seem to register. In trying to fix everyting I flashed the firmware too. I'm wondering if that has killed it? Reverting to version 346 doesn't reslove this either. Do I need to flash the firmware back to an earlier version? What am I doing wrong here? It feels like something is dead inside the base.
Interestingly, the fan is now working on the podium base for the first time ever.
A few hours on raceroom and assetto corsa with driver 352/669/38 it's fantastic but some concerns:
-DD1 makes noise which will be attenuated by INT4 and FEI80
-Slight oscillation
-clack at the stop of DD1
-and randomly clicks while driving.
Here I hope to have been useful. I am back on 346 for the moment.
DD1 BMW GT2
Driver version: 352
FW base version: 669
Wheel FW Version: 28
Does Marcel or Fanatec plan on addressing this power OFF thump bug? It's hardware related...which is probably a bigger issue than your software car not "feeling right".
Electrical motors should NEVER make a mechanical noise. If there is mechanical noise coming from an electrical motor when the motor is switched off, that generally means there is a switching transient and a resulting power surge that is causing back EMF and rotor imbalance. There resulting imbalance is causing the stator to get in contact the rotor in the outrunner motor. This not only causes permanent damage to the magnets but also to the windings.
Can you please solve the Thump Bug on a priority basis? Also does this bug exist on the other driver revisions? I will be uninstalling this beta until it is safe to use on the DD.
Tested it, when [LIN] and [FEI] at 100 , still very heavy random spikes. Also the overall feeling with LIN activated is really weak, so I wouldn't recommend that setting on a DD.
I recommend [FEI] 70 , with [FEI] 80 the spikes will appear, but if you don't pay close attention you will think it's a road texture, but it's definitely thumps to the wheelbase. 90 or 100 FEI shouldn't be used by anyone at all, I hope this stuff didn't damaged my wheelbase.....
Yes having the same, when the steering wheel is in center position you will get small vibrations, moving the steeringwheel a littlebit to one or the other side stops it.
I would recommend that you uninstall 352 and reinstall 346 and report back.
The evidence seems to support that there are power management problems with this software revision and this would corresponds with the Thump Bug during power off. Power surges and over current conditions definitely accelerate dendritic damage on the DD controller.
Personally, I don't think your warranty is being extended for beta testing 352. It is my opinion that this revision does not feel like it was ever ready for public beta. I suspect the software development team was pushed to get this out to the public on Dec 16. Reading all the comments and the laundry list of problems people are facing, it feels like a distraction Fanatec manufactured for missing commitments on other parts of their business.
NOBODY reads the terms and conditions in the software agreement. Continue using 352 Beta at your own risk.
Everyone with a DD will likely see the Thump Bug. The DD1, DDPS4, DD2 all share the same motor and power management chipsets.
This is not a normal condition for operating the motor. I have uninstalled this faulty release as Fanatec will not replace my DD if the lifecycle for the base is diminished due to damaged stator, rotor, and controller.
I forgot to tell you that the DD1 heats more with the 352 than with the 346 and also the steering wheel vibrates when stopped and immediately stops when it is moved slightly.
I forgot to tell you that the DD1 heats more with the 352 than with the 346 and also the steering wheel vibrates when stopped and immediately stops when it is moved slightly.
i have solved it unchecking on map sequential shifter to the shifter paddles and it begans working ok. After that i checked on "map sequential shifter to the shiftyer paddles" and it works.
Comments
Thanks we will investigate on that. Is it always have also when not in-game, or only in-game?
Getting user feedback early and often is entirely consistent with modern software development practices. However, at some point, you have to be able to deploy a production release that isn't experimental. That hasn't happened in at least six months (since v335).
What happens is, when you don't keep a release branch in a ready-to-ship state, then you can't respond with a targeted fix when a bug is found in your current production release (as in the aforementioned v335). You end up having to fix the bug and then ship whatever else is in your development branch alongside the fix, regardless of whether those other commits are ready.
Marcel,
I'm seroius about the fact the Fanatec wheel bases don't reboot to PC mode after a firmware update. Reading through this forum here and several other simracing forums I find, that one out of three complaints regarding this new firmware is related to the base rebooting to something else than PC mode after updateing the firmware. Please put that on your buglist with high priority and have it fixed asap (sorry for the harsh word).
Gives people more confidence and saves you a lot of time and probably some grey hair ;-)
Matthias
Hi,
Florians post under yours contians the settings in case you haven't seen it yet.
In my case i use INT4 not INT6. Every other setting matches perfect.
DD1 here
Win7
I have tested this update and my USB froze when I tried to go to game controllers after doing all FW updates, it actually froze all USB devices and I had to restart (via RDP from a laptop, PC still worked fine).
Also when idle in Windows or driving, my rim is getting a weird tingling/trickling, maybe a FFB noise? I always had this even with 335 but very very low, with this update it became uncomfortable and noticeable. I tried FEI and INT but none of the changes fixed it, tried erasing and calibrating motor couple times.
This update seems to have bricked my Podim base. I can't get it to work with any driver now. My PC doesn't seem to even know its connected. Any idea on how to solve this?
Any advice from the devs what I should try to solve the sensitivity bug?
@Marcel Pfister
Yes it always has it, exact from the moment when i install the new firmware and also i have the exact same issue like the other guy, when im trying to click on update motor firmware the software freezes.
I haven't upgraded to v352 yet, given that some CSW 2.5 users have reported issued with it I held off. I do still have the notchy feeling on 347 with motor FW 20 - but based on the testing a few of us did in a previous FW update thread, that combination seemed to be the best balance of notcy feeling and coil whine. This combination still has both the notchy feel and coil whine for me, but not to the extreme that other combinations did.
For me, it is easy to reproduce though, as it begins happening as soon as the wheel base is powered on.
For me this was fixed using another USB Port, although it was a 3.1 USB Port.
I noticed a while back that all USB ports seemed to work except 3.1 Gen2. Gen1 did work though and that's also what I'm using.
This seems to have worked a bit and now Fanalab again detects my base. THANK YOU!!!! So simple!
However, in game it cannot detect any steering angle. The shifters and everything else work but there's no response to steering when setting up my inputs. Furthermore, the settings seem unresponsive to the maximum steering anlge. I assume this is the SEN bug people are mentioning????
Int 4 is also possible , tested it a minute ago :D
But even with 80 FEI some of the random FFB spikes are still noticeable, so 70 FEI is the setting if you want them to be completely gone. Raceroom and ACC , DD1.
I only have Gen 1 ports so lucky me 😃
You're welcome.
Are you using the latest Fanalab version? In 1.23 the SEN issue is fixed. Try using 1080° instead of AUTO ingame and in the tuning menu, this might help.
ClubSport Wheel Base V2.5
CSL Elite Steering Wheel P1 for Xbox One
PC Driver: 352
Wheel Base Firmware: 669
Wheel Base Motor Firmware: 22
When the base is upgraded to 669, I can't flash the motor firmware anymore (firmware updater doesn't appear and leds are blinking like in this video: https://streamable.com/8niko). I have to downgrade the firmware before.
Yes I've got 1.23 runnning at the moment and the 352 driver but the steering angle detection and sensitivity doesn't seem to register. In trying to fix everyting I flashed the firmware too. I'm wondering if that has killed it? Reverting to version 346 doesn't reslove this either. Do I need to flash the firmware back to an earlier version? What am I doing wrong here? It feels like something is dead inside the base.
Interestingly, the fan is now working on the podium base for the first time ever.
I don't remember... FW 22 is more notchy than FW 20?
Just like to confirm that I also have this. At drift 0 (or off), it feels like being at -5 quite heavy.
I feel no change switching between -5 to 0 at all.
From 0 to +5 it gets lighter again. And at +5 it feels closer to what 0 (off) should be. Perhaps still a bit heavy and dampened.
This is both in game and out of game.
CSW 2.5
PC Driver: 352
Wheel Base Firmware: 669
Wheel Base Motor Firmware 22
+1, same experience here.
Florian, just a theoretical though: shouldn't leaving FEI at 100 and activating LIN actually give about the same results when it comes to spikes?
Does Marcel or Fanatec plan on addressing this power OFF thump bug? It's hardware related...which is probably a bigger issue than your software car not "feeling right".
Electrical motors should NEVER make a mechanical noise. If there is mechanical noise coming from an electrical motor when the motor is switched off, that generally means there is a switching transient and a resulting power surge that is causing back EMF and rotor imbalance. There resulting imbalance is causing the stator to get in contact the rotor in the outrunner motor. This not only causes permanent damage to the magnets but also to the windings.
Can you please solve the Thump Bug on a priority basis? Also does this bug exist on the other driver revisions? I will be uninstalling this beta until it is safe to use on the DD.
Does anyone else feel a constant slight vibration in the steering wheel as soon as the DD1 is powered up? (in a wheel without vibration motors)
I can’t remember feeling that with driver 346.
DD1 + Xbox Hub on latest drivers and firmware for both base and motors.
Tested it, when [LIN] and [FEI] at 100 , still very heavy random spikes. Also the overall feeling with LIN activated is really weak, so I wouldn't recommend that setting on a DD.
I recommend [FEI] 70 , with [FEI] 80 the spikes will appear, but if you don't pay close attention you will think it's a road texture, but it's definitely thumps to the wheelbase. 90 or 100 FEI shouldn't be used by anyone at all, I hope this stuff didn't damaged my wheelbase.....
Also having the tactile sound when turning the DD1 off.
Yes having the same, when the steering wheel is in center position you will get small vibrations, moving the steeringwheel a littlebit to one or the other side stops it.
I would recommend that you uninstall 352 and reinstall 346 and report back.
The evidence seems to support that there are power management problems with this software revision and this would corresponds with the Thump Bug during power off. Power surges and over current conditions definitely accelerate dendritic damage on the DD controller.
Personally, I don't think your warranty is being extended for beta testing 352. It is my opinion that this revision does not feel like it was ever ready for public beta. I suspect the software development team was pushed to get this out to the public on Dec 16. Reading all the comments and the laundry list of problems people are facing, it feels like a distraction Fanatec manufactured for missing commitments on other parts of their business.
NOBODY reads the terms and conditions in the software agreement. Continue using 352 Beta at your own risk.
Everyone with a DD will likely see the Thump Bug. The DD1, DDPS4, DD2 all share the same motor and power management chipsets.
This is not a normal condition for operating the motor. I have uninstalled this faulty release as Fanatec will not replace my DD if the lifecycle for the base is diminished due to damaged stator, rotor, and controller.
Thanks for the info and confirmation Florian. Turning FEI down to 70.
i have solved it unchecking on map sequential shifter to the shifter paddles and it begans working ok. After that i checked on "map sequential shifter to the shiftyer paddles" and it works.