So who wants their ECU's "Chromed"?

[Greg E]

I've never checked to see if there was a difference between the 96 and 99 speed sensors but you're the first one to report a CEL for it. I'd first double check your adaptor harness just to make absolutely sure that pin is in the right spot. I'm sorry I don't know which pin it is supposed to be off hand. I can check later.

[Monster Stealth]

I've never checked to see if there was a difference between the 96 and 99 speed sensors but you're the first one to report a CEL for it. I'd first double check your adaptor harness just to make absolutely sure that pin is in the right spot. I'm sorry I don't know which pin it is supposed to be off hand. I can check later.

I had that CEL, cleared it and went away. The speedometer works perfect though even when it was on.

[tfw a-ok]

Yeah I cleared mine as well but it comes back it seems every other drive cycle. I also feel a flutter when it comes on. Interestingly, P0500 is not a valid code for '96 so something must be different. I'm guessing your car was not OBDII to begin with correct?

[Greg E]

I had that CEL, cleared it and went away. The speedometer works perfect though even when it was on.

The speedo sensor has 2 outputs. One goes to the ECU, the other to the gauge. Theres no connection between the gauge and the ecu. This is why I would like to verify if the speedo pin maybe wrong in your adaptor harness.

Can you guys also verify that logging speed in EVOscan matches your speedo?

[Greg E]

Yeah I cleared mine as well but it comes back it seems every other drive cycle. I also feel a flutter when it comes on. Interestingly, P0500 is not a valid code for '96 so something must be different. I'm guessing your car was not OBDII to begin with correct?

The 99 ROM uses different codes than the earlier gen cars and other Mitsubishis.

[Monster Stealth]

The speedo sensor has 2 outputs. One goes to the ECU, the other to the gauge. Theres no connection between the gauge and the ecu. This is why I would like to verify if the speedo pin maybe wrong in your adaptor harness.

Can you guys also verify that logging speed in EVOscan matches your speedo?

I verified the connection at my harness before clearing the CEL, I will do some logs and verify they match tonight.

Edit: Looking back at some logs where I logged speed, I calculated what speed I should have been going based off gear ratio and tire OD. It looks like my logs are typically with in 2%-3% with only a couple instances differentiating by 7.5%. I never have checked but I am pretty sure I still have the original speedometer gear which is known to be off.

[Monster Stealth]

Yeah I cleared mine as well but it comes back it seems every other drive cycle. I also feel a flutter when it comes on. Interestingly, P0500 is not a valid code for '96 so something must be different. I'm guessing your car was not OBDII to begin with correct?

Correct, 93 OBD1

[tfw a-ok]

The 99 ROM uses different codes than the earlier gen cars and other Mitsubishis.

OK - I was not aware of this, thanks.

[Jeff V.]

The 99 ROM uses different codes than the earlier gen cars and other Mitsubishis.

Umm...OBD2 is a standard. Any P0xxx code since 1996 should use the same codes per SAE J1979. I have the 96 Stealth manual, and the codes listed are the same as the ones in the 99 3K book.

Proprietary codes are allowed, but they start with P1xxx.

[Greg E]

Umm...OBD2 is a standard. Any P0xxx code since 1996 should use the same codes per SAE J1979. I have the 96 Stealth manual, and the codes listed are the same as the ones in the 99 3K book.

Proprietary codes are allowed, but they start with P1xxx.

I was talking about the OBD1 cars...