Opel antara 2007

[gobe]

Hello

please help me need dump opel antara 2007
eeprom 93c86
Cluster number 96673660
My dump is corrupt.
Best Regards

[ION CRISTI]

check this dump

[gobe]

Thanks
but no work

[ION CRISTI]

try with swap. the bin is good.

[pinkfloyd5eg]

Try this also >>>

[gobe]

Thank but no work

I tried to dump a lot but do not work
somebody help me
a good dump
Unfortunately, the show badly km
only three digits are displayed

This is the label on the dashboard

http://s13.postimage.org/lm89dat0n/DSC00426.jpghttp://www.digital-kaos.co.uk/forums/%3Ca%20href=%27http://postimage.org/image/rn5yadfmr/%27%20target=%27_blank%27%3E%3Cimg%20src=%27http://s13.postimage.org/rn5yadfmr/DSC00426.jpg%27%20border=%270%27%20alt=%22DSC00426 %22%20/%3E%3C/a%3E

[vasa]

maybe it will help you both have a 0 km

[gobe]

ok thanks
I will try

antaraOKM ver1 (http://www.digital-kaos.co.uk/forums/attachments/f174/102074d1328651483-opel-antara-2007-antaraokm-ver1.rar)

work perfect

I modified the right km
it works perfectly

Thank you everyone for your help

[erich.hai]

With Tool read the Dump?

[cliomanremi]

With Tool read the Dump?

Hi Everybody,
Thanks for this old thread that is giving me a lot of interesting data :).

Now, i would like to know if somebody can still help.
In fact, i have an Opel Antara from 2009 and my IPC (instrument panel control) or cluster (call it like you want) has been corrupted few months ago.
Since that time, i have only 8888 display for the odometer and also the "gearshift indicator (speed gear display)".
Moreover, i got some "option" that i don't have on the car (like "speed alarm above 120km/h, quite annoying OR also some "park assistance", only the symbol is lighted on).
Well, i asked to Opel to look at it, their conclusions, you have to change the IPC, almost 1500€...

I searched on internet, i found all those interesting links :
https://www.vauxhallownersnetwork.co.uk/index.php?threads/vauxhall-insignia-odometer-and-trip-disappeared.440216/page-5
http://astra.cinebob.net/opcom/
http://www.forum-opel.fr/forum/index.php?topic=29976.0
http://astra.cinebob.net/opcom/
https://www.youtube.com/watch?v=KTUoVKWr32A
https://www.youtube.com/watch?v=L-WSXbthTBs&t=904s
https://www.youtube.com/watch?v=EsP07FYGtYE
https://www.youtube.com/watch?v=grhJ4nARJkY
https://www.youtube.com/watch?v=g39yBTUN4fw
https://www.youtube.com/watch?v=QCBfwDx_2kw
https://www.swvaux.com/op-com-software-download-installation/
http://diagopcom.blogspot.com/2012/04/resume-du-tuto-opcom.html

http://www.obd2diy.fr/wholesale/opcom-op-com-2010-2014v-can-obd2-for-opel-firmware-v17.html

(http://www.obd2diy.fr/wholesale/opcom-op-com-2010-2014v-can-obd2-for-opel-firmware-v17.html)
Well, after looking at those links, i ordered the OPCOM with version V1.7.
I was able to access the IPC with OPCOM, not with VAUXCOM (even with different versions ; not able to know why).
After several tests and hours, i got the conclusion that there is something wrong with the IPC, proof with this picture showing bad data (ÿÿ instead of hex ok data) :
595205
Some menus remained grey (not available) on OPCOM as, unfortunately, variant programming.
I was only able to program the VIN.
And here it is interesting. I need 3 tries to be able to write the correct VIN !
First time, only 50% of the VIN was correctly flash in the EEPROM, read by OPCOM.
Second time, 25% more, third time, full OK, still read by OPCOM.
This is strange.

I opened the IPC after that, checked all solderings (i refreshed some in case of), check connectors, contacts and crimping, all seems ok.
No change on my issues after this.

I tried then to flash the OPCOM with older firmware to check if menu's behaviors remained the same.
Unfirtunately, the VAUXCOM software i tried, detected the old version, updated it by itself (flash from V1.39 to V1.45) and since, i cannot dial with my car anymore with OPCOM/VAUXCOM.
So, now i have to use my PICKIT3 from Microchip to solve my firmware issue (error message from OCFLASH to flash OPCOM firmware is "bootloader did not respond...either killed interface, empty pic or new protection!".
Not sure about what it means, but i think there was some kind of protection set by the VAUXCOM software regarding a too old and not allowed firmware version, my guess.
Anyway, once i will have fixed my OPCOM, i will try :
_ open again the IPC, check supply voltage of the EEPROM 93C86a
_ Check supply voltage also of the CAN tranceiver
_ THEN, depending on results, i will buy a new 93c86a, an universal EEPROM programmer and i will try to read the content of my OPEL 93c86 dump, save it, and compare it to your version
_ After understanding bytes meanings, i will try to modify it according to my real odometer values and also VIN number.

But i need your help for :
_ My Hardware reference is 96673661 (yours was 96673660) ; do you think it will change a lot the EEPROM structure ?
_ As i can access with OPCOM the IPC to get all data shown on the picture, do you think the issue could come from the CAN trasnceiver ?
=> Reasons of my thinking :
a) gearshift displays only 8888
b) odometer displays only 8888
c) i got several options not mounted on my car ; happened at same time than crashs of above displays
d) i can access with OPCOM to IPC data BUT NOT to "measuring blocks or variant programming options" ; they remains grey....
_ Or, do you think it could be ONLY the EEPROM which is corrupted ?
=> Reasons of my thinking :
a) ÿÿ read are equivalent to FF (for instance when you read the .bin file with Ultraedit)
b) Odometer and geasershift displays only 8888 (which makes think about having only FF data read)
c) I neede 3 tries to be able to flash the correct VIN number in the EEPROM from OPCOM
_ Or, do you think it could be only bad supply voltage, creating drop on the chip's supply lines, creating bad data exchange, and EEPROM corruption ?

