Register
Page 338 of 847 FirstFirst ... 238288328333334335336337338339340341342343348388438838 ... LastLast
Results 5,056 to 5,070 of 12705
  1. #5056
    Top Poster
    Join Date
    Apr 2010
    Location
    RF
    Posts
    133
    Thanks Thanks Given 
    1
    Thanks Thanks Received 
    39
    Thanked in
    21 Posts

    Default

    Quote Originally Posted by eliotroyano View Post
    In fact even usb port is not recognizing FTDI IC in cable, why this happends? I have try changing FTDI IC without luck at all?
    If the chip of FTDI is destroyed physically, then I will give advice, not to connect a notebook to a network of 220 volts, during diagnostics.
    If the chip of FTDI is destroyed by software.
    And if you want to protect FTDI chip from reprogram of internal EEPROM. That is necessary in the RT-USB.inf file, to add or change record:
    [FtdiBus.NT.HW.AddReg]
    HKR, "ConfigData", 0x00010001,1
    And reinstall driver.
    Or to change(add) the appropriate value in the system registry.
    Last edited by magadan; 14th July, 2017 at 12:12 PM.

  2. #5057
    DK Veteran
    Join Date
    Aug 2009
    Posts
    288
    Thanks Thanks Given 
    11
    Thanks Thanks Received 
    16
    Thanked in
    11 Posts

    Default

    Quote Originally Posted by magadan View Post
    If the chip of FTDI is destroyed physically, then I will give advice, not to connect a notebook to a network of 220 volts, during diagnostics.
    If the chip of FTDI is destroyed by software.
    And if you want to protect FTDI chip from reprogram of internal EEPROM. That is necessary in the RT-USB.inf file, to add or change record:
    [FtdiBus.NT.HW.AddReg]
    HKR, "ConfigData", 0x00010001,1
    And reinstall driver.
    Or to change(add) the appropriate value in the system registry.
    Is this possible inclusive in an interface with FT232BL with external eeprom?

    Enviado desde mi Life One X mediante Tapatalk

  3. #5058
    Top Poster
    Join Date
    Apr 2010
    Location
    RF
    Posts
    133
    Thanks Thanks Given 
    1
    Thanks Thanks Received 
    39
    Thanked in
    21 Posts

    Default

    Quote Originally Posted by eliotroyano View Post
    Is this possible inclusive in an interface with FT232BL with external eeprom?
    http://www.ftdichip.com/Support/Docu..._AN_000073.pdf.
    Part: "5.6 Disable EEPROM Writes".

    But better read all document.

    Or
    http://www.ftdichip.com/Support/Documents/AppNotes.htm
    Last edited by magadan; 14th July, 2017 at 01:43 PM.

  4. #5059
    Junior Member
    Join Date
    Feb 2017
    Location
    Poland
    Posts
    25
    Thanks Thanks Given 
    18
    Thanks Thanks Received 
    7
    Thanked in
    5 Posts

    Default

    Quote Originally Posted by BASi77 View Post
    Perhaps this chip STM32F072 in LQFP64 package, it?s easier and cheaper, fully suitable for this device. What driver is used for this cable? This is emulation of FT232 functions on the CPU or substitution at the software level?
    Also, sorry I missunderstood that. What I ment is that it is probably CPU emulation of the FTDI chip.

    The .exe file is original by Ross-Tech. Sorry once again

  5. #5060
    Member
    Join Date
    Jul 2017
    Posts
    52
    Thanks Thanks Given 
    18
    Thanks Thanks Received 
    32
    Thanked in
    14 Posts

    Default

    Quote Originally Posted by ireun View Post
    ...The .exe file is original by Ross-Tech.
    It's necessary to check whether the original rt-usb.dll and whether it changes after applying VCDS setup.exe.
    Last edited by BASi77; 16th July, 2017 at 08:18 AM.

  6. #5061
    DK Veteran

    Join Date
    May 2010
    Posts
    634
    Thanks Thanks Given 
    140
    Thanks Thanks Received 
    195
    Thanked in
    123 Posts

    Default

    Quote Originally Posted by ireun View Post
    [...] What I ment is that it is probably CPU emulation of the FTDI chip.

    [...]
    In this chip are emulated more: FTDI, ATMEGA, MPC2515, GAL/ATF.

    In the neighborhood of uC and Xtal 8MHz exist another chip, SOIC8 case. I don't see if is MPC2551, 2561 or TJa1050 or..another CI for CAN.

    And, the quwstion is: what uC exist in new original HEX-V2 cables?

    If is the same or again a big "Fssssss"

    A person said me "First two times we wil show you how to make updates, after will make yourself".
    Asked and person answered "update mean COPY-PASTE one or few files"

    In my opinion, this seems to be like in "multilanguage solution.
    But another person said: "No, you only use OEM installer"..
    2 different opinions, not OK. But this is only discutions, i wait my "V2" arrive for make tests.
    Last edited by liviudiaconu; 17th July, 2017 at 06:21 AM.

  7. The Following User Says Thank You to liviudiaconu For This Useful Post:

    paro44 (17th July, 2017)

  8. #5062
    Junior Member
    Join Date
    Feb 2017
    Location
    Poland
    Posts
    25
    Thanks Thanks Given 
    18
    Thanks Thanks Received 
    7
    Thanked in
    5 Posts

    Default

    Quote Originally Posted by liviudiaconu View Post
    In this chip are emulated more: FTDI, ATMEGA, MPC2515, GAL/ATF.

    In the neighborhood of uC and Xtal 8MHz exist another chip, SOIC8 case. I don't see if is MPC2551, 2561 or TJa1050 or..another CI for CAN.

    And, the quwstion is: what uC exist in new original HEX-V2 cables?

    If is the same or again a big "Fssssss"

    A person said me "First two times we wil show you how to make updates, after will make yourself".
    Asked and person answered "update mean COPY-PASTE one or few files"

    In my opinion, this seems to be like in "multilanguage solution.
    But another person said: "No, you only use OEM installer"..
    2 different opinions, not OK. But this is only discutions, i wait my "V2" arrive for make tests.
    Hey there! This chip for CAN connection is..



    As for the original V2.. On the website of HEX Microsystems.. http://www.hex.co.za/products/ You can find a photo of the PCB of original V2..



    Indeed it uses ARM ST chip, you just can't see which one exactly.. Though it's definitely larger package that on the clone..
    Attached Images Attached Images

  9. The Following 3 Users Say Thank You to ireun For This Useful Post:

    liviudiaconu (17th July, 2017), paro44 (17th July, 2017), Qwarz (17th July, 2017)

  10. #5063
    Newbie
    Join Date
    Jul 2017
    Posts
    7
    Thanks Thanks Given 
    0
    Thanks Thanks Received 
    0
    Thanked in
    0 Posts

    Default

    Please , does anyone know why this cheap cable (vcds409.1) is listed as NOT compatible with Audi A4 B7 (ok with oher A4 versions) ??
    Thank you

    image1.jpg

  11. #5064
    Member
    Join Date
    Jul 2017
    Posts
    52
    Thanks Thanks Given 
    18
    Thanks Thanks Received 
    32
    Thanked in
    14 Posts

    Default

    The original HEX-V2 enumerates as an HID device and does not require a special driver and for aliexpress ?HEX-V2?, it seems to me need a ftdi driver.

  12. #5065
    Member
    Join Date
    May 2017
    Posts
    72
    Thanks Thanks Given 
    3
    Thanks Thanks Received 
    2
    Thanked in
    2 Posts

    Default

    Hi all
    I buy also from china clone VCDS Hex V2 version 17.1.3. Today recived it and start test. Connect it to my notebook with windows 10 x64 and to my car Seat exeo 2010. After connect and start diagnostic on my intrument start blink some icons and bip bip bip and saved in some modules more errors. Example in engine, abs, tyre pressure and other. Some i can delete but some can not and must use my old vcds 11.11.5
    Before connect to car my car has no errors. After that i must use my old vcds to delete errors which was generate by VCDS Hex V2.
    Please help.

  13. #5066
    Top Poster
    Join Date
    Sep 2009
    Posts
    172
    Thanks Thanks Given 
    1
    Thanks Thanks Received 
    14
    Thanked in
    11 Posts

    Default

    That is not HEX V2.
    See test results window.

  14. #5067
    Member
    Join Date
    May 2017
    Posts
    72
    Thanks Thanks Given 
    3
    Thanks Thanks Received 
    2
    Thanked in
    2 Posts

    Default

    Ok but why not working and generate in modules in my car errors ?
    In test show Ross Tech Hex USB CAN
    Look on video what is problem...
    https://www.youtube.com/watch?v=GKxlidU0vLk

    In test on K1 show info SHORT TO +12
    But how find issue on PCB ?VCDS17.1.3.jpg

    20170721_111122.jpg

    20170721_111136.jpg




    I have old interface on ATMEGA chip version VCDS 11.11.5 and all works OK and on K1 and K2 and CAN show info OK.
    Last edited by pepeEL; 21st July, 2017 at 10:32 AM.

  15. #5068
    Member
    Join Date
    Jul 2017
    Posts
    52
    Thanks Thanks Given 
    18
    Thanks Thanks Received 
    32
    Thanked in
    14 Posts

    Default

    Quote Originally Posted by pepeEL View Post
    ... china clone VCDS Hex V2 version 17.1.3. Today recived it and start test. ...
    Could you copy the installation CD from the cable "HEX-V2" on ge.tt and post the link.

  16. #5069
    Member
    Join Date
    Jul 2017
    Posts
    52
    Thanks Thanks Given 
    18
    Thanks Thanks Received 
    32
    Thanked in
    14 Posts

    Default

    The message was deleted.
    Last edited by BASi77; 21st July, 2017 at 10:19 PM.

  17. #5070
    Member
    Join Date
    May 2017
    Posts
    72
    Thanks Thanks Given 
    3
    Thanks Thanks Received 
    2
    Thanked in
    2 Posts

    Default

    Can you explaine me more ? WHat i must do ? Remove this capacitor ?

    Soft is here on zippyshare
    http://www69.zippyshare.com/v/8F7atkRJ/file.html
    Last edited by pepeEL; 21st July, 2017 at 07:03 PM.

  18. The Following User Says Thank You to pepeEL For This Useful Post:

    BASi77 (21st July, 2017)

 

 

Tags for this Thread

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.