This is french, mate… Or rather, french translated to english then back to french again (or so it seems…)
^^
1 Like
Oh but I have no idea what happened, I just corrected the text and translated it into English with my excuses
Next release is ready for testing. Changelog is already at
https://granitedevices.com/wiki/Simucube_2_True_Drive_releases
Any testers? 
3 Likes
I like the way “Improvements” sounds rather than the most common “Fixes” in last releases
1 Like
Good evening / Hello
I would like to test this new version, I don’t know if I would be of a good opinion, but I would like to try, I will be available to download it tomorrow around 5 pm, French time zone and not working on Wednesday I could deepen my tests.
I’m hoping to release it tomorrow if I get one or two test reports that it is OK to use (in addition to our internal test cycle tomorrow).
Good morning,
Mika, i’ve been reading the information about the next release and sounds good.
There’s a point: “Fixed the Simucube Wireless Wheel Receiver not starting up in releases 2021.11 or 2021.12.”.
I made an order with an Ascher Wireless from SC webpage on Sunday. Does this steering wheel model have any issue like this?
I’m very very happy with the actual version and after reading some comments about old versions and some issues (downgrading too) i’m afraid of upgrading it. Are these changes noticeable enough to upgrade to the new version?
I could test the new steering wheel with actual version, then with the new one if it’s worth it.
Greetings.
The wheel is not affected.
A small number of Simucube 2 units had issues with how the receiver module on the Simucube 2 itself was communicated with. Issue was only in firmware releases 2021.11 or 2021.12.
2022.2 - is this only software upgrade or will have new firmware? If new firmware, is it mandatory to update it, or I can use the software with my current firmware?
I only own SC2 for about three months and I have no “update” experience so far.
p.s. Asking, because previously I had Fanatec and their releases were a bit mix bag - sometimes you can use only the software, sometimes you are forced to do the included firmware.
Ok. Understood. I didn’t know it. Thanks Mika.
Greetings.
Simucube 2 True Drive will prompt the firmware update after launching when a software update is installed. This happens, if True Drive has a new firmware to install. The firmware installation cannot be skipped.
Some corner cases came up in internal testing, we are investigating. Should not block the release.
Hi Mika and everyone,
I just updated my Truedrive to the 2022.2 version. All was going well until near the end of the firmware update my computer started buzzing and then shut down. Upon restarting all went well until I turned on my Simcube 2 Pro and then my PC shut itself off.
Now it seems that I can’t turn on the SC unit without the computer shutting down, so downgrading the firmware is impossible.
Windows 11 PC.
Can’t get the device running and the PC running at the same time now. I tried different USB ports to no avail.
Please help!
1 Like
This is really unexpected. Is there another PC or laptop you can try?
Basically the firmware update process itself is very much proven already from Simucube 1 days in 2017, so it is really odd fault.
If the buzzing sound came from the speakers on your PC, then it is likely that it is some type of a driver crashing. What others software do you have installed?
Hi Mika,
Thank you for the fast response!
The buzzing was coming from the PC itself. Not the speakers. It sounded like something was going to blow up but then it shut itself off.
I only use this PC for iRacing.
Also, now, when I tried again, when in I turn the unit on I get a blue screen that says Windows Has Encountered a Problem. Your PC will shut down.
Then it shuts down and the Simcube unit is off. Then the PC starts normally.
I’m thinking that the firmware did not complete it’s update on the Simcube unit.
I’ll try a different USB card now.
Kind regards,
James
Mika,
It seems that my USB card got fried. I installed a new one and all seems well.
Pretty bizarre though.
Kind regards,
James
1 Like
So now the wheel works with a different USB card. The new problem is that the iRacing Profile does not seem to save to the SC unit and has to be reloaded each time I come back to race.
Something is certainly buggy here now. Here is my event log:
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
Drive init stage 1, position : 3275159
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 : 2580
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 : 2580
Waiting for servo to be ready : 0
Drive init stage 3, position after faults cleared : 3275160
Drive init stage 4, phasing, current position : 3275160
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 : 3275160
State: Waiting for Drive to get ready : 0
Drive init stage 4, phasing, current position : 3275156
State: Waiting for Drive to get ready : 0
Drive init stage 4, phasing, current position : 3275158
State: Waiting for Drive to get ready : 0
Wireless: State change : 3
State: Waiting for Drive to get ready : 0
Drive init stage 4, phasing, current position : 3275156
State: Waiting for Drive to get ready : 0
Drive init stage 4, phasing, current position : 3275158
State: Waiting for Drive to get ready : 0
Drive init stage 4, phasing, current position : 3275157
State: Waiting for Drive to get ready : 0
Drive init stage 4, phasing, current position : 3275072
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
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
event 260 : 0
State: Operational : 0
event 261 : 0
State: Operational : 0
event 262 : 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
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 bytedata for profile : 0
State: Operational : 0
quick note : placed the order on monday morning at 11am, received the wheelbase in Italy at 1pm today. I guess long gone are the days when I had to wait 3 months for a unit from the 2nd batch, back in 2019. congrats Granite!
6 Likes
What if you save the default profile again, does it then work as expected? I will look around if there is an unneeded profile reset after firmware update.
The way I would like it to work is like this:
Download a profile from the online portal thing, imeediately be able to adjust the sliders in the FFB setup, if I want to save it I click ‘save’ and it saves it locally. Why should it overwrite the original online?
1 Like