Ksuite 3.40 2.47 Download FREE + 100% Tested

Free download Ksuite 3.40 2.47 for ECU programming:

Part 1: Ksuite 3.40 2.47 download
Part 2: Ksuite 3.xx update info
Part 3: Ksuite 2.47 test report

in detail…

Part 1: Ksuite 3.40 2.47 download

Ksuite 3.40 download

https://mega.nz/#!E19l1arK!LGaSzd60MHfOuAlsX4HhHihhLa88pEAw-gugO_QITqI

Free version: unknown risk
Ksuite 2.47 download

Free version: unknown risk

https://mega.nz/#!UsFX0SzJ!wk4Z3H1FEED2WzgMeQbgWhszRagRC7g2L5yEHcykMq4

Tested version: 100% security

Part 2: Ksuite 3.xx update info

Ksuite 3.10 – Auto ECU Programmer Ksuite 3.43 Released Note:

Changelog:
K-SUITE 3.43 – KTAG TSM TC1724,TC1762,TC1767
K-SUITE 3.43 – KTAG TSM TC1796
K-SUITE 3.42 – KESS MERCEDES MED17 via OBD
K-SUITE 3.41 – K-TAG DELPHI DCM6.2AP, MARELLI 9GC, SIM2K, DENSO
K-SUITE 3.40 – K-TAG TRICORE SERVICE MODE TC1762 TC 1766 TC1767 TC1793 TC1797
K-SUITE 3.39 – KESS BMW MD1CS003 via OBD
K-SUITE 3.38 – K-TAG TRICORE SERVICE MODE TC1762 TC 1766 TC1782
K-SUITE 3.37 – K-TAG TRICORE SERVICE MODE TC1793
K-SUITE 3.36 – K-TAG TRICORE SERVICE MODE TC1767
K-SUITE 3.35 – KESS JEEP EDC17CP27 via OBD
K-SUITE 3.34 – KESS BMW G-SERIES MD1CP002 and MD1CS001 via OBD
K-SUITE 3.33 – K-TAG TRICORE SERVICE MODE TC1724
K-SUITE 3.32 – K-TAG MITSUBISHI , DENSO , KEIHIN, DELPHI, SID94
K-SUITE 3.31 – K-TAG TRICORE SERVICE MODE TC1797
K-SUITE 3.30 – MERCEDES EDC17CP46 via OBD
K-SUITE 3.29 – BMW MEVD17.2 , MEVD17.2.4, MEVD17.2.9 via OBD
K-SUITE 3.28 – MERCEDES edc17cp57 edc17c66 via OBD
K-SUITE 3.27 – NISSAN SH7055 and SH7058 via OBD
K-SUITE 3.26 – FIAT – JEEP  – MASERATI – LANCIA edc17c49 – edc17c79 via OBD
K-SUITE 3.25 – HONDA ACURA Keihin sh7058 and Continental mpc5554 via OBD
K-SUITE 3.24 – NISSAN INFINITI MEC100, MEC7x e DEA030 Hitachi ecu via OBD
K-SUITE 3.23 – BMW edc17 E series via OBD
K-SUITE 3.22 – CVN on VAG
K-SUITE 3.12 – DCM6.1
K-SUITE 3.20 – Bosch MG7.9.8  MEVD17.4.4 Motorola CM876
K-SUITE 3.19 – Toyota and Lexux OBD
K-SUITE 3.18 – Honda Civic Med17.9.3
K-SUITE 3.17 – Toyota Hilux Denso
K-SUITE 3.16 – SIM2K-240 Delphi DCM3.7
K-SUITE 3.15 – VAG BOSCH EDC17CP74 VIA OBD!
K-SUITE 3.14 – DSG MQB VAG TCU REMAPPING WITH KESSV2!
K-SUITE 3.13– DODGE RAM 1500 5.7 FROM TODAY IN OBD!
K-SUITE 3.12: BMW MOTORRAD BOSCH ME17.2 BMS-X IN OBD
K-SUITE 3.11: NISSAN LEAF!
K-SUITE 3.10: VOLVO DENSO VIA OBD!

