What is going on with the encoder resolution of DD wheelbases?
I've recently purchased a DD1 wheelbase and have always been mocked by my friends saying that simucube products are a bit better on the FFB side. I wouldn't comment on this as I buy Fanatec products simply because of their eco system.
However this constant input of idea makes me start researching. General comments from every Youtube review is that FFB of simucube is a bit more detailed. What might cause that? Other than software issues, the only thing I get from the internet is that it might be affected by encoder resolution (this might be wrong but it's what I get from the research)
So I investigated the encoder resolution of both products. Simucube has stated the resolution of 22bit on their website (more than 4million counts per revolution). However, Fanatec does not state this value very clearly.
I've found this thread of Fanatec's software update, where it's stated that the resolution has unlocked from 8bit to 16bit (around 65000 counts per revolution). It's explicitly explained by the Fanatec staff that the increased resolution makes the FFB more detailed. Thus, it might be true that the 'slightly more detailed' FFB from simucube is a result of their high-res encoder (4,000,000cpr compared to 65,000cpr).
However, from Boosted Media's teardown video of a DD2, it's clear that the wheelbase has an MHL200 encoder chip. This is a 12bit encoder (only 4096 counts per revolution!), you can get the datasheet of the chip from the internet.
Now here comes the problem, how do Fanatec manage to get 65536cpr (16bit) from a 4096cpr (12bit) encoder???
I hope that there's somehow a hidden encoder in the motor itself that Boosted Media's teardown did not cover, rather than Fanatec just scaling up their low-res signal of positional data.