Let's see your customized EvoScan Data.xml
 

I figure there'd be some interest in what everyone's logging and in what order. I'm sure plenty of people out there have their own custom little calculations in EvoScan, so perhaps we can get a thread goin.

Mine's not too fancy:

http://puremhz.com:8080/images/uploa...32-evoscan.PNG

Man you always want to see other people's stuff :lol:. First timing maps, then dataxml, whats next?

Above is similiar to mine...only difference being that I didn't remove the other stuff I don't log. I just left in in unchecked.

Like the idea...makes it widely known and helps a lot of ppl.

ZZZZiiiiiiiipppppppppp............ Flop...... :eek:

Please, Ignore the ebonics... :D

When I get off of work and get home. Shameless I like how you condensed the Lbs/min routine...I wish I had thought of that.

It makes it easier to look at logs when you don't have so many empty columns.

I used to make Excel macros to hide unused columns and auto filter by TPS > 90, but when I change around what I log and what car I log, the macro's don't always apply, so this makes it much easier.

I just removed the stuff I don't use and made data.xml.removed so I can always add it back in.

JB, where are yours at!?

Sorry man...let things get in the way. A couple of quick notes. I like to rename things so some of what you are going to see is 2 byte but it might not say that:

http://img.photobucket.com/albums/v5...rikain/V99.jpg

I also have redone a few of the MUT requests so this data.xml will not work for everyone though it will show whats going on I think.

This is also V99...I do not use anything newer for a few reasons. The GUI isnt really much different and I dont need to edit the xml from Evoscan since V99 is really pretty much setup. If I add anything its just as easy to add it to the .xml with wordpad for me. Also since everyone else has problems with maptracer, and I have been using excel for so long that part doesnt really excite me. I will end up getting 2.1 probably though, just for the STi stuff.

Like the MIVEC/Alternator features you added/changed JB.

Cool. Does logging MIVEC require any changes to the MUT table ?

Well yes and no. You need to add the values of 7650 and 7651 to an open MUT location..I think I used 40 and 41 as per Tephra's orginal instructions (all the 4x are unused addys) and then make sure that those MUT addys are the same as request ID1 and 2.

Other than that you are good to go.

MIVEC was courtesy of mrfred, and I dont like looking at the "battery" label when its not the battery its the stinking alt.. :lol:

Also while I am thinking of it, about the timing...the 3 of them and some of the other stuff as well...

Timing Advance is what the car runs

Timing Alpha appears to be what the positive modifiers want to add (not counting knock, which would be a negative modifier). I have this as a total value but you could change the xml to subtract Beta to see what the total change is. I could, I am just lazy and dont care enough since I compare them all side by side.

Timing Beta appears to be what the map actually physically says for that rpm/load.

G/rev I keep seperate though Cookie put it together (I do like that btw) because since I also do subarus I can compare and see where a subaru is for the amount of g/rev (in their case they dont use "load" just g/rev) and lbs per min to hp against a known quantity like an Evo. I can look at a nearly stock Sti and see it hit 3.25 g/rev at low boost where you have to flog an Evo to do the same thing but the Evo still makes more power. Not anti-sube, just one more piece of the puzzle I am trying to figure out.

wait your able to log mivec in evoscan now? thats something I wanna do for sure.

Thats exactly why I didn't remove those from the xml. The columns stay constant regardless of car.