Part 3: Ksuite 2.47 test report
polo tdi 1.6 2011
pcr 2.1
full by obd2 ok
my kess is real eu clone

porsche 958 turbo 2011 SIEMENS SDI8
read is by Virtual read ,for ME impossible
write i have message CHANGE STAT IMPOSSIBLE
NO SUCCES

new beetle tdi 105cv 1.9tdi 2004 edc15p
read ok

Opel Astra H 1,7cdti 2008 81kw denso ecu
Read/write ok no problem

bosch me 7.1 golf 4 2,8 24v AUE engine

read/write ok!
But on bosch me7.1 older software only ecu id read non read file , i have error “change speed read” something like that but i got that message also on 2,23ksuite i try all speed read but same error all time …

with older kess pcr2.1 when is unlocked no problem for kess read write min 10times no problem

Bmw Edc16c31 read/write ok!
vag Edc16u34/31 read/write ok!
So for now works like 2,23
Just to mention bosch me7.1 on 2,23 need to read trought protocol 64 i think , but on 2,47 read regular , choose on list model year hp engine code hit read work perfect no protocol need

Delphi (mercedes sprinter om651) read / write by obd
Ford fiesta 2008 1.6 tdi edc1634 read write by odb
VW passat 1.9tdi PDI read/write by obd
Mercedes w211 om646 read/write by obd

Edc17C46 writing on obd TESTED !

First I read with KTAG and after write with Ksuite 2.47.

Renault scenic 1,5dci 2007 delphi ecu ddcr read/wirte ok!
Vag edc15 read/write ok!
Bmw ms42 read/wirte ok!
Bmw ms43 read/write ok!
c220 w204.. delphi CRD3…read write ok..
VW Crafter Bosch EDC17CP20 Tricore External read-write OK!
w212 220cdi CRD 2.16 read write obd ok..

Golf 5 EDC16U1 OK
Sharan EDC16U31 OK
Passat PCR2.1 Write OK (ECU was already unlocked)
Alfa 147 ME7.3.1 OK
Audi A6 4G 2012 EDC17cp44 Obd Write ok!

Mercedes-Benz CLS 350 CDI BlueEFFICIENCY 4Matic 7AT with Bosch EDC17CP46 was read with Kess 2.34 Tricore and written with Kess 2.47 Tricore

BMW 320 E46 EDC16C31 OK
Ford Focus TDCI 1.6 EDC16C36 OK
Peugeot 307CC 1.6/PETROL ME 7.4.5 OK

BMW E92 M3 2008 Continental MSS60 read and write over OBD work without a problem
Vag dq250 read / write no problem
Audi A4 Engine: CABB 118 kW (160 HP) 1.8 l Bosch MED17.5 read over OBD OK!

Car: Audi A5
Year: 2008
Body type: Coupe
Engine: CAPA 176 kW (240 HP) 3 l
ECU: EDC17CP04
Read over OBD OK, write I don’t want to try my luck
Problem when reading and writing with Kess Tricore, checksum error!

Audi RS6 4F 5.0 TFSI V10 MED9.1 BUH
Read Master ECU OK -OBD
Write Master ECU OK – OBD
Write Slave ECU OK – OBD
When you write master ECU, fan are running, you need a good battery charger

Audi S8 V10 MED9.1 BSM protocol 196
Read Master OK
Read Slave OK
but incorrect File Size! 2.5 MB instead of 2MB
Write fail at 84%, car stuck in programming mode.
Don’t use on this type of car!

Audi A4 EDC17C46 03L906018HE
Write OK with a frf to bin file made with winols

VW TOURAN (EDC17c46)

can’t read on OBD, only in boot mode.

My tool is Kess 5.017 EU clone with red PCB. Did already so many cars successfully.
Also MED 9.1 but on VW GTI, Read/Write OK. But the S8 no chance, tried 7 times flashing and recovery by OBD with different files, also choose smaller File type with 2.048 KB for the Flash, KESS didn’t even start programing.
My experience with the tool:
EDC15V, P+ all R/W OK
EDC16U, U31, U34, C35, CP35, CP34, all R/W OK
EDC17CP14, CP20, CP44, C64, C46 Read via KTAG-Boot or virtual Read file, Write OK
MED 7.5.11 R/W OK
SIMOS 3.3, PCR 2.1 R/W OK (PCR first unlock with KTAG)
Denso R2AB R/W OK
and a few others i can’t remeber now

