Jump to content

taedla01

Membri
  • Content Count

    20
  • Joined

  • Last visited

  • Days Won

    19

taedla01 last won the day on February 16

taedla01 had the most liked content!

About taedla01

  • Rank
    *
  • Birthday 04/15/1988

Profile Information

  • Locație:
    Spain
  • Interese
    Aeronautical Engineering, Automobile Performance, and my Opel Corsa-C of course!
  • Mașină / Motor
    1.3 CDTI
  • An fabricație
    2006
  • Combustibil
    Motorină
  • Cod motor
    Z13DTJ (Converted from Z13DT)
  • Cutie viteze
    Manuală
  • Jante/Roți
    205/40 R17 84W 4x100 ET44

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hello @liviu2004 The conversion from CE59 to CG83 is done through the normal SPS update process using the original TECH2 tool so all MCUs are programmed. Cheers, Darío.
  2. Hello @liviu2004 The conversion from CE59 to CG83 is done through the normal SPS update process using the original TECH2 tool so all MCUs are programmed. Cheers, Darío.
  3. Some images... Converted CE59 into CG83: Unsolder AM29F160DB from converted CE59 PCB (with CG83 software): Resolder detail: Comparing hardware (CE vs CG CIDs): If you are interested in more documents, eeprom and flash readings, please, send a private message. Cheers, Darío.
  4. Hello everyone. @liviu2004: Sorry for the delay in answering. I need time to write in more detail but I will try to shed some light now: - First step: Is it possible to convert a CID CE59 display from Vectra-C to a CID CG83 display for Meriva-A? The answer is yes. I have managed to record the CG83 software on a Vectra-C screen and it works perfectly. Obviously the hardware is not the same and for example the steering wheel controls will not work on a Meriva or Corsa-C. - Second step: We have to see by comparing both screens what hardware differences there are between them. T
  5. Hello everyone! Great job @Catastefan! Congratulations! And thanks for share your results! Regards. Dario.
  6. Hello, Sorry for the delay in answering but I'm very busy with my work. It's not as simple as just using a VIN from a 3-line display vehicle and writing the 3-line EEPROM to the 2-line display. It is not possible to downgrade or equalize the software, that is, you cannot rewrite a three-line software using a three-line EEPROM. The program answers you saying that the software is the same and that reprogramming is not possible. You need to use a two-line EEPROM and a three-line VIN. Besides that, you have to make modifications at the byte level in the programming. If you do not do the abo
  7. Hi @liviu2004, I do not want to reflash or touch my KW CID due as you already know it is very dificult to find it and it is the only CID that works with Corsa-C. I have a broken CID (CE59) which coming from my father´s Vectra-C (display LCD with scratches) and maybe I can use it as guinea pig. What could happen if I flash CG83 into CE59? Thanks for your time, Regards from Spain, Dario.
  8. Hello everyone, @liviu2004 thanks for comment. I have found ESP pump but not with connector, so I am not bought it. I have yaw sensor and his connector, not found steering wheel sensor yet. I have been searching trough the CG83 firmware files and I have located where languages are defined. What I want to do is flash a new open logo and search if could be possible implement TPMS in Corsa-C because Meriva-A CID has this option (not implemented of course). I know, low speed Can-BUS is not possible with standard Meriva CID, but looking at the PCB I see that some components are missi
  9. I am not sure if CE83 do not exist in GTIS32. For CE83, GE83 and Corsa-D Delphi displays I used Tis2Web server. Thanks for your work @liviu2004 Next step is to retrofit ESP. Do you know any good site for spare parts? Cheers, Dario.
  10. Hello everyone, In case it can be useful to the community, to say that the adaptation of the rear disc brakes on a Corsa-C Z13DT has turned out to be simple. The rear bump of the car is compatible with the disc brake system. In my case, I have needed the following pieces (everything comes from a Tigra-B with ABS 8.0): - Brake calipers, brake discs (240mm) and brake pads. - Protectors of the disc brakes. - Supports of the brake calipers. - Full handbrake cord and seats for the handbrake ends. - New matches (racors). Maybe I will change brake pipes.
  11. Hello everyone, It's been several months since my last post and I think it's fair to show the advances. @liviu2004, thanks for the offer and sorry for late response. For now I do not need a BQ CID unit. I have already managed to update my CID screen with the latest available software (CG83). I have also been able to update more screens (CE83 and CD83) without needing to have an original EEPROM dump. I have also been able to prove that this method is used to reprogram the ECM of my Z13DT (from 70CV to 90CV). By way of summary and without going into technical details
  12. Hello everyone, After retrofitting my anti theft warning system, I have discovered that I need to place other wires to complete the system. Indeed, it appears to be another item for detect the state of the trunk door. @liviu2004, have you retrofitted this? Did you have to buy other parts? Here you can see what I mean: Thanks for your time and effort. Regards from Spain, Dario.
  13. Hi @liviu2004, Maybe we can try new tricks: - Can you reproduce this problem in others PCs? Perhaps your OS has installed new drivers that are not supporting your hardware version. Before attempt to do anything, install FTDI drivers 2.8.14 and then follow my tutorial. - Is this Op-Com a real HQ Clone? Be careful with this, I saw HQ Clones that have MCU PIC18F4580 (id=0x1a80) instead of PIC18F458 (id=0x860), you can check it using MPLAB IPE. - Can you verify your FTDI chip? Maybe is a fake chip. Check this out: https://electronics.stackexchange.com/qu
  14. Hello everyone, Many of us have official diagnostic tools: TECH2, MDI, VCI… But many troubles can be searched and solved with simplest tool: OP-COM OP-COM (or VAUX-COM) sometime gets corrupted due to a firmware change or a low voltage connection. When OP-COM software shows no connection or interface error is caused mainly by two troubles: the FTDI communication chip and the MCU chip itself (PIC18F458). Next steps will help you in the task of bring back to life your bricked OP-COM. *Note: this tutorial is only intended for those like have an OP-COM with the original Microchi
  15. Hi @liviu2004! Thanks for response! I understand you, I have spent too many time searching and looking for solutions in others engineerings fields and I know how frustratted is give solutions for others and then see how people make the most of your work for make money. This is not my case in terms of assume your knowledge. I want to get the CID updated on my own because it is a personal challenge for me, not a necessity. If I would have another CID but in this case a BQ would be very easy... just change VIN in KW CID and swap CIDs like a magician in the exact moment... Hey! Hey! I kn
×
×
  • Create New...