“This means that any alteration of that implementation in the servo drive firmware algorithms would change feedback feel, which is exactly what we do not want to do.”
Simucube will be a professional ffb SYSTEM for simracers, not a pure technical motor control part. A system must be designed to satisfy users, not to satisfy the devs. "We don´t want to change the feedback feel in firmware? OK, but than there must be an additional part in or beside the firmware, which allows useres to set up the system as their own visions.
Non professional users who don´t want this, are buying Logies, Thrusties or Fanas. But this is not your target group. If a professional software do not offer more options than a one click solution, there is no need to use.
Eddy, we do now acknowledge the setting you would like to change, and in principal, we know how it changes the feel of the wheel. However, we will have describe it with some other means than a random servo drive power consumption parameter.
Target group will want to know what it does and how exactly it affects the feel. We absolutely do not want people guessing and trying random things on forums, which will confuse a lot of users and also make it seem that the system is difficult to use or hard to set up - which it is not, and it will only be easier in the future. Random setting discussions and second guessing on forums will only give more sales to our competitors. For the SImuCUBE system to be relevant in the market, we want to make it very easy to use, give good documentation, and also keep all required advanced settings accessible for advanced users like you to tinker with. Adding a parameter to the UI is not just a simple job, we must provide documentation and default settings too.
If we enabled MPP adjustment right now, there would be no documentation and it would only confuse users. Also, how would we know or limit the MPP value as some of our retailers and also some DIY builders have set it to a particular point because of power supply reasons.This would require some serious thought on how to implement it - maybe similar way to the MMC adjustment would work, but perhaps not. Not a simple one-day job to add it.
Mika, “Do not change a running system” is my motto. For me every thing ist ok so far. My system works well with Granity and mmos. I was only a little bit inquisitively about the beta an thought it was a good idea, to make your life a litte easier with constructive infos. Good luck with Podium, I´m out here…
Your suggestion and feedback has been constructive and very much appreciated.
We hope you understand why we don’t want to have all servo drive engineering parameters visible. We want SimuCUBE to be usable for every sim racer with advanced, meaningful and well explaiend configuration options, without having to know about servo drives, servo motors and their configuration parameters.
Are you still using small Mige?
What power supply?
Looking at your setting your MCC ends up being 4amps + higher than MMC when running slider at 55%. This goes against our previous thinking of where to set the MCC. Many people are running in a similar situation, so I guess it as not as much of an issue as we thought before?
I guess this is a Tero question, how much higher or lower can the MCC be than the MMC without causing problems? And what problems should we expect having the MCC this much higher or lower than the MMC?
You should have the best settings in the world! LOL
The nice thing about having your settings is on new builds if something does not feel right, a person could load your settings to see if the problem still exists. That way we are comparing apples to apples.
In testing different MCC Values I have never really felt a difference between low and High settings as long as it is far enough away from MMC to be able to allow the system to initialize… In the drc files that I have on iRacing they have the MCC set for the Peak Of Sine Continuous Current level of the Servo via it’s specs and that is what I have been running for a long time… I have found that having them with that sort of spread helps to keep anomalies in PSU thresholds from affecting whether or not the SimuCUBE works as I have found some systems tolerated .5A difference some needed more Like 1A difference and others required even more than that… I could not tell you why those differences were required but they were…
After reading things in this thread Brion I am wondering why things like the spread between MCC and MMC do matter. That is why I am asking the questions I am asking.
I have not found that it does matter and I have had the MCC way down at one point something like 3A… Someone, I think it was Esa (asked a long time ago, I think it was basically in reference to what happens when the SimuCUBE software drops MMC lower than MCC, Which is what you asked) because I was having issues with the calibration closeness mentioned and was curious about the above and it was said it was the Fallback current that goes into effect if there is a thermal issue detected or some other errors where it needs to protect things… The only other time it is used is during the phasing. This means the likely hood of actually ever using the MCC current in our application is minimal. This is why in the .drc files I just chose to use the Continuous Current settings for the servo so that if it ever did have to trigger it would trigger to within spec of the servo’s continuous running parameter.
