couple of questions regarding EvoScan

1. my AFR log show 10 across the board, i know that is not right. I m on E85
2. my boost log shows 48psi I know thats not correct.
3. can i find out my boost with looking at Loadmut? my max Loadmut was 403

thanks

 

The Tephra v7 patch is a lot more descriptive as to what a lot of the settings are actually for and what the settings are actually adjusting. There is a wiki page for it as well which should help some.

 

How do you log boost and afr with evoscan?
i have innovative but having hard time connecting to the laptop.

 

There is a thread that covers the innovative WB install and how to set it up through evoscan.

 

I have a question, now that I am running speed density I threw a check engine light on the way home from the dsm/evo shootout and now my evoscan wont let me check it. I haven't read through all the pages, but it says:

"arithmetic operation resulted in an overflow"

Can anyone help me on this one. I have tried to load and reload evo scan and to no eval its not working for this any idea's?

 

that does not sound good.

 

No and the only thing is it only started this when I converted to speed density. I mean I don't know what the code is and its pissin me off. I added more fuel on my cold start up and it seemed to have went away but now it is back.

 

have you managed to read it yet with evoscan? what version are you using and what cable?

thanks

 

No I have not. I just got an email with the newest version of evoscan that has come out so I downloaded it and its finishing up as we speak so I will run out there and see if it works.


EDIT:

No the new software did not help. It still says "Arithmetic operaion resulted in an overflow." Now it says this in the troble cods section and the clear dtc does not clear this code so Idk wtf to do now anyone have any ideas where I should or who I should talk to? And sorry AND I missed answering your question. I am currently using a 1.3 tactrix cable and new 2.7 evoscan software.

 

I recently got an openport 2.0 (with the Mitsu flash cable) and upgraded to Evoscan 2.7 and the beta ECUflash all at the same time. I can log just fine (except it no longer reads DTC codes), but nothing I do seems to allow ECUflash, either the beta version or the previous version, to connect to the ECU. The buttons aren't even highlighted. It's as if the cable isn't connected. I'm trying to tune a friends car and convert it to SD. It's been 2 days of messing with everything and still no luck. Any ideas? I've uninstalled ECUflash and cleaned out the registry to remove all traces and still no luck. I'm getting frustrated.

 

Nevermind I finally figured it out. The beta version of ECUflash uses a new 2.0 driver that isn't backwards compatible with older versions. Since the beta just crashed whenever I opened a V7 ROM I gave up on it and went back to 1.42. For future reference if this happens to anyone go into windows "add or remove programs" and delete all the openport drivers then reinstall ECUflash 1.42 until the newest beta is more stable. The newest driver won't work at all. I also got EVOscan 2.7 to read DTC codes again when I went back to the older 2.0 driver.

 

why is that load doesn`t go further than 160 in evoscan? thats because the table of the map in ecuflash doesn`t pass 160 because stock boost? thanks

 

Juan, you'll need to set up and use 2byte load to accurately log load values beyond 160.

 

Change the 2byte to 1byte load factor to something higher than 1.2 in both the ROM and Evoscan. I have mine at 1.6.

 

sorry i`m new to this but how do i do that? thanks for the quick reply guys