1-VW Golf 6 GTD edc17c46 Tprot tricore
Read and write without error CRC OK
2-VW Tigoun EDC17C64 GPT Tricore
Read and write without error CRC OK
3-SEAT LION EDC17C64 GPT TICORE
Read and write without error CRC OK

vag med17.5.21
GENERIC ERROR when i try to open file read by ktag

Golf 4 2.0 TDI 2017 year. EDC17c74 KESS V2 5.017 v2.47 with Obd write

Volvo EDC16C31 read-write on K-line…TESTED !
Volvo S40 continental SID803A read/write ok

MED17.1 2.0 TFSI Audi A5 tested without problems (VR)
EDC16CP34 3.0 TDI without problem
EDC17C64 Skoda Octavia without problem (VR)
only problem is on getting ID -> have to switch many times the ingnition on off. Then I get an error, that ID can’t be read. And after pressing OK it is showing the whole ID and I can save it.

Porsche 997 3.8S Year 2006
Bosch ME7.8.x CARTRONIC
HW: 0261207987
SW: 1037369642
Spare: 99761860101
SW upg.: 0041900007103A08
Installation: ME7.8.1
WRITE PERFECT OK
by k-line
tested in bench

Porsche Cayenne 4.5s Year 2004
Bosch ME7.1.1 Cartronic
HW: 0261207696
SW: 1037371766
N°.VIN: WP1ZZZ9PZ4LA43312
Moteur: 0041800144FI8SE4
SW màj.: 8SE4AKN0000 0133
Read ok
write NOT OK
message change speed impossible
i test in speed min and maximun
SAME PROBLEM

Mercedes Sprinter 906 2008 edc16c31 Read write obd OK!
Mercedes B180 CDI 2010 EDC16C32 R/W OBD….OK !
MB A180 CDI and B180 CDI, both EDC16c32 R/W OK! Write time very short, but fans running!
Ford Galaxy Delphi DCM3.5 R/W OK!
BMW Bosch EDC16+C35 via CAN Read/Write OBD ok
BMW Z4 35i E89 Siemens MSD81 Read/Write OK! Reading time about 50 min.

BMW E70 X5 Bosch EDC17CP09
Bootloader Tricore Protocol 226
Read OK
Write Not OK, problem with checksum correction
After writing with K-Suite 2.34 no problem with starting engine

Opel Combo 1.3cdti Obd2 Read/write ok!
Fiat Linea 1.3cdti MJ8DF Obd2 Minimum Speed Read/Write Ok! Note:Kline reading time 2 hours…

Today I try to read with kess VW Golf 1.6 tdi pcr 2.1 via OBD and I read it.
ON id it says it locket, but I read it without problem.
But when I select to read eeprom, it cant.
I didn’t try option to unlock ecu.
Here is the picture where I am read with kess.
Later i read file with winOls to see structure, and I think that is all ok.
VW Golf 6 2012
1.6 tdi 66 kW

kess-v2-ksuite-2.47-Golf-6-test-1
kess-v2-ksuite-2.47-Golf-6-test-2

Hyundai IX35 EDC17CP14
Read: Bootmode
Write: OBD
WORKING PERFECT !

It doesn’t read on OBD, and this was the safety, but before I read with Kess, I make a full backup (Micro+EEprom) with Ktag. I have important the safety.

Autel Maxisys Bluetooth Vehicle Communcation Interface (VCI)

General Notice

The Bluetooth Diagnostic Interface has been carefully designed and tested to comply with OBDII protocols. However, some vehicle models are not in full compliance with these protocols for various reasons. In addition, the computer control systems or sensors on any given vehicle may be malfunctioning. While Autel’s testing and the experiences of the users have shown the unit to be safe and reliable, there is an inherent risk in using any product that may potentially affect the operation or drive-ability of your vehicle.

