Any Reason to Keep These in the ROM?
Any Reason to Keep These in the ROM?
Some maps/tables I see in the evolving Tephra ROM don't seem to have any function that is particularly useful in tuning the car (unless I'm missing something), while others appear in duplicate:
- Open Loop Load #2
- Knock Sensor Filter 1-12 (Probably mislabeled)
- Boost Enhancement Adv/Ret Map #2
- Boost Desired Engine Load #4
- Max Wastegate Duty #4
Is there a reason why these should be retained?
And can anyone clarify the reason for the duplicates (e.g. #1 and #2, or #1 and #4 of a particular table)?
- Open Loop Load #2
- Knock Sensor Filter 1-12 (Probably mislabeled)
- Boost Enhancement Adv/Ret Map #2
- Boost Desired Engine Load #4
- Max Wastegate Duty #4
Is there a reason why these should be retained?
And can anyone clarify the reason for the duplicates (e.g. #1 and #2, or #1 and #4 of a particular table)?
I believe mrfred is removing the knock filters from the base ecuflash definition files in the next release since we know they done do anything.
The max WGDC table is not used with the Tephra 5.10 rom.
I am not sure about the rest - never even seen boost enhancement adv table before.
The max WGDC table is not used with the Tephra 5.10 rom.
I am not sure about the rest - never even seen boost enhancement adv table before.
The Max Wastegate Duty table does indeed control boost solenoid duty. The settings of this table are how those of us who do not (or cannot) use MAP based boost control set our boost.
Does that universally explain why there are duplicate tables for some functions? I've been wondering why we have a #1 and #2 or #1 and #4 table for some functions, and it seems as though no one has figured that out yet.
Does that universally explain why there are duplicate tables for some functions? I've been wondering why we have a #1 and #2 or #1 and #4 table for some functions, and it seems as though no one has figured that out yet.
Multiple tables are generally for a cold/warm/problem state, but may also be for different vehicles. The desired idle RPM tables are a good example ... there are like 6 idle tables and only 1 actually changes the desired idle RPM. I assume this is code for other models that was just left around for the sake of reducing time to port the ROM for all models. I don't do disassem though, so those guys could give better opinions.
Ok, so that tells us that the #4 Max WGD table has no effect and is not used. I'm just suggesting that we make it disappear from future versions to reduce clutter and the potential for confusion if it is useless to us. I am making the same suggestion for any other tables that are effectively useless to us (e.g. 12 different "Knock Sensor Filter" tables), or, carry the same name as a used table (e.g. Max WGD #4) and are unused.
I suppose I can just remove them from the XML myself, but I don't want to screw up anything!
I suppose I can just remove them from the XML myself, but I don't want to screw up anything!
Last edited by Ted B; Dec 16, 2008 at 06:30 AM.
Trending Topics
Ok, so that tells us that the #4 Max WGD table has no effect and is not used. I'm just suggesting that we make it disappear from future versions to reduce clutter and the potential for confusion. I am making the same suggestion for any other tables that are unused (e.g. 12 different "Knock Sensor Filter" tables), or, carry the same name as a used table (e.g. Max WGD #4) and are unused.
For the next tephra patch the boost stuff will all be changed with gear dependent boost which will have 6-7 MWGDC (or baseline WGDC) tables
Would there be any issues from me just removing them from the XML? If all the XML table entries do is provide a conduit to manipulate something that exists in the ROM, then it shouldn't affect the function of a table if we just make it disappear in the XML, correct?
I just want to reduce clutter for the sake of my programming laptop's small screen.
I just want to reduce clutter for the sake of my programming laptop's small screen.
oh you mean personally? I thought you meant removing them from the ECUflash install package. You are safe to remove anything from the definitions file and it wont harm the rom. Personally i comment them out. Wrap the tables you dont want to see with <!-- text -->.
I think eliminating maps where the functions are known is a step backwards. I've just gone through and set the levels up to what I would use them for.
Level 4 = normal tuning, fuel and timing maps and rev limiters is about all that shows up
Level 3= More in-depth tuning, fuel and ignition trims, etc., nothing that really impacts HOW the ECU works though
Level 2 = Everything else that is properly defined
Level 1= maps that are questionable in nature and not well defined
Set it to level 4 (beginner) and I only have a very few number of maps to sort through, which makes it fast and easy to do 95% of the tuning.
Level 4 = normal tuning, fuel and timing maps and rev limiters is about all that shows up
Level 3= More in-depth tuning, fuel and ignition trims, etc., nothing that really impacts HOW the ECU works though
Level 2 = Everything else that is properly defined
Level 1= maps that are questionable in nature and not well defined
Set it to level 4 (beginner) and I only have a very few number of maps to sort through, which makes it fast and easy to do 95% of the tuning.






