I circled the terminator plug in red in the attached image.
Edit: Joe, your picture is much better :)
Regards
Paul
Printable View
I circled the terminator plug in red in the attached image.
Edit: Joe, your picture is much better :)
Regards
Paul
lol... I think I overdid my pic... :hihi:
I love you guys :)
I can't believe that this little dead end plug is whats needed to make this work. It doesnt make sense to me, but what do i know. As soon as i plugged it, the 2nd from left orange light started blinking every second.
It is working at laaaaaaaaaaaaaaaast. I drove around and the AF was perfect showing mid 12's under WOT.
Thanks a bunch for all the help. Really appreciate it.
Is this wiring right or wrong if it wrong so can you show a correct onehttp://forum.efilive.com/attachment....6&d=1278553107
Is that a null modem or a gender bender?
A null modem is needed.
That little plug is detected by the LC1. As soon as it detects the plug it starts transmitting the serial wide band data. If it does not see the plug then it does not transmit the data.
I'm pretty sure it has something to do with the LC1's ability to be daisy chained with other LC1's. Each LC1 in the chain waits for the previous LC1 to transmit its data, then it appends its own data to all the previous LC1s' data.
So basically the furthest away LC1 needs to be "told" not to wait for any other previous LC1's data (since there is no further LC1 in the chain) and to just transmit its data, to which all the other LC1's will append their data as the data makes it way back to FlashScan along the chain.
If you only have 1 LC1, it doesn't know its the only one and therefor the furthest one and that it should just transmit its data and not wait for another (further away) LC1 to start transmitting. The only way to "tell" it that information is to plug the loop back dongle into its serial cable.
That's my understanding it could be wrong, the guys at Innovate would know more...
Regards
Paul
My A/F is reading 5 AF which is not right. The Lambda is reading 1.0 around idle like before when it was reading 14.5-14.7 AF.
I re-calibrated the sensor and it is still showing 5 AF. Is there a way to diagnose the problem? I mean how can i know if the problem is the Oxygen Sensor itself or a calibration problem?
Did you install the latest software/firmware from here.
V8 build 106 includes firmware 2.6.36, you have to flash this into V2.
Yes, nothing changed from before. Everything was working fine and reading as the Dynojet AF gauge. All of the sudden it started reading off. I'm not sure if it is the Oxygen sensor being off or something else.
Is there a direct relationship between the Lambda reading and the AF? Can you convert the Lambda reading to AF mathematically?
I'm asking because the Lambda reading did not change while the AF number changed. I'm trying to diagnose the cause of the problem.
Direct relationships: AFR = STOICH_AFR * Lambda and EQR = 1 / Lambda
So with your LC-1 you're seeing V2 say Lambda = 1.00 and AFR = 5...?
Can you check this: with LM Programmer software check what STOICH AFR the LC-1 is programmed for.
Can you post a log file showing WO2AFR1, WO2LAM1, WO2EQR1, WO2ST1.
Attached you will find the log file.
I will have to make another log to capture all the variables you wanted below.
My LMprogrammer doesn't work. I have never accessed the LM Software before. It was working before so I'm assuming nothing has changed there.
Have you tried re-installing LM Programmer...?
Sometimes the LC-1's value for STOICH AFR changes by itself, a few of us have seen this.
Yes, do get another log that also includes WO2EQR1 for sanity check.
SERIAL IN <-- 2.5mm blank stereo plug (leave this permanently connected)
SERIAL OUT --> LC-1 serial cable --> PC/laptop (i.e. remove the null-modem adapter)
I changed the first page setting to Gasoline and it worked just fine.
I guess LC1 setting did change by itself.
Thank you
Yes, keep an eye on it, this is an LC-1 quirk.
Set the LC-1 stoichiometric AFR to the same value as your B3601.
In your PCM's calibration...
Did you read your PCM and save it to .tun file...? If you do this then you can view your calibration tables.
Or, more simply, when running in closed loop, just log GM.AFR... during closed loop this will be equal to B3601.