If you are concerned about the operation of your vehicle at any time while using the Bluetooth Diagnostic Interface: ? Pull off the roadway immediately or as soon as it is safe to do so. ? Disconnect the device from the OBDII port. ? Consult a licensed mechanic or automobile service center. Contact your local distributor, or visit www.auteltech.com for issues or concerns about the product. We maintain an active database of the feedback we receive, and your comments can help us continuously improve the product.

Introduction

The Bluetooth Diagnostic Interface is a multi-brand device which comes with the Autel Maxisys kit. It is designed to connect wirelessly with the MaxiSys Display Tablet, as well as standalone PCs, as a vehicle communication interface (VCI) for vehicle data transmission. Thanks to the wireless Bluetooth technology, with which you are allowed to work freely around the vehicle. This interface device can communicate with vehicles’ electronic control units (ECUs), guaranteeing performance and speed that redefine multi-brand diagnostics. The development of this interface has been focused on reducing the communication time, and ensuring the tool is practical to use.

Autel Bluetooth

The MaxiSys diagnostic platform combines the VCI device and the display tablet with technical information into a single program, ensuring quick and simple access to the vehicle to perform comprehensive diagnostics applications.

Wireless Communication

The Bluetooth Diagnostic Interface supports Bluetooth communication. It can transmit vehicle data to the MaxiSys Display Tablet without a physical connection. The working range of the transmitter through Bluetooth communication is about 755 feet (about 230 m). A signal lost due to moving out of range automatically restores itself when the display unit is brought closer to the VCI unit. For detailed information about VCI connection with the MaxiSys display tablet, please refer to the MaxiSys User Manual.

USB Connectivity

The VCI device also provides a direct connection to the MaxiSys display tablet or a PC via a USB 2.0 full-speed connection. All of the electronics are contained in the device shell, making it a compact and rugged vehicle communication tool.

Power Source

The Bluetooth Diagnostic Interface operates on 12-volt vehicle power, which it receives through the vehicle data connection port. The unit powers on whenever it is connected to an OBD II/EOBD compliant data link connector (DLC). It can also be powered through connection with a PC via the USB cable, so there’s no need to connect the device to the vehicle when performing firmware update through the PC.

Functional Description

The Bluetooth Diagnostic Interface device package, which includes the unit, user manual, and a CD with driver program and update agent, comes along with the MaxiSysTM/MaxiSys MiniTM tool kit. Please refer to the MaxiSys User Manual for additional information.

1. Vehicle Data Connector (DB15-Pin)
2. Power LED
3. Vehicle LED
4. Error LED
5. Bluetooth LED
6. USB LED
7. USB Port

Vehicle Data Connector

The vehicle connector connects the device to the vehicle’s DLC via a standard DB15 – Pin OBD II cable.

Status LEDs

There are 5 status LEDs on the front panel of the VCI device, which indicates its working status as well as the hardware conditions, and are very useful for troubleshooting the device’s communication or connection to the Vehicle, display tablet and/or the PC. See Table 1 for detailed description of the status LEDs.

Table 1 – Status LEDs on the Front Panel

USB Port

The USB port provides the easiest connection between the device and the display tablet or the PC via a USB cable, and is used to control the device from the software application running on the PC.

Technical Specifications

Capabilities

When used in conjunction with the display table or the OEM softwares from the PC, the Bluetooth Diagnostic Interface device is able to perform the following functions: ? Auto diagnostics to read and clear the error memory, to display system parameters and the status of the ECU; ? Activation, adjustments and configurations that are essential for ensuring a complete repair; ? Resetting the service lights or the airbag systems; ? Configuration of the ECUs, keys and remote controls, etc

Product Troubleshooting

This part describes problems that you may encounter while using the VCI device.

Vehicle Linking Error

A communication error occurs if the interface device fails to communicate with the vehicle’s control module when performing diagnostic procedures. You need to do the following check-ups: ? Verify that the ignition is ON. ? Check if the interface device’s OBD II connector is securely connected to the vehicle’s DLC. ? Turn the ignition off and wait for about 10 seconds. Turn the ignition back to on and continue the operation. ? Verify the control module is not defective.

