topblog Ivoire blogs

01/11/2016

V2.04.87 Volvo Premium Tech Tool Download

Free download Volvo Premium Tech Tool PTT software 2.04.87 here and get all info.

 

premuim tech tool version 2.04.87 highlights:

* Last official version Volvo TechTool 2.04.87 Development (or non official 2.5.30)

* Full Techtool Activating (For all volvo brand !!!)

* Last ACPI+ update for standard and for development AND special DESIGNER user !!!

* You can Choose User ID like: A123456 or M555555 OR TECHTOL OR ANY OTHER..

*You can choose your logo or name to stay in techtool

ptt-developer-tool-software-2-04-85

premium tech tool download:

premium tech tool software v2.04.87

https://goo.gl/IosntW

V2.03.20 volvo premium tech tool download

https://goo.gl/lqdY6n

 

premium tech tool free download:

https://goo.gl/3gCQ0b

 

OS requirement:

Windows 2003/XP/Vista/7/8/10

 

Workable device:

Volvo 88890300 Vocom Interface

 

Premium tech tool manual:

https://goo.gl/7mH2eG

source:http://blog.obd2express.co.uk/2016/10/31/v2-04-87-volvo-p...

31/10/2016

VVDI2 reviews on Key Program And Corretion Mileage

Test ok 

I added these keys experience with :
Added a key bcm2 on a 2013 Audi A5 worked flawlessly.

Add a spare key Audi BCM2 by OBD worked fine.

A6/Q7 EZS Kessy:

Added a dealer key (remote source from the dealer) without issues, seemed to read everything properly but I had a working key to begin with.

Audi A6:

Tested with A6 read kessy working, learned new key

Skoda Octavia 2006:

Got CS & PIN, programmed key fine.

VW Passat B5:

Pulled PIN and programmed key ok.

VW Passat B6 2009:

Pulled PIN but couldnt get 6 bytes CS, needed comfort dump.

VW Transporter T5 2006:

Pulled PIN Programmed key, no remote programming.

I use VVDI2 to change mileage on following cars:

Audi A4 2006:

Mileage correction success

2007 Audi A4 B7 RB8 crypto

Mileage correction ok

VW Passat B5:

Corrected miles.

Fail:

Audi A6 2003:

Mileage correction fail. car not start. remove battery terminal. car start.

vvdi2-key-Key-Programmer

source:http://www.mileageprogrammer.com/vvdi2-test-key-program-a...

28/10/2016

DAS not recognize all ECUs through 38 pin cable,how to do

MB Star diagnosis DAS is working perfect on any car with the 16 pin cable and Xentry also is working perfect. But when DAS is connecting with the w210 car through 38 pin cable, DAS only recognize 3 ECUs then nothing, i changed the 38pin cable gives me the same result.

das-hhtwin-not-recognized-ecus

i used windows7 ultimate x64bit with Xentry openshell 5.2016, all patches and fixes are applied.

 

I changed the old cable with another HQ 38 pin cable, but the same problem!

tried on different car, same problem,
same car tested on old system (MB Star C3 Multiplexer+ Windows XP) works perfect

 

HHT-win system, simply a message said:" HHT-WIN is not available on this system"
but as per the photo only few ECUs are detected, then nothing....

 

 

User suggestion on this topic:

Depends on which W210 it is facelift or pre-facelift with FBS3 or older system? For facelift version have to working shortest through DAS. Pre-facelift version/older model is automatically switched to HHT-Win. For example as I remember W168 model year 2003-2004? /I forgot/ is full short test in DAS and then if you click on some ecus then is switched to HHTWin. Facelift W210 model have to working full short test in DAS. This is not HHTWin problem. Maybe your hardware have problem with connection to older cars.

 

Professional advice from mbstartool engineer:

It’s normal. DAS / HHTWin does recognize some ECUs only through 38 pin cable. And there is not ECUs in old cars as many as new cars.

On a side note, no need 38 pin cable if obd connection is ok.

09:37 Publié dans Blog, Shopping, Web | Tags : mb star c3 | Lien permanent | Commentaires (0)