Innovate Wideband working, but not logging correctly
Jul 9, 2008, 10:06 AM
#17
yeah i had it logging in logworks fine. it just that it didnt have any other parameters such as rpm or anything. im not sure if it would benefit my tuner just having an afr log in logworks without knowing what rpm and stuff i was at.
Jul 9, 2008, 12:59 PM
#18
Evolving Member
iTrader: (3)
Join Date: Jul 2004
Location: Richmond, VA
Posts: 179
Likes: 0
Received 0 Likes
on
0 Posts
I had the same symptoms when trying to use Lc-1 w/ evoscan .99. The problem occurs when you plug into the lc-1's serial out while the unit is powered on. To fix: launch lm programmer and reset lc-1 to gasoline, 14.7:1. For some reason when plugging in w/ power on, the programmer sets it to a custom configuration hence the 3-4.xxx. If this is your problem, be sure to hook up all cables (openport, serial to usb) to car and laptop before powering the car.
Hope that fixes your prob, it fixed mine.
Hope that fixes your prob, it fixed mine.
Jul 10, 2008, 09:02 AM
#21
Evolving Member
iTrader: (3)
Join Date: Jul 2004
Location: Richmond, VA
Posts: 179
Likes: 0
Received 0 Likes
on
0 Posts
Hook everything up, then configure it following the LC-1 instruction manual. After configuration always have everything plugged in before starting the car.
Jul 10, 2008, 09:54 PM
#22
Evolving Member
Join Date: Sep 2005
Location: Va Beach, VA
Posts: 109
Likes: 0
Received 0 Likes
on
0 Posts
Basically, you plug everything in before you turn the car to the ON position(or however you have your power setup for the LC-1). Turn the power to the LC-1 on. From there, Open LM programmer. Using LM Programmer check to see that your sensor config is set to default. Once it is set to default you're good to go. Just make sure that the LC-1 is off every time you, plug-in to or, unplug from it.
Jul 11, 2008, 04:24 PM
#24
alright, so i tried doing the lm programmer thinger, seriously it took 50 tries for it to stay on 14.7, i would click on it and then it would just make up a custom number. then when it finally worked my lc-1 wouldn't read right at all, so now i have to do a free air calibration or something, im starting to get pretty pissed. alright ill keep trying everything.
Jul 12, 2008, 05:58 PM
#25
alright i just installed 2.4 and tried and its still not working right. i recalibrated the gauge in free air again becuase i messed it up with the lm programmer trying and finally getting it onto 14.7 now its reading at like 10.x im so pissed i really don't knwo what else to try. i can't configure it with the lm programmer without it making the lc-1 not read at all and then i have to do a free air calibration and im not trying to jack the car up everytime i try to fix it with the lm programmer.
Jul 12, 2008, 06:31 PM
#26
sorry to hear you have so much problems with your system.
If I remember correctly you set the reading to gasoline. this can be done in logworks before after or during a log.
Since you are bound to use evoscan, might i suggest you get everything working in logworks first so you know where your issue is coming from.
open openport 1.3, select what you want to log, press log, and then open logworks, connect, {AND now you can adjust your afr reading from lambda or gasoline} and then start a real time log.
let us know if you can get that going.
If I remember correctly you set the reading to gasoline. this can be done in logworks before after or during a log.
Since you are bound to use evoscan, might i suggest you get everything working in logworks first so you know where your issue is coming from.
open openport 1.3, select what you want to log, press log, and then open logworks, connect, {AND now you can adjust your afr reading from lambda or gasoline} and then start a real time log.
let us know if you can get that going.
Aug 12, 2008, 06:51 AM
#30
Evolving Member
your [cough] wife [gag] crashed [sputter] your [spew] evo?!?!?! My consolation on your divorce :O ok ok just kidding. Sorry to hear it, and I assume (and sincerly hope) she is OK.
