SC 2 Pro in Asetto Corsa disconnecting/turning all the way to right

Hi There,

I am new here but it has been a while since I owned my SC2 Pro, roughly a year and a half.
Not put it to too much abuse over this time.

I had a race today that I needed my device to work, but it sadly failed me.
In the middle of my stint the SC2 Pro motor just turned my wheel all the way to the right, like I cannot turn it anywhere else.
I tested it since a few times, and either the FFB completely goes or just turns all the way to the left, and there is a spring effect pulling it that way, even if I try to center it, it goes back to the full left lock.

Tried to reinstall the firmware for an older one that worked before, no luck.
Turned off all extra settings in the CSP for Asetto Corsa but no luck.
The biggest problem is, it happens totally randomly, sometimes it takes just 2 laps and the motor is out, sometimes I do 30 min and nothing happens then bum, here it goes again.

The only remedy after this happens is to power cycle the motor.
I tried everything I could think off, my suspicion is that this is a HW issue as it never happened before.
The biggest let down is that it happened during a very important race, which I had to retire because of this.

video:

I am going to RMA the unit, tried in different sims and same reaction, either I loose all FFB or wheel goes all the way into the bumpstop either left or right…

1 Like

This can also happen when there is another USB device that disconnects, and the game controller order changes. Games do not generally handle this situation.

Have you tried if this same happens when you drive without the wheel (display) being connected via USB?

1 Like

I will test this, however a couple weeks back, everything worked just fine.
The motor itself doesn’t disconnect, there is like a second and all FFB is gone.
No other device disconnects or connects.

Just to clarify, the motor still functions, steering still reacts in the game, however the damping effect either pulls the wheel to one side or completely removes all FFB effects…

I should have clarified in the title, the FFB disconnects, motor still works, however not as intended.

This is very strange indeed.

1 Like

Are you sure its the damping effect that pulls the wheel? How about when this happens, and you change the Directinput damping effect to 0%, then the Damping does not do anything.

Sorry using wrong terminology, it’s like a spring pull, as seen on the video in the original post.
It’s like a centering force, but instead of centering, it pulls to the side.
Also the FFB effect loss happens more frequently.
I even turned off the safety features when your hands are off, and lovered everything to minimum.
The unit is also not overly hot, just warm in the back when the connection ports are.
Top and bottom is almost cold.
After the loss of FFB effects the motor is useable but to regain FFB a power cycle is required.
The whole thing is weird as it happens randomly, sometimes within 2 minutes other times in 15min etc…

You are not the only one to report this in the last two weeks. It is almost as if there is something else going on. :thinking:

1 Like

Maybe something in the driver?
Not sure, I have uploaded my log data from the unit to the cloud if that helps, however true drive is reporting the unit to be working just as if nothing happened.
Might be a fault on the PCB?
I can downgrade the firmware even further, as previously I only went one release back…maybe I should try to go back more.

We haven’t released any new firmware over the last month, so it can’t be that.

One more thing I was thinking about is, I know there were issues with some devices with DirectInput couple weeks back, due to a Windows Update.
Recently there were many more windows updates (when I get home I will check the history of updates).

Up until around last week, the issue was not present, so there might be a chance an MS Windows Update might have broken something…

I must also mention that at one point last week, there was a moment when there was an overcurrent problem in the TrueDrive software, it stated “high voltage current spike protection”…
I will have to dig out the error code however as I cannot remember exactly what was it but I took a screenshot of it.

Hope the above helps…

Error code was “440205” to my above comment.

Can you please let me know how to proceed going forward?

We have gotten a few (around 5) of similar reports very recently over the last two weeks. Its not completely out of the question that this would be hardware related, but to me it does seem that something else is going on. Certainly any USB issues have previously turned the wheel always to the left, if even that. Turning right is a news to us, and that there are suddenly these reports (and none during the 3+ years previously) is strange.

I just checked whether or not any recent Windows updates could have anything listed on them related to gaming, devices and such, and couldn’t find anything.

Hi,

What other software are you running on your PC related to simracing? Have you recently made changes, e.g. updated to the new Heusinkveld Live software?

Hi Mika,

I only run a Moza FSR steering wheel (Moza PitHouse), have Simforge MK-1 pedals (no software needed), have a simagic SQ8 shifter (no software), I have SimHub installed but not running (not running my transducers for races at night for obvious reasons).
Other than that, I do not recall running anything else.
I am on Win 11 Pro, few months old system. Antivirus is Bitdefender Total Security.
I am running Razer Synapse for my keyboard and mouse.
MSI Center for my motherboard and RGB.

Hope the above is sufficient information.

