Nothing has changed in the basic FFB code that iRacing uses since… well, 0.7 or something.
1 Like
The corruption issue is just to do with the saved settings data, and user would get that fixed simply by reflashing everything. There is no way to totally brick the SimuCUBE.
Downgrading is even more non-recommended.
0.9.8 currently has the fixes that are listed in the release page, and none of them could affect your issue in any way
I see you have the sincos encoder as you previously told me. I will try to repeat your issue. I also have the sincos encoder, but it appears that my index signal is not wired up for some reason. Interesting, as it definitively was with MMOS when I used the 10k encoder and exactly the same cable…
Thanks Mika.
Well, I might stick with what I have right now as it seems to work, despite us both seemingly not really knowing why? At least I don’t have to always recenter the wheel each time I use Simucube.
Gremlins…
I’ll try the new FW when it’s released.
PS - if there’s any tests or procedures you would like me to try, I am more than happy to try anything.
have you tried the centering with the automatic mode yet?
Yes, that’s what I’m using right now.
It only worked once using 0.97 config tool, but works 100% of the time with .97 firmware but using the .94 config tool.
you mean the automatic worked only once? or the index point based indexing?
that really weird it has nothing to do with the tool.
it does that when you turn on the wheel. even without the tool running.
Using the automatic indexing option when the Simucube turns on vs the manual version where you have to physically turn the wheel after phasing to find the index point - with the 0.97 config tool it only ever found the correct point once. All other times the virtual wheel in the config tool was not in sync with the actual wheel.
With config tool 0.94 it always syncs correctly after phasing and the virtual wheel is in the same position as the physical one.
Very interesting, as the config tool has nothing to do with it. Wheel should be at center if you run the wizard with 0.9.7 config tool (note: it might actually not do all required things with 0.9.4 tool).
Simplest explanation is:
.97 config tool - virtual wheel in tool is not in same position as actual wheel (the wheel is registering movement so it has found an index point, just not in sync with the position of the physical wheel
.94 config tool - after phasing the virtual and physical wheel are alligned
You did re run the wizard with 0.9.7,right?
You mean the “configure motor, encoder and center point”?
Yes.
Or do you mean the “start everything from scratch” option?
Start everything from scratch does not do anything yet. So I meant the wizard.
It would help, if you did the wizard, and then used SimuCUBE as normal while configuration tool is totally closed.
And report back if there is any difference in having the tool open or not. You can go to any game to see if the wheel is straight or not.
There might be a bug, but as there are no wide spread reports, I really need to narrow this to either the configuration tool or the firmware.
So to be clear I understand.
I used the “firmware update” button when I initially downloaded 0.97.
The Simucube updated, asking me to center the wheel a couple of times during the process.
Are you asking that I forget about opening the config tool (whether it’s 0.94 or 0.97) and just use the simucube for racing in iRacing, Assetto Corsa etc to see if the physical wheel is straight since we know it’s using the 0.97 FW regardless of which config tool is opened to do things like change profiles etc?
Thanks.
Yes. That would isolate the config tool messinging anything up.
Ok.
I will power down the Simucube, close the config tool, power the simucube back up and test in game without any config tool open.
Give me a minute
1 Like
The wheel (my physical one) was off to the right about 45-60 degrees when I powered up Simucube and started iRacing without running the config tool.
And now the config tool is showing the virtual wheel not in sync with the real wheel.
I’m at a loss at this point and it’s getting somewhat tedious having to keep re-running the wizard every time I want to use my Simucube.
Appreciate your guidance Mika. If there’s a way to reset everything and just start again I will do that rather than have to essentially run the wheel config every time I power it up.
I may have found something that could cause this to happen with sufficiently high resolution encoder, but I will need have a setup with a suitable encoder and working index signal to debug.
1 Like
Beano is coming over… have him put the kollmorgan into his hand luggage 
1 Like
Hi Mika…
I decided to reflash the .97 FW over the top of the installation to see if it was ok.
The issue was happening but I am pretty sure I have recognized a pattern that I’ve been able to recreate 10 out of 10 times so unless this 100% success rate is just a coincidence, I think I’ve found the issue. Well, I’ve found a pattern but maybe you can figure out why.
If the Simucube is powered up and phases BEFORE the Simucube tool is opened (I’m using 0.97) then the wheel will almost always be off from the virtual wheel, in my case it’s close 45 degrees to the right when the virtual wheel in the tool is centered.
Similarly, if the Simucube is powered up (I always have the wheel centered) and a SIM title opened without opening the Simucube tool, it’s the same result with the wheel being off to the right about 45 degrees.
However, when the Simucube tool is opened before the Simucube is powered on, then it seems to work every time I’ve tried.
If you like I can do this 20-30 times if you feel that gives a better data point?
Hope this helps.
Sean