topblog Ivoire blogs

12/07/2019

(Solved)kess v2 2.47 clone read ecu tmax 2007 error "Invalid protocol file"

Trying to use a kess v2 2.47 clone to read an ecu of tmax 2007 and when I click on its protocol I get the error ""Invalid protocol file".

sd-creation-guide-for-kess-v2-k-tag-01sd-creation-guide-for-kess-v2-k-tag-02

 

Possible reason:

You have maybe bad protocol file for this ECU on SD card.

 

Solution:

SD image needs to be created for CID Number SD-card.

Follow the below guide to creation SD card for Kess and Ktag:

 

 SD Creation Guide for Kess V2 & K-Tag (5.017 & 7.020):

Tools / Software that you will need:

  • Winhex (full version is recommended)
  • Xorfiles
  • win32diskimager

 

The files I used to do my Kess SD Card, where made / shared by Svvag2000 (Give a Big Thanks to him) and you can search online for this tutorial / files (Guide to creation SD card for Kess and Ktag):

  • Kess_5.017 (decrypted SD Image for Kess 5.017)
  • KTag_7.020 (decrypted SD Image for KTag 7.020)
  • KeyFileGenerator.cmd (Script to generate KeyFile needed)

 

You can review this video Svvag200 made for help on the procedures:

https://www.youtube.com/watch?v=sE2xVdhSFew

 

#1: Insert your SD Card in the Card Reader, and Open WinHex

#2: Hit F9 and Select the SD Card / Drive Letter:

sd-creation-guide-for-kess-v2-k-tag-03

 

#3: Select “Edit – Select All”

sd-creation-guide-for-kess-v2-k-tag-04

#4: Select “Edit – Fill Block”, and make sure value is “00” – Hit OK

sd-creation-guide-for-kess-v2-k-tag-05

 

Depending on your SD Card Size and reader/system, this might take a while. (my 16Gb Kingston took 30min. so, grab a few beers )

 

#5: After this is done, you need to remove the SD Card, and put in the device (Kess / KTag), connect to the computer and open KSuite.

Note: If you get the error “External exception EEFFACE”, don’t freak-out. I also had it. Just try several times, connect / disconnect tool from computer or try to leave the tool connected for some minutes, and them open again K-Suite. (I also had to try more than 10times with one of my cards)

Some say the protocols, should be “greyed out”, but in my case they where normal. When I tried to “open” the protocol it just gave me the “No Protocol Found” warning.

After this is done, disconnect the tool from computer and remove SD Card.

#6: Insert SD Card into the Computer, and Open again in WinHex (same as point #2)

#7: Select “Edit – Define Block” – End (Write the blocks we need to select and hit “OK”)

sd-creation-guide-for-kess-v2-k-tag-06

These are the Blocks Value: 000000D0 - 0000019F

 

#8: Select “Edit – Copy Block – Into New File” (a window will pop out for you to save this new file in the desired location)

sd-creation-guide-for-kess-v2-k-tag-07

 

Give the file name: “Key” and save it.

sd-creation-guide-for-kess-v2-k-tag-08

 

#9: Then we need to run the script / batch file “KeyFileGenerator.cmd”

sd-creation-guide-for-kess-v2-k-tag-09

 

Note: The “Key” file we generated, must be in the same location as the script/batch file.

Some files will be created, but we just need the “KeyFile.bin”, and it should have 127,139,792 bytes.

#10: We format the SD Card in FAT / FAT32 (I don’t think you guys need help on this one)

sd-creation-guide-for-kess-v2-k-tag-10

 

#11: We copy the content of the folder “Kess_5.017” (decrypted SD Image for Kess 5.017) to the SD Card.

sd-creation-guide-for-kess-v2-k-tag-11

 

#12: Then, we open again the SD Card in WinHex (same as #2)

#13: Then we do the same as #3 and #8 (Select All & Copy Block Into New File)

sd-creation-guide-for-kess-v2-k-tag-12

 

