Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


taedla01 last won the day on February 16

taedla01 had the most liked content!

About taedla01

  • Birthday 04/15/1988

Profile Information

  • Locație:
  • Interese
    Aeronautical Engineering, Automobile Performance, and my Opel Corsa-C of course!
  • Mașină / Motor
    1.3 CDTI
  • An fabricație
  • Combustibil
  • Cod motor
    Z13DTJ (Converted from Z13DT)
  • Cutie viteze
  • 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.

taedla01's Achievements

  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. The motherboards are identical and so are the processors. What is missing are the components for reading the analog sensors on the CE screen and the installation of the necessary parts for low and high speed CANBus on the CG screen. - Third step: If we compare the CE hardware with the CG we will see that it is easier to install the missing components on the CG screen. With this we will have the low-speed CANBus network functional. My current situation: I have a CE converted to CG display with which I am investigating the tire pressure reading using TPMS equipment from a Vectra-C. I have readings of the AM29F160DB memory although I have never gotten serious to investigate more. In a Vectra-C forum the user Pepasz found a way to edit the software of the CID screens to be able to modify the logos and more. I have found out that the source code programming was done with SEGGER's EmWIN software modules. The logo is a set of 16 compressed images of 400x234 pixels in 16 bits. I am going to try to make time and upload photos and files of everything I have researched so far. Greetings from Spain. Dario.
  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 above, the process is doomed to failure. Regards, Dario.
  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 missing. This components are the Low Speed Can-BUS and comparing with a Vectra-C CID I think maybe we can convert a Meriva-A CID into same Vectra-C CID Low Speed Can-BUS. Has anybody test any of this ideas? Probably most simple could be change English language into Romanian...? Thanks for your time and effort. Regards from Spain, Dario.
  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. Some images: Greetings from Spain, Dario
  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, this has been the process: -Inverse engineering of an EEPROM dump to know how is encoded the VIN, Alpha code and part number within the EEPROM. The EEPROM of the ECU is modified and it is verified that the data matches with the model that has the software updated (we convert the EEPROM of Cx55 / Cx59 into Cx83). -We request SPS in Tech2 for the ECU that we want to update. -The contents of the Tech2 PCMCIA card are modified. The new content is loaded on the card. -We plug Tech2 into GlobalTIS and request SPS. GlobalTIS loads the new update software on the PCMCIA card. -We update the ECU through SPS. Two months of hard investigation and this is the result: Regards from Spain, Dario.
  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/questions/196154/how-to-detect-fake-ftdi-chips If you can read your PIC18F458 with PICkit3 software and in the "program memory" fields you can see the bits configured, you have your MCU chip programmed, so the problem could be your FTDI chip. You can compare the bits between the firmware file “FW1.39+Bootloader.hex” and the MCU chip to confirm if the chip is correctly programmed. - What OP-COM software version are you using? What was the firmware loaded into the Op-com interface before the problem occurred? Remember that if the previous firmware was >=1.60 you need to flash onto MCU chip that version or newer due to a change in bootloader version, i.e, you can not update firmware from 1.39 to 1.60 directly with OC-FLASH. Regards from Spain, Dario.
  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 Microchip PIC18F458 chip, forget to attemp with fake chips. TOOLS FOR REPAIR ARE ATTACHED TO THIS POST First part: regarding OP-COM FTDI chip. Firstly, we have to check FTDI chip. Go to Control Panel -> Device administrator and search for “USB Serial Converter” or “OP-COM USB V2”. Right click and open properties dialog, serch for “hardware ID” in details dialog. If yours shows 0000 at the end of the PID properties, as would be in this case: USB/VID_0403&PID_6001&REV_0000 instead of USB/VID_0403&PID_6001&REV_0600, your FTDI chip is corrupted. Sometimes is showed “4F50” instead of “0600”, both values are good. Next step is to flash FTDI chip with trusted OP-COM .ept file, wich contents rights properties for OP-COM software connections. So open MProg, go to Device -> Scan, this will show detected FTDI devices: Go to:File -> Open, and select OP-COM.ept from downloaded folder: Now, check for correct values (in GREEN). If all is right, flash FTDI chip (in RED): When finish, you will have a new serial number assigned to your OP-COM interface: Pay attention to next: close all and disconnect OP-COM from USB. Restart computer. Once operating system has been loaded, plug in OP-COM, go to Control Panel -> Device administrator, and search for “OP-COM USB V2” which appears with no driver installed: Right click, open Properties -> Driver -> Update Driver, search for driver in computer (not internet), select from a list of drivers, click on “show all devices”. Select from disk and search for driver included in downloaded folder (ftdibus.inf). Windows will ask you if you want to install non validate driver, click yes and wait for installation. Once finished, check in “Device administrator” if OP-COM appears as “USB Serial Converter” and if in Properties -> Details -> Hardware ID (PID) is correct . If you have done all, open OP-COM (or VAUX-COM) software and go to Settings -> Test interface. If your FTDI chip and your MCU PIC18F458 are ok, you will see your OP-COM firmware versión: If not, you have a bad day… MCU chip must be flashed and you need a Pickit programmer or any other compatible programmer. Second part: How to flash MCU chip. *This tutorial is for Microchip Pickit V3. Firstly, dissasembly your OP-COM and solder some wires as described here: Secondly, connect these wires to Pickit like this: You must to have something like this (do not take care about programmer used in image): Next, install PICkit3Setup.exe from downloaded folder. Connect all systems (OP-COM <-> Pickit <-> USB) before open Pickit software. Open software, go to “device family” and look for “18F4XX”. Software will now show chip as detected. "Read" chip and then "Erase" it. Wait. Verify chip, do a “Blank Check” and "Read" chip again. In “programm memory” all values must show FFFF in bits locations. Go to File -> Import HEX and search for “FW1.39+Bootloader.hex” file included in downloaded folder. In main window, under “Program memory” there is a field named “Source”. There must appears our firmware file “FW1.39+Bootloader.hex”. If all is ok, press “Write”. Pickit will program the MCU chip with OP-COM Bootloader and Firmware. When finish, make a “Verify” and a “Read”. If all goes well, now you have your OP-COM resurrected. Open OP-COM (or VAUX-COM) software and go to Settings -> Test interface. If your FTDI chip and your MCU PIC18F458 are ok, you will see your OP-COM firmware versión: *Note: If you want to update your interface from 1.39 to newer version, you can use OC-FLASH tool for do it (OC-FLASH is not included). Hope it helped you. Regards from Spain, Dario. OPCOM V5 Repair.rar
  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 know you understand what I want to say. Thanks for this site liviu2004. Hope to help this great comunity in future. Regards from Spain, Dario.
  • Create New...