Register
Results 1 to 9 of 9

Thread: OPCOM problem

  1. #1
    DK Veteran
    lkjubaking's Avatar
    Join Date
    Feb 2013
    Location
    Serbia
    Posts
    446
    Thanks Thanks Given 
    135
    Thanks Thanks Received 
    413
    Thanked in
    156 Posts

    Default OPCOM problem

    I have problem with my OPCOM clon

    Number of interfaces: 1
    Description: OP-COM USB V2
    FTDI USB Serial: FTUB2223
    FTDI-ChipID ChipID: 0xA4C5A7D5
    FTDI-ChipID Location ID: 0x41
    O***M Serial-Number (calculated): 4GKMQ9VU
    O***M FW UPdate Code (calculated): 5PB18YCV
    Interface opened. Handle: 90770240
    Baudrate 500kBit/s
    Dataformat 8N1
    Flowcontrol NONE
    SetChars
    Timeout 5 seconds
    Set DTR and RTS Low = PIC Reset
    DTR low
    RTS low
    Wait 1 second for reset
    Set RTS High = PIC running
    RTS high
    Wait 1.5 second, so bootloader can start FW...
    RX Buffer clear... OK
    FW Versions- and Interface ID- request send.
    Timeout - is your PIC empty? No Firmware?
    *** Firmware Version: 7F.0
    **
    *
    Set RTS to LOW = PIC Reset
    RTS low
    Communication closed. Handle: 90770240


    Is there a possibility of repair?
    Thanks

  2. #2
    DK Veteran
    lkjubaking's Avatar
    Join Date
    Feb 2013
    Location
    Serbia
    Posts
    446
    Thanks Thanks Given 
    135
    Thanks Thanks Received 
    413
    Thanked in
    156 Posts

    Default

    SOLVED
    Thanks

  3. #3
    DK Veteran
    speedy100's Avatar
    Join Date
    Jul 2010
    Location
    Athens
    Posts
    1,171
    Thanks Thanks Given 
    673
    Thanks Thanks Received 
    323
    Thanked in
    217 Posts

    Default

    How did You solve it?
    Can You share please?
    Knowledge is to share... so if I have helped just press [Thank You + Rep.]...

  4. #4
    DK Veteran

    Join Date
    Aug 2008
    Posts
    1,034
    Thanks Thanks Given 
    99
    Thanks Thanks Received 
    471
    Thanked in
    327 Posts

    Default

    reprogram pic
    i think dumps on here or net somewhere

  5. The Following User Says Thank You to tango For This Useful Post:

    speedy100 (15th June, 2014)

  6. #5
    DK Veteran
    speedy100's Avatar
    Join Date
    Jul 2010
    Location
    Athens
    Posts
    1,171
    Thanks Thanks Given 
    673
    Thanks Thanks Received 
    323
    Thanked in
    217 Posts

    Default

    Hi tango,
    I have been playing all day trying to repair my OpCom.
    I have found the hex file etc. and I am using Willem ver. 5.0 programmer in serial mode.
    It reads, erases, writes code but does not write Data!
    Do I need to lift any pin of the board? or any other idea?

    Thank You for Your time!
    B.R
    Knowledge is to share... so if I have helped just press [Thank You + Rep.]...

  7. #6
    Member
    Join Date
    Feb 2014
    Posts
    74
    Thanks Thanks Given 
    0
    Thanks Thanks Received 
    5
    Thanked in
    5 Posts

    Default

    i think reinstall and this problem will sloved

  8. The Following User Says Thank You to Tomthomasxx For This Useful Post:

    speedy100 (20th June, 2014)

  9. #7
    DK Veteran
    speedy100's Avatar
    Join Date
    Jul 2010
    Location
    Athens
    Posts
    1,171
    Thanks Thanks Given 
    673
    Thanks Thanks Received 
    323
    Thanked in
    217 Posts

    Default

    Quote Originally Posted by Tomthomasxx View Post
    i think reinstall and this problem will sloved
    Problem solved.
    It was the software version of my programmer... After updating it was a one minute job.
    It works fine again.

    Best Regards
    Knowledge is to share... so if I have helped just press [Thank You + Rep.]...

  10. #8
    Banned
    Join Date
    Jun 2010
    Location
    Usa
    Posts
    37
    Thanks Thanks Given 
    4
    Thanks Thanks Received 
    254
    Thanked in
    12 Posts

    Default

    Problem can solved only with reprogram firmware in version PCB v5 china clone (and older) with REAL MCU PIC18F458 inside.
    New version PCB v6 china clone have inside FAKE MCU PIC18F458, so if kill interface with wrong version software it is impossible to reprogram MCU with firmware.
    Last edited by tango5; 11th July, 2014 at 10:20 PM.

  11. The Following User Says Thank You to tango5 For This Useful Post:

    speedy100 (11th July, 2014)

  12. #9
    DK Veteran
    speedy100's Avatar
    Join Date
    Jul 2010
    Location
    Athens
    Posts
    1,171
    Thanks Thanks Given 
    673
    Thanks Thanks Received 
    323
    Thanked in
    217 Posts

    Default

    Quote Originally Posted by tango5 View Post
    Problem can solved only with reprogram firmware in version PCB v5 china clone (and older) with REAL MCU PIC18F458 inside.
    New version PCB v6 china clone have inside FAKE MCU PIC18F458, so if kill interface with wrong version software it is impossible to reprogram MCU with firmware.
    Thank You for Your reply tango5!
    My problem was my Whillem programmer. It was solved by updating the Whillem software.

    One problem I have encounter lately though with OPCOM 1.39 is In Opel Corsa D 1.2 gasoline (Z12XEP) 2008 model. OPCOM can not communicate with CAN Dash (IPC) and Airbag (SDM) modules. It shows that it tries to initialize communications and that is all.
    Communications and programming with other modules are working fine.
    Are there any special communications parameters to change in order to overcome this problem or any other idea?

    B.R.
    Knowledge is to share... so if I have helped just press [Thank You + Rep.]...

 

 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.