Had enough of fake opcom? Lets repair it, from v6 to v5

[liviu2004]

I bought a few opcoms from china and ended up with some fake mcu inside. Famous and infamous firmware version 1.45. I did upgrade them to 1.59 (maybe my mistake) and they never worked on my Corsa C. Not that they actually did with 1.45. No way.



While v5 hardware works without issues. I found out from reading on the net that you can change from v6 to v5. Some have done it already for loooong time. So I will do also.



First of all, lets compare v5 to v6. v5 has a PIC mcu, model PIC18F458-I/PT. v6 has another chinese MCU, marked OP-COM.









I found this picture which shows what changes are needed:





And started doing my own thing. Hot air soldering is the key. I managed to remove the MCU using 350 degrees on a square output flow head. The extra capacitor and diode also went away.





























What next, I have the PIC kit 3 programmer ordered (missed the post today) and few PIC chips, hope to get it this week. As software, I found an archive with fw 1.39 and bootloader hex file. I will try it and let all know if it worked.



Just for fun! :thumb Can somebody translate in dutch for me, please? :wors

 

[liviu2004]

Job done, chips came today. I used soldering pasta, a bit more than needed. I shooted fw 1.39 + bootloader in the PIC and all went ok. So, don't through away your dead opcom, maybe they have a chance to be fixed.

















Me happy!

 

[turbo.d]

@liviu2004 wrote:Job done, chips came today. I used soldering pasta, a bit more than needed. I shooted fw 1.39 + bootloader in the PIC and all went ok. So, don't through away your dead opcom, maybe they have a chance to be fixed.

















Me happy!

I think your conclusions are very interesting to me.

Do you have any clue why there are extra components installed on the fake-units :?:



Good job and keep me informed about the functionality from the refurbished units.

Greetz

Marcel

 

[liviu2004]

Apparently these fake MCUs need those extra 2 pieces. This revised opcom has been fully tested on my Corsa C, I have tested all systems on the car, including mid speed canbus, including security code reading from clocks, all OK.

 

[turbo.d]

As those units don't seem to work, these components wouldn't need to fitted anyway.

They could have saved some money there.



I'm happy to read you've sorted it out. Good job.

 

[liviu2004]

Got some practice.

 

[Ron50]

Hallo,



Ik heb weer een andere OP-COM......



Op de chip staat:



MICROCHIP

PIC 18 F458

IPT e3

1438KQA



Op de print staat:



OPCOM-NEW



Firmware version:



V01.45



Meegeleverde software:



OPCOM CHINA-CLONE 08/2010



Mijn auto:



1999 Opel Frontera V2.2 Benzine





Ik kan nu alleen Body en Infotainment system uitlezen (CRC Error=00 / used pin = #07)

Engine geeft bekende melding.... ECU does not reply... Please wait 2 seconds





Vragen:



- Kan ik met deze chip veilig updaten of downgraden naar V1.59 of V1.39 met OCFlash ?

- Welke versie firmware is voor mijn auto goed?

- is andere (versie) software beter. Welke?

- Kan het zijn dat dat ik iets moet wijzigen aan de ISO9141 settings?



Al vast dank voor info

 

[liviu2004]

@Ron50 wrote:

- Kan ik met deze chip veilig updaten of downgraden naar V1.59 of V1.39 met OCFlash ?

- Welke versie firmware is voor mijn auto goed?

- is andere (versie) software beter. Welke?

- Kan het zijn dat dat ik iets moet wijzigen aan de ISO9141 settings?



- ja, 1,39 is better

- 1.39 voor oudere auto

- nee

- Laat alle instellingen standaard



misschien heb je een relais kapot? driver is ok?

 

[Ron50]

Hello liviu2004,



Thanks for your anwer.

I dowgraded the firmware succesfully to V1.39

However testing the engine resulted in the same announcement.... ECU does not reply... Please wait 2 seconds

I now realise that in the provided software there is no option for my engine type:

There is only one button to choose X22DTH , wich is a diesel engine

I have a X22SE engine



The software version is OPCOM CHINA-CLONE 08/2010



Do you know of any version in wich i can choose my engine type?



Regards,



Ron

 

[liviu2004]

this is the list of the same injection models:



Multec S (2-Stellig)

X14XE, Z14XE, C16XE, X16XE, X16XEL, Y16XE, Z16SE, Z16XE, Z16XEP, Z16YNG, Z16LET, X22SE, Y22SE



try them.

 

[iquick]

I also get CRC Error=??00 and used pin=#07. I think my opcom asks for you to repair it :jerry



It is strange because it reads and programs, I can select everything. :hmmz

 

[liviu2004]

Open it and see if the chip is fake or not. If not, try to run in with administrator rights.

 

[iquick]

I already did, I opened my op-com and my chip is V5



Chip details:



Microchip

PIC18F458-I/PT



I updated my firmware successfully to V1.59, but it is not working with vaux-com 120309a. It says FTDI ID Faker 1.5 and the opcom version need to be activated. It also says please install USB drivers. With 2010-08, it is working. Is there any solution for this?

 

[liviu2004]

strange, 120309a does not ask for activation. And indeed, it has the ftdi faker to fake the serial number. My v5 works ok with 120309.

 

[iquick]

Well, I finally sorted it out, I think my op-com went blank when I upgraded it from V1.39 to V1.59. I used MProg 3.5, looked inside the program, it was completely blank, strange because my op-com worked with 2010-08 and not with the vaux-com 120309a. Did a rewrite with op-com V2.ept settings. Removed USB put it again in my USB port and it installed drivers, now it is working fine, no activation needed for 120309a, except for one thing, the CRC Error=??00 and used pin=#07. Is this a problem with soldering as you mention it before?

 

[liviu2004]

Can be a relay broken inside. The problem with those is that are double side soldered, so you need hot air gun to heat all 8 connections in one go. Or you can send it to me, I can replace it.

 

[iquick]

I have send you a pm.

 

[AL corsa]

pictures are gone?

 

[liviu2004]

Ja, sorry, ik heb de photobucket account verwijderd.

 

[AL corsa]

Jammer