PC Communication Error

Verify the interface device is powered, and the green power LED is illuminated. ? Check if there is any firewall software interfering with the connection port. ? Check if the green status light is illuminated for USB communication. If these issues have been addressed, verified, and you are still having trouble, please contact technical supports for assistance. Refer to the MaxiSys User Manual for additional information.

Driver Setup

In order for the Bluetooth Diagnostic Interface device to operate correctly with the diagnostic applications on the PC, you will need to first install the device’s driver onto the PC that controls the device. The program package requires Windows XP, Windows Vista (32 or 64 bit), or Windows 7 (32 or 64 bit).

IMPORTANT: Do not plug the interface device onto the PC until you have installed the driver program.

The following steps may vary depending on the operating system or components that are installed on your computer, but in general this is the standard installation process. 1 Insert the CD that came with the MaxiSys tool kit into the CD/DVD slot of the PC. The driver installation wizard will load momentarily. Follow the Setup Wizard instructions to complete the whole installation process.

2 Click on “Next” on the welcome page.

3 Select “Next” on the installation location and installation name. It is recommended not to change the default settings; otherwise the computer may have a hard time recognizing the driver.

4 Click on “Install” and the driver program will be installed onto your PC. NOTE: During this part of the process a MS-DOS style window will pop up and may remain on your screen for a short while, which is perfectly normal. Do not attempt to close the MS-DOS style window manually as this will prevent the device driver being installed successfully. It will close automatically when the device driver installation is complete.

5 When the driver is successfully installed, a confirm window will appear.

6 Click on “Finish”, and connect the interface device to the PC’s USB port.

8 Select “Install the software automatically (Recommended)”, and click on “Next”. After the progress bar finishes, click on “Finish”. Users have finished installing at this point and can run the software working with the interface device.

Firmware Update

Autel periodically releases updates to the device’s drivers. Updates are necessary to solve specific problems and to ensure the VCI device is working properly with the OEM software. If you are experiencing any problems during use, always make sure that you have the latest device software and drivers.

Update Online

This function allows you to update the driver software for the device through the PC. Make sure the PC is connected to the Internet before using this function.

1 Power up the interface device and connect to the PC via the USB cable.
2 Verify the Power and USB LEDs on the front panel are illuminated.
3 Click on “All Programs” from Windows Start Menu, find the “MaxiFlash Bluetooth” entry under “Autel”, click on “UpGrade”, and wait for the program interface to pop up.

Autel Maxisys Bluetooth

4 Select the “Update” tab and the update agent will automatically check for the available update online.
5 Press the “Next” button to install the newest firmware.
6 Press the “Cancel” button to exit.

Warranty and Service

Limited One Year Warranty

Autel warrants to its customers that this product will be free from all defects in materials and workmanship for a period of one (1) year from the date of the original purchase, subject to the following terms and conditions: 1) The sole responsibility of Autel under the Warranty is limited to either the repair or, at the option of Autel, replacement of the device at no charge with Proof of Purchase. 2) This warranty does not apply to damage due directly or indirectly, to misuse, abuse, negligence or accidents, repairs or alterations outside our Service Center or facilities, criminal activity, improper installation, normal wear and tear, or to lack of maintenance. 3) Autel shall not be liable for any incidental or consequential damages arising from the use, misuse, or mounting of the device. Some states do not allow limitations on how long an implied warranty lasts, so the above limitations may not apply to you. 4) All information in this manual is based on the latest information available at the time of publication and no warranty can be made for its accuracy or completeness. Autel reserves the right to make changes at any time without notice.

Service Information

If you have any questions, please contact your local distributor or visit our website at www.auteltech.com. If it becomes necessary to return the tool for repair, contact your local distributor for more information.

What is the best universal auto key programming tool

Look here: How to choose a decent car key programmer for universal vehicles?

Good to know:
Lonsdor K518S is the most populous key programming tool in the year 2019.

