99 E150 Airbag Help
#1
99 E150 Airbag Help
Hi all . long time reader fist time poster, I recently acquired a 1999 ford e150. A little background on the truck it has low miles but did sit for about a year before i got it. That being said the day i got it the air bag light was on solid, no blinks. It would come on then go off then come right back on solid. I did a bunch of work on the truck so i had the battery disconnected a few times during the work. After re connecting the battery the light stayed off for about a week then out of no where back on solid... Fast forward about a month to now i got in the truck and started the truck the air bag light began to flash i got code 32... I was told this is the clock spring if anyone can confirm. So i checked out the clock spring My horn works (no cruse control equipped)I removed the clockspring and it looks fine i couldnt find any stresses or breaks ect. with the horn working does that mean the clocksprings fine? my larger concerns is that it does not always flash sometimes it will just be solid. Before i start throwing money at this anyone have any ideas?, i was thinking maybe a ground wire? i checked the plugs under the seats they are plugged in and clean. anyone have anything i can test before i changed out part? thanks let me know Daniel
#2
I have somewhat of a similar situation but I know I caused this myself--a few of the seat base wires running to the seat belt pre-tensioning devices has been crushed, most likely loss of continuity which triggers the SRS warning lamp.
If your horn and cruise control works that's a fair guess thinking the clockspring is working properly. Retrace any work done inside the front seating area, if necessary pull the carpet or rubber pad up to check the seat base wiring. This is best done with seats removed, an easy thing to do. One T-55 Torx PLUS socket, an 18mm deep well and suitable ratchet---they're out inside of 10 minutes each.
If you find nothing there its possible whatever work was done affected the crash sensor wiring mounted up front. It could also be that sensor has failed for any number of reasons and needs replaced. I believe the only good way to full diagnose your SRS is finding someone with a scanner than can read those codes---the typical hand held types or free scans at AutoZone etc etc don't have that capability.
If your horn and cruise control works that's a fair guess thinking the clockspring is working properly. Retrace any work done inside the front seating area, if necessary pull the carpet or rubber pad up to check the seat base wiring. This is best done with seats removed, an easy thing to do. One T-55 Torx PLUS socket, an 18mm deep well and suitable ratchet---they're out inside of 10 minutes each.
If you find nothing there its possible whatever work was done affected the crash sensor wiring mounted up front. It could also be that sensor has failed for any number of reasons and needs replaced. I believe the only good way to full diagnose your SRS is finding someone with a scanner than can read those codes---the typical hand held types or free scans at AutoZone etc etc don't have that capability.
#3
Ok , well I pulled the passenger seat checked the wires with my tester using a closed loop the wires going to the passengers side are fine . No breaks same voltage through and through. Put the passenger side back together. Guess I'll have to look into the driver side now. I will say that with both seats disconnected I'm still getting code 32.
#4
This thread summarizes what I read about 3-2 code - https://www.ford-trucks.com/forums/1...ck-spring.html
- actual clockspring failure is most likely cause
- after airbag causes code, cruise if equipped then horn will fail
Sixto
93 E150 Chateau 5.8 191K miles
- actual clockspring failure is most likely cause
- after airbag causes code, cruise if equipped then horn will fail
Sixto
93 E150 Chateau 5.8 191K miles
#5
And here's one more link to an FTE thread about this same code: https://www.ford-trucks.com/forums/9...code-32-a.html
FWIW that code would be shown as B1932 with the proper scanner. Because most hand-held scanners cannot read the B series codes (along with quite a few more the ECM can generate) these aren't available on the less powerful scanners.
FWIW that code would be shown as B1932 with the proper scanner. Because most hand-held scanners cannot read the B series codes (along with quite a few more the ECM can generate) these aren't available on the less powerful scanners.
Thread
Thread Starter
Forum
Replies
Last Post
b4hntn
1978 - 1996 Big Bronco
13
02-07-2010 10:53 AM
jjknightstar
Aerostar
27
04-27-2004 12:28 AM
deanfulmer
1983 - 2012 Ranger & B-Series
3
01-25-2004 05:25 PM