Rough idle at operating temperature
#11
#12
#13
If ya wanna know, or at least know what it ain't, try that unplugging the front oxygen sensor thing. Running hard lean is a classic symptom of a crap sensor -- the signal from a failing sensor is overly rich and the PCM is trying to haul that false reading back into line.
#15
#16
I haven't ever been fortunate enough to actually see an OBD-II vehicle set an O2 code before driver annoyance has reached critical levels. The early 1980's logic that was capable of detecting the normal end of life (falsely rich signal) condition got removed because a tangentially related piece of faulty logic made owners complain too much.
Or because all of the automotive engineers on Earth suddenly got stupid.
Or because all of the automotive engineers on Earth suddenly got stupid.
#17
I haven't ever been fortunate enough to actually see an OBD-II vehicle set an O2 code before driver annoyance has reached critical levels. The early 1980's logic that was capable of detecting the normal end of life (falsely rich signal) condition got removed because a tangentially related piece of faulty logic made owners complain too much.
Or because all of the automotive engineers on Earth suddenly got stupid.
Or because all of the automotive engineers on Earth suddenly got stupid.
#18
#19
Parts are designed to last just a bit beyond the warranty period. Sometimes the manufacturing process goofs, and they fail sooner.
#20
It's kinda the opposite of that. The sensor technology improved to the point that they quit failing during the warranty period. That made the whole matter into a case of doan wanna, doan hafta, not gonna.
I used to have enormous good fun watching Hewlett-Packard's quality removal engineers squirm when their changes broke my junk. Their changes always broke my junk because I knew better than to try to sneak anything more than the lowest acceptable quality into the junk in the first place, but they still always made them. I don't really think they knew what they were doing and just changed stuff randomly because no one else knew what they were doing, either, and changing stuff kept the paychecks coming.
I used to have enormous good fun watching Hewlett-Packard's quality removal engineers squirm when their changes broke my junk. Their changes always broke my junk because I knew better than to try to sneak anything more than the lowest acceptable quality into the junk in the first place, but they still always made them. I don't really think they knew what they were doing and just changed stuff randomly because no one else knew what they were doing, either, and changing stuff kept the paychecks coming.