Possibly Related Threads…

***stmilosh*** · (This post was last modified: 04-09-2017, 11:48 AM by stmilosh.)

(04-09-2017, 06:54 AM)Akada Wrote: Is it possible to brick V5 connecting to 121241i or 13223d EN?
Everything working with 120309a but something tempted me to run v5 with these versions.
Cause - no connection, no bootloader...
I've got embosed Pic so I thinked that it's safe to make some tests.
Is it posiible to flash brute force Pic by Willem programmer?
Op-ComFut gave me response that firmware is 07a and nothing more.
Shitty China-clone, it's time to buy Tech2 or MDI.

No it is not bricked, "HQ clone" software can't physically harm device. Also your PIC firmware is perfectly fine, so don't bother trying to reflash it. What HQ clone "protection" does is, it makes changes in FTDI EEPROM which are always fully reversible.
In case of OP-COM B2 (HQ clone) with wrong user data bytes ("protection") it silently changes PID in device driver. In case of OP-COM V2 product descriptor (china clone) in addition to that it also inverts TX pin.
The solution is quite simple. Go to device manager, uninstall the driver for USB Serial converter, rescan for hardware changes and let Windows reinstall the driver. Then go to MProg and reflash .ept file.

OP-COM is not a bad hardware, china clone V5 is identical to HQ clone and to most real OP-COMs. It is cracked HQ software "protection" that is creating all the mess.

***Akada*** · 04-09-2017, 16:39 PM,

I didn't use FT_Prog.
I did it by OcflashFW and I did use backup copy of my FTDI chip.
Thanks stmilosh bring my Op-com back to life.

(04-09-2017, 11:41 AM)stmilosh Wrote: No it is not bricked, "HQ clone" software can't physically harm device. Also your PIC firmware is perfectly fine, so don't bother trying to reflash it. What HQ clone "protection" does is, it makes changes in FTDI EEPROM which are always fully reversible.
In case of OP-COM B2 (HQ clone) with wrong user data bytes ("protection") it silently changes PID in device driver. In case of OP-COM V2 product descriptor (china clone) in addition to that it also inverts TX pin.
The solution is quite simple. Go to device manager, uninstall the driver for USB Serial converter, rescan for hardware changes and let Windows reinstall the driver. Then go to MProg and reflash .ept file.

OP-COM is not a bad hardware, china clone V5 is identical to HQ clone and to most real OP-COMs. It is cracked HQ software "protection" that is creating all the mess.

***obdstart*** · 28-09-2017, 19:25 PM,

(04-09-2017, 06:54 AM)Akada Wrote: Is it possible to brick V5 connecting to 121241i or 13223d EN?
Everything working with 120309a but something tempted me to run v5 with these versions.
Cause - no connection, no bootloader...
I've got embosed Pic so I thinked that it's safe to make some tests.
Is it posiible to flash brute force Pic by Willem programmer?
Op-ComFut gave me response that firmware is 07a and nothing more.
Shitty China-clone, it's time to buy Tech2 or MDI.

This v5 is not shity clone.
Ignorance of user this v5 interface is bigger "shity"
You bricked your interface because use wrong version of software, because every version opcom software have own version firmware inside of interface.
You can not do the upgrade of interface just as you want it, let it be known straightaway
You eraised PIC and now need reprogram interface.

***stmilosh*** · (This post was last modified: 02-10-2017, 21:26 PM by stmilosh.)

(28-09-2017, 19:25 PM)obdstart Wrote: This v5 is not shity clone.
Ignorance of user this v5 interface is bigger "shity"
You bricked your interface because use wrong version of software, because every version opcom software have own version firmware inside of interface.
You can not do the upgrade of interface just as you want it, let it be known straightaway
You eraised PIC and now need reprogram interface.

