Quote:
uphill previously said:
I have a scanguage mounted to the FJ that provides the same diagnostics that the dealership would use and it shows "no message" which means that things are running OK as far as the rig is concerned. I suspect it might have something to do with a bad sensor. The lights popped on when I turned it on this morning, I've run it about 60 miles since then - no problem, and according to the scanguage, still no problem.
|
This is incorrect - the ScanGauge does not have the same capability as the Star Sytem testers the dealerships use.
A couple of misconceptions to clear up for everyone:
The scangauge can read OBD II codes stored in the ECU's memory, and clear some of them. It cannot read all codes - manufacturer-specific codes are not accessed through the OBD II system, but the dealer's scan tool can access and analyze them. The dealer's system is interfaced with direct connection to Toyota corporate computers, which provide scenerios of likely causes based on shop data, as well as procedures for finding the vehicle-specific cause, and live data capture to check and test sensor operation directly. The scangauge cannot do any of these things.
THere are different types of codes stored in the ECU - intermittant, which clear out on their own after so many engine cycles if the triggering event does not repeat, and memory codes that will not passively clear - they require an operator reset.
The Skid control / ABS system indicators do not go through the OBD II system, and are not accessed or cleared by the ScanGauge - these are triggered by sensors connected to the ABS system, 4WD computer, Differential computer, transfer case sensors, wheel sensors, etc... If triggered by a random event, restarting the vehicle, or engaging 4wd / 4wd low and back to 2wd, and then restarting the vehicle will reset those lights (the system goes through a self-check of the sensors every time you start the car, so if they stay on, the triggering event is still occurring).
This is why the scangauge will not show any code or problem, even though the dash indicators remain lit. To properly analyze the problem, you need a more sophisticated vehicle diagnostic system, and an operator qualified to understand the information it is capable of displaying.
I have worked as a mechanic for more years than most on this forum have been around, and the number of times I have seen a rat eat through wiring are very few - it does happen, but not frequently, and usually in vehicles that have been sitting for a substantial amount of time unused. And there have been a many instances of those same indicator lights lighting on FJCs, and it is much more reasonable to believe a sensor is at fault than a rat ate the wires. The dealer should show you the chewed wire harness - or I would insist they repair it under warranty (if still in warranty). Rats leave plenty of droppings, nesting materials, etc., so you'd see evidence of rats long before you'd find chewed wires. They should have no problem isolating the sensor / wire circuit at fault IF they spend the time to properly check / test the system.
2007 TITANIUM SILVER FJ CRUISER 6MT
Boss
/ WPOK492 
Linear Mode
