Minimum IPW
HTML Code:
<table name="minimum ipw #1 shll2-nop (0x4908 - 0x0009)" category="misc" address="2af7a" type="1d" scaling="hex16"/> <table name="minimum ipw #2 shll2-nop (0x4908 - 0x0009)" category="misc" address="2af7c" type="1d" scaling="hex16"/> <table name="minimum ipw #3 shll-nop (0x4900 - 0x0009)" category="misc" address="2af7e" type="1d" scaling="hex16"/> <table name="minimum ipw shll0" category="misc" address="1102" type="1d" scaling="ipw16:shll0"/>
Last edited by pisyakot; Sep 23, 2015 at 03:11 AM.
I don't seem to have scaling="ipw16:shll0 i have InjectorLatency and IPW mcsec under scaling.
HTML Code:
<table name="minimum ipw #1 shll2-nop (0x4908 - 0x0009)" category="misc" address="2af7a" type="1d" scaling="hex16"/> <table name="minimum ipw #2 shll2-nop (0x4908 - 0x0009)" category="misc" address="2af7c" type="1d" scaling="hex16"/> <table name="minimum ipw #3 shll-nop (0x4900 - 0x0009)" category="misc" address="2af7e" type="1d" scaling="hex16"/> <table name="minimum ipw shll0" category="misc" address="1102" type="1d" scaling="ipw16:shll0"/>
Yea the source code in post 211 and 212 do not work for me. Using 88591715 and inserted patch into 88590715 xml file and i can't view anything in ecuflash when the tune opens.
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
Its probably not what you want to hear, but the minimum IPW patch is totally unnecessary if the injectors are tuned properly. In fact the minumum IPW is a complete kluge for when we had no idea about partial opening injector response. See my thread on 2150 settings.
I read through that thread a while ago but didn't get the above understanding. Are you saying that with the latency value added to the pulsewidth adder added to the commanded pulsewidth the value will be above the standard minimum IPW?
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
The best way I can explain it is that the minimum pulsewidth trick is being used as a hack way to represent the partial opening non-linear flow response of these injectors. However, it only works at one specific condition, namely at idle. The pulsewidth linearization table covers the entire offboost driving range.
Thread Starter
Joined: Feb 2007
Posts: 9,486
Likes: 67
From: Melbourne, Australia
so... really the MinIPW patch is meant to help people with their stock rom setup with 1.280... obviously people that have 1.024 as their stock value wont see much value from this patch...
Having issues with 96530706. 1650s on pump. Evoscan logs no less than 1.28ms, Have applied the patch my xml, tables show up in rom. Change Min to less than 1.28 and never see less than that in evoscan, Idle AFR in the 13's. Anyone able to shoot me a tested/working rom and their 9653 xml to see what my issue is? Email is hernandez.954@gmail.com
a couple of things your going to want to look at:
Your injector voltage latency table. Because its a hard coded value that is added to every fuel calc.
Injector flow rate linearization table: https://www.evolutionm.net/forums/ec...ion-table.html
Hope that info helps.
Your injector voltage latency table. Because its a hard coded value that is added to every fuel calc.
Injector flow rate linearization table: https://www.evolutionm.net/forums/ec...ion-table.html
Hope that info helps.
I run the FIC 1650's on pump with no problem using a different rom for a IX, but idle is ~1.1ms. Injector linearization tables won't affect your problem because they don't apply until below ~0.6ms. You got something restricting the lower limit of the injector pulsewidth so make sure you added the correct XML for MIPW. If you have maxed out your trims and your latency is around what I have below then you probably need to increase your injector scalar. Here are my values...
Minimum IPW = 0.024
Injector Size Scaling = 1392
Injector Latency = 0.936@14.06V
Minimum IPW = 0.024
Injector Size Scaling = 1392
Injector Latency = 0.936@14.06V








