SophieSleeps

iTrader: (19)

I use multiple computers to tune so I have a few questions on making xml definition changes.

If I change an XML definition on computer A.
I edit my maps and save them.
I transfer my maps to Computer B (does not have the xml definition changes)

If I load my maps into my car with Computer B...will those changes take effect?

When you add maps to ecuflash via the front end interface, is it pretty much the same as adding xml code into the definition file?

codgi

iTrader: (22)

All the xml definition file does is allow ECUFlash to show some particular part of the rom in the UI for the user and allow changes to it. That part of the rom was there before the definition, and will exist even if you don't have that definition. When you save it on the first computer, ECUFlash writes to changes the part of the rom that the definition specifies.

Even though you then move it to another PC that does not have the definition, the change has been physically saved into the rom itself. At flash time (and I haven't flashed in a while so I might be wrong here), I'm pretty sure that the routine does a quick compare between the rom to be flashed and the rom currently on the ECU and only changes whichever blocks have been changed.

So short answer is yes, the changes should work .

C6C6CH3vo

iTrader: (9)

Just save a notepad copy of the edited Xml to use for editing your new Xml

SophieSleeps

iTrader: (19)

Thanks guys. What I've been doing is just uploading my most recent XML file to my server so if I'm using a diff ECUflash I can download my file.

SophieSleeps

iTrader: (19)

So what's the difference between editing the XML for stuff like 2 byte load and doing stuff like adding a map for lean spool disable that does not require any XML edits?

mplspilot

iTrader: (7)

Think of a ROM as a book.

XML tables are the bookmarks that let you see and change certain pages.

Some bookmarks come with ECUflash definitions. When more stuff gets discovered you add more of those to edit and change more things.

If you do not have all the bookmarks the info is still in the book, you just cannot see it.

codgi

iTrader: (22)

^^ this analogy is pretty good actually

Give an example of the stuff in bold?

SophieSleeps

iTrader: (19)

When you add a map for lean spool disable you are doing it in the front end of ecuflash.

Right click, add map...blah blah blah.

You aren't editing the XML directly.

Is that different than editing the XML or does that accomplish the same thing?

tephra

iTrader: (6)

i think you will find that the XML gets updated with any new maps you add into the GUI...

C6C6CH3vo

iTrader: (9)

I thought you had to update the xml in order to add the new maps.

1.31 screwed up my xml, I had to find an old notepad of my worked xml and paste it on the altered xml that 1.31 changed. Even after uninstalling 1.3 the xml will now default back to what 1.31 changed it to. This includes changes in adresses and missing words.

Is this all because my ECU is flashed to my original "worked" xml and thats the reason the 1.31 xml doesnt work?


What is the possibility of two different values working for an address?


For instance my original B/E enhance stop address is 1684, but the 1.31 shows 1682, is 1.31 flat out wrong?

mplspilot

iTrader: (7)

It's the same.

You can add a table through the program or if you know how to write xml code you can add directly into the definition. End result is the same.

codgi

iTrader: (22)

I never added that table through the UI so thats why I was confused. It should be the same and as a simple test just save the xml, add a table through the UI and then the xml should get updated.

codgi

iTrader: (22)

Which xml file did you change? Rom specific? Or the base xml from which your rom inherits?