You can do the individual 1D tables for each and then you have to make your HEX code changes in the ECUFLash window just like all the other tables. The 3D map is much more useful and will be easier to find the info you need. With the 3D Table, you have ONE address for all of the MUT addresses and just change those particular MUT address locations on the chart. Its a better way to go in the long run. I honestly don't know where to get the 1D addresses you'll need.

 

Try to keep the unknown issues out of this thread guys. Try to keep this one as the "SOLUTIONS TO THE PROBLEMS" thread. If you having issues and the FIX hasn't been added here yet, post your issue HERE.

If you DO find a fix, please come post it up in this thread.

Thanks Guys!

 

Another wierd thing I have noticed...


<DataListItem DataLog="N" Color="" Display="Airflow/Rev" LogReference="AccelEnrich" RequestID="1D" Eval="200*x/255" Unit="load" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="300" ChartMin="0" ChartMax="300" ScalingFactor="1" Notes="" Priority="1" Visible="false" />



Display = Airflow/Rev

LogReference = AccelEnrich


Which is it?

 

I don't know but when I added that in the EvoScan, now it doesn't show anyting in Estimated horse power Lbs/min and torque. Please tell me the original values cause I don't want to reinstall it. Or maybe the correct ones using 2byte MUT cause i have all 3 enabled. 10x

 

^^make sure that you have "LoadMUT2Byte" and "rpm" log items on top/before the estimated power items.

 

Forgive me for not understanding and this may have been mentioned before but, could someone explain how those equations translate to HP?

 

edited:

 

I just swapped my map sensor for the JDM, and now I can NOT connect to Evoscan??? I keep getting this:

Info: Initialize Vehicle ECU...
Info: Initializing At 5 baud...
Info: Initialization Complete...
Info: Waiting for INIT Response...
Info: ECU ID: E4C7
Info: Connection successful...
Error: Index was outside the bounds of the array.
Info: Datalogger Ended.

I tried to change the formula for the JDM MAP to match my altitude 14.3, but when I open data .xml file w/ notepad it still reads 14.5? So I tried to edit while I was in notepad... And it wouldnt let me??? I went through comp>program files>evoscan>evoscan 2.1>data settings>data .xml and it said to make sure the paths are right??? i opened up my evoscan checked properties and its in this place???
I ended up uninstalling and reinstalling evoscan 2.1 and the problem remains???

 

Are you running vista? Their stupid 'compatibility files" option is annoying since it shows the old datasettings file first. If it shows up correct in evoscan, its saved in the correct datasettings file.

 

UNFORTUNEATELY yes, running vista... in "properties" it read from:C:\Program Files\EvoScan\EvoScan v2.1, also reads file as .exe, shouldnt it be in .hex?
and when I tried to edit, it read from: C:\Program Files\EvoScan\EvoScan v2.1/data settings... u have to open the data file to get to it??? maybe I am not editing properly... I just deleted the .5 in the JDM MAP formula to proper compensate for elevation and made it a .3. 14.3, go to file save???

damn it...it keps reading cannot create C:/program files/evoscan/evoscan2.1/data settings/data.xmlfile
make sure path and file name are correct!

 

When you open the datasettings folder, you'll see the data.xml file. On the top taskbar in the window, it should say COMPATIBILITY FILES, click that. This should be the ACTUAL data.xml file you are using with evoscan 2.1.

Evoscan.exe is the actual evoscan program and its supposed to be an .exe file.

With Evoscan 2.1, you can edit everything directly from the chart so there isn't any need to really go into the actual data.xml file anymore.

 

cheers to u kind sir! when I open up it w/ notepad w/out hitting the "compatablity files" it still read .5, but after hittin it, showed up .3!
definitely good to know!
thank u
any ideas on why I am unable to connect?

 

I just got my JDM mapr sensor, installed it w/ help from kreionic (big shout out to Charlie! thank u so much!)w/ the rom mods. Basically he gave me his 15 rom. I see some definitions like "MAP SCALING" and "MAP FAULT TRIG HIGH" and "LOW"(also had all of the good stuff like NLTS, and tephra mods etc.) but i dont see some...and unfortuneately he doesnt actually use ECU controlled BOOST... So there are many things left out of my rom file... MY questions are these:
1. Can I just add the full line up of ROM mods to the bottomper MRFRED, or am I going to have to add JUST THE ONES THAT ARE LEFT OUT? meaning can i have "2" of the same definitions in the xml file?
2. Does it matter the placement of the new definitions?
3. It says in the thread to do all the rom mods @ the same time as the JDM Map Sensor or the car wont start or throw a cell... Am I going to be able to just make the ROM mods???
4. am I gonna have to hit compatibility file for any files in ecuflash?

 

i just changed the formula to (.1961*x)-25 and while connected, its reading Nan...??? any1 ever encounter this?

 

you know.. with all these errors i think evoscan should be free.. or atleast this verion. i mean people pay for a working product and it doesnt seem to be working all that great :P