There is no separate EEPROM chip. The settings are written on block in the flash memory on the microcontroller (CPU). The manufacturer of these microcontrollers quarantees at least 10000 write cycles on the flash, it should be enough for the lifetime of the product. Probably there is a very large margin before they start to fail. Also, there haven’t been any related issues in the lifetime of Simucube 1 yet.
10000 write cycles with 100 changes in a week will last you 1 year 11 months, guaranteed.
Nothing to worry about, SC3 will be out way before that.
On a serious note, may be hitting that Save button only for fully tuned profile, not after each and every change, is not such a bad idea. I know some people even have car specific profiles, so it’s not just per title save.
With MMos only one profile was stored in EEPROM and the rest was in a file system, SC2 as SC1 are still young, so it’s not an issue now, but may be when things get less busy GD can consider similar practice or at least give option on where to store profiles, if that’s even possible with current HW.
Yes would je a shame if simucube has to ben thrown away after some years because of An eeprom that costs only some euro. If saving profiles to other location is possible that would eliminatie that possible problem. I Mean dd Wheels are supposed to be built to last…
I have thought about this aswell, but not bothered writing this question on the forum.
But I think it is iimportant not to use the flash-memory to save settings if it only have 10000 write-cycles, only for important firmware upgrades, even though it is very highly possible it will not happen for a normal user to write that much.
Hence, there are some POWER-users out there @Mika.
It depends on if the changed settings is getting applied directly to the FFB after editing, without saving it to the flash-memory, and the settings getting lost if turning off the Simucube.
If it works like that, I guess it is okay to save to the flash-memory, if any changes are made, after poweroff, and with the user permission.
Hence, if a user makes any changes of a profile, the user feels that directly in the FFB.
If satisfied, the user presses the save button, and Truedrive software confirms that and notifies the user that changes will be saved to flash-memory after poweroff, or something like that.
Though, if it is required to save the changes on the flash-memory to feel the changes having made, it is another case, because as a user, I may change a profile for my needs, several times until I am satisfied. Limiting the flash-memory saves each hour, or only on poweroff, is not good in this case.
The only thing that can somewhat reduce number of actual saves, is to warn the user of limited writes to the memory, sadly it is…
settings are applied to the device automatically. There used to be a notification of that, but it was taken out for some reason (not my decision). So save button only has to be pressed for permanent saving.
Unless we can change things so we can run the device in high torque mode without the software i almost see no point in ever saving profiles to eeprom.
Once the software is open and we have enabled the high torque it is trivial to select the profile we intend to run and only keep it in memory.
I would certainly prefer to have the option to know when saves are being made rather than having auto saving slowly degrading the lifespan on a wheel which theoretically should last a really long time.
Auto save on power off, user prompt, all that sounds like over-engineered and confusing to end user solution.
MMOs saves all profiles in MMosForceFeedback.ini file located in the same directory as executable.
But it’s just plain standalone exe without install, for those with install, the best practice for user specific settings, files is User\Documents.
MMOs app starts, the default is loaded from EEPROM, then you can pick up one from the list and it’s loaded from disk into memory. Can TD do the same, you need to choose profile anyway, does it really matter where it gets loaded from?
Can someone explain to me how exactly Ture Drive works. If I change a setting in True Drive, do I need to Save to Simucube for the change to take effect? How about when I change the profile in True Drive, do I have to do anything else for the change to take effect or is it done instantly?
Switching profile switches the profile instantly on the device.
Changes to any profile parameters are applied to the device once every second (if any changes.)
Save button saves the settings on the device permanently.
Thanks for the info. So what exactly is the point of saving to Simucube? We have to start up True Drive to enable High Torque mode, why not just load profiles from disk and use those?
Also where do the profiles at True Drive start up get loaded from? Simucube or the last used ones? So for example if I save my settings to Simucube and then change one parameter (lets say reconstruction filter from 3 to 5) and don’t save it to Simucube, what will the value of the setting be once True Drive is restarted (3 or 5)?