MB Star C4 Xentry Mercedes Software HHTwin User Manual

HHTwin software is one parts of Star Diagnosis MB Star C4 Xentry Mercedes software.Many clients wanna know what is HHtwin software and which Mercedes vehicle & module HHTWIN supports? Bellow,OBD2tool.com share you the user manual of Xentry Mercedes HHTwin software.

All MB from late 80’s to 99 = HHT-WIN
All MB from 2001 to 2009 = DAS
All MB from 2010+ = Xentry

The year 2000 is a weird transition period — some MB made in 1999 but the model year is 2000 will be diagnosed from the 38-pin under the hood and thus use HHTwin. Other MB made in early 2000 and sold as a 2000 model will have the OBD port and the SDS will require the OBD cable to diagnosis….and will use DAS.

And then there are orphan cars, like some SLK models — some 2000-2001 SLK require the 38-pin.

I’ve even seen a 2000 E320 that had both 38-pin and OBD port — I could use either port to conduct a full diagnosis. That was funny.

Star Diagnoses HHTWIN supports modules on Mercedes vehicles:

HHTWIN should be able to read all Modules.
Having said that, for Model Years 1990 – 12/1993, the Roadster Soft Top Module has 30 possible fault codes associated with it.
Whereas for Model Years 1/1994 – 1996, the Roadster Soft Top Module has only 11 possible fault codes associated with it.

IMPORTANT: HHTWIN is updated to 2018.12 xentry mercedes software disk. Software released in 2017 and 2018 doesn’t come with HTTWIN. But now, it comes again!
MB-Star-C4-Xentry-Mercedes-Software-HHTwin

How to Install Xentry Mercedes Software HHTWIN on Windows 7 32 bit:

Disable UAC settings to “Never notify” -> Restart system if needed. It`s better to DISABLE idiotic Windows Defender too. Then, you could return UAC settings back.

First simply run HHT.exe, it will install HHT to C:\HHT, then start Xentry.OpenShell.XDOS.HHT.C4.exe/Xentry.OpenShell.XDOS.HHT.C3.exe … that`s all.
Some systems must be restarted at the end.

The problem with “–” version was fixed.
Delete C:\HHT directory and begin from the first step.
If you will update your Xentry.OpenShell.XDOS version … just apply the patch once again.

Xentry Mercedes HHTWIN Trouble Shooting:

HHTWIN setup on Dell D630 install
Error: I got my SDS last week , initially I chose the external USB disc option but have now installed it on my recently acquired Dell 630. Everything installed well, however when I get to the point of using it and it automatically goes to use HHT(as my car is a 1993 model)it says”diagnostic connector is being initialised” however then it says”com port assigned! close other use!”

I took this to mean I had it on wrong COM port and sure enough I had it on COM 1 but have changed it to COM 2 both on the machine XP and on the virtual XP machine ( I am using the RS232 connector to the 38 pin diagnostic connector) but it said the same thing again.

Solution: go to the windows system menu in control panel and under the harware section look at the com port assignmennts and make sure the com port you designated isn’t already assigned to something else.

also, does the dell630 have a dedicated RS232 com port or are you using a usb/pcmcia/cardbus to RS232 converter.

HHTwin resets the switches:
Error: How do I reset the switches with HHTwin? Or do I need a different software? My MUX is C3 Star.

MB-Star-C4-Xentry-Mercedes-Software-HHTwin-1 MB-Star-C4-Xentry-Mercedes-Software-HHTwin-2

Solution: you can’t reset the switches. you can clear error codes, but the switch state is what it is. DAS is telling you what the switch state is. Or at least what it thinks the switch state is.

you’ll need to examine the switches and see if either they are misadjusted, not connected, or not functioning.

How to use SDconnect C4 + XentryDAS on Macbook Pro

I’m running Xentry/DAS 2018.05 (not OpenShell) on my MacBook Pro together with SDconnect C4 via LAN cable and VMware. Works without problems.
Need bridged networking in VMware. And adjust the network settings/IP addresses.

VMware:

Use VMware Fusion Professional and and allocate enough resources to the VM.

Mac hardware specification:

MacBook Pro, Core i7, 16GB RAM, 512 SSD, 15″ 1GbE, SuperDrive, Mid-2012

Virtualization:

That is the magic of virtualization. If you can locate a copy of Star Diagnosis that was intended for the IBM ThinkPad T30 running Windows NT 4.0 Workstation, you could easily install Windows NT 4.0 in a virtual machine and replicate that environment with near native performance. If you prefer to use a Windows XP-based version, that is easily done as well, up to and including Windows 10 1709 or Windows Server 2016. Almost any computer you purchase now will not have drivers available for Windows XP, so either an old PC such as a Dell D630/D830 will allow you to install Windows XP natively and make it work, but virualization takes the headache out of that. OS X us built on UNIX, so it is a very stable host OS and can run nearly any version of Windows was a guest with easy, stability and performance. The only think I would refrain from doing at this point in time, is if you are using OS X 10.13 High Sierra, do not use APFS just yet. It still is not as stable IMO as HFS+. You certainly don’t want to introduce system instability when programming a control module!

Battery:
The battery life is good when running Windows in a VM, as OS X has excellent power management. Allocate at 2 cores to the Windows VM, and if using an XP-based version, 2048GB of RAM should be sufficient.

In detail…How to setup Xentry/DAS on a Mac OS X

It is very straight forward. I elect to not use the automated installation of Windows, as it automatically configures the partition sizes, formats them, etc. Instead, do a custom installation and select your ISO. It will then determine the contents of the OS ISO and select your low-level hardware components automatically, such as CD-ROM bus, HDD bus, etc.

For the network cable, it defaults to NAT, so it shares the IP of OS X, but cannot receive unsolicited network traffic due to the nature of NAT. You can select Bridged, and it can have an IP on the same subnet as OS X.

I think I would prefer to install my installation from scratch, as the pre-built images that are distributed have an unknown product key, and also could contain malware or other unwanted applications.

If you are installing the XP version of DAS/Xentry, specify your virtual disk to be about 120GB, and when Windows XP asks you to specify your partition size, instead of pressing Enter and allowing it to consume the disk specify 20GB and quick format as NTFS. Create the remaining three partitions in Disk Management after XP completes installation.

Also, the first thing you will want to do is install VMware Tools after XP installs. If you want to install all available updates for Windows XP, and download WSUS Offiline version 9.2.3 and it will get your all of the available updates that were released when XP reached EOL.

I have used 12.2015, but if I still used Star Diagnoses, I would revert back a few months to avoid the hard-coded timebomb that was implemented at the end of 2015.

Result:

I have used this setup for many years for control module programming and SCN coding with no issues.