Wierd Evoscan 2.5 Problem
Wierd Evoscan 2.5 Problem
So I finally decided to upgard from my trusty Evoscan ver 0.99 (the best one IMO) to ver 2.5.
I am having this problem:
For some odd reason everytime the driver lifts off the gas and the oxygen content in the exhaust stream goes above ~17% (Evoscan says that in a little window) the wideband stops registering on Evoscan. The wideband still registers on the screen of the innovate LM-1. It is very normal for O2 content to go up to 20% when lifting off the gas.
The wideband sensor was plugged in place of the stock rear O2 sensor. The car had a test pipe
I had to go back to my trusty ver 0.99 and things wroked great. I have never had this problem with ver 0.99
Anyone has any idea how to fix this?
I am having this problem:
For some odd reason everytime the driver lifts off the gas and the oxygen content in the exhaust stream goes above ~17% (Evoscan says that in a little window) the wideband stops registering on Evoscan. The wideband still registers on the screen of the innovate LM-1. It is very normal for O2 content to go up to 20% when lifting off the gas.
The wideband sensor was plugged in place of the stock rear O2 sensor. The car had a test pipe
I had to go back to my trusty ver 0.99 and things wroked great. I have never had this problem with ver 0.99
Anyone has any idea how to fix this?
Ok, so I tried getting Evoscan 2.5 to work one more time and still have the same problem.
This time I tried it on my own car with the same results. When I lift off the gas and the oxygen content in the exhaust goes above ~17%, Evoscan stops logging the LM-1. The LM-1 is still wroking fine, so it is not an LM-1 problem. The LM-1 and ver 0.99 do not have this problem.
Is there anyone who is using Evoscan ver 2.5 with the LM-1 who can help?
This time I tried it on my own car with the same results. When I lift off the gas and the oxygen content in the exhaust goes above ~17%, Evoscan stops logging the LM-1. The LM-1 is still wroking fine, so it is not an LM-1 problem. The LM-1 and ver 0.99 do not have this problem.
Is there anyone who is using Evoscan ver 2.5 with the LM-1 who can help?



