How does ECUflash use definition/xml-files?
How does ECUflash use definition/xml-files?
I am a little curious how definition selection works - I mean; when opening a ROM-file, does EcuFlash automatically use the definition file named the same as as the Internal ID?
In other words, if the Internal ID in the ROM "reads" 88840016 - then it automatically uses the 88840016.xml definition - provided it's there?
What is the "Inherits: evo9base"?
How is evo9base.xml used?
Here is the reason I got confused:
I tried to disable the rear O2 sensor by changing the definition file (88840016.xml). But the changes didn't appear in ECUflash when opening the ROM. Then I saw the Inherits: evo9base, and tried to change the evo9base.xml file, and then the definition changes became visible when opening the ROM...
In other words, if the Internal ID in the ROM "reads" 88840016 - then it automatically uses the 88840016.xml definition - provided it's there?
What is the "Inherits: evo9base"?
How is evo9base.xml used?
Here is the reason I got confused:
I tried to disable the rear O2 sensor by changing the definition file (88840016.xml). But the changes didn't appear in ECUflash when opening the ROM. Then I saw the Inherits: evo9base, and tried to change the evo9base.xml file, and then the definition changes became visible when opening the ROM...
I don't think so (and I am aware of the user lever setting which quickly leads to trouble if forgotten). But still, it could have something to do with that, or some other bug (like restaring ecuflash etc). Will test again soon (thinking of reinstalling - I couldn't manage to change the immobiliser code on a map), but I still would like to know what the evo9base-file does/how it is used.
Evolved Member
iTrader: (37)
Joined: Sep 2003
Posts: 3,146
Likes: 2
From: Spec-Ops Motorsports, Fayetteville, NC
I don't think so (and I am aware of the user lever setting which quickly leads to trouble if forgotten). But still, it could have something to do with that, or some other bug (like restaring ecuflash etc). Will test again soon (thinking of reinstalling - I couldn't manage to change the immobiliser code on a map), but I still would like to know what the evo9base-file does/how it is used.
I think though that whatever changes you are trying to make to ecuflash will show once you change user level from beginner to developer. then open your rom, and it should appear if you did it right
I am a little curious how definition selection works - I mean; when opening a ROM-file, does EcuFlash automatically use the definition file named the same as as the Internal ID?
In other words, if the Internal ID in the ROM "reads" 88840016 - then it automatically uses the 88840016.xml definition - provided it's there?
What is the "Inherits: evo9base"?
How is evo9base.xml used?
Here is the reason I got confused:
I tried to disable the rear O2 sensor by changing the definition file (88840016.xml). But the changes didn't appear in ECUflash when opening the ROM. Then I saw the Inherits: evo9base, and tried to change the evo9base.xml file, and then the definition changes became visible when opening the ROM...
In other words, if the Internal ID in the ROM "reads" 88840016 - then it automatically uses the 88840016.xml definition - provided it's there?
What is the "Inherits: evo9base"?
How is evo9base.xml used?
Here is the reason I got confused:
I tried to disable the rear O2 sensor by changing the definition file (88840016.xml). But the changes didn't appear in ECUflash when opening the ROM. Then I saw the Inherits: evo9base, and tried to change the evo9base.xml file, and then the definition changes became visible when opening the ROM...
Base seems to be used for parts of the maps that are shared across one type of car. I.e Evo9base, Evo7base. Then the ID seems to be for specific roms in that type of car.
Just going off of what I can gather from the xml files.
Base xml's (5,7,9) draw tables that you see when you open ECUFlash. They are all the same for those groups of ECU's.
Specific xml's contain request addresses for specific ECU's that tell ECUFalsh where the needed information is stored.
Base is the book.
Specific xml's are bookmarks.
Specific xml's contain request addresses for specific ECU's that tell ECUFalsh where the needed information is stored.
Base is the book.
Specific xml's are bookmarks.
Thread
Thread Starter
Forum
Replies
Last Post









