Evoscan and Innovate LC1
Evoscan and Innovate LC1
Well I got everything hooked up in my car but I'm having a bit of a problem here. I've logged 3 runs. 1st run at 10lbs(for ****s and giggles)
2nd and 3rd run at stock boost.
My evo 8 is completely stock. I'm having a problem with evoscan logging A/F ratio from innovate lc1. It looks to be correct and reading right but when I floor the gas, the a/r reading from innovates software drops down to 10a/f ratio but the A/F in Evoscan still says ~14.5a/f ratio. Is there something I'm missing here?
BTW - Stock evo is at 217hp? Does that sound correct? accroding to virtual dyno.
Car has 55k miles on it.
Please advise. Something seems wrong here. Maybe evoscan not logging correctly? I can email you the data log if need be.
2nd and 3rd run at stock boost.
My evo 8 is completely stock. I'm having a problem with evoscan logging A/F ratio from innovate lc1. It looks to be correct and reading right but when I floor the gas, the a/r reading from innovates software drops down to 10a/f ratio but the A/F in Evoscan still says ~14.5a/f ratio. Is there something I'm missing here?
BTW - Stock evo is at 217hp? Does that sound correct? accroding to virtual dyno.
Car has 55k miles on it.
Please advise. Something seems wrong here. Maybe evoscan not logging correctly? I can email you the data log if need be.
right port? I know its on the right serial port. I just don't know if its a bug or not. I'm wondering if its working for others or are they experiencing the same problem.
When I WOT the car, I can see that the a/f ratio drops in logworks but then in evoscan, its still showing the same thing.
When I WOT the car, I can see that the a/f ratio drops in logworks but then in evoscan, its still showing the same thing.
A/F in Evoscan still says ~14.5a/f ratio.
what does this mean? do you have the mrfred fix for logging afr or are you looking at the "afr map"?
you should be looking at the afr that evoscan logs of the lc-1.
what does this mean? do you have the mrfred fix for logging afr or are you looking at the "afr map"?
you should be looking at the afr that evoscan logs of the lc-1.
I'm not sure if its an evoscan bug or a problem between evoscan and logworks serial.
here is the file of the pulls. i had to copy and paste whats in WOT only.
You can see what I mean. Mind you this car is all stock and the a/f ratio on log works in the 10s but evoscan sees it in the 14s.
I' wondering is i'm missing something when setting it up.
You can see what I mean. Mind you this car is all stock and the a/f ratio on log works in the 10s but evoscan sees it in the 14s.
I' wondering is i'm missing something when setting it up.
Trending Topics
yes I'm using 2.5 evoscan. How do yo log a/f ratio if you dont mind me asking.
I'm wondering if it has something to do with logworks. Does evoscan work with only a certain version of logworks?
I'm wondering if it has something to do with logworks. Does evoscan work with only a certain version of logworks?
since you ask I assume I am not interpreting your post correctly. since I don't think you can log the two at the same time.*
are you using the term logworks generically as in the output configuration aspect of the program?
if you are seeing the correct afr some of the time I would imagine the configuration of the lc-1 output is correct....?
*you don't need logworks to log to evoscan, I always did one OR the other.
just take the serial cable from the lc-1 put a usb adaptor on it and plug that into the laptop.
check to make sure evoscan is seeing the usb port, that the lc-1 wideband is checked and you should be good to go.
or are you getting a reading from one of the ecu mods mrfred devised for evoscan/lc-1?
are you using the term logworks generically as in the output configuration aspect of the program?
if you are seeing the correct afr some of the time I would imagine the configuration of the lc-1 output is correct....?
*you don't need logworks to log to evoscan, I always did one OR the other.
just take the serial cable from the lc-1 put a usb adaptor on it and plug that into the laptop.
check to make sure evoscan is seeing the usb port, that the lc-1 wideband is checked and you should be good to go.
or are you getting a reading from one of the ecu mods mrfred devised for evoscan/lc-1?
since you ask I assume I am not interpreting your post correctly. since I don't think you can log the two at the same time.*
are you using the term logworks generically as in the output configuration aspect of the program?
if you are seeing the correct afr some of the time I would imagine the configuration of the lc-1 output is correct....?
*you don't need logworks to log to evoscan, I always did one OR the other.
just take the serial cable from the lc-1 put a usb adaptor on it and plug that into the laptop.
check to make sure evoscan is seeing the usb port, that the lc-1 wideband is checked and you should be good to go.
or are you getting a reading from one of the ecu mods mrfred devised for evoscan/lc-1?
are you using the term logworks generically as in the output configuration aspect of the program?
if you are seeing the correct afr some of the time I would imagine the configuration of the lc-1 output is correct....?
*you don't need logworks to log to evoscan, I always did one OR the other.
just take the serial cable from the lc-1 put a usb adaptor on it and plug that into the laptop.
check to make sure evoscan is seeing the usb port, that the lc-1 wideband is checked and you should be good to go.
or are you getting a reading from one of the ecu mods mrfred devised for evoscan/lc-1?
I was using the 2 software at the same time.
So you are suggesting that I can't run logworks and evoscan at the same time and I shouldn't?
What mod are you referring to? I've left everything as is and I didnt' change a thing. BTW I appreciate the help.
I suppose you could run them at the same time, but what do you do, split the serial out of the lc-1? hmmm there might be some interference between evoscan and logworks if you are tapping the same signal into to two programs.
Anyway try just evoscan with the lc-1, without logworks on. That will tell us if there is a conflict running the lc-1 through both programs.
btw, some one has posted the way to run evoscan logs through logworks, somewhere, I don't know where or how much effort that takes.
mrfred has two mods for the lc-1. one, allows you to read the lc-1 via the ecu by inputting the data in an unused ecu wire. with one of the signal wires
(yellow) in the lc-1 bundle. two, escapes me at the moment.
Anyway try just evoscan with the lc-1, without logworks on. That will tell us if there is a conflict running the lc-1 through both programs.
btw, some one has posted the way to run evoscan logs through logworks, somewhere, I don't know where or how much effort that takes.
mrfred has two mods for the lc-1. one, allows you to read the lc-1 via the ecu by inputting the data in an unused ecu wire. with one of the signal wires
(yellow) in the lc-1 bundle. two, escapes me at the moment.
I suppose you could run them at the same time, but what do you do, split the serial out of the lc-1? hmmm there might be some interference between evoscan and logworks if you are tapping the same signal into to two programs.
Anyway try just evoscan with the lc-1, without logworks on. That will tell us if there is a conflict running the lc-1 through both programs.
btw, some one has posted the way to run evoscan logs through logworks, somewhere, I don't know where or how much effort that takes.
mrfred has two mods for the lc-1. one, allows you to read the lc-1 via the ecu by inputting the data in an unused ecu wire. with one of the signal wires
(yellow) in the lc-1 bundle. two, escapes me at the moment.
Anyway try just evoscan with the lc-1, without logworks on. That will tell us if there is a conflict running the lc-1 through both programs.
btw, some one has posted the way to run evoscan logs through logworks, somewhere, I don't know where or how much effort that takes.
mrfred has two mods for the lc-1. one, allows you to read the lc-1 via the ecu by inputting the data in an unused ecu wire. with one of the signal wires
(yellow) in the lc-1 bundle. two, escapes me at the moment.
I'm trying to avoid sending an analog signal to the ecu to log it in evoscan if it logs directly using the serial.
Thread
Thread Starter
Forum
Replies
Last Post




