Hey guys, I have this problem where my Tactrix cable will log faster than my LC-1, so Evoscan will just leave that row blank in the csv file, which screws up the logs when you use the log viewer. So i made a fix . It needs .Net framework 2.0 and just loads the .csv file, parses it into a bunch of strings. Looks to see if the WidebandAF row is filled in, if so it saves the value. If it is not, it just uses the previous value. It starts with a default of 14.7 If the first row is blank. Here are some screen shots.

Before:


After:


Here it is --> https://www.evolutionm.net/forums/at...1&d=1217779830

Let me know if any problems/errors/it screwed up my log stuff happens.

 

Seems like a good tool. How are you determining the wide band column?

 

Why didn't you just ask if anyone else has this issue or check with evo4mad for a fix? I have a LC1 and have never had an issue???

 

I already talked with Evo4Mad and discussed the problem and ways to fix it.

I only log like 5 things when i run, Engine rpm , load, afr, knock, timing adv, throttle pos. And at 150+ samples a second, the lc-1 just cant keep up (its running at 9600baud i believe) while the tactrix runs at 15625 baud. So i dont get an LC-1 sample every line.

codgi, i took the index of the column named "WidebandAF". Then when you parse the file, for every value at column "index" i check it, thats the wideband afr column. If you want the source code, its like a page long. Really simple.

 

yeah if you wire it into the ecu you will fix that..

 

Yeah run it off the rear o2 sensor is the trick. But... Id rather spend 15 minutes programming than rip into my ecu's wiring again.

 

That looks like the problem I am having when I try to view WBO2 in DLL in a graph. When I graph it in Evoscan it's ok though but it looks related to the same issue you have.

 

yeah, try it out.

 

Perhaps update interval configured in lc1 is not real time? maybe 1/12 update interval?

 

yeah I'll fix it for EvoScan v2.6

 

The update intervals are only for the analog outs. The digital signal isn't delayed or smoothed.

I don't have this issue with my LC-1 or my LM-1. Have you tried running your LC-1 on a different COM port?

 

my LC1 logging has the same issue, its annoying me

 

I see the same thing with my LC-1. I just added some logic to my spreadsheet to "fill in" the data. It would be nice if it didn't happen though.