Well, my last questions (sorry for all those questions) :
1) What was the behavior on your car with your corrupted EEPROM ? Same than me ?
2) Does anyone has the Dump file for 93c86 for an antara 2009 with IPC reference 96673661 ?

Thanks in advance guys. :)

[cliomanremi]

Hi,
For people who could face same issue (Instument Panel Control - IPC odometer displays only 888 ; same for gearshift position for the OPEL ANTARA 2008) in further time, here is the solution :
Issue is probably created thanks to a low battery voltage or a almost-dead battery.
Thanks to this, the EEPROM 93c86a soldered on main PCB of the IPC got corrupted.
When i say corrupted, it means that it lost the VIN number of the car, lost PN, SN and variant configuration.
At same time it happened to me, i got additional variant (not present on the car ; for instance, park assistance, speed overspeed alarm...).
Well, here is the process to follow :
_ Buy an universal programmer of EEPROM (example TL866CS)
_ Buy one or two 93C86a spare parts (needed only if you are unlucky and destroy parts)
_ Search on internet (soft dump russia site) for a dump file (copy of existing EEPROM for your car, search by PN) ; download it
_ Open the .bin downloaded and modify the VIN numver according to CARPASS data for your car
_ Remove the main connector on the IPC back
_ Lock your car
_ Teardown entirely the IPC
_ Unsolder the 93c86a from the IPC board (not possible to progamm it insitu)
_ Read the EEPROM content and save it as a backup
_ Flash and verify the EEPROM with the dump file .bin downloaded
_ Solder the EEPROM back to the board of the IPC
_ WAIT 1h30 min between the time you lock your car and the time you will unlock it !!
This is important as it seems there is a timing where the system doesn't look at the EEPROM content ; so new data will be taken ONLY after this timing.
_ Assemble again the IPC
_ Unlock the car
_ Connect the back connector again
_ Turn on the start key (just supply the system) ; You should get the new mileage (taken from the dump file)
N.B.: If you want to adapt your IPC to the real previous mileage, you can either take the information from the backup file you created at real beginning OR use Tachosoft to find what should be the values and position in the memory for your mileage)

On internet, some people said that doing a reset (blanking the VIN in the ECU) on the BCM and flashing it again (flashing only the VIN) is enough to fix such kind of issue. This is probably true on other Opel's cars, but not for the Antara.

Other comment, i tried to use OPCOM to do first tests. It was great to access to different ECUs and detect that data from the IPC were wrong (for instance written as ÿÿÿÿ which is FF in the memory). But then, as some menus were grey, i tried to downgrade the firmware (V1.7) to an older version(V1.39), and once i launched again OPCOM or VAUXCOM, the software detected the old version, flashed automatically the firmware to a version V1.45 and then, no possibility to communicate with the interface anymore. Even after changing the µcontroler PIC18F458 (from China ; which was a fake one) by a real from Microchip (flashed with V1.7 and others), it was not working anymore. Driver for the FTDI inside were ok, but well...after hours, i gave up.

So, don't hesitate if you need any support ; on my side, i spent dozen hours to fix my issue !
Thanks.

[Pali33]

hi all,
i have the sami problem, display show 8888888
i have tried the dumps from this thred, but nothing works, always the same problem, on display 888888 (i test the dash onthe bench)
have anybody goiod dump for my dash?
96673661, PB 061223 S:AB H:AB S:00012294

many thanks in advance

[bidu20]

hi all,
i have the sami problem, display show 8888888
i have tried the dumps from this thred, but nothing works, always the same problem, on display 888888 (i test the dash onthe bench)
have anybody goiod dump for my dash?
96673661, PB 061223 S:AB H:AB S:00012294

many thanks in advance

i use this dump a few times.. 68'000km..

[Homiczek]

I have te same problem with 88888 on friend Antara


Some menus remained grey (not available) on OPCOM as, unfortunately, variant programming.
I was only able to program the VIN.
And here it is interesting. I need 3 tries to be able to write the correct VIN !
First time, only 50% of the VIN was correctly flash in the EEPROM, read by OPCOM.
Second time, 25% more, third time, full OK, still read by OPCOM.
This is strange.

I saw this option in opcom - but I dont click yet :)

I understand it didn't help nothing ??


I have programmer with clips, and I will try to fix this, but maybe is easier way ? Any obd programmer