I think Bill told me about this before but I wasn't sure if it was a bug or not. Something to do with conversion to binary maybe?
I enter 1.1300 ms into a cell in the min injector pulsewidth table and the result is 1.125. This is not the only table that does this but there are tables where this does not happen.
There are 2 issues with this to me:
1. You don't know if the commanded value is truly 1.13 even if it is just a conversion problem.
2. If you try to copy this data out of the vcm editor for calculations in something like excel you won't get 1.13.