Astra H 1.7 2005 13227920 Temic - 9S12DG128 error B1000

[RadovanPetkovic]

I need help.
I read Eprom from Temic - 9S12DG128 using a UPA programmer.
I used the TahoSoft calculator to clear the original file of crash data. When the ABS control panel was returned to the car, an error was reported among the other B1000
Since the operation failed, I calculated with all the calculators that I have the following files. Some are the same, some have a different first byte, and some are completely different.
TahoSoft and EVS calculator have exactly the same file *Which doesn't work well on a car*
NYO and AirBag Service Tool 9S12DG128 have the same file except the first byte 00 and FF
The AirBag Service Tool 9S12DG128E makes a completely different file from all calculators
WHICH FILE IS CORRECT?

[chiorbeq]

Try with this clear file.Can see crash file,clear file and flash file .

[RadovanPetkovic]

I tried all the listed files I got with the calculators. They all had different error codes and B1000. When I loaded the File that NYO made, I only got two errors for the passenger and driver tensioners. Delphi diagnostics sees only those errors may be real, I don't know because I'm not an auto electrician so I don't work with cars. The car owner took over the car due to road needs. I didn't read Flash because it wasn't written anywhere in my calculators, so I didn't use chiorbeq files. Thanks for the chiorbeq neighbor's files
The car should be inspected for real tensioner errors that have 7oms. If it is NYO has done a good job

It is necessary to check the pretensioners, but I did not have time for that.


The pictures show how the UPA programmer should be connected. Be sure to pin pin 30 off the PCB board. Only then will the UPA be able to read and write the contents of the file to the processor


Delphi diagnostics read the live data as in the picture. I think the job is just done to replace the pretensioners or emulate

[chiorbeq]

I don't use UPA when I read/write the micro,I use Smok.All files are tested!

[RadovanPetkovic]

I use Beeprog for correct reading / writing but it was easier for me now UPA. She did the right thing, too. The problem was in the Calculators that make four types of Crash data files .....

[robert1232]

press thanks+reputation=pass

raport here



I need help.
I read Eprom from Temic - 9S12DG128 using a UPA programmer.
I used the TahoSoft calculator to clear the original file of crash data. When the ABS control panel was returned to the car, an error was reported among the other B1000
Since the operation failed, I calculated with all the calculators that I have the following files. Some are the same, some have a different first byte, and some are completely different.
TahoSoft and EVS calculator have exactly the same file *Which doesn't work well on a car*
NYO and AirBag Service Tool 9S12DG128 have the same file except the first byte 00 and FF
The AirBag Service Tool 9S12DG128E makes a completely different file from all calculators
WHICH FILE IS CORRECT?

[RadovanPetkovic]

The car has not yet come to be repaired from the trip. The car mechanic ordered a used part. Next week we will know the details, my opinion is that the car will behave the same with the used part. Because the guarantor pretensioners are cracked ..... We will check everything then
The file from colleague Robert is almost the same as NYO makes except for one small piece as in the picture. Although it also means a lot because the first byte itself when FF instead of 00 does not work properly. The contact itself includes all four hazard warning lights. So the data crash has not been cleared.
With the NYO file, it only shows the error for the pretensioners, which the car mechanic did not check ....

[RadovanPetkovic]

The final solution of the case.
As I thought. I was right in everything I wrote so far.
They finally brought me a car. But with the replaced Airbeg electronics exchange. Usually the waste seller says the thing is 100% correct. So I lost half a day solving the problem. When I requested the original part, I deleted the crash data of the NYO program. Using the diagram, I discovered where the belt tensioners were connected, soldered to 2.2 ohm terminals in the Airbeg central electronic unit. To simulate belt tensioners.
The real repair is the replacement of new ones, but the car owner wanted it to be done like this, that is, to pretend that they are correct.
Everything was working properly, it no longer showed a DTC malfunction.
Note: When contacting the car if the HAZARD direction indicators are working and can be switched off by pressing the danger button twice. There are DATA ON COLLISION of vehicles. DTCs cannot be cleared even if live Delphi diagnosis data is correct. For all airbags it is 2.2om. DTCs that cannot be cleared are visible.
The NYO calculator works correctly for this model of central airbag unit. When the vehicle collision data is properly deleted from the central unit, the hazard direction indicators will no longer work when the car is contacted. This is a sign that everything is correct and that the DTC errors will be real, not those after the collision.

[RadovanPetkovic]

When you think you have learned something, you realize that you have never learned everything in this business. After successfully solving the problem, a new car with the same problem. And normally nothing is the same. I read the contents of Eprom from the 9S12DG128 with a UPA programmer, modified the file with a Nyo calculator and reloaded it. Deleted errors and tracking live data. I added 2.2 ohms where the airbag is missing. All values ​​were between 2-3 ohms looking at Delphi diagnostics. However, there was a constant error B0020. I disconnected all the existing connectors for the airbags in the airbeg control panel itself, installed 2.2 ohm resistors and there was no way I could undo the error B0020. "Passenger airbeg squib circuit (stage 2) Low resistance". I checked the resistance of all inputs / outputs from the central unit. No input / output has a small resistance (I disconnected everything). I suspected a software bug. For two days, I wrote various files, even the one that worked on my previous car. Error B0020 always remained.


I attached live data files and read errors to OPCOM and Delphi diagnostics.
Has anyone had similar problems and how did they solve them? Any help would be welcome.
Some things really drive a person crazy, you do one car relatively easily and you think you know the procedure, when after that the same car arrives with completely different problems .....