If we create a profile with less overall strength it will also affect bumpstop strength. Is there a way around this without having to change bumpstop maximum strength manually every time when switching profiles?
The overall strength is now set via adjusting the motor current. This is to negate the need for the confusing two-slider strategy (signal scaling and motor amperage setting).
As no consumer wheels have that type of setting, we wanted to remove the need for that. Eventual target remains to remove access to Granity altogether for average users. Whether this is done with the input signal scaling (like it was in 0.7.x series and earlier) or by scaling the motor amperage (as 0.8.0) remains to be seen, but the result of the 0.7.x vs 0.8.0 poll seems to indicate pretty conclusively that if there should be one slider, the motor amperage slider is the one to have.
The result, however, is that also the bumpstops are of course affected. There is no way around that for now, until I revisit the bumpstop code. Boosting it to be proportional to the motor current setting is one option. There is also the bumpstop damping effect that could be redone to utilize the general damping that has since been implemented to SimuCUBE firmware.
Depending on how much you reduced the FEV you might not be getting the error that mika is wanting as if the FEV is too low the servo will fault WHILE phasing and it probably won’t do what mika is attempting to have done… Set the FEV so it shows about 1-2 rev per sec in granity if you were not already at around this point. You will then be able to go into iRacing or another game and get the wheel to fault by turning the wheel fast. you can then reset it by the e-stop to regain function and not have to restart the SimuCUBE which will clear the fault.
Update: getting really close to next release. Solved motor fault reason parsing with Tero. It was totally something I overlooked. Also found out that effect loop was running at 1.25 kHz - and had been, for quite many releases. Upped the rate back up to 2.5 kHz
Please do move it back up to 2.5 kHz.
But maybe not now if it will delay the new firmware by a lot, but for the next release.
And could you tell us until what FW version it was 2.5 khz.
was it before or after the scaling method was changed? or way before that, or even public beta ?
maybe i never tested a version with 2.5kHz
It appears that I made the change on July 20th already. I must find out what caused me to do that change and whether it can be reversed. I don’t believe changes in the effects can be really felt between 1250 Hz and 2500 Hz - please do take notice that these are not related to the torque bandwidth, that is a different thing.
Tero releases it when its time. Its not worth to release only “some minor changes”, as some testing has to be done with our industrial partners, etc. before every release. It would be dangerous to release something that is untested…