Note: Now, assuming your SD is bigger than ±122mb, we need to “cut” the image file we just made.

#14: Open in WinHex, the Image we just created (if you didn’t close, it might be already open in WinHex) and repeat the same operation as #7 & #8, but this time with this block sizes: 0-793FFFF

sd-creation-guide-for-kess-v2-k-tag-13sd-creation-guide-for-kess-v2-k-tag-14

This is the file we need to use combined with the “Key” file we made in #9. The file should have 127,139,792 bytes

#15: Now we open “XorFiles.exe” and select the files by this order:

FileName 1: KeyFile.bin (Created in #9)

FileName 2: Decrypt_SD.img (Created in #14)

FileName 3: This is the File we Need for our “New SD Card” – Give the Name and Location you like.

sd-creation-guide-for-kess-v2-k-tag-15

 

#16: New we just need to “Write” our Image file in the New SD Card.

Open and select the drive you want to “write”, select the Image File and hit “Write”:

sd-creation-guide-for-kess-v2-k-tag-16

 

After this is done, you can put the Sd Card in the Tool, and your all set…

(Finally, you can have some more beers )

NOTE: I´m not the author of any of the information shared in this file. I just put this together to make life easier to other people that might be finding hard to have this SD Card made.

All Credits must go to the Author of these Files (Svvag200), and at least to “pocinas” that made me clear point #14.

I hope this works for you guys… Cheers to All…

 

Big thanks to @ boxsport (DK forum member).

 

Last edited by Laurance on July 11, 2019.

 

www.obdexpress.co.uk

 

 

Source:http://blog.obdexpress.co.uk/2019/07/12/sd-creation-guide...

05:09 Publié dans Car ECU programmer | Tags : kess v2 | Lien permanent | Commentaires (0)

SD Creation Guide for Kess V2 & K-Tag (5.017 & 7.020)

Trying to use a kess v2 2.47 clone to read an ecu of tmax 2007 and when I click on its protocol I get the error ""Invalid protocol file".

sd-creation-guide-for-kess-v2-k-tag-01sd-creation-guide-for-kess-v2-k-tag-02

 

Possible reason:

You have maybe bad protocol file for this ECU on SD card.

 

Solution:

SD image needs to be created for CID Number SD-card.

Follow the below guide to creation SD card for Kess and Ktag:

 

 SD Creation Guide for Kess V2 & K-Tag (5.017 & 7.020):

Tools / Software that you will need:

  • Winhex (full version is recommended)
  • Xorfiles
  • win32diskimager

 

The files I used to do my Kess SD Card, where made / shared by Svvag2000 (Give a Big Thanks to him) and you can search online for this tutorial / files (Guide to creation SD card for Kess and Ktag):

  • Kess_5.017 (decrypted SD Image for Kess 5.017)
  • KTag_7.020 (decrypted SD Image for KTag 7.020)
  • KeyFileGenerator.cmd (Script to generate KeyFile needed)

 

You can review this video Svvag200 made for help on the procedures:

https://www.youtube.com/watch?v=sE2xVdhSFew

 

#1: Insert your SD Card in the Card Reader, and Open WinHex

#2: Hit F9 and Select the SD Card / Drive Letter:

sd-creation-guide-for-kess-v2-k-tag-03

 

#3: Select “Edit – Select All”

sd-creation-guide-for-kess-v2-k-tag-04

#4: Select “Edit – Fill Block”, and make sure value is “00” – Hit OK

sd-creation-guide-for-kess-v2-k-tag-05

 

Depending on your SD Card Size and reader/system, this might take a while. (my 16Gb Kingston took 30min. so, grab a few beers )

 

#5: After this is done, you need to remove the SD Card, and put in the device (Kess / KTag), connect to the computer and open KSuite.

Note: If you get the error “External exception EEFFACE”, don’t freak-out. I also had it. Just try several times, connect / disconnect tool from computer or try to leave the tool connected for some minutes, and them open again K-Suite. (I also had to try more than 10times with one of my cards)

Some say the protocols, should be “greyed out”, but in my case they where normal. When I tried to “open” the protocol it just gave me the “No Protocol Found” warning.

After this is done, disconnect the tool from computer and remove SD Card.

#6: Insert SD Card into the Computer, and Open again in WinHex (same as point #2)

#7: Select “Edit – Define Block” – End (Write the blocks we need to select and hit “OK”)

sd-creation-guide-for-kess-v2-k-tag-06

These are the Blocks Value: 000000D0 - 0000019F

 

#8: Select “Edit – Copy Block – Into New File” (a window will pop out for you to save this new file in the desired location)

sd-creation-guide-for-kess-v2-k-tag-07

 

Give the file name: “Key” and save it.

sd-creation-guide-for-kess-v2-k-tag-08

 

#9: Then we need to run the script / batch file “KeyFileGenerator.cmd”

sd-creation-guide-for-kess-v2-k-tag-09

 

Note: The “Key” file we generated, must be in the same location as the script/batch file.

Some files will be created, but we just need the “KeyFile.bin”, and it should have 127,139,792 bytes.

#10: We format the SD Card in FAT / FAT32 (I don’t think you guys need help on this one)

sd-creation-guide-for-kess-v2-k-tag-10

 

#11: We copy the content of the folder “Kess_5.017” (decrypted SD Image for Kess 5.017) to the SD Card.

sd-creation-guide-for-kess-v2-k-tag-11

 

#12: Then, we open again the SD Card in WinHex (same as #2)

#13: Then we do the same as #3 and #8 (Select All & Copy Block Into New File)

sd-creation-guide-for-kess-v2-k-tag-12

 

Note: Now, assuming your SD is bigger than ±122mb, we need to “cut” the image file we just made.

#14: Open in WinHex, the Image we just created (if you didn’t close, it might be already open in WinHex) and repeat the same operation as #7 & #8, but this time with this block sizes: 0-793FFFF

sd-creation-guide-for-kess-v2-k-tag-13sd-creation-guide-for-kess-v2-k-tag-14

This is the file we need to use combined with the “Key” file we made in #9. The file should have 127,139,792 bytes

#15: Now we open “XorFiles.exe” and select the files by this order:

FileName 1: KeyFile.bin (Created in #9)

FileName 2: Decrypt_SD.img (Created in #14)

FileName 3: This is the File we Need for our “New SD Card” – Give the Name and Location you like.

sd-creation-guide-for-kess-v2-k-tag-15

 

#16: New we just need to “Write” our Image file in the New SD Card.

Open and select the drive you want to “write”, select the Image File and hit “Write”:

sd-creation-guide-for-kess-v2-k-tag-16

 

After this is done, you can put the Sd Card in the Tool, and your all set…

(Finally, you can have some more beers )

NOTE: I´m not the author of any of the information shared in this file. I just put this together to make life easier to other people that might be finding hard to have this SD Card made.

All Credits must go to the Author of these Files (Svvag200), and at least to “pocinas” that made me clear point #14.

I hope this works for you guys… Cheers to All…

 

Big thanks to @ boxsport (DK forum member).

 

Last edited by Laurance on July 11, 2019.

 

www.obdexpress.co.uk

 

 

Source:http://blog.obdexpress.co.uk/2019/07/12/sd-creation-guide...

05:07 Publié dans Car ECU programmer | Tags : kess v2 | Lien permanent | Commentaires (0)

01/07/2019

Ksuite V3.37 free download and Kess 2 clone test results

Ksuite V3.37 free download, installation instructions, test reports...... Ksuite V3.37 or Ksuite V2.47 which one is reliable? If Ksuite V2.47 free download and test reports.

 

Ksuite V3.37 free download:

https://mega.nz/#!8JI0iKCD!3ir72eWkba3VBXVT6CW2WLCVybD0PQ...

No password

 

Ksuite V3.37 installation instructions:

1 Internet off

2 intstall ksuite.exe

3 plug in kessv2 hardware to pc usb port

4 run ksuite v3.37

5 start working( never use with internet )

 

Ksuite V3.37 test reports: All failure.

  1. it will not work, but it will not destroy a Kess V2 5.017 clone. the Problem is the clone will not be recognized by the Software and you cannot see the green button to start the procedure.

ksuite-3-37-01

 

  1. Ksuite V3.37 doesn't work with ktag 7.020.

software not recognized ktag.

 

  1. Did not work. Ksuite V3.37 redirects to the Alientech store website.

 

Therefore, Ksuite V2.47 is the newest and reliable version working fine with Kess V2 5.017 clone and Ktag 7.020 ECU programmer.

 

Crack Ksuite V2.47 free download on mega:

https://mega.nz/#!8QgwSboa!XLUqAJBt6ISsL4ijpdxZ68emHJa8EM...

Password: laura168.

After free update the newest ksuite v2.47, you can have extra 7400 Vehicles.

No need active, it's crack!

OS: Works on Win XP / Win7 32bit, Win 8, etc.

Multi-language available: English, German, Spanish, Italian, Portuguese, French.

Security: Yes, offered by obdexpress.co.uk engineer.

 

Crack Ksuite V2.47 workable Kess V2 Clone:

  1. SE137-C (green PCB)
  2. SE137-F (only main unit)
  3. SE137-C1 (red PCB)
  4. SE137-C2 (green PCB, Support Online EDC17 Protocols)

ksuite-247-pcb-se137-c

ksuite-247-pcb-se137-c1ksuite-247-pcb-se137-c2ksuite-247-unit-se137-f

 

Reviews on OBD Read/Write ECU with Ksuite 2.47 running Kess V2 5.017:

Opel Astra H 1,7cdti 2008 81kw denso ecu

Read/write ok no problem

 

Tested also on bosch me 7.1 golf 4 2,8 24v AUE engine read/write ok!

Edc16c31 bmw read/write ok!

Edc16u34/31 vag read/write ok!

 

Bosch me7.1 on 2,23 need to read trough 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

this is the difference between 2,47 vs 2,23.

 

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

 

With version 2.11 I already write flash for EDC17CP64 by obd, can't read it by obd, yes I write virtual file, it takes about 13mn to be written.

 

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 readed with Kess 2.34 Tricore and written with Kess 2.47 Tricore

 

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

i test in bench

 

BMW 320 E46 EDC16C31 OK

Ford Focus TDCI 1.6 EDC16C36 OK

Peugeot 307CC 1.6/PETROL ME 7.4.5 OK

 

Volvo EDC16C31 read-write on K-line...TESTED !

 

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.

 

Mercedes Sprinter 906 2008 edc16c31 Read write obd OK!

 

BMW Bosch EDC16+C35 via CAN Read/Write OBD ok

 

Volvo S40 continental SID803A read/write ok

 

BMW E92 M3 2008 Continental MSS60 read and write over OBD work without a problem

Audi A4 Engine: CABB 118 kW (160 HP) 1.8 l Bosch MED17.5 read over OBD OK!

 

Vag dq250 read / write no problem

 

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

 

Mercedes B180 CDI 2010 EDC16C32 R/W OBD....OK !

 

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

 

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

 

- Renault Latitude 1.5 Dci 110Hp Sid 305 - Ok.

 

- Ok audi q5 2.0tdi 2009 EDC17CP14 with protocol 501 work flawless add a good battery charger

 

- Tested on mercedes gla 220 cdi 4matic crd3

HW: 6519040800

SW: 6519027201

Ricambio: 6519010902

SW agg.: 6519030050

Impianto: CRD3-651-WMIA4D1

read, write and checksum ok, protocol 350

 

- Renault SID309 ok (car my 2015)

kess-v5017-eu-version-cover

Thanks.

Source:

http://blog.obdexpress.co.uk/2019/07/01/ksuite-v3-37-free...

08:29 Publié dans Car ECU programmer | Tags : kess v2 | Lien permanent | Commentaires (0)