HEX+CAN Interface not detected! :(

   #1  

Deplore

Verified VCDS User
Verified
Joined
Jul 11, 2014
Messages
5
Reaction score
0
VCDS Serial number
C?ID=220327
I vaguely remember that approximately month ago my VCDS stopped working, and it would not be recognized by VCDS, would throw "Port Status: OK" and interface not found!" message.

VCIConfig.exe also does not see it. I've seen previous posts here on this forum for this exact issue, and in device management it shows as "Ross-Tech Direct USB Interface".

PID and VID shows as USB\VID_0403&PID_FA24&REV_0600.

However, when I connect with a FTDI reader like FT_Prog from the FTDI website, it reads the FTDI eeprom on the VCDS and the serial number on it shows as RT000001. I'm reasonably sure this is my problem.

VCDS does not show the serial number when plugged in (in about menu its blank) and it just fails the test.

Is there anything I can do to repair this? I'm fairly handy with eeprom level stuff.
 
   #2  

Zenerdiode

Verified VCDS User
Verified
Joined
Jun 26, 2014
Messages
1,436
Reaction score
2,156
Location
Newcastle, England
VCDS Serial number
C?ID=24330
However, when I connect with a FTDI reader like FT_Prog from the FTDI website, it reads the FTDI eeprom on the VCDS and the serial number on it shows as RT000001. I'm reasonably sure this is my problem.

VCDS does not show the serial number when plugged in (in about menu its blank) and it just fails the test.
That’s not your problem. All HUC interfaces show the serial number as RT000001 with FTDI utilities. However, if you’re faffing around with FT-Prog or M-Prog you can destroy the interface license very easily and rightly so, you won’t get support from RT to repair that.

VCIConfig will only work with the newer interfaces - HEX-V2 or HEX-NET.
 
   #3  

Deplore

Verified VCDS User
Verified
Joined
Jul 11, 2014
Messages
5
Reaction score
0
VCDS Serial number
C?ID=220327
Oh. Then I'm at a loss to explain why HEX+CAN stopped connecting. It is noticed in the device manager, the PID and VID comes up correct (if the previous posts on this forum is anything to go by) and everything else looks good, just....no bingo?
 
   #4  

Uwe

Benevolent Dictator
Administrator
Joined
Jan 29, 2014
Messages
52,822
Reaction score
35,753
Location
USA
VCDS Serial number
HC100001
I'm at a loss to explain why HEX+CAN stopped connecting
What computer? What version of Windows? Plug it in, pull up Device Manager and show us the properties sheet. Drivers loaded?

-Uwe-
 
   #5  

Deplore

Verified VCDS User
Verified
Joined
Jul 11, 2014
Messages
5
Reaction score
0
VCDS Serial number
C?ID=220327
Any computer. I have access to easily over a dozen computers, it does it with all of them. W7, W10, W11, laptop, desktop, clean install, dirty install, doesn't matter. IDs the same.

Yessir, drivers loaded. I did select the legacy drivers in the VCDS install.

 
   #6  

Uwe

Benevolent Dictator
Administrator
Joined
Jan 29, 2014
Messages
52,822
Reaction score
35,753
Location
USA
VCDS Serial number
HC100001
^^^ That looks & sounds OK.

I'm scratching my head.

What's the status of the LED on the interface?

-Uwe-
 
   #7  

Deplore

Verified VCDS User
Verified
Joined
Jul 11, 2014
Messages
5
Reaction score
0
VCDS Serial number
C?ID=220327
Orange if USB only is plugged in, green if plugged in a car it my bench harness.
 
   #8  

Uwe

Benevolent Dictator
Administrator
Joined
Jan 29, 2014
Messages
52,822
Reaction score
35,753
Location
USA
VCDS Serial number
HC100001
Orange if USB only is plugged in,
Hmm... The LED on a HEX+CAN should not be lit at all when only plugged into USB, so that sounds like a hardware failure of some sort.

-Uwe-
 
   #9  

Deplore

Verified VCDS User
Verified
Joined
Jul 11, 2014
Messages
5
Reaction score
0
VCDS Serial number
C?ID=220327
Really? Damn, was afraid of that. Guess I'll have to spring for the new one.

Thanks for the assist.
 
Back
Top