Airbag Light After a Crash: How SRS Reset Really Works
Two Different Jobs Both Called "Airbag Reset"
A car arrives with the airbag lamp on. One workshop quotes twenty minutes and a scan; another quotes a bench session and a module out of the car. Both are describing "airbag reset" and they are not the same operation at all. Getting this distinction right is the difference between a repair that stays fixed and a comeback that ends with a customer asking why the light came back on the motorway.
The first job is diagnostic. A scanner talks to the SRS module over the diagnostic socket, reads the stored trouble codes, shows you which squib circuit, sensor or seat-belt pretensioner the module is unhappy about, and clears the code once the fault is genuinely repaired. This is ordinary diagnostics and any capable scanner with SRS coverage does it.
The second job is data. When a car is involved in an impact, the airbag module writes a crash record into its own memory — a latched flag plus stored impact data. That record is not a trouble code in the ordinary sense: clearing codes will not remove it, and the module will keep the lamp on until the record itself is reset. On most cars that means reading the module's microcontroller or EEPROM on the bench, clearing the crash area, correcting the checksum, and writing it back. This is what the devices in this article actually sell.
What Is Actually Stored Inside an Airbag Module
An airbag ECU is a small computer with a pyrotechnic licence. Inside you will find a microcontroller — Renesas SRS parts, Infineon XC236x, Tricore TC1766/TC1767/TC1796/TC1797, and on newer platforms RH850 derivatives such as the R7F701407 — plus serial EEPROM for calibration and event data, often an M35080 / 35080V6 class device. Alongside the crash record the module holds vehicle coding, sensor calibration, deployment counters and, on some platforms, VIN and component protection data.
That mixture explains why "reset" is rarely one button on the bench. If the tool cannot read the specific microcontroller family in front of you, it cannot touch the crash area; if it reads the chip but not the checksum scheme, the module will reject the write and stay latched; and if the module is coded to the car, a careless write can leave you with a module that no longer talks to the vehicle at all. Coverage lists matter more than screen size.
Family 1 — One-Click Pin-Port Reset Tools
The newest category removes most of the disassembly. The CGDI CG70 Airbag Reset Tool (product code OS3705, $379 from a $439 list) is built around exactly this idea: no opening the module cover, no soldering, no lifting the chip. You connect to the module's pin port, the tool identifies the airbag module, reads its information, and clears the fault record with a single key press.
That workflow is a genuine time saving in a body shop, where a module may need resetting the same day the car comes off the jig. The trade-off is breadth: a one-click tool is only as good as its model list, so check that your regular traffic — the three or four module families you actually see — is covered before buying. For a workshop that does repeat volume on a narrow set of brands, it is the cheapest route from "light on" to "light off".
Family 2 — Bench Programmers With Real ECU Coverage
When the module is not on the list, or when the job is a mixed diet of SRS, mileage and chip work, the general-purpose bench programmers earn their price. Three current options cover the range.
The CG100 PROG III Full Version ($449, list $589) is the workhorse: software V6.0.1.0, all Renesas SRS functions plus Infineon XC236x FLASH, and read/write of secured and non-secured Tricore TC1766, TC1767, TC1796 and TC1797 EEPROM over CAN. It also carries built-in calculators for mileage, DPF, ECU system time and ISN, and lets you edit the CRC area of the EEPROM — the detail that decides whether a cleared module boots or bricks. A separate listing for the V5.0.3.0 CG100 PROG III ($479) exists for buyers who need that specific software generation.
The CGDI CG100X ($739, list $819) is the same idea pushed onto newer silicon: MQB platforms and RH850 R7F701407 support, coverage quoted at around 90% of models and modules across American, German, French, European, Korean, Japanese and Italian lines, and the bundle includes the Pro V2 and D1 MQB adapters. If your work includes late-model European clusters as well as SRS, this is the one that will not run out of road next year.
The OBDSTAR P50 Airbag Reset Tool ($549) takes a different route: a dedicated SRS bench tool with one-click reset across 86 brands and more than 11,600 ECU part numbers, one year of free updates, and SAS reset alongside the airbag work. The CAN FD adapter in this bundle is what unlocks bench reset on Hyundai/Kia TC2xxx and Toyota R7F7-series modules — cars that older CAN-only reset tools simply cannot address.
At the bottom of the price ladder sits the Iprog+ programmer ($49 for the base model, with option tiers at +$10, +$18 and +$55). It is a universal EEPROM/MCU tool with IMMO, mileage and airbag functions, coverage to 2023, and support for Atmel, Fujitsu, Microchip, Motorola and NEC V850 families. It is not a one-click SRS tool and it expects you to know which chip you are attacking — but as a second bench device for older modules it costs less than most single adapters.
Adapters Decide Your Real Coverage
Two accessories are worth understanding before you order, because they are the difference between "supported" and "supported with a cable you do not have".
The CG100 ATMEGA adapter ($119) adds 35080 / 35160 / DQW080 / DQW160 / 35080V6 and VP EEPROMs, parallel FLASH with anti-theft cancellation, 8-pin chips and ATMEGA reuse to a CG100 PROG III. It cannot be used on its own — it is a companion board, and the listing says so plainly.
The Special BDM+4 adapter ($69.99) is the Renesas BDM route for CG100 users: any CG100 software above version 3.0 requires this newer adapter to update. Note that this line is currently showing out of stock on our listing — if you need it in a hurry, ask us before you plan the job around it.
Family 3 — Scanners That Clear Codes, Not Crash Data
It is worth being blunt about where a diagnostic scanner stops. The Autel MaxiCheck Pro ($185) is a specialist service tool for body shops: ABS, SRS, EPB, SAS and oil-light resets, free lifetime online updates and a one-year warranty, with language options across the main European markets. It will read SRS codes, show you the live data behind them, and clear a code once the underlying fault is repaired.
What it will not do is rewrite the crash record. If the module is latched by an impact event, a scanner will report codes, offer to erase them, and watch them return — because the memory that produced them has not changed. That is not a limitation of this particular tool; it is true of the whole diagnostic layer. Every workshop needs both: a scanner to find out what happened, and a bench tool to clear the record when the answer is "crash data".
The Volkswagen Case, and a Tool Built Only for It
Some modules are common enough to justify a dedicated device. The Yanhua Airbag Resetting and Anti-Theft Code Reader 2-in-1 ($308.99) covers Volkswagen vehicles and does two jobs that often arrive together in the same car: resetting the airbag controller and reading the anti-theft code so a replacement radio or cluster can be matched. The listing is equally clear about the limit — this device cannot be updated, so treat it as a fixed-coverage tool for the VW work you already do, not as a platform for the future.
The Workflow That Avoids Comebacks
Tool choice gets the attention; process gets the results. The sequence below is what keeps a reset from turning into a second visit.
| Step | What you do | Why it matters |
|---|---|---|
| 1 | Scan every system, not just SRS, and save the before-scan | Impact codes usually travel with ABS, restraint sensors and pretensioner faults |
| 2 | Record the SRS module part number and read the chip marking | Decides whether your tool's list actually covers this module |
| 3 | Check the OEM procedure for that module | Some manufacturers require replacement after deployment, not reset |
| 4 | Read and archive the original dump before writing anything | The only rollback you will have if the write goes wrong |
| 5 | Clear the crash area and correct the checksum/CRC | Skip the CRC and the module rejects the file or fails to boot |
| 6 | Refit, clear codes, cycle the ignition, re-scan | Confirms the lamp logic and the readiness state, not just the code list |
| 7 | Replace every deployed component — bags, pretensioners, sensors | A reset module cannot refill a fired inflator |
Step 4 is the one people skip. A dump taken before the write costs two minutes and has saved more modules than any feature on a spec sheet. If your bench work is going to grow, treat archiving as part of the job, exactly as you would log a mileage correction before touching a cluster — the same discipline we describe in mileage correction tools.
Safety, Liability and the One Thing You Must Not Do
Airbags are pyrotechnic devices. They are also the only system in the car designed to fire without warning, which is why OEM procedures — not tool menus — decide what may be reused. Clearing crash data is legitimate repair work on an undamaged module; it is not a way to put a car back on the road with fired inflators, missing sensors or a bypassed lamp.
Do not fit simulators or resistors to silence an SRS lamp, do not reset a module whose housing or connector is damaged, and do not return a car with a lamp that has been "fixed" by clearing codes on a fault that is still present. Beyond the obvious safety argument, a restraint system that has been tampered with is a liability that follows the workshop, not the tool seller.
Before you condemn a module, prove the circuit. A large share of "airbag module faulty" diagnoses are a chafed loom, a corroded connector or a sensor that has lost its ground reference — and no reset tool will fix a wiring fault. The ten-minute test sequence in circuit testing with a power probe, meter and scope is the right pre-check, and it is cheaper than a module.
Which One Should You Buy
| If your work is… | Buy | Price |
|---|---|---|
| Repeat SRS resets on a known brand list, fastest turnaround | CGDI CG70 one-click pin-port tool | $379 |
| SRS plus late Hyundai/Kia TC2xxx and Toyota R7F7 bench work | OBDSTAR P50 with CAN FD adapter | $549 |
| Mixed bench work: SRS, clusters, EEPROM, checksums | CG100 PROG III Full Version | $449 |
| Newest European platforms, MQB and RH850 modules | CGDI CG100X with Pro V2 and D1 adapters | $739 |
| Body-shop service functions and SRS code diagnosis | Autel MaxiCheck Pro | $185 |
| VW-only airbag reset plus radio/cluster anti-theft codes | Yanhua 2-in-1 | $308.99 |
Two combinations cover most small workshops better than one expensive device: a scanner for diagnosis plus one crash-data tool for the modules you see weekly. Add adapters only when a job actually requires them — the ATMEGA and BDM+4 boards exist to extend a CG100, not to replace it. If you are new to bench work in general, read OBD vs bench vs boot first: the access routes, the power-supply discipline and the backup habits are the same, whatever module is on the bench.
Quick Answers
Can a diagnostic scanner clear a crash record?
No. A scanner clears diagnostic trouble codes. A crash record is data written into the module's own memory during an impact, and it has to be reset on the bench by reading and rewriting that memory.
Does resetting bring a deployed airbag back?
No. Reset restores the controller. Every fired inflator, pretensioner and impacted sensor is a replacement part, and the OEM procedure for the vehicle decides what may be reused.
Why did the light come back after a reset?
Usually one of three reasons: the original fault was never repaired, the checksum was not corrected so the module rejected the file, or a second module in the restraint chain still holds its own crash record.
Do I need internet access on the bench?
It depends on the tool. The CG70 and P50 workflows are built around on-device model lists and updates; CG100-family tools are updated from a PC. Check the update policy of the specific listing before you buy, since free-update periods differ between products.
All of the devices above are stocked in our car diagnostic tool and ECU chip tuning categories, and the CGDI and OBDSTAR lines are listed together under original brands. If you are unsure which module family your next job uses, send us the part number and the chip marking — that is a two-minute question with a much cheaper answer than a wrong tool.