Moderator: Freon
A418t81 wrote:v.97 does not log my LC1 correctly. I log values of 5.xx at idle. Also, I tried checking "log wb to .csv" but it weirds my laptop out, logs at 1 sample per sec and generally crashes my computer. WB logs perfectly along with all other data, but obviously shows incorrect values. Would you like any files generated, evo4mad?
Edit: To add to this, LC-1 is selected as the WB as well as the correct COM port. Also, opening log works during the same session (obvious evoscan not logging) shows idle AFRs to be dead on.
hexman wrote:A418t81 wrote:v.97 does not log my LC1 correctly. I log values of 5.xx at idle. Also, I tried checking "log wb to .csv" but it weirds my laptop out, logs at 1 sample per sec and generally crashes my computer. WB logs perfectly along with all other data, but obviously shows incorrect values. Would you like any files generated, evo4mad?
Edit: To add to this, LC-1 is selected as the WB as well as the correct COM port. Also, opening log works during the same session (obvious evoscan not logging) shows idle AFRs to be dead on.
Make sure that you do not have log works open when running EvoScan or visa versa. The com port can only be used by one app at a time.
A418t81 wrote:hexman wrote:A418t81 wrote:v.97 does not log my LC1 correctly. I log values of 5.xx at idle. Also, I tried checking "log wb to .csv" but it weirds my laptop out, logs at 1 sample per sec and generally crashes my computer. WB logs perfectly along with all other data, but obviously shows incorrect values. Would you like any files generated, evo4mad?
Edit: To add to this, LC-1 is selected as the WB as well as the correct COM port. Also, opening log works during the same session (obvious evoscan not logging) shows idle AFRs to be dead on.
Make sure that you do not have log works open when running EvoScan or visa versa. The com port can only be used by one app at a time.
Yes, I understand this, its not the problem. I'm going to try another machine with a built-in serial connector.
3gturbo wrote:Is there any way to fix the problem of evoscan outputting incorrect values on decelaration. evo scan logs 80-120 afr on decel when it should be reading 20.9:1 and my lm-1 is outputting 20.9:1. this messes up the scaling when trying to view the logs.
laakness wrote:Evoscan will read in the serial data that your Wideband is sending it. Do you have the XD gauge hooked up, because by default THAT has a max of 20.9 on it, so if it goes out of range it will display that and the word o2 repeating...just a guess.
laakness wrote:You're right, my log showed a 60 then a 30 after i let out of the gas on a drag-strip run, so it's logging everything the wideband is sending. What are you viewing your log with that scales it like that?
I use DataLogLab and you can view sections of your log so I never see stuff like that.
Return to Data Logging Software
Users browsing this forum: No registered users and 2 guests