Since last week, i’ve got an issue with the True Drive 2022.2 build and my SC2 Pro.
Mate in my team got the same setup and the same problem too. SC2 PRO v2 / Ascher B16-L HUB Wireless BTLE
We’re loosing the bluetooth SC2 <> HUB Ascher connection, USB.
Need to wait 3-5 seconds to resync, the wheel control come back and again after few seconds we lost again the device.
It’s totally random.
Closing True Drive and hardware restart of the SC2 don’t fix the problem.
Only switch off SC2 and reboot computer fix it for a few moment.
Simucube Boot : 1
Simucube Boot : 3
Simucube Boot : 12
Wireless: State change : 0
Flash settings data loaded : 0
First-time drive initialization : 0
Initial config has been previously performed. Initializing Drive. : 0
State: Initializing Drive : 0
Drive Firmware update : 0
Drive Firmware update : -100
Drive firmware updated successfully : 0
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 : 1296739
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 : 9147
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 : 9147
Waiting for servo to be ready : 0
Drive init stage 3, position after faults cleared : 1296409
Drive init stage 4, phasing, current position : 1296386
State: Waiting for Drive to get ready : 0
Wireless: State change : 2
State: Waiting for Drive to get ready : 0
Drive init stage 4, phasing, current position : 1295689
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 : 1295684
State: Waiting for Drive to get ready : 0
Drive init stage 4, phasing, current position : 1295912
State: Waiting for Drive to get ready : 0
Wireless: State change : 3
State: Waiting for Drive to get ready : 0
Wireless: Scan response : 62
State: Waiting for Drive to get ready : 0
Wireless: State change : 4
State: Waiting for Drive to get ready : 0
Wireless: State change : 5
State: Waiting for Drive to get ready : 0
Drive init stage 4, phasing, current position : 1295970
State: Waiting for Drive to get ready : 0
Wireless: Connection parameters : 1
Wireless: Connection parameters : 6
Wireless: Connection parameters : 0
Wireless: Connection parameters : 50
Wireless: Connection parameters : 27
State: Waiting for Drive to get ready : 0
Wireless: Connection parameters : 1
Wireless: Connection parameters : 6
Wireless: Connection parameters : 0
Wireless: Connection parameters : 50
Wireless: Connection parameters : 251
State: Waiting for Drive to get ready : 0
Drive init stage 4, phasing, current position : 1295980
Wireless: Connection parameters : 1
Wireless: Connection parameters : 6
Wireless: Connection parameters : 0
Wireless: Connection parameters : 50
Wireless: Connection parameters : 251
State: Waiting for Drive to get ready : 0
Drive init stage 4, phasing, current position : 1296056
State: Waiting for Drive to get ready : 0
Drive init stage 4, phasing, current position : 1296074
State: Waiting for Drive to get ready : 0
State: Drive initialization was successful : 0
State: Set baudrate : 0
SM Watchdog enabled successfully : 0
SMBus baudrate initialized successfully : 4500000
State: Before operational - calculating new constant values : 0
State: Operational : 0
Wireless: Connection parameters : 1
Wireless: Connection parameters : 6
Wireless: Connection parameters : 10
Wireless: Connection parameters : 200
Wireless: Connection parameters : 251
State: Operational : 0
Wireless: Low RSSI detected : 20
Wireless: Battery Voltage : 0
State: Operational : 0
event 260 : 0
State: Operational : 0
event 261 : 0
State: Operational : 0
event 262 : 0
State: Operational : 0
Wireless: Connection parameters : 1
Wireless: Connection parameters : 6
Wireless: Connection parameters : 10
Wireless: Connection parameters : 200
Wireless: Connection parameters : 251
State: Operational : 0
Wireless: Uptime : 1056
State: Operational : 0
Wireless: Uptime : 1057
State: Operational : 0
Wireless: Uptime : 1058
State: Operational : 0
Wireless: Uptime : 1059
State: Operational : 0
Wireless: Uptime : 1060
State: Operational : 0
Wireless: Uptime : 1061
State: Operational : 0
Wireless: Uptime : 1062
State: Operational : 0
Wireless: Uptime : 1063
State: Operational : 0
Wireless: Uptime : 1064
State: Operational : 0
Command: Request profile number : 0
State: Operational : 0
Command: Request profile number : 0
State: Operational : 0
Command: Request profile number : 0
State: Operational : 0
Command: Request profile number : 0
State: Operational : 0
Command: Request profile number : 0
State: Operational : 0
Command: Request profile number : 0
State: Operational : 0
Command: Request profile name for profile : 0
State: Operational : 0
Command: Request profile byte data for profile : 0
State: Operational : 0
Command: Request profile number : 0
State: Operational : 0
Command: Request profile number : 0
State: Operational : 0
Command: Request profile number : 0
State: Operational : 0
Command: Request profile number : 0
State: Operational : 0
Command: Request profile number : 0
State: Operational : 0
Command: Request profile number : 0
State: Operational : 0
Command: Request profile name for profile : 0
State: Operational : 0
Command: Request profile byte data for profile : 0
State: Operational : 0
Command: Request hardware settings : 0
State: Operational : 0
Command: Request hardware settings : 0
State: Operational : 0
Command: Request hardware settings : 0
State: Operational : 0
Command: Request hardware settings : 0
State: Operational : 0
Command: Request hardware settings : 0
State: Operational : 0
Command: Request hardware settings : 0
State: Operational : 0
Command: Request hardware settings : 0
State: Operational : 0
Command: Set calibrated analog axis mode : 0
State: Operational : 0
Command: Request profile byte data for profile : 0
State: Operational : 0
Command: Request profile name for profile : 0
State: Operational : 0
Wireless: Uptime : 1065
State: Operational : 0
Wireless: Uptime : 1066
State: Operational : 0
Wireless: Uptime : 1067
State: Operational : 0
Wireless: Uptime : 1068
State: Operational : 0
Wireless: Uptime : 1069
State: Operational : 0
Wireless: Uptime : 1070
State: Operational : 0
Wireless: Uptime : 1071
State: Operational : 0
Wireless: Uptime : 1072
State: Operational : 0
Wireless: Uptime : 1073
State: Operational : 0
Wireless: Uptime : 1074
State: Operational : 0
Wireless: Uptime : 1075
State: Operational : 0
Wireless: Uptime : 1076
State: Operational : 0
Wireless: Uptime : 1077
State: Operational : 0
Wireless: Uptime : 1078
State: Operational : 0
Wireless: Uptime : 1079
State: Operational : 0
Wireless: Uptime : 1080
State: Operational : 0
Yup but sad to downgrade, gonna loose all the improvements done by the new build.
I’m running True Drive in debug mode with full logs, waiting to the issue reappear to post it.
But clearly, it’s the build 2022.2 the issue. Never got that with the older.
Going to downgrade next week for the 24h Nurb if i don’t find a fix, yeah.
As far as we know, the issue affects only the detection of the wireless wheel receiver module in the Simucube 2 wheelbase. If it is detected at all on device start, then everything will work fine afterwards.
It is detected at the start, no problem. The issue come after and it’s totally random.
Loosing direction during session.
Listening “tada” windows sound like new USB is on.
After few seconds, wheel come back.
Look like True Drive “time out” -> “Lost connection” to Paddock Profile few moment. Refresh and reload the profile.
Going to “stable AGESA build” on my C8H with old 3XXX bios version for USB support.
The only modification i’ve done to my setup was this bios upgrade for new AGESA 0.6 branch.
Problem is here since this flash.
Checked windows events and no errors found about sys / app.
Version 4006
2022/03/10 20.65 MBytes
ROG CROSSHAIR VIII HERO BIOS 4006 "1. Update AMD AM4 AGESA V2 PI 1.2.0.6b << this b (beta build may be the source !) 2. Improve system performance for AMD Ryzen 7 5800X3D 3. Improve system compatibility and stability
Thinking about the new v.4006 ASUS BIOS issue with True Drive. They’ve got usb support problem since the launch of the x570 chipset series. Interesting to downgrade it to check this theory !
Smelling chipset bug somewhere
Flashing =>
2021/12/15 20.65 MBytes
ROG CROSSHAIR VIII HERO BIOS 3904
"1. Update AMD AM4 AGESA V2 PI 1.2.0.5 << stable version
2. Improve system performance
I’ve switched my electrical plug (was on inverter) for direct 230v only device pluged in.
No problem after 1h20 on pratice. Hope it’s just an max output (W) problem from my inverter. Cannot deliver the full (W) required. Got no more idea to test
Away this week-end, i will practice more monday if it’s ok or if my sc2 pro base as an issue with USB interface.
To me this sounds like some type of an USB issue, and if you also loose the connection to the wheel at the same time, it is well possible that the whole wheel base reboots due to loss of USB power for some reason. It is impossible to say whether the fault is in the wheel base or somewhere else,without also trying another PC.
How about trying out the latest chipset drivers. I doubt that those are the real issue but it’s something else you could try to rule out if you haven’t done so already.
@EsxPaul I’ve already the last build of x570 drivers. @mixer49 Installing it and tested it, i’ve found my SC2 & 100 mA.
I uninstall all USB devices and reinstall them to assign new mem.addr to the SC2.
@Mika yes, the base reboot with message : device found on True Drive.
My inverter is an 1200 VA EATON
1050W computer + Neo G9 + SC2 was plugged on it.
I move the SC2 alone on another 230v outlet.
ATM, i’m running practice of 3h30 on Nurb24 without USB lost / base reboot
