I understand the VE value that appears in logs is taken directly from the VE table(s). I observed values for VE in the log that are definitely not in in the VE table. In this screenshot note the logged VE is 332.80 and the table value is 16.7.
The value interpolates between cells. So the exact value from the table cell will display only your RPM and Load has exactly the same values as the table axes.
Also the log graph interpolates between logged data. Press shift S on the graph log to change line style for the line with dots (what represent logged data samples).
The largest value in VE 1 is 82.8 so there’s no way to interpolate a value of 302.8.
I have not observed another occurrence of this. When it happened, I had just updated the firmware and immediately started up and drove off. Could it have been an initialization issue that was resolved when cycling power on the ECU? As I said, I have not seen a repeat incident.
Simple mistake here. You aren’t looking at the right portion of the log. It states that you hit a max of 332.80 in that particular section. However your cursor (big line down the log file) is NOT even on that mark that is reading 332.80 but rather your cursor is slightly to the right of that where you are indeed reading the exact VE that is in your table.
I had moved the cursor out of the way to make the “flagged” maximum more visible. My question is how did that flagged maximum of 302.80 happen when the VE 1 table has a maximum entry of 82.8? The 302.80 is not an isolated blip; If I sweep the cursor across that area I get a range of values in the 200s and 300s. The maximum log scale for VE is 200, so I can’t display the whole peak.