mfb wrote:MechEE wrote:For me the sample config file was wrong. I used
Confirmed for me as well: 0x0101 is the correct paramid for logging lambda on the LC-1. I was pulling my hair out trying to figure out why I was getting such a strange calculated AFR (~72:1) after flashing to the latest OpenPort firmware. It turns out it was a combination of an error in the sample LC-1 logcfg.txt suggesting the paramid should be 0x0102 and the infamous LC-1 reset bug that had a stoich of ~4.7:1 set. Oops!
Yep, I got this one too. Only problem is we all followed the address in the sample file. No biggie... Its one or the other, haha There's only 2 channels to choose from. If you look at LM programmer, you'll see it there.
Just be careful to make sure that you only pull the lc1 plug or attach it to OP2 if LC1 is off meaning ignition is off. Not doing so and operating this while on may cause LC1 to be sent a "recalibration" command and you will just get a 7 or 22 afr reading. This happened to me thrice already and in Colby's post here, it confirms and solved my issue. You can see it here http://forums.openecu.org/viewtopic.php?f=57&t=4319&start=420#p23313I think I covered this somewhere before - it is basically a minor hw/sw design flaw in the LC-1 that can cause it to lose its settings when you you plug it into another device. What happens is that the tip terminal of the 2.5 plugs can get grounded as you plug them in, which is not a big deal in itself since it is an input, but some unfortunate protocol choices can make that glitch look like some sort of "clear calibrations" command. This isn't speculation - I heard this from the engineers at Innovate. So the solutions are to:
1) Plug the LC-1 in to the OP2 only when the LC-1 is off
2) Let the OP2 take care of the AFR scaling so that you don't notice the problem
Best to make OP2 do the scaling as per the sample file. Btw, once you got it calibrated and working, dont be surprised to see a custom settting when you go back to LM Programmer. I just chose gasoline again. I dont know why it went to custom, maybe it because Im using ethanol 10 based gas? But non issue as we scale using OP2.
My understanding is that the accidental "clear calibrations" command only affects things if you rely on the LC-1 to do the fuel-specific gain from lambda to AFR. Since we're doing it now within the OpenPort software, this shouldn't be an issue any longer, correct? "Clear calibrations" seems like a strange name though... that suggests it will clear the sensor calibration, possibly initiating a new sensor calibration when the sensor isn't in open air.