Governor requested RPM is an inaccurate calculaion

In case you do not know something or you are not sure, here is the right place for your question.
Post Reply
thestructured
Posts: 157
Joined: Thu 24. Dec 2015 20:13:20

Though this has not caused any issues that I'm aware of I've always been a bit curious as to why the requested RPM in the gov screen is a different number than you'd get doing the math yourself. It's usually around 10 RPM off. For example I have "max headspeed' set to 3060 rpm and with a 56% throttle curve it should be about 1714 rpm but it shows the requested value of 1704. Or 61% it shows 1848 instead of 1867.

etc.

It is impossible to set perfect numbers like 1700, 1850, 1950, etc. because no matter what you type into max headspeed and what % you use the calculation is off.

Why?
ZeXx86
Site Admin
Posts: 12836
Joined: Mon 29. Apr 2013 16:06:44
Contact:

Hello,

the calculation is performed in the Spirit unit where range is converted to internal one. So there might be a small difference. The difference is rather in the software where rounding can play a role. We will make it consistent so your calculation will fit.

Thank you for your hint.
Spirit System developer
Post Reply