Unfortunately we do not accept new members for free, Now Registration cost 30€, if you are interesting Send Email to [email protected]
Solved! Opcom V1.99 communication error
15-06-2018, 22:30 PM,
Post: #1
|
|||
|
|||
Solved! Opcom V1.99 communication error
Hello,
I got an Opcom clone V1.99. first I had no issue, but I tried to test different software versions coming with hardware ending connection error with ecu. When I check interface by software, 120309a, I get the version and interface passes the test. But when I try to connect the car i receive " Interface communication error, or interface not powered from car!" Does anyone have an idea? |
|||
16-06-2018, 03:13 AM,
Post: #2
|
|||
|
|||
RE: Opcom V1.99 communication error
(15-06-2018, 22:30 PM)irarkh Wrote: Hello, Sounds like hardware error |
|||
16-06-2018, 06:16 AM,
Post: #3
|
|||
|
|||
RE: Opcom V1.99 communication error
The hardware has real pic and ftdi chip. I could re-program ftdi with mprog but I'm not sure it's completely hardware issue. I can connect the same car with software china clone 2010 faster than 120309a. but it's limited to DTC and no programming. I read somewhere checking car's OBD2 connector 16 pin for 12V and 4 5 pin for ground. Any ideas?
|
|||
16-06-2018, 06:23 AM,
(This post was last modified: 16-06-2018, 07:59 AM by mattydr67.)
Post: #4
|
|||
|
|||
RE: Opcom V1.99 communication error
Are you using win 10? If yes go to youtube and you find how solve this.
Check the VID/PID to be 0403/6001 Check driver version to be up to 2.8.30 Check tge VCP in driver properties to be Untick it. Good luck |
|||
16-06-2018, 09:25 AM,
Post: #5
|
|||
|
|||
RE: Opcom V1.99 communication error
(16-06-2018, 06:23 AM)mattydr67 Wrote: Are you using win 10? If yes go to youtube and you find how solve this. Thanks for sharing. Yes I use win 10. but no problem with driver signing if you mean checking YouTube by that. Here are some more info: FW: V1.99 Interface: 120309a Driver date: 7/12/2013 Driver version: 2.8.30.0 VCP in uncheck USB\VID_0403&PID_6001&REV_0600 USB\VID_0403&PID_6001 One more thing, when the hardware is connected to car I receive " Interface communication error, or interface not powered from car!" message in the first attempt to automatic vehicle identification. But when the hardware is not connected to OBD2 I don't receive error text. Instead the hardware passes through and ECU communication page opens. Then no communication with ECM appears due to not connecting with OBD2 port. |
|||
16-06-2018, 10:05 AM,
(This post was last modified: 16-06-2018, 15:08 PM by mattydr67.)
Post: #6
|
|||
|
|||
RE: Opcom V1.99 communication error
Share the pics with your both sides PCB.
If the tool is working with OpCom China clone and not with the vauxcom 120309a then there is a drivers issue. Or your tool has a fake MCU Also the fw 1.99 is a fake one ( the real firmware version is fw1.39 ) And in this case the firmware is not matching with the software version and it cannot decode the car. With other words you cannot connect to the car. Good luck |
|||
17-06-2018, 05:20 AM,
Post: #7
|
|||
|
|||
RE: Opcom V1.99 communication error
Here are some photos attached.
I didn't get what you mean by the real FW is 1.39. The china made ones or real Op-com device? Also I noticed the hardware is not working with china clone software anymore, doesn't pass interface test. Actually I made another change, I noticed hex file change after I reprogrammed FDTI by Mprog. Cause I made a backup by ocflash first. I rewrite the original hex file by ocflash. Now china clone is not working any more but 120309a stil functions the same. |
|||
17-06-2018, 06:04 AM,
(This post was last modified: 17-06-2018, 06:14 AM by mattydr67.)
Post: #8
|
|||
|
|||
RE: Opcom V1.99 communication error
First of all your microprocesor is not the real one PIC18F458. Its as we calling a "fake" one
This because allways when you have on PCB the components D5 and C22 this is specific to Pic18F45k80 microprocesor wich using a diffrent bootloader. ( always when you try to flash it you will damage it and it will not work anymore ) The real firmware is fw1.39 and its easy to install the fw1.39 by OCFlash and make it show as fw1.99 or any other. So in this case the interface is working only with OP-COM China Clone software. If yours is not working with this version either then your microprocesor has a damaged bootloader and there is no solution for it to flash it back. The only solution there is and you can find it in this forum is to change the MCU with a real one and make some hardware modifications on PCB. But this solution it doesn't worth in my opinion. Good luck |
|||
17-06-2018, 06:54 AM,
Post: #9
|
|||
|
|||
RE: Opcom V1.99 communication error
So IYO the only way to identify real MCU is the pcb without D5 and C22? Cause the chip is printed as real MCU. The only clone, on Aliexpress, I found without 2 mentioned elements on pcb are the boards called FW 1.7 with FW upgrade possibillity as seller describes. If you approve I'll order one. Also about present one, as I said, it's working with 120309a same as first post. Interface test is ok. tries to communicate with ECU nut communication error appears. Do you think its brick? or there is hope for it?
|
|||
17-06-2018, 07:07 AM,
(This post was last modified: 17-06-2018, 07:16 AM by mattydr67.)
Post: #10
|
|||
|
|||
RE: Opcom V1.99 communication error
Yes that two components let you know that the MCU is not a real one. Even that on pcb there are only the pads of that components and the components are missing.
We talked too much about this and soon chinese will find a new "solution" to make a new fake. As you can see your PCB is printed OP-COM v5 and its actually an OP-COM v6 Try it with OpCom China clone software If its works with that version then your tool is not brick it. If will not work then it is. But if you flashed the MCU then the tool cannot be fix it till you will not change the MCU with an original one. I cannot aprove you to buy any chinese clones. Its your choice what you buy. I am just tried to help you solve your issues. Good luck |
|||
« Next Oldest | Next Newest »
|
Users browsing this thread:
1 Guest(s)
1 Guest(s)
Return to TopReturn to Content