Two unique problems with Evoscan
#1
Evolving Member
Thread Starter
iTrader: (7)
Join Date: Dec 2005
Location: Jeanette near Pittsburgh
Posts: 240
Likes: 0
Received 0 Likes
on
0 Posts
Two unique problems with Evoscan
Ok i have two problems with Evoscan that ive never had before.
First Problem
The evoscan version im using is .99
~The remote tuner im using wants me to use this version~
However, when connected to my LC-1 Evoscan only returns single digit numbers when logging the air-fuel ratio.
When i checked the sensor using logworks, the sensor returned a normal reading.
This problem is independent of the second.
Second Problem
The second issue I am having is regarding a custom Data.xml file that the tuner has asked me to use.
The data.xml replaces the normal one that comes with Evoscan, however when attached to the car and i attempt to Datalog.
The idle races, and the car begins to sound rather unsettled, misfiring, running terrible.
Upon shutting off the dataloging, the problem is gone. The problem is also alleviated when restoring Evoscan .99 to its original Data.xml
First Problem
The evoscan version im using is .99
~The remote tuner im using wants me to use this version~
However, when connected to my LC-1 Evoscan only returns single digit numbers when logging the air-fuel ratio.
When i checked the sensor using logworks, the sensor returned a normal reading.
This problem is independent of the second.
Second Problem
The second issue I am having is regarding a custom Data.xml file that the tuner has asked me to use.
The data.xml replaces the normal one that comes with Evoscan, however when attached to the car and i attempt to Datalog.
The idle races, and the car begins to sound rather unsettled, misfiring, running terrible.
Upon shutting off the dataloging, the problem is gone. The problem is also alleviated when restoring Evoscan .99 to its original Data.xml
#2
Evolved Member
iTrader: (18)
For your second problem, from my experience, If you have the white connector plugged in and are trying to run a faster baud rate then what your car is setup for it will cause this to happen.....change the baud rate to 15625 and make sure when you datalog or are doing ANYTHING but flashing to disconnect the white connector...
#4
Evolving Member
iTrader: (9)
Join Date: Feb 2006
Location: willcox, az
Posts: 444
Likes: 0
Received 0 Likes
on
0 Posts
Good luck, old problem with lc-1, mine has never worked with evoscan, none of the versions, i get a reading of 4.7-4.8, I have tried all fixes suggestions, still waiting for newest evoscan, should have fix. I am using ecuedit until then.
Thread
Thread Starter
Forum
Replies
Last Post
6spdlegend
ECU Flash
5
Apr 30, 2015 11:48 AM