Former User

Is code 17 thrown?

A better strategy is to dust off the multimeter and use it to pinpoint the problem.

Test the VSS signal wire for continuity between the VSS and cluster connectors.

Test the other two wires in the VSS connector for power and ground.

Dseriesish

I have an elm327 wifi reader and dash commander as an app for it I think there's a communication error because it's a jdm ecu??? Works fine in the wifeys Mazda 3 and my ecoboost f150 but can't read from that ecu??? So I do have a cel but I can't read the damn ecu p2004 came up on a palm reader and that's intake something stuck open but other than vtec not kicking unless hooked up to a switch which both solenoids click and it does kick in when I hit the switch and going fast enough you can hear it I was reading about faulty soldering but if that were the case then both clusters would be by chance faulty??? Didn't think so I tried hooking a drill up to the sensor with the car on and spinning it but I still got no reading on the cluster is there something between that could be the problem?

Dseriesish

I've read that vss issues will cause vtec to not engage I haven't checked continuity in the wires yet but I thought I would source out sensor or component malfunction first junkyard is easy to pick stuff out of and I'm not great with metering I'm confident with mechanical but electro magic is something I need help on love my honda but they're quite fun for troubleshooting

Dseriesish

That's pretty much where I'm at

Dseriesish

Dseriesish

Thanks I'll try it out I appreciate the input Ron and b20 is there anything between the sensor and cluster fuse or relay wise?

Former User

Pull the CEL code by jumping the service connector.

The VSS connector has 3 wires --> Blk/Yel = battery voltage; Blk = ground; Blu/Wht = signal to speedometer that pins to B11 in the cluster

tony_2018

Check continuity to from vss to ecu, then from vss to cluster. I have a feeling there could be corrosion on the vss plug.