cant believe it...we have been having a problem with the excursion for a few weeks now,...the glow plugs just arnt working...we took the ex into the stereo king and had them install a viper 560x remote start and alarm system (same sys. i have in my truck)...the next morning we tryed the remote start and it just started cranking away like crazy blowing massive amounts of white smoke...i eventually had to get in the ex and push the throttle while cranking...still blew some white smoke but it eventually started...we had to do this every morning...
took the rig into york automotive and had them check the uvc harness...replace the relay...did a pulse check....the computer came back reading that air temp was -40 deg. water temp read 203 deg. and then checked the pugs themselfs...
he told us that the curcuit from the ecu that goes to the relay was dead....told us that the alarm install was done wrong and shorted out the ecu....
last night i pulled out the dp chip and wated till this morning to use the remote start....guess what?...it fired up without a single problem...no white smoke...
for some reason jody's chip has blocked the glow plug usage in the ecu....once its warmed up it starts fine and runs great with the chip in...but it still throws 670 and 683 codes while the chip is in....
cant believe im gunna have to send both our f5 chips in to him...
took the rig into york automotive and had them check the uvc harness...replace the relay...did a pulse check....the computer came back reading that air temp was -40 deg. water temp read 203 deg. and then checked the pugs themselfs...
he told us that the curcuit from the ecu that goes to the relay was dead....told us that the alarm install was done wrong and shorted out the ecu....
last night i pulled out the dp chip and wated till this morning to use the remote start....guess what?...it fired up without a single problem...no white smoke...
for some reason jody's chip has blocked the glow plug usage in the ecu....once its warmed up it starts fine and runs great with the chip in...but it still throws 670 and 683 codes while the chip is in....
cant believe im gunna have to send both our f5 chips in to him...