Start-up Fuel and ISCV Tables
Feb 15, 2013, 06:23 AM
#31
Yeah, in the first two posts. Some are already known tables that I just put together as a group and relabeled, though the 'post-cranking ISCV adder' was one that I had never seen posted before, at least not defined. I basically just showed the major settings I found to be the most useful for dialing-in start-ups.
-Jamie
-Jamie
Mar 16, 2013, 05:09 PM
#33
After helping someone remotely, I found the start-up issue was their injector latencies were too high in the 9.0-12v range. Logging the battery voltage and injector latency in evoscan while cranking the starter helped track down the issue rather quickly. It's not uncommon to see voltage drop to the 9.0v range while cranking the starter, especially with any voltage drops at the ECU power/ground connections. Just figured I'd share since it may help track down some issues people might be having.
-Jamie
-Jamie
Mar 16, 2013, 05:18 PM
#34
thanks for the heads up, happen to have the proper evoscan formula to log the small IPW values? I can only see .256 increments and even doh i have the MIN IPW patch, my logs only show 1.024 as my min no matter what i do.
from what i have found FIC 2150 should not be run lower than 1.1 IPW so that should be most peoples issue with cold start and E85 although still havent found a solution to my issue but im still trying.
from what i have found FIC 2150 should not be run lower than 1.1 IPW so that should be most peoples issue with cold start and E85 although still havent found a solution to my issue but im still trying.
Jan 12, 2014, 08:24 PM
#38
I have also noticed that the datalogged 'Target Idle' is higher than the 'desired idle' table in ECUflash for the first 15 or so seconds after startup sometimes, then decays back down to the 'desired idle' parameter. I would liketo find that table as well. It's probably an RPM adder.
-Jamie
-Jamie
Jan 13, 2014, 12:19 PM
#39
Jay, in 9417 if you pull up that table in ecuflash and Mrfred's iscv tables and change parameters it will change one of those tables as well... one of the old 3 ISCV tables changes nothing, but two of the old tables port over to Mrfred's tables...
Apr 10, 2014, 08:19 PM
#41
Changing one table will automatically make the same change in its duplicate. So you can either leave them there if you don't want to mess with it, or remove them if you want to clean up your xml. Your choice. The difference will only be visual, there won't be any functional difference.
Apr 10, 2014, 09:42 PM
#42
Originally posted by Raptord
Changing one table will automatically make the same change in its duplicate. So you can either leave them there if you don't want to mess with it, or remove them if you want to clean up your xml. Your choice. The difference will only be visual, there won't be any functional difference.
Changing one table will automatically make the same change in its duplicate. So you can either leave them there if you don't want to mess with it, or remove them if you want to clean up your xml. Your choice. The difference will only be visual, there won't be any functional difference.
Jul 20, 2014, 03:31 PM
#44
Hello Jamie & All,
Thanks for the great write up!
Have a couple of questions that I hope someone could help me with;
1)When modifying an xml, where do I copy paste these definitions into? My ROM ID is 94171715, do I modify the associated xml in order to show your ISCV tables? This is the xml I am using among the other bundle downloaded form the Tephra thread (TephraMOD-94171715-v7.xml)
a.Also, where in the xml should the definitions be pasted into? Bottom, middle …etc
b.FYI lowest battery voltage experienced during the drop was ~11.9V and coolant was ~181F
c. I tried copying the definitions into the 94171715 xml but I wasn't able to see the tables.
2)I am running an engine die out or near stall events on my current setup and I was wondering if you were ever able to find the calibrations that locks the timing to 5*. In the data below you can see the engine is struggling to recover while the timming is locked.
Mods: stock 2.0l, hta86, FIC 1450, GSC S3, AMS F1, E85
Thanks in Advance!
Here is how my ISCV sections looks like.
This is the idle error offset I played with in anticipation to save the maneuver. I also tried messing with the timing offset based on rpm error but that didn't seem to make a difference.
Thanks for the great write up!
Have a couple of questions that I hope someone could help me with;
1)When modifying an xml, where do I copy paste these definitions into? My ROM ID is 94171715, do I modify the associated xml in order to show your ISCV tables? This is the xml I am using among the other bundle downloaded form the Tephra thread (TephraMOD-94171715-v7.xml)
a.Also, where in the xml should the definitions be pasted into? Bottom, middle …etc
b.FYI lowest battery voltage experienced during the drop was ~11.9V and coolant was ~181F
c. I tried copying the definitions into the 94171715 xml but I wasn't able to see the tables.
2)I am running an engine die out or near stall events on my current setup and I was wondering if you were ever able to find the calibrations that locks the timing to 5*. In the data below you can see the engine is struggling to recover while the timming is locked.
Mods: stock 2.0l, hta86, FIC 1450, GSC S3, AMS F1, E85
Thanks in Advance!
Here is how my ISCV sections looks like.
This is the idle error offset I played with in anticipation to save the maneuver. I also tried messing with the timing offset based on rpm error but that didn't seem to make a difference.
Jul 20, 2014, 04:18 PM
#45
Evolved Member
In the example shown above, the spark advance is locked to 5*BTDC because the engine speed did drop below 500rpm (475rpm or something like that is the threshold) and the ECU thinks its in cranking mode again.
Look in your xml in Idle section, find the table with address 4324.
This is the "Idle-up Position Decay Time (After Starting)" table. Make the times a lot longer so it will keep the ISCV open.
That should help, if not fix the problem.
Look in your xml in Idle section, find the table with address 4324.
This is the "Idle-up Position Decay Time (After Starting)" table. Make the times a lot longer so it will keep the ISCV open.
That should help, if not fix the problem.
Last edited by merlin.oz; Jul 20, 2014 at 04:25 PM.