Fixed my WGDC problem, that was it I has my stock table maxed out at like 160 load so it would only go 100% WGDC from 160 to 200 load, never pretty much. So I changed that table back to stock and bam! Works perfect and feels really snappy during daily driving!

Another issue though, when I try and do the map tracing function I am getting the same error as above that seanV is getting. I use this function a lot during tuning and with it not working I have reverted going back to using DataLogLab (which works perfect)

Any help would be appreciated.....

 

Thx

I will give this a bash, probably going to need some help with it

 

I tried this and used only the 96530006 XML and it didn't give me the error but it would not show the map tracer data. Not sure what's up, I am going to try to copy in the Alternate maps into a different XML and try again.

Any other idea's?

 

Read through the rest of that thread I posted. It looks like you are not logging ECULoad. You'll have to log it, copy a row to it, or fake it after the fact. There are instructions for all 3 methods in the thread I linked. (this is just a guess)


Either way map tracing should be independent of your Tephra Mod. This is the only reason I could assume it would be the xml/rom you have selected (though it seems like you are saying this didn't work, this is the only "link" to your actual rom).

 

Tried that.....nothing

If I load just the 9653006 XML not the Tephra XML it doesn't give me the error and does load the high / low ignition / fuel maps. However if I select a value it doesn't map it in the tracer or any value for that matter.....am I doing this wrong?

~Zach

 

okay I assume you are talking about the top part of the map tracer.
If so, make sure you log the 1 byte load (2 byte not needed) and the normal RPM. When you have logged your run either,

1) open in the map tracer and then select the 1 byte load from the drop down menu for load options

or

2) open the CSV file and simply copy the 1 byte load column into the normal load column (only values not the header!), save and then open in the map tracer.

I had a similar problem as I had logged different loads and did number 2 above after deleting the standard load values. Now I only log 1 byte load and it seems to open it.

Hope that answers your question, if not ignore this!

 

Sure sounds like you need to slim down the XML to only normal/alt Fuel/timing tables like I originally suggested.

When you are loading the tephra XML the includes and the blobbits and all of the other tables aren't really necessary for the map tracer. Here is my Evo IX example for v6t. Notice it is only the scalings (all of them, it was just easier that way) and the 4 pertinant fuel + ign tables.... nothing else.

http://thefrost.net/randomfiles/tuni...590615_ALT.xml

Get it?

It is either that or the ECUload thing. I really can't imagine what else it could be. (other than possibly an empty header column or something stupid like that.... but it doesn't sound like we have gotten there.)

An even sillier test to see if we are actually having a problem with your tephra rom (which should be impossible) would be to look at your log for a v6/v7 run and just try to load your v5.12 xml and hex map. If it works, then it is 100% guaranteed that it is just your xml setup. If not, then its only likely

 

Did what you suggested, and after making the XML file and copying 1ByteLoad to ECUload it worked great. Once that was done it traced it perfectly.

To fix it so I didn't have to do that every time (since I don't use ECULoad) I just made ECULoad the same request and formula as 1ByteLoad this way it works right after logging without any modification. Any problems with that?

Thanks for the help

 

Not necessarily a "problem" but it is not the ideal way to do it. See the other thread where I posted how to make it a "calculated" item that will just copy the value from 1 byte load rather than making another MUT request and lowering your logging resolution/speed.

 

Well now EVOScan is really messing with me. I got it to work but today it is not working. I used to be able to choose the XML / ROM I wanted to use but now I can only pick the ROM. I right click on the graph and it only asks for the ROM not the XML too. Any ideas?

BTW this is EVOScan 2.6 beta 11

I get the same error as before now that I can't select my XML I want to use.

P.S. - how do I set it up so that it is a calculation and not a MUT Request, what post are you referring to?

 

Tephra we can haz V7 thread yet?


Would help make sense of some stuff.

 

waiting for confirmation of the ADC0F map switching problem.. either it works or it doesn't..

someone else needs to test it

 

Yes, someone else please test it! I cannot get it to work

 

I tested it on a '05 that was previously running a 96530006 with your v5.10, than I converted it to 96530706. It entered into the alt map function via the TPS indicated by the CEL light flashing but, I wasn't able to verify through logging that it was indeed referencing the alt maps.


One question I have is that mrfred's MAT patch - are the values in v7 correct? Previously the values were there but, one had to copy mrfred's values from his patched ROM into a specific ROM in order for it to be enabled. Does this need to be done with v7 in order for the MAT patch to function properly? Or is it simply enabled/disabled by selecting it in the Mods drop down menu (0 = disabled 1 = enabled)??

 

I quicked glanced at what mrfred had previously for his MAT patch and what is in v7 for the MAT patch and the scaling table is no where near the same. mrfred's table is much, much longer than v7??