Injector flow rate linearization table
This is all I see when I quote text for the table definition....
"The table definition is listed below for the USDM Evo 9 88590015 ROM. <strong>For the 94170015 ROM, change "31db" to "37c7".</strong> <strong>For the 96530006 ROM, change "31db" to "37c7".</strong> <strong>For the 90550001 ROM, change "31db" to "3977".</strong> <strong>USDM Evo 9 88590015 ROM</strong> </p><table></table><p> 0.016 0.048 0.080 0.112 0.144 0.176 0.208 0.240 0.272 0.304 0.336 0.368 0.400 0.432 0.464 0.496 0.528 0.560 0.592 0.624 0.656 0.688 0.720 0.752 0.784 0.816 0.848 0.880 0.912 0.944 0.976 1.008 1.040 1.072 1.104 1.136 1.168 1.200 1.232 1.264 1.296 1.328 1.360 1.392 1.424 1.456 1.488 1.520 1.552 1.584 1.616 1.648 1.680 1.712 1.744 1.776 1.808 1.840 1.872 1.904 1.936 1.968 2.000 2.032 2.064 2.096"
there's no definition/address or scaling...just numbers.
Am I missing something???
"The table definition is listed below for the USDM Evo 9 88590015 ROM. <strong>For the 94170015 ROM, change "31db" to "37c7".</strong> <strong>For the 96530006 ROM, change "31db" to "37c7".</strong> <strong>For the 90550001 ROM, change "31db" to "3977".</strong> <strong>USDM Evo 9 88590015 ROM</strong> </p><table></table><p> 0.016 0.048 0.080 0.112 0.144 0.176 0.208 0.240 0.272 0.304 0.336 0.368 0.400 0.432 0.464 0.496 0.528 0.560 0.592 0.624 0.656 0.688 0.720 0.752 0.784 0.816 0.848 0.880 0.912 0.944 0.976 1.008 1.040 1.072 1.104 1.136 1.168 1.200 1.232 1.264 1.296 1.328 1.360 1.392 1.424 1.456 1.488 1.520 1.552 1.584 1.616 1.648 1.680 1.712 1.744 1.776 1.808 1.840 1.872 1.904 1.936 1.968 2.000 2.032 2.064 2.096"
there's no definition/address or scaling...just numbers.
Am I missing something???
Thread Starter
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
Quoting the post worked when I first tried it. Its not now though. It appears that the admins are trying to fix all these definitions but not doing it in a way that preserves the original information. I'll check to see what they are doing because I really don't want to have to redo all my posts with this kind of information.
Thread Starter
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
<p>Hey I apologize, but is a bug that should be fixed this week, I hope. </p><p>Bob</p><p>https://www.evolutionm.net/forums/si...l#post11496812</p>
We have the table address, but need the scalings which I would assume would be hex16? but need the x axis address?
Last edited by jedibow; Sep 26, 2015 at 11:38 PM.
Thread Starter
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
ok folks, its fixed. The problem is that the new EvoM text parser is interpreting anything with a < or > as being a parser command. When it encounters the ECUFlash definitions, rather than ignorning the incomprehensible command, it decides to delete it. Yay.
Thread Starter
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
I fixed my first post yesterday. It's had the pulsewidth linearization table information on 9417 and 9653 for a while. I don't have the closed loop integral gain table.
Maybe I am going off topic, but where did you get the integral gain table from? I ma using mrfred's wideband closed loop patch. It works fairly well but it doesn't keep the AFRs as tight as the factory narrow band closed loop. Likely due to the fact that my wideband sensor is further down the exhaust. Tweaking the gain may improve the response.
Maybe I am going off topic, but where did you get the integral gain table from? I ma using mrfred's wideband closed loop patch. It works fairly well but it doesn't keep the AFRs as tight as the factory narrow band closed loop. Likely due to the fact that my wideband sensor is further down the exhaust. Tweaking the gain may improve the response.






