B1620 on most KIA SRS Modules How to Fix?

**magnacin** · 7th October, 2021, 07:17 PM

Hello all,

I have been receiving some KIA modules (Sportage mostly) with B1620 Internal SRS fault. Almost 70% of the sportage modules have that failure.
PN are 95910 D9200 and 95910 D9270
Tried to clear them with cleaner and manually but that code does not go away. Even tried using previous tested solutions but the I get a lot of Unknown Error messages.
So basically my questions are:
a) Does anybody else have same issues as I do?
b) Does anybody else has a solution?

Its driving me crazy not being able to fix them.

Thanks for all help.

**BigPapaGotti** · 8th October, 2021, 01:55 AM

I'm battling this issue. I have a 2011 Kia Sorento and was able to clear the code by flashing the module via ODB with the module installed in the vehicle.

Hope this works for you.

**fuzz1** · 8th October, 2021, 02:24 AM

HiMaybe you should add the details of the flashing by obd. The tools you is used for that.

Thanks

**BigPapaGotti** · 8th October, 2021, 02:54 AM

Originally Posted by fuzz1

HiMaybe you should add the details of the flashing by obd. The tools you is used for that.

Thanks

I used AlexFlasher version 2.4.0a Beta version. This exe can be found within the "Mini Full" folder of AlexFlasher. The version found within the "SRS Full" folder did not work for me, for some reason. I suggest you try both versions and make sure you Read the EEPROM before you start writing to the EEPROM.

I used a tactrix open port 2.0 (not a clone) connected to my computer via USB. This was written directly via ODBII. I was successfull in using Windows 10 x64, Windows 7 x64 and Windows 7 x32.

Based on some searching I've done on this site Carprog is also able to write this BIN file directly to the module's EEPROM via ODB. I am not sure what version of carprog though. Unfortunately the version I have is apparently running an old firmware version as the ODB feature within the carprog application shows as "not activated" I think I can rework the carprog and flash a new version of firmware. From there I believe I would either need to use the A1 cable or the A1 Multi cable.

Hope this helps!

**datapage** · 8th October, 2021, 02:27 AM

yes common, 1:clear or reset ok,
2

on't use scanner to delete errors when too bad or bench mode.
3:Fix it.
4:B1620 always appears after clear dtc scan.

**magnacin** · 8th October, 2021, 06:10 PM

Thanks all for yur comments, it seems that it is a software issue within the module and it is individual for each module as I got help to clearing this one, I tried it on a different one and got error message. So basically they are a pain in the a...
Will keep trying to solve as they come.

**BigPapaGotti** · 8th October, 2021, 06:33 PM

Originally Posted by magnacin

Thanks all for yur comments, it seems that it is a software issue within the module and it is individual for each module as I got help to clearing this one, I tried it on a different one and got error message. So basically they are a pain in the a...
Will keep trying to solve as they come.

Can you please elaborate and say what you did to clear the module that you got help with?

What hardware and software are you using to communicate with the airbag module?

Are you working with these modules on the bench?

**magnacin** · 15th October, 2021, 04:21 PM

-BigPapaGotti,
module was cleared by other fellow that has helped me before. As for hardware and software used is CPT via JTAG and to read the modules on bench I use CAN Reader by CPT also.