Fuel Consumption (L/h): Is the Resolution Too Coarse?

Due to implausible values in MWB 15 (during an economy driving mode), I...
I noticed that the values for "consumption in liters/hour" are all multiples of a certain number.
"It's 0.39, which means the grid is really quite coarse."
In this case, all you really need to adjust is the speed, fuel injection amount, and...
Adjust the speed appropriately (using a fixed, assumed value).
Fuel density constants), and these 3 values are accurate to a certain degree.
A document that does not explain this coarse grid.
Am I being completely clueless?
The KFuel plugin might do a better job, but I haven't tried it.

Best regards, Klaus.

The diagnostic data, which is sometimes presented with a relatively coarse resolution, is partially due to the 8-bit format.
For example, the EDC15 in the more powerful engines only displays the ambient pressure with a seemingly unnecessarily coarse 12 mbar grid.
When considering the pressure range, the 12 MB suddenly make sense, as they allow for covering the expected data bandwidth (up to 3060 mbar) with only 255 value levels.

Okay, thank you, then it will be clear.
It appears that the aim was to cover the range from 0 to approximately 100 liters per hour.

Best regards, Klaus.

Klausel wrote:

It seems that the intention was to cover the range from 0 to approximately 100 l/h.

. . . and this was simply imposed on many (even much weaker) engines.
If you know where to modify the MSG hex dump, you can almost precisely adjust the consumption scale to match the maximum consumption of many engines.
It can be done on the computer in a few seconds, but apparently the original equipment manufacturer (OEM) considered it unnecessary to calibrate their diagnostic equipment so precisely.

Counter question: Does the average customer even notice? For the 0.01% of technology enthusiasts, the effort wouldn't be worthwhile. Ultimately, the OEM might not have considered it important from a superficial standpoint, but simply didn't pay for it. Therefore, it won't be implemented or adapted.

Sometimes it seems like you have nothing better to do than to criticize and dissect things in areas that are not interesting to anyone who actually has real problems. :p The diagnostic functions are intended for customer service, not for tuners or similar applications. In customer service, the value ranges are perfectly sufficient. Of course, there are always individual cases, but the OEM is not concerned with individual cases; first and foremost, the general functionality must be in place, which is also known as the 80/20 or 90/10 rule.

Okay, and now let's continue. It's fun to read what people come up with to overcome apparent boredom...