For the n-th time, stop spreading misinformation. No software can brick the device and no HQ clone would touch PIC firmware on the china clone. The only thing that HQ crappy "protection" does is silently changes PID in device driver. In case of OP-COM V2 product descriptor (china clone) in addition to that it also inverts TX pin.
To recover it is enough to remove device in device manger, plug it back and once drivers are reinstalled reflash FTDI in MProg or using OCflash.

And HQ clone itself has nothing to do with PIC firmware version. HQ clone just prints fake message about wrong firmware if FTDI protection bytes are not correct.
Firmware version is updated to the minimal one required for that software version automatically by the original software not HQ clone wrapper around it. And ofc you can always use the most recent firmware version with the older software, i.e. firmware v1.64 can be used with any software.

***szalay*** · (This post was last modified: 10-03-2018, 16:41 PM by szalay.)

HI,

I bought the OP-COM called V5 with FW1.45 (201008-China Clone 08/2010)
and tried using newer software and it will immediately updated itself to FW1.65 (so i'm trapped)

The PCB similar or same as what @Astrid shown, but came with PIC18F45K80 MCU (as we call it fake)
I did replaced with right PIC18F458, and flashed back with external flasher to FW1.45, everything
seems ok led's flashing proper when i hit diagnostic button, but can't get to talk with cars.

I guess my op-com PCB is not V5 unit, the seller are so he doesn't know what he's talking about. (typically)

any suggestion ?

(Sorry my bad English)

***mattydr67*** · (This post was last modified: 10-03-2018, 16:46 PM by mattydr67.)

If you will read again this thread you will see that s not enought to change the MCU with a real one.
You need to do some changes in PCB too
You have no other choices then to buy a good one from a trustable source
Good luck

***szalay*** · (This post was last modified: 10-03-2018, 16:53 PM by szalay.)

Bad news but thanks the quick response

EDIT: "You need to do some changes in PCB too"

I see but how i do it? i can't find picture about "how to" for my unit

***mattydr67*** · (This post was last modified: 09-06-2019, 17:50 PM by mattydr67.)

As I remember wasn't pics added on web for your kind of hardware.
But if you have skils in electronic then if you find the solution for opcom v5 hardware you can do it in this one too. Its the same hardware but with a diffrent design and in my opinion with a bad quality
Good luck

***szalay*** · 10-03-2018, 17:37 PM,

Thanks the help, i'm really appreciate...
I have skill and i'll check it, and i have few idea, but lots of different in PCB/PCB circuit between..
lets see what i can to do..

***BS68*** · 20-06-2018, 11:04 AM,

(10-03-2018, 16:49 PM)szalay Wrote: Bad news but thanks the quick response

EDIT: "You need to do some changes in PCB too"

I see but how i do it? i can't find picture about "how to" for my unit

It's piece a cake! Just remember to cut off pin 1 from pcb then connect it to pin 23 MCU which C22 pin is going directly to MCU.

Possibly Related Threads…
Thread		Author	Replies	Views	Last Post
	REPAIR ERASED OP-COM CLONE BOOTLOADER FROM PIC18F458 MCU	fantomel	190	134,006	17-11-2023, 12:03 PM Last Post: mattydr67
	GM MDI2 REPAIR EXPERIENCE	12manux	1	233	03-10-2023, 19:24 PM Last Post: apol
	Opcom Bootloader Repair with TL866 ICSP port	aki1	3	1,648	07-10-2019, 13:07 PM Last Post: avepla
	opcom clone need help to repair	autosolutions	1	828	18-09-2019, 02:40 AM Last Post: mattydr67
	Op-Com Repair Tool	ircpoLice	44	49,081	25-08-2019, 05:40 AM Last Post: itman
	Opel meriva 1.6 xe ecu repair help	davor.touch	5	2,857	03-05-2017, 08:43 AM Last Post: dil6222
	Corsa C,central locking not working-BCM repair(SOLVED)	grmsek.damjan	0	2,200	16-06-2015, 08:02 AM Last Post: grmsek.damjan
	Y17DT repair	cicko	1	1,303	12-06-2015, 08:10 AM Last Post: domelec

Contact Us