When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
Well i removed all of the grounds, cleaned them up and re-installed them. Same problem!! I then cleaned the sensor on the rear bell housing with contact cleaner and still the same problem...... I don't get it, i guess im going to just replace the sensor and see if that fixes it. I don't know what else to do. I don't have access to an accelscope so i cant test the sensor properly. Does anyone know of any other suggestions????
So I finally got around to revisiting this issue I've had with AE not recognizing my vehicle speed. On Tuesday, I pulled the vehicle speed sensor from the differential, cleaned it up, ohmed it out and measured about 2000 ohms (seemed about right for that sensor) and then reinstalled it. No dice. I cleaned up the ground. No change. I then ordered a new F85Z-9E731-AB / DY1123 speed sensor.
I installed the new sensor tonight, took the truck out for a spin and...AE still recorded 0.1 MPH. Hmmm.... I noticed that when the truck was in motion, I got 0.1 MPH and when the truck was stopped, it went back to 0.0 MPH...something I had previously overlooked. It seemed like AE has some kind of multiplier issue...
I selected the MPH on the Live Data Meter. I then scrolled all the way down and selected Configure Active Sensor. The Vehicle Speed Configuration window opened and I then selected the Scale Value which had been set to 1. Through a lot of trial and error, I came up with 254 as the value that most closely approximated the speedometer on my dash.
So at least this issue is somewhat solved. It's troubling though that Bill and AE ignored our reports and blew at least 4 of us off regarding this issue...and it's their fault. Who knew we had to come up with our own scaling to derive the correct vehicle speed? Makes me wonder what other PIDs are incorrectly scaled...
Our friend Optimator really dug in to find this one. He used everything he learned to ferret that out and this is in line with a suspicion I've had all along (I've seen the data, but I don't have a bad version to test). He deserves some green Chiclets, guys.
Optimator, check your "User CP" in the upper left corner for a few days.
256 would be a good multiplier in computer language. Another great find! I'll try to rep ya.
I had the Garmin GPS going...it updates kinda slow. You have intel of it being 256?...I'd be down with that...small difference though.
'Member when I sent you some data and I thought I had it eff'ed up...had speed max 1100mph? Yeah, that was before this scaling factor was applied as well.
Took me a couple hours today to record, and then re-record some data the tuner asked for. I couldn't find the "Gear Commanded" so I selected a bunch of things. Coast clutch, TC apply, shift solenoids 1-2-3...made data capture slower than Ideal, but hey, I thought the gear could be figured out from that...and it can, but they wanted "Gear Commanded by Module"...so out I went again. Data stream is a lot faster with few PID's being logged.
Rezvani's Latest Post-Apocalyptic Monster Is a Ford F-150 Raptor Underneath
Slideshow: Called the Fortress, the 850-horsepower pickup combines Raptor underpinnings with military-inspired features, survival equipment, and a starting price of $285,000.