LC1 datalogging, log works and crome wont match up!
 

so i finally got logworks running with the lc1, i planned on using the offset correction in crome pro to sync them up. I got it close (sometimes) with a corretion of .09. Problem is, cromes afr's dont change as rapidly as log works. It will stay at certain values while logworks will vary slightly.

settings in crome are

lamda value .5 - 1.5

throttle 5 - 110%

normal coolant temp and map readings (i dont remember what they are)


Do i have to change the settings in the lc1 to read 0-3v instead of 0-5V? Or is this not needed?

Re: LC1 datalogging, log works and crome wont match up!
 

Unless you've modd'd the ECU to read 0-5v, you have to have the LC1 read0-3 volts, I believe.

Re: LC1 datalogging, log works and crome wont match up!
 

i thought crome just wouldnt log anything above 1.5 lamda or something. So it just wouldnt record 17's and up ???

Re: LC1 datalogging, log works and crome wont match up!
 

theres a refresh rate in crome too, just because it isnt changing rapidly on the screen, doesnt mean its not logging correctly...

basically, it turns down the rate of speed the screen refreshes so that its less intensive on the ecu and it can take more data samples from the datalogging cable.

Re: LC1 datalogging, log works and crome wont match up!
 

yea, i kinda figured it wouldnt update as rapidly. But it shouldnt keep logging the same numbers all over the place right? Like from 11" to .93psi it would record 13.3. In all cells, regardless of rpm. I used xeno's settings in crome, and it had no effect. The only accurate reading i get is from log works???

at this point, it either has to be the settings in crome, or the physical wireing of the controller. As stated, i used xeno's settings, and the controller is wired like sm95's. (or whatever his name is)

should the lc1 be programmed to read 0-3V, or the preprogrammed setting of 0-5V?

using the innovative wideband correction in crome yields an 8.32 reading when its actually 14.5 (according to log works)

we just street tuned based solely on the logworks screen and using datalogging in crome to see what cell it was in. I cant imagine how much better it would be if it were to datalog exact afr's in each cell. I also cant imagine how stupid i must be for this not to be working.