Innovate LC-1 Trouble
07-25-2010, 04:03 PM
#1
Junior Member
Thread Starter
iTrader: (3)
Join Date: Apr 2010
Location: Belcamp, Maryland
Posts: 55
Total Cats: 1
Innovate LC-1 Trouble
I was having some issues with the DIYPNP I installed, but I have sourced the trouble to the LC-1.
I installed a BRAND NEW LC-1 and it is wired as so:
RED: 12V supply
BLUE: Ground
WHITE: Ground
BLACK: Ground (with calibration button and LED in between)
YELLOW: Innovate DB gauge
BROWN: DB15 to DIYPNP
The ground is off of the ECU ground at the engine near the CAS. I also tried a two other ground spots with identical results, but it is currently on the engine
The problem I am having:
1. The gauge reads 7.7 after free air calibration. During driving it goes from 7.7 at no throttle straight to 10.6 at open throttle (any). this part is now fixed, thanks Scott
2. The DIYPNP reads 22.39 A/F always. Now reads AFR as 10.9 @ closed throttle and 7.7 @ open (any)
3. The computer (via the serial cable) reads everything fine in LogWorks (free air is 20.8% O2 and thus it seems to run fine while driving).Still works fine
4. During startup the gauge flashes 7.4 and the LED blinks. Once the unit is warmed up the gauge reads 7.7 and the LED is solid (no error codes). Fixed, same issue as number 1
See below for explanation of what I did
Obviously the problem is either in the wiring or the software. I'm leaning towards software.
A few questions:
1. The Innovate manual says to run the brown wire to the ECU and the yellow to the gauge. Some threads I have found here have said the opposite.
2. What the hell do I do with the serial IN and OUT cables when not using them? Do I leave the terminators in them? Do I loop them? Does it matter?
3. WHY THE HELL DOESN'T THIS THING WORK?
I would think even with the wires (yellow and brown) going to the wrong spots (ECU/gauge) the signals should be different.
I am definitely trying to figure this out and I know there should be something simple.
I installed a BRAND NEW LC-1 and it is wired as so:
RED: 12V supply
BLUE: Ground
WHITE: Ground
BLACK: Ground (with calibration button and LED in between)
YELLOW: Innovate DB gauge
BROWN: DB15 to DIYPNP
The ground is off of the ECU ground at the engine near the CAS. I also tried a two other ground spots with identical results, but it is currently on the engine
The problem I am having:
1. The gauge reads 7.7 after free air calibration. During driving it goes from 7.7 at no throttle straight to 10.6 at open throttle (any). this part is now fixed, thanks Scott
2. The DIYPNP reads 22.39 A/F always. Now reads AFR as 10.9 @ closed throttle and 7.7 @ open (any)
3. The computer (via the serial cable) reads everything fine in LogWorks (free air is 20.8% O2 and thus it seems to run fine while driving).Still works fine
4. During startup the gauge flashes 7.4 and the LED blinks. Once the unit is warmed up the gauge reads 7.7 and the LED is solid (no error codes). Fixed, same issue as number 1
See below for explanation of what I did
Obviously the problem is either in the wiring or the software. I'm leaning towards software.
A few questions:
1. The Innovate manual says to run the brown wire to the ECU and the yellow to the gauge. Some threads I have found here have said the opposite.
2. What the hell do I do with the serial IN and OUT cables when not using them? Do I leave the terminators in them? Do I loop them? Does it matter?
3. WHY THE HELL DOESN'T THIS THING WORK?
I would think even with the wires (yellow and brown) going to the wrong spots (ECU/gauge) the signals should be different.
I am definitely trying to figure this out and I know there should be something simple.
Last edited by NateTheShake; 07-25-2010 at 08:49 PM.
Reply
0
0
07-25-2010, 06:41 PM
#2
Senior Member
iTrader: (4)
Join Date: Jan 2008
Location: Falls Church, VA
Posts: 1,361
Total Cats: 17
Connect to it with Logworks and make sure your outputs are configured properly. My recollection is that one output comes preconfigured to run the DB gauge, and the other is configured to simulate a narrowband sensor. You have to change that in Logworks. Just remember it's like pee-pee and poo-poo, yellow is #1 and brown is #2. I think I ran #2 to the gauge, and #1 to my MS, but it doesn't matter which goes where as long as they are configured appropriately.
EDIT: Your DB gauge is probably reading like it is because you have it hooked to the output that's simulating a narrowband, that's why it's only reading 7.x or 10.x (NBO2s have a range of 0-1V).
I leave the in & out cables kind of tucked into the center console with the connectors dangling out a little bit between the console and passenger seat so I can access them if needed (extremely rare). Once you get things configured & running properly you may never use them again, so tuck them wherever. The serial terminator I keep in the original box in my garage, otherwise I'd lose it.
EDIT: Your DB gauge is probably reading like it is because you have it hooked to the output that's simulating a narrowband, that's why it's only reading 7.x or 10.x (NBO2s have a range of 0-1V).
I leave the in & out cables kind of tucked into the center console with the connectors dangling out a little bit between the console and passenger seat so I can access them if needed (extremely rare). Once you get things configured & running properly you may never use them again, so tuck them wherever. The serial terminator I keep in the original box in my garage, otherwise I'd lose it.
Reply
0
0
07-25-2010, 08:47 PM
#3
Junior Member
Thread Starter
iTrader: (3)
Join Date: Apr 2010
Location: Belcamp, Maryland
Posts: 55
Total Cats: 1
Connect to it with Logworks and make sure your outputs are configured properly. My recollection is that one output comes preconfigured to run the DB gauge, and the other is configured to simulate a narrowband sensor. You have to change that in Logworks. Just remember it's like pee-pee and poo-poo, yellow is #1 and brown is #2. I think I ran #2 to the gauge, and #1 to my MS, but it doesn't matter which goes where as long as they are configured appropriately.
EDIT: Your DB gauge is probably reading like it is because you have it hooked to the output that's simulating a narrowband, that's why it's only reading 7.x or 10.x (NBO2s have a range of 0-1V).
I leave the in & out cables kind of tucked into the center console with the connectors dangling out a little bit between the console and passenger seat so I can access them if needed (extremely rare). Once you get things configured & running properly you may never use them again, so tuck them wherever. The serial terminator I keep in the original box in my garage, otherwise I'd lose it.
EDIT: Your DB gauge is probably reading like it is because you have it hooked to the output that's simulating a narrowband, that's why it's only reading 7.x or 10.x (NBO2s have a range of 0-1V).
I leave the in & out cables kind of tucked into the center console with the connectors dangling out a little bit between the console and passenger seat so I can access them if needed (extremely rare). Once you get things configured & running properly you may never use them again, so tuck them wherever. The serial terminator I keep in the original box in my garage, otherwise I'd lose it.
I switched the settings for the analog wires so now they read like this:
Analog Out 1: 0.00V = 7.35 AFR / 5.000V = 22.39 AFR
Analog Out 2: 1.10V = 14.00 AFR / 0.10V = 15.00 AFR
Now the gauge (wired to yellow Analog Out 1) reads very close to correct, it's only off by a little bit in free air. However now the TunerStudio reads the AFR as either 10.9 at closed throttle and 7.7 at open throttle.
The big question: What settings should I be putting in for the TunerStudio (brown, Analog Out 2)?
It looks like it was definitely an issue of the software, I just have to make the TunerStudio understand what the LC-1 is telling it. I tried making both of the Analog Out's read as wideband (0-5V) but it still didn't understand. Am I missing something?
I have the TunerStudio project setup for Innovative LC-1 Wideband in the AFR settings so it should understand what it's seeing, but obviously I'm messing something up.
Reply
0
0
07-26-2010, 12:40 AM
#4
Senior Member
iTrader: (4)
Join Date: Jan 2008
Location: Falls Church, VA
Posts: 1,361
Total Cats: 17
The settings you just posted for output #1 are correct for the gauge. You have output #2 simulating a narrowband sensor so that's what needs to change. Configure #2 so 0-5V = 10-20:1 AFR.
If by "it didn't understand," you mean the values didn't "stick" in Logworks, then yeah I've had it do that to me. There are a couple solutions... you can try a few times to store the values and it may eventually work. But I think the software more easily stores the values if you input them as lamba instead of AFR. Don't know why, it's just how mine was. So you can try 0-5V = 0.68-1.36 lambda. Those lambda values correspond to 10-20:1 AFR for gasoline (stoich = 14.7:1) and that's what I used and it stuck the first time. Give that a try.
If by "it didn't understand," you mean the values didn't "stick" in Logworks, then yeah I've had it do that to me. There are a couple solutions... you can try a few times to store the values and it may eventually work. But I think the software more easily stores the values if you input them as lamba instead of AFR. Don't know why, it's just how mine was. So you can try 0-5V = 0.68-1.36 lambda. Those lambda values correspond to 10-20:1 AFR for gasoline (stoich = 14.7:1) and that's what I used and it stuck the first time. Give that a try.
Reply
0
0
07-26-2010, 05:28 AM
#5
Junior Member
Thread Starter
iTrader: (3)
Join Date: Apr 2010
Location: Belcamp, Maryland
Posts: 55
Total Cats: 1
The settings you just posted for output #1 are correct for the gauge. You have output #2 simulating a narrowband sensor so that's what needs to change. Configure #2 so 0-5V = 10-20:1 AFR.
If by "it didn't understand," you mean the values didn't "stick" in Logworks, then yeah I've had it do that to me. There are a couple solutions... you can try a few times to store the values and it may eventually work. But I think the software more easily stores the values if you input them as lamba instead of AFR. Don't know why, it's just how mine was. So you can try 0-5V = 0.68-1.36 lambda. Those lambda values correspond to 10-20:1 AFR for gasoline (stoich = 14.7:1) and that's what I used and it stuck the first time. Give that a try.
If by "it didn't understand," you mean the values didn't "stick" in Logworks, then yeah I've had it do that to me. There are a couple solutions... you can try a few times to store the values and it may eventually work. But I think the software more easily stores the values if you input them as lamba instead of AFR. Don't know why, it's just how mine was. So you can try 0-5V = 0.68-1.36 lambda. Those lambda values correspond to 10-20:1 AFR for gasoline (stoich = 14.7:1) and that's what I used and it stuck the first time. Give that a try.
0V = 10 AFR OR 0V = 0.68 Lamba
5V = 20 AFR OR 5V = 1.36 Lamba
Correct?
Also I am putting these in the LM Tuner, not LogWorks right? Not trying to argue semantics, but I'm making sure I'm not missing something in LogWorks. As far as I can tell LM Tuner is for setting the parameters and LogWorks is for reading the output.
Thanks for the insight! Hopefully I get this thing working soon.
Reply
0
0
Thread
Thread Starter
Forum
Replies
Last Post
