Well, I copied the scaling over to the newest updated xml and so far it shows up exactly as it should. Once I opened the box it showed the current setting for the fuel temp ADC and I changed it to the IAT ADC like I used to run, but I haven't gotten to test it out. I'm pretty sure it'll work though. Here it is in case you guys want to add it and don't have the older 9653xxxx xml...



<table name="SD Option: IAT Input for MAT - Use 0x03, Fuel Temp ADC_0E for MAT - Use 0x0E" category="Speed Density Programming" address="a821" type="1D" level="1" scaling="Hex8"/>

 

Stupid question, probably because I'm finally interested in map switching since it can be controlled through TPS, but where are the ALT Low Octane Fuel and Ignition Maps in recompiles modded version?

 

Just out of curiosity, why are we bothering distributing both livemap and non-livemap versions? If you don't use the live mapping client, you won't even know it's there (there's literally three MUT commands added, and a few maps moved to RAM instead of ROM, that's it).

Less ROMs = less confusion. But, maybe I'm missing something fundamental? I am running on a lack of sleep right now.

 

The only Low Octane maps are the Main Low Octane maps. They are shared between Main & Alt.

 

another noob question: where do i change my Load 1 Byte setting to 1.4, in EvoScan? it's done in EcuFlash.. just need to find where i do it in EvoScan.

thanks!

 

any rom for 88570008 yet?

 

Right-click the Data Item list and select Edit Data Items. For 1 Byte Load, change Eval (aka Function) to 1.4*x

 

i guess i should have guessed that. dur. okay. thanks. is it under "E1 RAM 1Byte Mod"? here is what i have in EvoScan:

Load Calculated
ECULoad
Load11bit4
Load MUT 2Byte Mod
E1 RAM 1 Byte Mod

i entered the code from post #2 into one of the "Mode 2" areas. did i miss something?

 

Yes, you missed something. Look at post #2 and you can see:
That is what it would be called in evoscan.

 

figured. i cut/pasted the coding from post 2 into evoscan but do not have the option to log. i'll have to do some investigating. thanks.

 

Paste it into the first section of values. You can easily find the correct section by looking at the order of items when you have the program open and comparing it to the order of items as-listed in the xml.

 

I added the Evoscan stuff to the data.xml and now when I go to "Logging > Edit Data Item List" it gives me a "Index was outside the bounds of the array" error message. What's the deal with that?

 

It means you need to send another $50 to evo4mad.

 

guys, when using SD Rom, do we monitor Manifold Air Temp (connected to Fuel Temperature input on ECU) in evoscan using request 3A or 09 ?

 

I get that all the time and its super annoying. What IS the deal with that? I thought it was from an error in the XML file but I couldn't find anything wrong with it.