Hello guys,

i bought a 2008 Fiesta Titanium Mk 7 with the airbag warning light on. The airbag light would go off occasionally but only for a couple of mins then back on. Iv had the seats out and checked/cleaned all connections to no avail. The diagnostic cpu shows code B10FD Drivers side peripheral accelerator sensor - internal fault - current. I purchased another sensor off e bay fitted it and it seemed to be fixed. The car run on my drive for 30 mins with no light which it has never done since I bought it. I got in the car and the light came strait on. I stopped the engine, restarted and light off again. I drove the car for about 10 miles with no airbag light then went over pothole and the light came on. Now the light is on almost permanently again. Any ideas? Cheers Gareth

Is it a 3dr car? Connections under the seat due to moving back and forth maybe?

Its a five door. Iv checked all the seat connections and they are ok

Have you scanned for fault codes again?  If it's the same code, then there's likely to be a fault in the wiring to that crash sensor.

Hiya, ive got the same issue. I’ve brought a new sensor same, fault code same as yours B10FD any ideas, tomorrow I’m removing the seat to a closer look at the wiring, 2010 Ford fiesta zetec 

Need help with a wording i issue on my 3 door fiesta 2010 B10FD fault code,  change the sensor,  same,,, any ideas???

 

Many thanks

 

On 11/19/2022 at 5:51 PM, Aldridge Andy said:

Is it a 3dr car? Connections under the seat due to moving back and forth maybe?

Hi Andy, hopefully you’re still replying to questions, can you help at all with this issue? Thanks Mark

On 11/22/2022 at 10:14 AM, TomsFocus said:

Have you scanned for fault codes again?  If it's the same code, then there's likely to be a fault in the wiring to that crash sensor.

Hi Tom, replaced the sensor ,code B10HD came up one the old one , ordered a replacement same code ,airbag light still on! Any ideas?

Just now, Mark shipman said:

Hi Tom, replaced the sensor ,code B10FD came up one the old one , ordered a replacement same code ,airbag light still on! Any ideas?

 

2 hours ago, Mark shipman said:

Hi Andy, hopefully you’re still replying to questions,

What are you using to read the DTC's ?

Have you checked the connector under the drivers seat ?

11 hours ago, Mark shipman said:

Hi Tom, replaced the sensor ,code B10HD came up one the old one , ordered a replacement same code ,airbag light still on! Any ideas?

If it's the same code, then there's likely to be a fault in the wiring to that crash sensor.

13 hours ago, unofix said:

What are you using to read the DTC's ?

Have you checked the connector under the drivers seat ?

I’ve just had the drivers seat/seatbelt and seat module out and tested the wiring to all, all getting continuity, so I’m happy that the plugs are all good. Could it be the main air bag module faulty? Thanks

4 hours ago, TomsFocus said:

If it's the same code, then there's likely to be a fault in the wiring to that crash sensor.

I’ve brought a second hand sensor with a plug so I’ve tested resistance through this and same with the old module, traced the wiring back to the foot well and tested the plug by continuity back down the Lium all seems good. I’m happy that the sensor wiring is all good,, anything else that you might think?

2 minutes ago, Mark shipman said:

I’ve brought a second hand sensor with a plug

What is the part number of the sensor please?

12 minutes ago, Mark shipman said:

I’ve brought a second hand sensor with a plug so I’ve tested resistance through this and same with the old module, traced the wiring back to the foot well and tested the plug by continuity back down the Lium all seems good. I’m happy that the sensor wiring is all good,, anything else that you might think?

If it's not the sensor or the wiring then that only leaves an internal module fault.  Unless this code covers more than one sensor that we aren't aware of.

If the sensor is confirmed as correct by Unofix then I might be inclined to send the module away for testing.

3 hours ago, unofix said:

What is the part number of the sensor please?

7 hours ago, Mark shipman said:

I’ve just had the drivers seat/seatbelt and seat module out and tested the wiring to all, all getting continuity, so I’m happy that the plugs are all good. Could it be the main air bag module faulty? Thanks

 

7 hours ago, TomsFocus said:

If it's not the sensor or the wiring then that only leaves an internal module fault.  Unless this code covers more than one sensor that we aren't aware of.

If the sensor is confirmed as correct by Unofix then I might be inclined to send the module away for testing.

 

7 hours ago, unofix said:

What is the part number of the sensor please?

Just had a thought, my obd reader has only said drivers side peripheral acceleration sensor. I’ve tested the side ones and see resistance in both. Just checked the one under the bonnet nothing! Check the wiring for continuity one side of the plug works, and the other wire I cannot get a test. Can I assume it could be this one not the B pillar like I’ve originally thought? Thanks Mark

7186-0559-80

Fiesta crash sensor 2008 - 2012

As far as I know this is not an item that the user can reset once it has detected a crash.

 

13 hours ago, unofix said:

7186-0559-80

Fiesta crash sensor 2008 - 2012

As far as I know this is not an item that the user can reset once it has detected a crash.

 

Hi again, would you expect to see resistance in the front crash sensor , as I’ve tested it and it came to show open circuit unlike the B pillar sensors which shows resistance! Could the front sensor be called drivers peripheral acceleration sensor?? Thanks

2 hours ago, Mark shipman said:

would you expect to see resistance in the front crash sensor

Yes. At a pure guess I'd think 330 Ohms but I stress that is a guess.

What are you using to read the DTC's ? 🤔

1 hour ago, unofix said:

Yes. At a pure guess I'd think 330 Ohms but I stress that is a guess.

What are you using to read the DTC's ? 🤔

Ancel fd700

4 hours ago, Mark shipman said:

Ancel fd700

That would explain the odd .....

7 hours ago, Mark shipman said:

drivers peripheral acceleration sensor

You're only seeing half the picture using Ancel. To be able to see and read all of the Ford specific DTC's you need to be using FORScan.

On 4/7/2024 at 8:59 PM, unofix said:

FORScan (for use with Windows Laptop) : https://forscan.org/download.html

It's what many Ford owners use including some Ford technicians.

• vLinker FS, cable for laptop: https://www.amazon.co.uk/Vgate-vLinker-Adapter-FORScan-MS-CAN/dp/B0952P4MLP

OR

• OBDLINK EX, cable for laptop: https://www.amazon.co.uk/OBDLINK-EX-FORScan-OBD-Adapter/dp/B081VQVD3F/ref=sr_1_5

For diagnostic use only:

• vLinker FD, for android phone: https://www.amazon.co.uk/Vgate-Bluetooth-vLinker-Scanner-Diagnostic/dp/B08H82WC8L
• vLinker FD+, for iPhone: https://www.amazon.co.uk/Vgate-Bluetooth-vLinker-Scanner-Diagnostic/dp/B08H8JHWP2

 

If the price of a crash sensor is less than the price of a Forscan cable, it still might be worth trying that anyway.  I do have vague memories of SRS codes not being particularly clear in the past.  I'm not sure Forscan will show anything better in this case.

Hi Tom, I’ve got to the bottom of this issue, I’ve re traced the wiring back to the air bag module and that’s all ok, it was the air bag module in the end throwing up a fault on the drivers rear crash sensor!! That’s for all that have shared their assistance!!