Honda Car Forum

'96 Civic LX w/manual transmission; 175K miles.

My speedometer/odometer suddenly become wildly erratic recently and
moments later the "Check Engine Light" illuminated. After researching
the
symtoms on this board and others, I replaced the vehicle speed sensor
but the problem remains.

I will read the OBD failure code tomorrow. Any and all other
suggestions would be appreciated.

rf_uw_engineer@yahoo.com wrote in news:1158799248.919327.78860
@e3g2000cwe.googlegroups.com:

> '96 Civic LX w/manual transmission; 175K miles.
>
> My speedometer/odometer suddenly become wildly erratic recently and
> moments later the "Check Engine Light" illuminated. After researching
> the
> symtoms on this board and others, I replaced the vehicle speed sensor
> but the problem remains.
>
> I will read the OBD failure code tomorrow. Any and all other
> suggestions would be appreciated.
>
>


You replaced the VSS *before* checking the error code? I think the cart and
the horse somehow got reversed from their proper order here.

The MIL is just an idiot light that can indicate over 200 specific errors.

--
TeGGeR®

The Unofficial Honda/Acura FAQ
www.tegger.com/hondafaq/

TeGGeR® wrote:

> You replaced the VSS *before* checking the error code? I think the cart and
> the horse somehow got reversed from their proper order here.
>
> The MIL is just an idiot light that can indicate over 200 specific errors.

You make a point, but consider that, based on logic as well as the
experiences of others, the symptoms strongly pointed to the VSS.
Further, the vast majority of MIL errors appear to bear no relation to
speedometer/odometer failures. Other than the VSS or its associated
wiring, it seems that the problem would have to lie within the ECM
itself.

rf_uw_engineer@yahoo.com wrote:
> TeGGeR® wrote:
>
>> You replaced the VSS *before* checking the error code? I think the cart and
>> the horse somehow got reversed from their proper order here.
>>
>> The MIL is just an idiot light that can indicate over 200 specific errors.
>
> You make a point, but consider that, based on logic as well as the
> experiences of others, the symptoms strongly pointed to the VSS.
> Further, the vast majority of MIL errors appear to bear no relation to
> speedometer/odometer failures. Other than the VSS or its associated
> wiring, it seems that the problem would have to lie within the ECM
> itself.
>
the question still is, why didn't you test or do any diagnostics? your
handle contains the word "engineer" after all. normally, if google
points towards the vss, that would make it the first thing to test.
once confirmed, you can replace. if not confirmed, revert to a more
methodical diagnosis route.

and you still need to check the mil code - there are no less than six
non vendor-specific codes relevant.

jim beam wrote:

> the question still is, why didn't you test or do any diagnostics? your
> handle contains the word "engineer" after all. normally, if google
> points towards the vss, that would make it the first thing to test.
> once confirmed, you can replace. if not confirmed, revert to a more
> methodical diagnosis route.
>
> and you still need to check the mil code - there are no less than six
> non vendor-specific codes relevant.

The only test I'm equipped to do on a VSS is to swap it with another
and observe whether the original problem remains. This is a legitimate
troubleshooting technique. And for a relatively low cost (lower than
what is typically charged for checking MIL codes), this is what I did.
And, as I said, I will have the MIL code scanned.

My original post wasn't seeking critiques of my troubleshooting
methodology. Rather, I am inquiring whether someone could venture a
possible explanation (other than the VSS, related wiring, or ECU) for
the cause of the problem I have described.

rf_uw_engineer@yahoo.com wrote:
> jim beam wrote:
>
>> the question still is, why didn't you test or do any diagnostics? your
>> handle contains the word "engineer" after all. normally, if google
>> points towards the vss, that would make it the first thing to test.
>> once confirmed, you can replace. if not confirmed, revert to a more
>> methodical diagnosis route.
>>
>> and you still need to check the mil code - there are no less than six
>> non vendor-specific codes relevant.
>
> The only test I'm equipped to do on a VSS is to swap it with another
> and observe whether the original problem remains. This is a legitimate
> troubleshooting technique. And for a relatively low cost (lower than
> what is typically charged for checking MIL codes), this is what I did.
> And, as I said, I will have the MIL code scanned.

replacement is a legit technique if it doesn't cost you anything and
there's no other convenient diagnostic route. since a code scan is FREE
at a number of auto spares retailers [you checked this group on google,
right?] i still don't see the excuse.

>
> My original post wasn't seeking critiques of my troubleshooting
> methodology. Rather, I am inquiring whether someone could venture a
> possible explanation (other than the VSS, related wiring, or ECU) for
> the cause of the problem I have described.
>
to which the answer is, "WHAT'S THE FREAKIN' CODE???" you come to a
news group wanting free advice, but you don't want to take that advice,
[which advice is by the way, exactly the first thing that would have
been done by a pro if you /had/ paid] but you also want your ass kissed
at the same time? something's strangely wrong with this picture.

rf_uw_engineer@yahoo.com wrote in news:1158810558.784842.315300
@b28g2000cwb.googlegroups.com:


>
> My original post wasn't seeking critiques of my troubleshooting
> methodology. Rather, I am inquiring whether someone could venture a
> possible explanation (other than the VSS, related wiring, or ECU) for
> the cause of the problem I have described.




NOBODY KNOWS until you GET THE CODE. Capisce?

If the code comes up VSS and yet it's not, then you have one issue. If the
code comes up something else, then you have another issue.




--
TeGGeR®

The Unofficial Honda/Acura FAQ
www.tegger.com/hondafaq/

My '96 Civic had the exact symptoms 2 years ago. It turned out to be a
short in the wiring harness where it is routed under the intake
manifold.

If I'm not mistaken, the problem has been reported by others in this
ng. It might be the source of your problem too.

My '96 Civic had the exact symptoms 2 years ago. It turned out to be a
short in the wiring harness where it is routed under the intake
manifold.

If I'm not mistaken, the problem has been reported by others in this
ng. It might be the source of your problem too.

R...@hotmail.com wrote:
> My '96 Civic had the exact symptoms 2 years ago. It turned out to be a
> short in the wiring harness where it is routed under the intake
> manifold.
>
> If I'm not mistaken, the problem has been reported by others in this
> ng. It might be the source of your problem too.

Extra Info:

http://groups.google.com/group/rec.a...5ce15b490ac1a7


http://downloads.hondatech.info/Auto...n/x99-029e.pdf