Current Versions

I notice a new feature in 15.5.0. When I save autoscans (every car that comes in), I am now seeing a log and a scan saved in my logs folder. As far as I can tell, only the time stamp and some extra numbers are added into the scan file.

Is there a way to turn this off? When I save other information to the log i.e. fuel trim or how long the CEL has been on, it only saves to the log file. So any reason for two files being saved?

We got tired of hearing, "Yeah, I did an Auto-Scan, but I didn't save it..."

So Auto-Scans are now automatically saved as "Scan-[VIN]-[Date]-[Seq.]-[Mileage].txt"

Content of the "Scan" file should be nearly identical to content of a "Log-[whatever]" file that was closed immediately after saving an Auto-Scan.

At present, I don't think there's any way to turn this off. Maybe we should auto-delete it if the next button the user clicks is [Save]?

-Uwe-

Uwe said:

At present, I don't think there's any way to turn this off. Maybe we should auto-delete it if the next button the user clicks is [Save]?

Click to expand...

Yes, please.

The original proposal was to keep the auto-saved files in a separate folder, similar to what we do with the adp and coding logs - those should only be used as a fallback and wouldn't interfere with the regular log files. Now that everything lands in the same folder, well it is messy.

I have to agree, it is messy.

Saving them in a separate sub-folder called Scans would make sense, I think.

-Uwe-

I just did an update check on my HexNet and DS 00000033 was installed. You may want to update post #1.

Uwe said:

At present, I don't think there's any way to turn this off. Maybe we should auto-delete it if the next button the user clicks is [Save]?

-Uwe-

Click to expand...

This or a separate folder is a great option! There probably aren't many that actually search their autoscans regularly, but keeping them tidy is important to those of us who do!

Well, that depends on whether DS 00000033 is actually supposed to be on the release channel, vs. just the alpha channel.

-Uwe-

Uwe said:

Well, that depends on whether DS 00000033 is actually supposed to be on the release channel, vs. just the alpha channel.

Click to expand...

Seems to be deliberate.

OK, how did I miss that?

-Uwe-

Yes, DS 00000033 is on the release channel, just to avoid any confusion.
It has some new label files that have been on alpha for a bit, and minor fixes to certain pages.

TTT for VCDS Beta 15.6.1.

-Uwe-

excited for a new Dataset hopefully my baby got some love!

I'm usually trying to get label file related projects (which are then included in the datasets) done based on feedback and demand. Your maps are in the queue, starting with the ECM.

Codeblock V0.4215 is now on the release channel. It is designed to be used with a new version of the USB utility and has a number of new features, including but not limited to:

CB V0.4215
* Support for new update version 2.0+ update utility
* Fixes for certain CAN modules, particularly for service 22 ID
* TP1.6 tries to fall back to kline if it doesn't receive the sync byte
* Fixes for text measuring values (display and logging)
* Retry on no response to service 22 ID
* Fix for downloading ASAM data
* Fix for TP2.0 comms with certain ABS


New USB utility is found here:
New 2.xxx utilities for CB V0.42xx+
Windows/Linux: HexNetConfigV2.005.jar
Mac: HexNetConfigV2.005

There are also several other updates that go along with this, including a new dataset with improvements to VIN management and a new FW with some optimizations
Check the changelog for more details

Important Note: The first time you install CB v0.42xx, (from v0.41xx) you must do so using the web interface (VCDS-Mobile: [Options] -> [Check for Updates]. You cannot update from CB 0.41xx to CB 0.42xx using the PC-based utility. Once you've got a CB v0.42xx in your HEX-NET, the old utility v1.9xx is deprecated and can no longer be used. You should then replace it with the current v2.xxx utility, and you should be able to use the new utility for all updates after that. Of course, you should also be able to do updates via the web interface if you choose.

Problem updating.

I connected my HexNet to my iMac with the USB cable, and launched my VCDS-Mobile bookmark in Firefox 39. I clicked on Options>Check for Updates and was told there were updates so I clicked on Download Update. It did and got as far as the rebooting step then said Update Failed! When I tried again, I was told it could not connect to the server. I then launched HexNetConfigV2.005 and had it check and was told an update was found. Here is the log of what happened next:

Update found!

Changelog:
CB: 0.4204
Features:
* Fix for flag 80 handling
* Fix for comms timing, particularly with certain CAN ABS modules
* Support for new update functionality
Note: Update repeats for testing

FW: 0.223
Features:
* Improvements to EEPROM management


CB: 0.4215
Features:
* Support for new update version 2.0+ update utility
* Fix for service 22 ID
* Fix for mv/logging
* Fix for downloading ASAM data

DS: 00000034
Features:
* Improvements to VIN management

DS: 00000035
Features:
* New codes list
* New asam data

Applying update...
Downloading FW
Downloading CB
Error code -8, download failed


OK so I then went back to Firefox and checked for an update again and it found Dataset 00000034 which I said to download. This time I was told the update had been successful so I told it to check again. First it immediately told me the server had timed out! However I tried again and this time it found Dataset 00000035 which I said to download. About 20 minutes later I was told the update had been successful and I could use the HexNet, but before I could disconnect the USB cable, ANOTHER screen appeared saying "Updating ASAM Dataset" then after about 3 minutes of no progress, I was told the update had failed and to check my Internet connection! So I went back to HexNetConfig and IT found another update: BL 0.26 which was downloaded and apparently installed successfully. I then told it to check again and it found BL 0.27 which was then downloaded again apparently successfully as both HexNetConfigV2.005 and VCDS-Mobile through Firefox say I'm up to date.


Any idea as to why this is/was so cumbersome?

romad said:

Any idea as to why this is/was so cumbersome?

Click to expand...

It's going to be a bit of a pain no matter what, 'cause there's a lot if interdependent stuff coming out of Alpha here at the same time, but your update was complicated by a dependency mis-direction on the server; it should not have given you CB 0.4204 first; that's since been fixed.

-Uwe-

And VCDS Release 15.7.0 is now available.

-Uwe-

Uwe said:

It's going to be a bit of a pain no matter what, 'cause there's a lot if interdependent stuff coming out of Alpha here at the same time, but your update was complicated by a dependency mis-direction on the server; it should not have given you CB 0.4204 first; that's since been fixed.

-Uwe-

Click to expand...

Ah. It looked like VCDS-Mobile was choking on the CBs and the HexNetConfig was choking on the datasets. I figured I'd have to run the latter first next time for the CBs then switch to the former to get the datasets.

Update failed using VCDS mobile. Got CB updated though

CodeBlock V0.4215
FW version: 0.214
Dataset: 00000033


looks like HexNetConfigV2.005.jar is included in the 15.7 VCDS release

Been stuck at about 55% Applying update; shows 100% setting up for the last 30+mins...pulled the plug on it and reopened update.jar


progress but still:
CB: 0.4215
FW: 0.223
CFB: 0.9
BL: 0.27
DS: 00000033

repeat utility.jar and finally:
CB: 0.4215
FW: 0.223
CFB: 0.9
BL: 0.27
DS: 00000035