Mazda - INJx_CMP as integer values?!?

[tzok]

INJx_CMP are reported as integer values, while they are injection volume corrections in mm^3/stroke, and are typically much less than 1, but different from 0. Typically they are reported with a precision of 0.01 mm^3/stroke.

[FORScan]

INJx_CMP are reported as integer values, while they are injection volume corrections in mm^3/stroke, and are typically much less than 1, but different from 0. Typically they are reported with a precision of 0.01 mm^3/stroke.

What is wrong exactly, only measurement unit (integer instead of mm^3/stroke) or the value is wrong as well?

Values returned by this PID may be different for different models. So investigation should be performed in every particular case. Either we need FORScan internal logs (sent to us by email), or vehicle info (content of Vehicle->configuration tab) and values returned by these PIDs (FSL or CSV).

[tzok]

The value should be float not integer, currently it shows 0, eventually 1 - value seems to be ok, but it lacks precision. I don't currently have any Mazda, so I can't send you logs.

[FORScan]

This is how it looks now in 2.1.19:

INJx_CMP.png (8.26 KiB) Viewed 7735 times

It looks like you use outdated version of FORScan.

[zboq]

This is weird, I also have the newest forscan and it also shows integer value :/.

Maybe You guys have newer version than we have ?
I will look into it again later after work and make a screenshot.

Edit:
This is how it looks like on my laptop.


And when I look at your screen I wonder if "zeroes" means "zeroes" or maybe it's negative value ?

[FORScan]

Looks like it was fixed only for newer Mazda. Mazda 6 diesel of 2002-2004 model year have another PIDs and it was not fixed. Will be fixed in the next version. If you need a test version with this fix, please email to support.