Wideband datalogging question re ECU pins and wideband
09-07-2006, 05:06 PM
#1
Honda-Tech Member
Thread Starter
Join Date: Apr 2004
Location: Winnipeg, MB
Posts: 1,040
Likes: 0
Received 0 Likes
on
0 Posts
Wideband datalogging question re ECU pins and wideband
Hello,
Uberdata has worked great for me for over a year and I have been running flawlessly with 550cc injectors until recently but I came across a good deal on some larger ones and seeing as I am building a turbo motor over the winter I decided to upgrade sooner, rather than later. I was dyno tuned with Uberdata 1.66 but only at WOT.
After I installed the injectors I had 2 BAD stumbles at 2000rpm and 3000rpm. Obviously this is because of the lack of part throttle tuning and the huge injectors so I bought an Innovate LC-1 this weekend to try some datalogging.
The LC-1 has 2 analog outputs which can be programmed. By default analog 1 simulates a narrowband and analog 2 is a 0-5v wideband. I have a 93 Civic Si with a 95 GSR motor and ECU. I hooked up analog 1 to pin d14 and analog 2 to pin d10 like I have read many times. I burned a ROM with the ost2 version of Uberdata since I also picked up a Moates Ostrich. I disabled closed loop and the O2 heater in the ROM and the car runs exactly the same as before so I went to do some street tuning.
The problem I have is that my A/F values were reading incorrectly - about 9 too low and the values went up instead of down as the A/F got richer. I have an Autometer A/F gauge and it was doing it's Xmas tree thing like it should and went rich when I was in boost like it was tuned for but the laptop would go from 7.x at idle to 10.x in boost.
Obviously I was getting a narrowband reading so I programmed the LC-1 analog 1 to be the wideband out and voila - it works perfectly.
My question is - why did I have to switch the outputs on the LC-1? I have read several places where they say to run the 0-5v output to the ELD pin (d10) and the 0-1v narrowband to d14.
I posted this on the uberdata forum but, as you know, it is kind of slow.
Modified by xrdriver at 11:01 PM 9/7/2006
Uberdata has worked great for me for over a year and I have been running flawlessly with 550cc injectors until recently but I came across a good deal on some larger ones and seeing as I am building a turbo motor over the winter I decided to upgrade sooner, rather than later. I was dyno tuned with Uberdata 1.66 but only at WOT.
After I installed the injectors I had 2 BAD stumbles at 2000rpm and 3000rpm. Obviously this is because of the lack of part throttle tuning and the huge injectors so I bought an Innovate LC-1 this weekend to try some datalogging.
The LC-1 has 2 analog outputs which can be programmed. By default analog 1 simulates a narrowband and analog 2 is a 0-5v wideband. I have a 93 Civic Si with a 95 GSR motor and ECU. I hooked up analog 1 to pin d14 and analog 2 to pin d10 like I have read many times. I burned a ROM with the ost2 version of Uberdata since I also picked up a Moates Ostrich. I disabled closed loop and the O2 heater in the ROM and the car runs exactly the same as before so I went to do some street tuning.
The problem I have is that my A/F values were reading incorrectly - about 9 too low and the values went up instead of down as the A/F got richer. I have an Autometer A/F gauge and it was doing it's Xmas tree thing like it should and went rich when I was in boost like it was tuned for but the laptop would go from 7.x at idle to 10.x in boost.
Obviously I was getting a narrowband reading so I programmed the LC-1 analog 1 to be the wideband out and voila - it works perfectly.
My question is - why did I have to switch the outputs on the LC-1? I have read several places where they say to run the 0-5v output to the ELD pin (d10) and the 0-1v narrowband to d14.
I posted this on the uberdata forum but, as you know, it is kind of slow.
Modified by xrdriver at 11:01 PM 9/7/2006
09-07-2006, 07:08 PM
#3
Re: (lightcrx)
There is only 1 input for the O2 signal in an OBD1 ECU...any signal you send to the ECU has to be through pin D14
maybe you read somewhere about someone logging a separate input, but thats not general practice
maybe you read somewhere about someone logging a separate input, but thats not general practice
09-08-2006, 08:23 AM
#4
Join Date: Jun 2003
Location: ca
Posts: 1,165
Likes: 0
Received 0 Likes
on
0 Posts
Re: (xenocron)
<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by xenocron »</TD></TR><TR><TD CLASS="quote">There is only 1 input for the O2 signal in an OBD1 ECU...any signal you send to the ECU has to be through pin D14
maybe you read somewhere about someone logging a separate input, but thats not general practice</TD></TR></TABLE>
so whats d10 for?
i only use d14 ;]
-joseph
maybe you read somewhere about someone logging a separate input, but thats not general practice</TD></TR></TABLE>
so whats d10 for?
i only use d14 ;]
-joseph
09-08-2006, 08:53 AM
#5
Re: (lightcrx)
D10 is ELD (electronic load detector), if you manipulate the code, it can be used as another input that can be logged...but this isnt something that is built into Crome/Uberdata so you need to know how to program assembly to do this I would imagine.
Thread
Thread Starter
Forum
Replies
Last Post
