PRA ECU - WIDEBAND O2 SENSOR?
The ELD wire is definitely disconnected and isolated. Only the analog two output is connected to it. There is a load of stuff about resistors that need cut in the S-Manager forum for a US ECU to improve input...wonder if this is the case for the PRA one too?Stuart wrote:that's intersting....
I wonder if the ELD input has a pull-up resistor in the ECU?
Can't say I have seen this before, are you sure nothing else is connected to it (like the ELD?)
Narrowband output should eb OK as it is, and looking at your earlier log, looked to be working about right?
The narrowband output does not seem to input correct voltages to the ECU either once connected. The O2 sensor in KManager displays different voltages than it is supposed to, unless this is not actually the voltage input of pin ECU A6.
0.24V at full throttle with a target AFR of 12.5 - should surely be higher than 1.1V? However, this is almost the same value as with the stock O2 sensor fitted.
The car does start to splutter and cut out once it has been idling in closed loop for a few minutes.
I'm afraid not as the LC-1 is now giving out crazy readings and I have forced the car into open loop. I'm suspecting the LC-1 is sooted up again so I will need to take it out, clean it and recalibrate again. I'll do a datalog once I've done this.Stuart wrote:got a datalog if it doing that?
I'm thinking of just using the stock primary sensor again as it works fine. I don't think my ECU is suitable for using the ELD pin for the input so it is kind of pointless. I might just stick the LC-1 in the sec o2 location and use Logworks to monitor the AFR instead as the serial output works fine.
It is a long shot, but...Hondata...any plans to integrate the serial input from the Innovate LC-1 into KManager for datalogging?
Calibrated the LC-1 again...seems to be working for now. Programmed analog output to default. I set the output to flatline set voltages and read the ELD pin voltage to work out a conversion table. Here's the results:
LC-1 V---ELD V------AFR
0---------1.333-------7.350
1---------1.958-------10.358
2---------2.681-------13.366
3---------3.413-------16.374
4---------4.145-------19.382
5---------4.853-------22.390
Looks to be giving reasonably accurate AFR's in KManager now :-)
Fingers crossed that it remains so. I'm not going to touch it now!
LC-1 V---ELD V------AFR
0---------1.333-------7.350
1---------1.958-------10.358
2---------2.681-------13.366
3---------3.413-------16.374
4---------4.145-------19.382
5---------4.853-------22.390
Looks to be giving reasonably accurate AFR's in KManager now :-)
Fingers crossed that it remains so. I'm not going to touch it now!
-
Garrett_si
- Posts: 253
- Joined: Wed May 17, 2006 9:49 am
The LC-1 has a serial output which allows accurate AFR values to be viewed on a PC using Logworks. This serial output is not effected by voltage offsets.Garrett_si wrote:there is one thing to keep in mind when using the ELD input for external wideband
you need to ajust the voltage offset
the big problem with the LC-1 is that you don't have a display so you aren't able to ajust your offset
and the offset could be of about 1:1 in some cases
The easiest way is to program the LC-1 to flatline a set voltage for all AFR values and check what voltage the ELD pin reads (eg. Program the LC-1 analog out 2 to 0V=7.35AFR, 0V=22.39AFR). This way you know the voltage output of the analog 2 wire regardless of AFR. I did this for 0,1,2,3,4 and 5V to make my conversion table. Now KManager is datalogging accurate AFR values when compared to Logworks. Now we're jamming :-)
Is there a way to work out how much to reduce the fuel table value by looking at a datalog? I would like to tweak my calibration on the road...