Update: I switched the USB-port to one of my PCI-Express-cards, put the power-supply-plug into another multi socket and so far so good, so it hasn’t appeared anymore since roughly 8 hours of usage. Is it possible the overvoltage protection of the multi socket have caused this issue? My other stuff is also connected (GS-5, G-Belt, amps for Buttkickers) and wasn’t failing, so seems far fetched, but the 442001-error has something to do with power and usually it happend when running over a curb, so some sudden spike in the FFB. It also happened since using more iRacing with and without irFFB.
PS: I just remembered that I had issues one day getting the PC to boot from the same socket and it was booting fine after changing the plug. This overvolt ‘protected’ multi socket is probably the vilian.
Unfortunately the problem came back again and started as usual: Two days ago first some FFB-drops in corners, like the high torque mode is off for some few seconds and goes on again and than a complete FFB-loss today with the same error-message. After my last post I had some drops as well, but after switching USB-cable and PC-plug it was fine for weeks until Wednesday. Parallel to these problems the base is also beeping occasionally for no obvious reason like it’s reconnecting to USB or or turned on. Usually when touching the wheel while not in the sim, but today even without. Now I’ve switched both USB- and power-plug again and problem seems vanished so far as well…
Since it can work for at least weeks between those FFB-drops without any issue, I guess it’s a software problem and possibly introduced by the first Paddock-update in May last year. Never had a problem until this update and the more recent problems happened right after updating to the current version. I was running Classic before.
No answer for my RMA-request since almost a week now and I hope I don’t have to spread the word
Some people have this problem right from the beginning: Fault Location 442001
With my little knowledge about electric motors I now guess it’s a problem with the copper wiring inside doing shorts after heat-expansion (even the base was never more than luke-warm), not the board that had been replaced already with a newer version. Similar problems are so rare, it can’t be EMI or anything else and my VRS DFP replacement-base works like a charme like the Accuforce before for almost 6 years.
Back to SC2 Pro since yesterday, put the new May firmware on, did some stress-tests and so far so good. Could really a firmware-update have caused the problems? I think I’ll sell it and if the new owner encounters the same problem, (probably) he can request RMA till the 2 years warranty expires. Or am I wrong?
First that was the plan, but if the newest firmware works, there is obviously no reason to downgrade. The error-code is saying: “Actual torque exceeded target torque indicating that torque controller might have became unstable” with a reference to this settings, not part of True Drive. Were there any changes under the hood in the last two updates?
No changes that would affect the operation of the servo drive, except for slightly more robust initialization of the hiperface encoder interface on the Ultimate.
So this problem could happen again I guess. And again my question: If I sell it and if the new owner encounters the same problem, can he or she request RMA till the 2 years warranty expires in August?
Btw I switched to the VRS-base soon after again since I’m clearly faster with it. In rF2 it’s like night & day with similar dampening/friction values and in AMS2 it’s about 3 tenths in the GT1 around Donington. The main problem with the SC2 Pro is, that it delivers far too spiky FFB over bumps and curbs I’m not in control of while the VRS with similar holding-torque just does some cues that doesn’t interfere with my racing-line. The VRS never hurt me while the SC2 Pro tried it numerous times and often succeed. But since the torque-control-sensor seems to have a problem, I don’t know if my experience is normal or not. If it’s normal i would suggest to provide better linear settings and if not I want another RMA. Since day 1 the base provided torque-spikes like it’s on Meth. Apart from that issue the SC2 is IMO the better product because of the QR-system, wireless-function, but certainly I keep what makes me faster and is more reliable.
Yes, the SC2-Pro-motor has far less dampening and friction on default and is stronger, but the delivery of FFB is still a software-thing and out of the box I’m quicker with the VRS and it doesn’t try to hurt me. The collision FFB is for example a fraction of the SC2 Pro and never tried to brake my wrist during an oversteer. The latest version of the VRS-software also provides 10 smoothing filters I miss in True Drive. Since I own both and even would prefer to keep the VRS regardless of the SC2-problems, some software-changes should be considered. Just saying.
So you’re still reluctant to try my suggestion which takes no longer than a minute to do? We’ve tried to help but you don’t want to try our solutions and I’d suggest you learn how to tune your True Drive settings
The question is, why are the defaults so high responsive and why are there no easy to choose presets like VRS is doing with it’s filters? I don’t need to change friction and dampening there to choose between responsive (2 levels) or soft (3 levels) or in between (5 levels). That’s IMO the better concept.
You seem to have problems with reading. The latest firmware was running fine and it could take weeks or months till the FFB-drops appear again if it hasn’t been fixed already, not minutes. And if the firmware is causing problems, many more people would have them, so it might not have been properly installed if it has anything to do with the firmware.
Different people, different taste in FFB feeling, different way sims implement in title dampening, some don’t even need any in TD.
And you got reasonable recommendation to revert to pre major rewrite FW version, yes, lots of people are trouble free on the new one, but seems like you might not be in that camp.
You also seem reluctant to take advice that might solve your issue
I have read everything you have said. You stated that you had no issues until you updated the firmware. You’re also saying that the new firmware is fine but then you are still having issues whether it takes a couple weeks or a month? So then it’s not fine?
My solution of downgrading to the firmware where you had no issues takes less than a few minutes.
It seems like a logical way to rule out the firmware and potentially fix your issue
Since there are regular updates, possible problems will always happen after one and there will be a past firmware without problems. I was testing the newest fimrware for several hours and it was running fine. It didn’t happen right after an update and the delay could’ve been weeks. I forgot and I doubt that it is a firmware-problem since it would be replicable and happen way more often here and elsewhere. Since problems appear and also vanish out the blue, it seems more likely there is a loose contact maybe inside a cable or inside the base itself.
I’ve put the base into the box after replicable drops every session within 20 minutes, put it back on, did the new update and it was running fine. So if it was the firmware, it’s fixed. Possible that the emergency stop is causing it? Is there a possibility to use the base without it?
