Register
Results 1 to 10 of 10
  1. #1
    Top Poster +
    jodank's Avatar
    Join Date
    Jul 2010
    Location
    Planet Earth
    Posts
    202
    Thanks Thanks Given 
    38
    Thanks Thanks Received 
    54
    Thanked in
    21 Posts

    Default Op-Com xyz error msg, why? How to solve?

    My OP-COM interface is a clone one with the original PIC inside.
    The firmware is 1.59, if I install it on my laptop I got two problems:
    1. When I start the VAUX-COM as an admin I get a message:
    "An xyz error occured:"
    I don't know what is this for.


    2. If I go to "Test interface" I got a msg:
    "Please connect your interface to the USB port, or install the USB driver!"
    My usb driver is installed and is listed in the Device Manager.
    It shows as "OP-COM USB V2 Interface" .


    The OS is Windows7 32bit Ultima.
    The whole installation I do from the cd what was shipped with the tool.

    I tried to figure out for a week or so what could cos this problem but without success.


    Any suggestion pls?


    Thnx.

  2. #2
    Top Poster

    Join Date
    Feb 2010
    Posts
    189
    Thanks Thanks Given 
    81
    Thanks Thanks Received 
    123
    Thanked in
    74 Posts

    Default

    ...version of software?Need change ept file of ftdi in case of use new version.

  3. The Following User Says Thank You to stas12 For This Useful Post:

    jodank (22nd November, 2018)

  4. #3
    Top Poster +
    jodank's Avatar
    Join Date
    Jul 2010
    Location
    Planet Earth
    Posts
    202
    Thanks Thanks Given 
    38
    Thanks Thanks Received 
    54
    Thanked in
    21 Posts

    Default

    On the CD what was with the tool are two versions of the software.
    1. VAUX-COM_120309a+131223d_GB --> this is the version that tells me "xyz" error.
    2. OPCOM 201008 --> this version is working but it is bugging.

    I wanna use the tool on Win7 Ultimate 32bit.

    Thanks for help.
    My best regards.

  5. #4
    Top Poster

    Join Date
    Feb 2010
    Posts
    189
    Thanks Thanks Given 
    81
    Thanks Thanks Received 
    123
    Thanked in
    74 Posts

  6. The Following User Says Thank You to stas12 For This Useful Post:

    jodank (22nd November, 2018)

  7. #5
    Top Poster +
    jodank's Avatar
    Join Date
    Jul 2010
    Location
    Planet Earth
    Posts
    202
    Thanks Thanks Given 
    38
    Thanks Thanks Received 
    54
    Thanked in
    21 Posts

    Default

    Hmmm....Ok.

    Maybe the problem is related to the 1.59 firmware? (I read the description on the link above).
    They are upgrading the firmware to v1.6.

    Maybe v1.59 won't work with the VAUX-COM_120309a?

    Thanks for the reply.

  8. #6
    Top Poster

    Join Date
    Feb 2010
    Posts
    189
    Thanks Thanks Given 
    81
    Thanks Thanks Received 
    123
    Thanked in
    74 Posts

    Default

    working,problem is in driver.

  9. #7
    Top Poster
    Join Date
    Mar 2010
    Posts
    152
    Thanks Thanks Given 
    11
    Thanks Thanks Received 
    40
    Thanked in
    33 Posts

    Default

    Quote Originally Posted by stas12 View Post
    working,problem is in driver.
    Where you get it and how you solve it?
    HEX FW 48 available
    Chiptuning solutions - dyno proven

  10. #8
    Newbie

    Join Date
    Mar 2010
    Posts
    11
    Thanks Thanks Given 
    1
    Thanks Thanks Received 
    30
    Thanked in
    6 Posts

    Default

    Quote Originally Posted by jodank View Post
    My OP-COM interface is a clone one with the original PIC inside.
    The firmware is 1.59, if I install it on my laptop I got two problems:
    1. When I start the VAUX-COM as an admin I get a message:
    "An xyz error occured:"
    I don't know what is this for.
    After spending _many_ hours trying to figure out why this bloody 'xyz' error pops up, I narrowed it down to Windows DEP (data execution protection), that I had enabled globally in the system. After disabling this - all works fine!

    It seems the cracked loader or the soft itself has some protections in it and it does not like Windows messing around with its code.

    i can imagine some AV/antimalware software could make OPCOM/VAUXCOM misbehave too.

    Therefore - it has nothing to do with the hardware or driver.

    Hope it helps someone.

  11. The Following 2 Users Say Thank You to barthek For This Useful Post:

    Brian 01 (3rd April, 2024), JHDSoft (1st October, 2022)

  12. #9
    Top Poster +
    jodank's Avatar
    Join Date
    Jul 2010
    Location
    Planet Earth
    Posts
    202
    Thanks Thanks Given 
    38
    Thanks Thanks Received 
    54
    Thanked in
    21 Posts

    Default

    Thanks for the replay.
    At the moment I can not try your solution but maybe it can be a good solution.

    Hope somebody can also check the solution and report...

  13. #10
    Newbie
    Join Date
    Nov 2021
    Posts
    10
    Thanks Thanks Given 
    3
    Thanks Thanks Received 
    0
    Thanked in
    0 Posts

    Default

    Quote Originally Posted by barthek View Post
    After spending _many_ hours trying to figure out why this bloody 'xyz' error pops up, I narrowed it down to Windows DEP (data execution protection), that I had enabled globally in the system. After disabling this - all works fine!

    It seems the cracked loader or the soft itself has some protections in it and it does not like Windows messing around with its code.

    i can imagine some AV/antimalware software could make OPCOM/VAUXCOM misbehave too.

    Therefore - it has nothing to do with the hardware or driver.

    Hope it helps someone.
    Thank you very much !

    I can confirm that it solved the "An xyz error occurred:" for the VAUX-COM (OP-COM) 120309a, my OS is Windows 10 Pro 22H2.
    All i did was: go to Performanece options -> Data Execution Prevention -> select "Turn on DEP for essential Windows programs and services only" -> click "Apply" -> close everything and restart your computer.

    I have read somwhere else that downloading and installing the "Net.Framework 3.5" can also help with this problem. Other fix (which I temporarily did before) may be to install the program in virtual machine (in my case it was Windows 10) with disabled virus protection.

 

 

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.