Guess-o-meter becomes too optimistic

[dalathegreat]

After upgrading and adding CAN-bridge, the GOM will be confused since the returned torque value is lower than actual. This will affect the range estimate negatively, it will be overly optimistic. The instant consumption values will also be slightly inflated.

How should we solve this? If we return actual torque applied fault codes will be set, since the returned values cannot differ much from the requested.

One quick fix we could try is to instead of always returning the demand as request, we could find the limit on how much it is allowed to deviate, and just report back the values on the edge of what is allowed. This would make the situation a bit better, but how much?