1
View single post by sheltonfilms | |||||||||
Posted: Fri Jan 19th, 2018 01:30 pm |
|
||||||||
sheltonfilms Electronicals / Forscan Expert ![]() Joined: Fri Nov 24th, 2017
Posts: 125
Status:
Offline
Reputation: ![]() ![]() ![]() ![]() ![]() ![]() Reputation Points: $user_rep
![]() |
I've seen this before and it is usually caused by a sensor that won't pick up a speed change until like 5 mph. Some times it's the sensor sometimes it's dirty. What happens is one side of the vehicle sees like 3 mph when slowing down when the other sensor sees 0 mph. The sensor that shows 0 will start to show the correct speed once it goes fast enough and that is why you don't see a code. There should be PIDs in Forscan for all 3 sensors (FR, FL, and rear) pull them up and slowly come to a stop and slowly accelerate. I bet you will see some drops in the signal.
____________________ 2000 XLT 2.5L A/T 2WD Mods: Power Windows/Locks Mirrors using OEM harness and parts Explorer Sportrac White Face Cluster Explorer OHC and Auto-dim Mirror Auto Door Locks Full HID Projector Retrofit |
||||||||
|