Current Versions

Bumping for CB V0.4231 and FW 0.238 release.

They have various fixes and improvements to networking and comms with certain modules.
See changelog post for more details

Also DS 00000036
which has updated chassis file and ASAM data

--Shaun

Bumping for release of CB V0.4301

Includes a variety of fixes, including comms fixes for certain modules
Also several usability improvements
Also changes the behavior of the heartbeat led slightly. If the USB has power, but is not enumerated, the heartbeat led will blink red instead of green
This lets you know you may have a USB problem, or you plugged it into a USB charger port, which is fine so long as you aren't trying to talk over USB

Changes are listed below:

* Fix for reading DTCs from certain modules
* Don't check ASAM data in AP mode
* Changes to idle timer handling
* Heartbeat shows USB enum status
* Support for registration functions
* Fixes for some rods
* Fix for EEPROM sync


--Shaun

Bump CB V0.4304
Features:
* Background support for updating/clearing labels
* Fix for VCDS comms issue when clearing faultcodes with certain modules
* VCDS VIN api

Bump for VCDS 15.7.4.

Specific HEX-NET relevance: It allows users with 10-VIN HEX-NET licenses to add/register a new VIN from within VCDS rather than having to do via a browser.

-Uwe-

Uwe said:

Bump for VCDS 15.7.4.

Specific HEX-NET relevance: It allows users with 10-VIN HEX-NET licenses to add/register a new VIN from within VCDS rather than having to do via a browser.

-Uwe-

Click to expand...

Any other change?

New label files, some fixes for a coding byte-length problem, and other small stuff.

-Uwe-

Bump for CB V0.4305

Has the following fixes:
* Fix for HTTP retry in certain cases
* Avoid DTC in B7 TDI 2.5 fuel pump

Bump for DP 10000039

Has new label files.

Bump for CB V0.4309,
Fixes several problems that could interfere with loading current ASAM data, possibly also causing updates to loop
Also fixes a bug where mobile updates could show completion exceeding 100%

Bump for CB V0.4313 release:

Fixes a problem with coding length on certain modules
Shows the file size in FW download (USB only)
More fixes for rod redirect
Improvements to background file clearing
Initial support for MLB evo subsystems
Fix for certain UDS modules missing from autoscan
Fix SSID encoding of special characters in web config

Bump for DS 10000042
* Updated label and chassis data

I'm really confused by what's going on with the updates . . . I fired up my MacBook Air in BootCamp running Windows 10 Home recently and received a notice that VCDS release 15.7.4 is available. It uploaded in the background but I didn't have the HEX-NET interface so I shut down after the update. Today I attempted to use the device on my wife's new '16 Golf TSI SE HB and each time I attempt to update via the <Port and Protocols Options> test tab for USB I receive a message stating port status OK, interface found version: CB 0.4215.4, FW: 0.223, WiFi: 310C Status Firmware Update Required! IP:10.0.1.83, K1: NO POWER, K2: NO POWER, CAN: Testing, VBat: 0.03V, Vlgn: 0.02 Press [OK] to open VCDS-Mobile firmware update. Press [Cancel] to abort.

So I press [OK] and it shows a file downloading (HexNetConfig.jar, 5.16MB) and I receive a dialogue box asking my in Internet Explorer "What do you want to do with HexNetConfig.jar?" My options are Open, Save and Save As. When I attempt to launch the HexNetConfig.jar it takes me to an Internet Explorer page stating the it "Can't reach this page"

Do I need to force Windows 10 to launch the HexNetConfig.jar download to open in another app and, if so, how do I go about that process?

I'm sure there is a very quick & easy solution . . . I just haven't figured it out yet!

Thanks in advance for your assistance!!!

Sincerely,
Paul

The HEX-NET Config utility currently requires Java. Go to java.com and download the latest release.

Santos said:

The HEX-NET Config utility currently requires Java. Go to java.com and download the latest release.

Click to expand...

Yes, I downloaded the most recent version of Java hence the reason why I'm asking why it is attempting to open in Internet Explorer instead of a different app.

the file association with your windows 10 is not correct. Quick fix appears to be reinstall java. You can also manually launch the file using command line. See this microsoft forum post for more info. http://answers.microsoft.com/en-us/...0/7cc493cf-507f-4494-bb52-c8ef6e202902?auth=1

Windows 8.1 and 10 sometimes botch up the .JAR file associations. There was a fairly straightforward downloadable fix for that, but I'll be darned if I can find it right now.

-Uwe-

Uwe said:

Windows 8.1 and 10 sometimes botch up the .JAR file associations. There was a fairly straightforward downloadable fix for that, but I'll be darned if I can find it right now.

-Uwe-

Click to expand...

Found it! http://johann.loefflmann.net/en/software/jarfix/index.html

Thanks - I'll give it a shot!!!

McSpiffy said:

Thanks - I'll give it a shot!!!

Click to expand...

Jarfix worked perfectly!

The next twist is no matter how many times I try updating (attempted both USB ports without success) I receive an error stating, "Version mismatch detected. Update may have failed." In the dialogue box it shows the following:
Update found!
Updated rod data needed

Changeling:
Applying update . . .
Downloading BL
Downloading DS update
Unpacking DS update
Version mismatch detected. Update may have failed.

Current versions
CB: 0.4313
FW: 0.238
CFB: 0.10
BL: 0.26
DS: 10000042

New versions
BL: 0.27

I tried downloading the HexNet.jar again and launch but I receive the same error.

Not sure if its worth removing the software and re-installing or if that will cause an issue.

Thanks in advance for your help - I really appreciate it!

We should stick that link in the FAQ or 1st post. I couldn't run Java on a clean (non-upgraded, freshly formatted partition) Win 10 PC until I ran it a while ago. I don't think reinstalling windows would have helped in my case since the botch existed from the beginning with that OS.