Announcement

Collapse

New topic template

Every new topic with dump file MUST contain those paragraphs
CAR BRAND NAME:
MODEL:
PART NUMBER:
CPU / EEPROM:
+ at least 4 pictures: of case with sticker, both sides of PCB and zoomed CPU (do NOT resize pictures!)
Subject should looks like "CAR BRAND, MODEL, YEAR, PART NUMBER" (for example: "Mazda 3 2015 BHS2-57K30A")
See more
See less

SUBARU 98221FJ241 become unresposive with Clear Crash By OBD

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • SUBARU 98221FJ241 become unresposive with Clear Crash By OBD

    Hello,

    I’d like to verify the accuracy of the 'Clear by OBD' information for this module. The app indicates it can be done via OBD, but in practice, the module becomes unresponsive. I found that I had to remove the module, solder a 10k resistor, and write back to it just to regain access.

    Could you please confirm if the OBD method is fully supported for this part number?"
    Screenshot 2026-02-22 233703.png
    After successfully writing the bin file back to the module and restoring communication, a new error code has emerged.

    BEFORE (ON OBD):
    ================================================== =========
    Processing... 21.02.2026 13.41.31
    Checking new version... ok
    Connection to server... ok
    Checking security... ok
    Start Manual Mode.
    Subaru 98221FJ241 (on bench with RES10K) H8SX1725
    --------------------------------------------------------
    DC power supply voltage +12.59V
    Turn on 12V on the adapter... ok
    Set ServiceMode... ok
    Read ECU Serial Number...
    98221FJ241
    Read Errors...
    B11F9:28-00 - !!! SIDE IMPACT DEPLOYMENT !!!
    B1831:28-00 - OPEN IN CURTAIN AIRBAG RH SQUIB CIRCUIT

    --------------------------------------------------------
    DC power supply voltage +12.63V
    Turn on 12V on the adapter... ok
    Set ServiceMode... ok
    Read ECU Serial Number...
    98221FJ241
    Enter security... ok
    Creating backup "Subaru 98221FJ241 H8SX1725 21.02.2026 13.42.26.bin" ok
    Reading EEPROM... ok

    Warning!!!
    TURN OFF IGNITION OR 12V POWER SUPPLY FROM AIRBAG, WAIT 30 SECONDS AND TURN ON

    Saved file: C:\SUBARUCROSSTRECK before2013.bin
    --------------------------------------------------------
    DC power supply voltage +12.64V
    Turn on 12V on the adapter... ok
    Set ServiceMode... ok
    Enter security... ok
    Erase Flash... ok


    AFTER (OBD) --------------------------------------------------------------------------------------------------------------------------------------> BECOME UNRESPONSIVE ON OBD !!!!
    --------------------------------------------------------
    DC power supply voltage +12.46V
    Turn on 12V on the adapter... ok
    Set ServiceMode... failed
    No answer from AirBag, check Airbag connection and power supply
    --------------------------------------------------------


    AFTER ON BENCH
    ================================================== =========
    Processing... 22.02.2026 23.10.47
    Checking new version... ok
    Connection to server... ok
    Checking security... ok
    Start Manual Mode.
    Subaru 98221FJ241 (on bench with RES10K) H8SX1725
    Opened file: C:\SUBARUCROSSTRECK before2013.bin
    --------------------------------------------------------
    DC power supply voltage +11.86V
    Turn on 12V on the adapter... ok
    Set ServiceMode... ok
    Load Bootloader... ok
    Enter Bootloader... ok
    Erase EEPROM... ok
    Set ServiceMode... ok
    Prepare write... ok
    Writing EEPROM... ok

    Warning!!!
    TURN OFF IGNITION OR 12V POWER SUPPLY FROM AIRBAG, WAIT 30 SECONDS AND TURN ON

    --------------------------------------------------------
    DC power supply voltage +11.86V
    Turn on 12V on the adapter... ok
    Set ServiceMode... ok
    Read ECU Serial Number...
    98221FJ241
    Read Errors...
    B1199:2E-00 - !!! AIRBAG ECU MALFUNCTION !!!
    B1801:2E-00 - OPEN IN DRIVER'S AIRBAG
    B1811:2E-00 - OPEN IN DRIVER'S AIRBAG DUAL STAGE - 2ND STEP
    B1806:2E-00 - OPEN IN PASSENGER'S AIRBAG
    B1816:2E-00 - OPEN IN PASSENGER'S AIRBAG DUAL STAGE - 2ND STEP
    B1901:2E-00 - OPEN IN FRONT P/T RH
    B1906:2E-00 - OPEN IN FRONT P/T LH
    B1861:2E-00 - OPEN IN DRIVER S KNEE AIRBAG
    B1821:2E-00 - OPEN IN SIDE AIRBAG RH
    B1826:2E-00 - OPEN IN SIDE AIRBAG LH
    B1831:2E-00 - OPEN IN CURTAIN AIRBAG RH SQUIB CIRCUIT
    B1836:2E-00 - OPEN IN CURTAIN AIRBAG LH SQUIB CIRCUIT
    B19F1:2E-00 - OPEN IN FRONT P/T 2 RH
    B1618:2E-00 - FRONT SUB SENSOR LH INITIALIZATION ERROR
    B1677:2E-00 - SATELLITE SAFING SENSOR INITIALIZATION INCOMPLETE
    B1623:2E-00 - SIDE AIRBAG SENSOR RH INITIALIZATION ERROR
    B1628:2E-00 - SIDE AIRBAG SENSOR LH INITIALIZATION ERROR
    B1660:2E-00 - PASSENGER S AIRBAG ON INDICATOR FAILURE
    B16F0:2E-00 - PASSENGER S AIRBAG OFF INDICATOR FAILURE
    B1650:2E-D7 - OCCUPANT DETECTION SYSTEM MALFUNCTION



    After recovering the module on the bench using the 10k resistor and writing the bin file, I am now seeing a new error code that was not present originally:
    • B1199:2E-00 - !!! AIRBAG ECU MALFUNCTION !!!

    Since this is a customer's module, I need to confirm: is this code triggered because the 'Clear' function in the app didn't calculate the checksum correctly for this specific firmware version? Or is there a specific 'Repair' function I should run to clear the internal controller state after an unsuccessful OBD attempt?

    Attached are the logs showing the 'Before' state (Crash data) and the 'After' state (Internal Malfunction).


    Last edited by Mcb; 23.02.2026, 08:50.

  • #2
    Read Errors...
    B11F9:28-00 - !!! SIDE IMPACT DEPLOYMENT !!!
    B1831:28-00 - OPEN IN CURTAIN AIRBAG RH SQUIB CIRCUIT

    Was this diagnostic on the bench?

    Comment


    • #3
      Yes that diagnostic done on car with one,
      Then I read the flash on obd
      Then I saved the file to PC
      Then I erased flash on obd
      Then I try to read error codes on obd it failed no communication was possible on obd after I erased the flash
      Then we removed the SRS module soldered 10k and removed 0 ohm
      I write back the saved bin file to the module on bench
      I read the error codes on bench and I saw module malfunction error etc
      I reset the module by power cycling
      Read the dtc again on bench , but airbag module malfunction dtc was still there

      Comment


      • #4
        This error indicates a hardware problem, carefully check the soldering points, clean the board and try Clear Crash by OBD again and Write Data.

        Comment

        We are open for you

        Collapse

        Mon - Fri
        10 AM - 6 PM


        Current time is:

        Latest Activity

        Collapse

        Working...
        X