Using a borrowed Ross-Tech HEX-CAN cable to modify CAN gateway coding resulted in unexpected issues. Changes made and seemingly accepted would revert upon re-entering the module. Subsequently, a “cable not valid license” message appeared, followed by the cable no longer being recognized by Windows. Reinstalling VCDS and drivers proved unsuccessful.
Speculation exists regarding newer VCDS versions incorporating code to detect and potentially damage counterfeit cables. While unconfirmed, this aligns with the experienced malfunction. It’s suspected that this anti-counterfeit mechanism may have inadvertently bricked a legitimate cable.
Ross-Tech, unwilling to assist without a $150 service fee for the older cable, cites the need for servicing. The concern remains that the software itself caused the damage, raising questions about paying for a repair that might be susceptible to the same issue. Lack of support for potentially legitimate customers facing this problem is disconcerting.
Is cable repair possible without the hefty Ross-Tech fee? Has anyone else encountered this problem and found a solution? More importantly, what guarantees are there that a repaired cable won’t be bricked again by the software? This raises serious questions about the reliability and potential risks associated with using Ross-Tech VCDS software.