It is the updated version of Lonsdor K518ise, an universal key programmer for all makes from Europe, America, Asia incl. a lot cars made in China. It  features built-in Volkswagen 4th 5th adapter & RFID transponder reader / writer, Toyota/Lexus smart key all keys lost via OBD and free BMW FEM key programming (for all keys lost, enter 32-bit ISN code). Besides, Lonsdor is good at Volvo, Maserati, Ferrari, Lamborghini, Bentley, Nissan etc. And it has no token limitation.

Look here: Lonsdor has a wide vehicle coverage

Europe:
Audi, BMW, Benz, VW, Volvo, Citroen, Ferrari, Maserati, Fiat, Lamborghini, Jaguar, MG,
Land Rover, Bentley, Lancia, Opel, Peugeot, Porsche, DS, Renault, Alfa Romeo, Smart,
Borgward

America:
Cadillac, Chevrolet, Dodge, GMC, Buick, Hummer, Ford, JEEP, Lincoln, Mercury

Asia:
Honda, Hyundai, Isuzu, KIA, Lexus, Mazda, Mitsubishi, Nissan, Ssangyong, Subaru, Suzuki,
Toyota, Shigaoka Queen

China:
Iveco, Trumpchi, BYD, Geely, Chery, Great Wall, Young Lotus (Basically all Chinese car
models are included)

in detail…

How to make VAS 6154 or TC XS work as PIWIS3 PT3G

There is only 3 ways that the VAS 6154 or TC XS will work as Porsche Piwis 3

1. you flash the GL123…… from VAS to pt3 (you will get also the Serial from the Donar)

2. You use some home made firmware (serial from VAS will stay there also you can see on the webserver that the emergency firmware is still VAS or TC XS)

3 you use the same way like the VCX do it. after the Piwis system will think it is a PT3G.
the VCX do the same

You buy a original or any decent china clone PT3G remove there the GL128, read the data out buy some new GL128 progamme it with the data and solder the ic back to the vas interface and you are done.

But you have to know the risked, we damage the pt3g and have to repair the board, we have to manufacture a plastice to fix the bold GL128 back on place right place you have only 1 chance.

for me as a solution to much work.

I paid some people to make some firmware but until now no 100% working firmware.

The last solution is the easy.
You just buy a xvc after the xvci is working on your system you change all know xvci data to vas 6154. and you are done.

You have to do it after every update.

last version is

you just pay some porsche sparepartmanager some money and order there your pt3g.

but than you will not get the interface for 1400€

Thanks to kiranabc for his contribution

GM Tech2 Diagnostic Scanner Descriptions

If you are looking for a car diagnostic tool, you could think of Tech 2 Scanner. This post will offer more information about it.

Tech2 scan tool Features

1) Authentic GM software in the Tech 2 Flash means the most comprehensive diagnostic software available for late model GM vehicles.
2) Support for on-board diagnostics on all GM systems 1992 thru 2011.
3) Removable hardware modules provide insurance against scan tool obsolescence.
4) Large, easy-to-read backlit screen.
5) RS232 & RS485 ports provide the avenue to connect future devices to your OBD2 Scanner Tech 2 Flash.
6) Ability to capture stored DTCs, Freeze Frame, and Failure Record for later review.
7) Ability to view the status of vehicle diagnostic tests as they run.
8) Bi-directional The authentic GM 1992-current year software will provide full bi-directional control when performing power train, chassis, and body diagnostics.

Tech2 Specification:

1) Dimensions: 12
2) Microprocessor: 32 bit,16 MHz
3) Memory: 32 MB flash type II PCMCIA. Type III slot available for future expansion.
4) Communications: Integral RS232 communication port.
5) Screen: 3.8.8 backlit monochrome with full graphics capability: 320,40 pixels. Displays up to 9 vehicle parameters at once. Download Tech2 Brochure (5.2 Mb)

GM Tech2 Package List:

Tech-2 Flash Tester
32 MB PCMCIA Card with GM OE Applications
CAN diagnostic interface module(Candi) and instruction sheet download (199.2 kb)
RS232 cable and user manual
RS232-DB9 adapter
DLC Cable, DLC Loopback Adapter
12V Cigarette Lighter Power Cable
SAE 16/19 Adapter
NAO 12/19 Adapter
Battery Power Cable
Storage Case
TIS 2000 CD