Took the log out:
Simucube Boot : 1
Simucube Boot : 3
Simucube Boot : 55
Flash settings data loaded : 0
First-time drive initialization : 0
Initial config has been previously performed. Initializing Drive. : 0
Wireless: State change : 0
Wireless Init: Starting to connect : 0
Wireless Init: Init complete : 0
Wireless: State change : 2
State: Initializing Drive : 0
Wireless: State change : 3
Command: Request profile number : 0
Command: Request profile name for profile : 0
Command: Request profile byte data for profile : 0
Command: Request profile number : 0
Command: Request profile name for profile : 0
Command: Request profile byte data for profile : 0
Command: Request hardware settings : 0
Drive init stage 1, position : 2581125
Read MMC value from Drive : 22800
Read Motor Resistance value from Drive : 700
Read CPR from Drive : 4194304
Read Drive Version ID from drive : 40000
Simucube 2 Serial Number : 11617
SM Watchdog disabled successfully : 0
Successfully applied DRC data to Drive : 0
Read MMC value from Drive : 22800
Read Motor Resistance value from Drive : 700
Read CPR from Drive : 4194304
Read Drive Version ID from drive : 40000
Simucube 2 Serial Number : 11617
Waiting for servo to be ready : 0
Drive init stage 3, position after faults cleared : 2581125
Drive init stage 4, phasing, current position : 2581125
State: Waiting for Drive to get ready : 0
Command: Set calibrated analog axis mode : 0
State: Waiting for Drive to get ready : 0
Command: Request profile byte data for profile : 0
State: Waiting for Drive to get ready : 0
Command: Request profile name for profile : 0
State: Waiting for Drive to get ready : 0
Drive init stage 4, phasing, current position : 2581125
State: Waiting for Drive to get ready : 0
Drive init stage 4, phasing, current position : 2581108
State: Waiting for Drive to get ready : 0
Drive init stage 4, phasing, current position : 2581101
State: Waiting for Drive to get ready : 0
Drive init stage 4, phasing, current position : 2581104
State: Waiting for Drive to get ready : 0
Drive init stage 4, phasing, current position : 2581102
State: Waiting for Drive to get ready : 0
Drive init stage 4, phasing, current position : 2581104
State: Waiting for Drive to get ready : 0
Drive init stage 4, phasing, current position : 2581049
State: Waiting for Drive to get ready : 0
State: Drive initialization was successful : 0
Command: Set baudrate state : 0
SM Watchdog enabled successfully : 0
SMBus baudrate initialized successfully : 4500000
State: Before operational - calculating new constant values : 0
State: Operational : 0
Command: Start reading some servo drive parameters : 0
State: Operational : 0
Command: Reading the requested servo drive parameters : 0
State: Operational : 0
Command: Write some servo drive parameters : 0
State: Operational : 0
Command: Unset temporary centering mode : 0
State: Operational : 0
Command: Set wheel center here : 0
State: Operational : 0
event 96 : 10295724
State: Operational : 0
Command: Request hardware settings : 0
State: Operational : 0
State: Saving settings to flash : 0
SM Watchdog disabled successfully : 0
SM Watchdog enabled successfully : 0
State: Operational : 0
Command: Set profile settings for profile : 0
State: Operational : 0
State: Before operational - calculating new constant values : 0
State: Operational : 0
Command: Set profile settings for profile : 0
State: Operational : 0
State: Before operational - calculating new constant values : 0
State: Operational : 0
Command: Set profile settings for profile : 0
State: Operational : 0
State: Before operational - calculating new constant values : 0
State: Operational : 0
Command: Set profile settings for profile : 0
State: Operational : 0
State: Before operational - calculating new constant values : 0
State: Operational : 0
Command: Set profile settings for profile : 0
State: Operational : 0
State: Before operational - calculating new constant values : 0
State: Operational : 0
Command: Set profile settings for profile : 0
State: Operational : 0
State: Before operational - calculating new constant values : 0
State: Operational : 0
Command: Set profile name for profile : 0
State: Operational : 0
Command: Set profile bytedata for profile : 0
State: Operational : 0
Command: Set profile settings for profile : 0
State: Operational : 0
State: Before operational - calculating new constant values : 0
State: Operational : 0
Command: Set profile settings for profile : 0
State: Operational : 0
State: Before operational - calculating new constant values : 0
State: Operational : 0
Command: Set profile settings for profile : 0
State: Operational : 0
State: Before operational - calculating new constant values : 0
State: Operational : 0
Command: Set profile settings for profile : 0
State: Operational : 0
State: Before operational - calculating new constant values : 0
State: Operational : 0
Command: Set profile settings for profile : 0
State: Operational : 0
State: Before operational - calculating new constant values : 0
State: Operational : 0
Command: Set profile settings for profile : 0
State: Operational : 0
State: Before operational - calculating new constant values : 0
State: Operational : 0

There is another state of this issue, a complete loss of any FFB and wheel stuck on the position I leave it on (sticky wheel).
I have recorded a video (bit dark environment but clearly when I am going for a deliberate crash into the walls, the wheel doesn’t move at all, FFB would normally steer the wheel in a direction of the impact/effect from ground and kerbs).
Video to follow once uploaded:

Did you ever get the issue fixed? My wheel base is doing the exact same thing right now. Was working perfectly fine and now just suddenly remembering I just updated windows and it got even worse can’t even go one turn without it turning all the way to the left or right. Spins it all the way to the wheel lock.