HexV2 Connecting, passing test,but not able to open modules

[ssullivan]

The cable and software were used on the car before, but for some reason gives "Failure to communicate (0)" when connecting to say, engine module. The software is out of date and the owner would prefer not to change anything on the tuning computer that worked before. It is a friend's car, computer, and cable but he showed me the receipt so I know it is a legitimate copy. Is there anything we can try to get it working again without updating?

 

[Derek]

From your screenshot it looks like the interface firmware is not a match for the VCDS software. I think the best way forward is to allow VCDS to update the interface firmware. This will only involve the config app downloading and installing the firmware to the actual VCDS HEX-V2 interface so if he is concerned about changes to the laptop, I don't think he needs to worry

Here's a video on the firmware update

Best regards
Derek

 

[ssullivan]

I believe he is more concerned about changes in features. How could this be mismatched if they are the same installation on the same laptop with the same cable? He bought it about 3 years ago.

Say we provide the receipt can this error be corrected without the update somehow? Or maybe reinstall with the 21.9.0 media he hopefully has?

 

[Derek]

OK, I don't think he needs to worry about features changing if he's worried about something being removed, but if that's his worry, let's gather some more information without making any changes for now

We'll need to wait for someone from Ross-Tech to answer fully, but in the meantime, ask him to open the config tool, click check for updates (note, that does not mean he has to apply the update yet if he does not want to) and post a screenshot so we can see the current firmware versions. That will help in understanding why they are not in sync now

Best regards
Derek

 

[Boki Ar]

I would add that the firmware update does not require power from the vehicle or externally.

I see 14V in the photo. USB connection is enough.

 

[Eric]

VCDS 21.9.0 requires CB 4555. If you got that exact version of the software to work before, it was with another interface with codeblock 4555 or higher. Or... if you got that exact interface to work before, it was with an earlier version of VCDS.

 

[Dr Sheldon]

The software is out of date and the owner would prefer not to change anything on the tuning computer that worked before.

That makes no sense - If he used it before then he clearly has changed something already !! That horse has bolted - Long gone !!

 

[Uwe]

The software is out of date and the owner would prefer not to change anything on the tuning computer that worked before.

He doesn't need to change anything on the computer, but the firmware in that HEX-V2 needs to be updated in order to work with the software he currently has on that computer.

Say we provide the receipt can this error be corrected without the update somehow?

No, it can't be corrected without either updating the firmware in the interface (which changes nothing on the computer) or reverting the VCDS software to an even older version (which does change something on the computer).

-Uwe-

 

[ssullivan]

Thanks for all the information, I asked him to look for the version he originally downloaded and will report back when we get it working, whether by downgrade sw or update fw

 

[AINils]

Why you didn't update software and firmware to solve all the issue?

 

[ssullivan]

It is a friend's car, computer, and cable

I believe he is more concerned about changes in features.

In addition, what you said was already recommended and acknowledged.