Throttle hang and the Idle Stepper Table
#482
Evolved Member
iTrader: (2)
David,
The subsequent XML file(s) that the ROM inherits tables from is taken from an <include>xxxx<include> statement in the XML. The intial XML file is based on the ECU Internal ID.
A ROM can include several different XML files, which is inheriting the definitions along the way.
For example (I'm not using any specifics here):
Let's say you have a ROM named 96531706. The ECU Internal ID that is in that ROM (you can see this in ECUFlash) will be named 96531706. ECUFlash will then look for a 96531706.xml to open that ROM. That 96531706.xml may have an 'include' statement. Perhaps you will see <include>96530006</include>. ECUFlash then includes/inherits all of those tables. The 96530006.xml will then have an include statement for a base xml file, such as EVO7base.xml. ECUFlash then includes/inherits the table from that XML.
That is how ECUFlash works with the ROMs that you are using. It's uses the ECU Internal ID that is set in the ROM and then opens the XML for that ID and then includes any additional XMLs that the initial and each successive XML specifies in it's include statment.
That is where all of these different names came from...965301706, 96532706, 96533706. This way each ROM can use their own special XML file with tables only specific to that ROM (so you don't see SD tables in a maf ROM for example), but still lead to all of the normal 9653006 and base XML files with all of the main tables common to all of the ROMs. Those special names are the ECU Internal ID and you set that in ECUFlash.
The subsequent XML file(s) that the ROM inherits tables from is taken from an <include>xxxx<include> statement in the XML. The intial XML file is based on the ECU Internal ID.
A ROM can include several different XML files, which is inheriting the definitions along the way.
For example (I'm not using any specifics here):
Let's say you have a ROM named 96531706. The ECU Internal ID that is in that ROM (you can see this in ECUFlash) will be named 96531706. ECUFlash will then look for a 96531706.xml to open that ROM. That 96531706.xml may have an 'include' statement. Perhaps you will see <include>96530006</include>. ECUFlash then includes/inherits all of those tables. The 96530006.xml will then have an include statement for a base xml file, such as EVO7base.xml. ECUFlash then includes/inherits the table from that XML.
That is how ECUFlash works with the ROMs that you are using. It's uses the ECU Internal ID that is set in the ROM and then opens the XML for that ID and then includes any additional XMLs that the initial and each successive XML specifies in it's include statment.
That is where all of these different names came from...965301706, 96532706, 96533706. This way each ROM can use their own special XML file with tables only specific to that ROM (so you don't see SD tables in a maf ROM for example), but still lead to all of the normal 9653006 and base XML files with all of the main tables common to all of the ROMs. Those special names are the ECU Internal ID and you set that in ECUFlash.
Last edited by l2r99gst; Feb 6, 2010 at 10:55 PM.
#483
Evolved Member
iTrader: (53)
88590715 is the Internal ID.
Then at the bottom it says: Inherits from 88590015_r3compile_20091010
That is what I have been trying to describe.
The ROM I have open is labeled: 88590715=TephraMod.bin
This is all from the standard 1.42 download and then some of it is from what is posted in zip files for the Tephra stuff here on the forums.
The only XML mods I have done are very simple ones like the decel and iscv tables in this thread.
Then at the bottom it says: Inherits from 88590015_r3compile_20091010
That is what I have been trying to describe.
The ROM I have open is labeled: 88590715=TephraMod.bin
This is all from the standard 1.42 download and then some of it is from what is posted in zip files for the Tephra stuff here on the forums.
The only XML mods I have done are very simple ones like the decel and iscv tables in this thread.
#484
Evolved Member
iTrader: (2)
If 88590715 is the internal ID, then ECUFlash is using the 88590715.xml to open it. Then it looks for any <include> statment that I mentioned above and reads that XML also, and any <include> statement in that XML, and so on.
That's how all of the tables are built. If you want some different XML for inheriting tables along the way, you change that in those <include> statements.
That's how all of the tables are built. If you want some different XML for inheriting tables along the way, you change that in those <include> statements.
#485
EvoM Guru
iTrader: (50)
88590715 is the Internal ID.
Then at the bottom it says: Inherits from 88590015_r3compile_20091010
That is what I have been trying to describe.
The ROM I have open is labeled: 88590715=TephraMod.bin
This is all from the standard 1.42 download and then some of it is from what is posted in zip files for the Tephra stuff here on the forums.
The only XML mods I have done are very simple ones like the decel and iscv tables in this thread.
Then at the bottom it says: Inherits from 88590015_r3compile_20091010
That is what I have been trying to describe.
The ROM I have open is labeled: 88590715=TephraMod.bin
This is all from the standard 1.42 download and then some of it is from what is posted in zip files for the Tephra stuff here on the forums.
The only XML mods I have done are very simple ones like the decel and iscv tables in this thread.
#486
Evolved Member
iTrader: (53)
mrfred, I moved both the r3compile xml's out of the EVO folder to my desktop. Restarted Ecuflash and reopened the Tephra ROM. Now I am missing things like idle, mivec and fuel tables.
I think until the actual ROM says it inherits from tephramod-88590715-v7 it is not going to read properly, right? It still says inherits from the r3compile xml and now that is on my desktop, which explains why some tables are missing, right?
Let me try to write the XML like l2r99 said. BRB.
I think until the actual ROM says it inherits from tephramod-88590715-v7 it is not going to read properly, right? It still says inherits from the r3compile xml and now that is on my desktop, which explains why some tables are missing, right?
Let me try to write the XML like l2r99 said. BRB.
#488
Former Sponsor
iTrader: (10)
Join Date: Dec 2009
Location: NY
Posts: 612
Likes: 0
Received 0 Likes
on
0 Posts
mrfred, I moved both the r3compile xml's out of the EVO folder to my desktop. Restarted Ecuflash and reopened the Tephra ROM. Now I am missing things like idle, mivec and fuel tables.
I think until the actual ROM says it inherits from tephramod-88590715-v7 it is not going to read properly, right? It still says inherits from the r3compile xml and now that is on my desktop, which explains why some tables are missing, right?
Let me try to write the XML like l2r99 said. BRB.
I think until the actual ROM says it inherits from tephramod-88590715-v7 it is not going to read properly, right? It still says inherits from the r3compile xml and now that is on my desktop, which explains why some tables are missing, right?
Let me try to write the XML like l2r99 said. BRB.
Some of the xml language can be more complicated then actually tuning the car.
#489
Evolved Member
iTrader: (53)
I got it!!!
Thank you mrfred and l2r99gst. It is now 2:17 am and I can finally go to bed!!
In the xml file I tried to do this the other night and figure it out but it wouldn't work then either. For anyone reading, using the Tephra XML's/ROM you only need to have the ROM ID in the internal ID. IF you write in Inherits from tephramodXXXXXXX in the XML it will lock up and can't find it. So when I just eliminated that it worked instantly. Boy was that a learning experience.
Who knows someday maybe I can help someone else like you guys have helped me!
Off to bed. Thank you all so much and good night.
Thank you mrfred and l2r99gst. It is now 2:17 am and I can finally go to bed!!
In the xml file I tried to do this the other night and figure it out but it wouldn't work then either. For anyone reading, using the Tephra XML's/ROM you only need to have the ROM ID in the internal ID. IF you write in Inherits from tephramodXXXXXXX in the XML it will lock up and can't find it. So when I just eliminated that it worked instantly. Boy was that a learning experience.
Who knows someday maybe I can help someone else like you guys have helped me!
Off to bed. Thank you all so much and good night.
#492
Evolved Member
iTrader: (1)
It would be nice to have a summary of the thread topic. I realize that there is a certain amount of pride in being involved with the whole thread. I've also found that if you stop reading constantly for a few weeks/months, you will be lost when you come back.
Anyone care to summerize the topic "Throttle hang and the Idle Stepper Table"?
Anyone care to summerize the topic "Throttle hang and the Idle Stepper Table"?
#493
Evolving Member
iTrader: (1)
Join Date: Aug 2007
Location: socal
Posts: 229
Likes: 0
Received 0 Likes
on
0 Posts
I am going to try to write a summary, please correct if I am wrong as I am not an expert on the rom. And note as this is a disassembly/discovery process things will change. Great work on the disassembly process everyone, I just would have thought that someone would have been able to beg/borrow/steal the oem program manual eventually.
The evo VIII and IX have a fuel cut delay after releasing the throttle. The purpose of which may be to reduce unburnt hydrocarbon emission or protection of the catalyst. The delay is very annoying because the car does not engine brake and for some tunes the rpms may actually increase during shifting.
The tables that define the decel fuel cut delay have been found for some roms
In particular, the rom # and a forum page are associated below.
94170015
https://www.evolutionm.net/forums/ec...-7-9-a-18.html
96530706
https://www.evolutionm.net/forums/ec...ttle-hang.html
88580015
https://www.evolutionm.net/forums/ec...-7-9-a-19.html
98640014
https://www.evolutionm.net/forums/ec...evo-7-9-a.html
96530006 and 88840016
https://www.evolutionm.net/forums/ec...o-7-9-a-4.html
The rom before the IX have 4 tables, the IX has two tables.
The settings used to reduce hang in the 4 table version are from the 96530706 rom.
https://www.evolutionm.net/forums/ec...ttle-hang.html
https://www.evolutionm.net/forums/ec...-table-28.html
My evom foo has not been able to find a table for the IX that reduces hang.
I am going to try
table 1
old
10, 100, 120, 120, 120, 120, 120
new
10, 50, 60, 60, 60, 60, 60
table 2
32, 110, 120, 130, 130, 130, 130
32, 55, 60, 65, 65, 65, 65
I will try to get back tomorrow.
btw
does anyone know what the decel cut retard in 88590015 is for as shown on
https://www.evolutionm.net/forums/ec...-7-9-a-19.html
additional notes
as advised in
https://www.evolutionm.net/forums/ec...ml#post7580026
zeroing out the ISCV demand rpm adder tables can help.
after trying both reducing decel cut and zeroing ISCV, I prefer the response with zeroing iscv
your mileage may vary
The evo VIII and IX have a fuel cut delay after releasing the throttle. The purpose of which may be to reduce unburnt hydrocarbon emission or protection of the catalyst. The delay is very annoying because the car does not engine brake and for some tunes the rpms may actually increase during shifting.
The tables that define the decel fuel cut delay have been found for some roms
In particular, the rom # and a forum page are associated below.
94170015
https://www.evolutionm.net/forums/ec...-7-9-a-18.html
96530706
https://www.evolutionm.net/forums/ec...ttle-hang.html
88580015
https://www.evolutionm.net/forums/ec...-7-9-a-19.html
98640014
https://www.evolutionm.net/forums/ec...evo-7-9-a.html
96530006 and 88840016
https://www.evolutionm.net/forums/ec...o-7-9-a-4.html
The rom before the IX have 4 tables, the IX has two tables.
The settings used to reduce hang in the 4 table version are from the 96530706 rom.
https://www.evolutionm.net/forums/ec...ttle-hang.html
https://www.evolutionm.net/forums/ec...-table-28.html
My evom foo has not been able to find a table for the IX that reduces hang.
I am going to try
table 1
old
10, 100, 120, 120, 120, 120, 120
new
10, 50, 60, 60, 60, 60, 60
table 2
32, 110, 120, 130, 130, 130, 130
32, 55, 60, 65, 65, 65, 65
I will try to get back tomorrow.
btw
does anyone know what the decel cut retard in 88590015 is for as shown on
https://www.evolutionm.net/forums/ec...-7-9-a-19.html
additional notes
as advised in
https://www.evolutionm.net/forums/ec...ml#post7580026
zeroing out the ISCV demand rpm adder tables can help.
after trying both reducing decel cut and zeroing ISCV, I prefer the response with zeroing iscv
your mileage may vary
Last edited by waynea; Feb 15, 2010 at 12:59 AM.
#494
Evolving Member
iTrader: (1)
Join Date: Aug 2007
Location: socal
Posts: 229
Likes: 0
Received 0 Likes
on
0 Posts
After settting decel fuel cut delay tables to 50% of original, the throttle hang is better, but there seems to be a little left. I may try some more later and/or the ISCV demand rpm adder later.
Last edited by waynea; Feb 11, 2010 at 11:53 PM.
#495
Evolved Member
iTrader: (22)
Join Date: Nov 2003
Location: Northern KY near Cincy
Posts: 2,408
Likes: 0
Received 6 Likes
on
6 Posts
The lower the values the less time is set before the engine starts braking the car. Thus the easy fix is to lower the fuel cut delay tables.
Another fix that others do is to go in the ISCV Demand tables for RPM adders and zero them out.
Another fix that others do is to go in the ISCV Demand tables for RPM adders and zero them out.