Reviews on Edc15c11 Read write with kess, ktag, mpps, galletto

To read and write Bosch edc15c11 for a Volvo xc90 2.4d5 2005 model, which ecu programmer? how? what about kess, ktag, mpps etc?

1. MPPS: worked

Only boot mode
I’m did this ECU in boot with MPPS 

2. Kess V2 via bootmode: worked

I made a few of these ECUs from Kess V2 via bootmode without any problems.

Guide: Use the help files of ksuite… its easy…

3. fgtech galletto: worked

I read EDC15C11 just a few days ago with fgtech galletto

and used the diagram posted below:

No problem reading/writing. FYI, you have to make checksum before writing new file, since galletto does not support chksum correction on these ECUs

4. MPPS: worked too

Mpps in bootmode, use bosch generic protocol. Works fine done it several times.
Ore you can desolder chip and use a eprom programmer.
I had no sucsess with kess ore ktag. Ktag would only write backup, and not the 29f200 only.
I use ktag to make backup, and read and write 29f200 with mpps in bootmode.

5. fgtech galletto on boot mode… very easy.

Read documents boot mode fgtech…

 

Good luck!

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!3ir72eWkba3VBXVT6CW2WLCVybD0PQ9sppwg5Xux25s
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.

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

software not recognized ktag.

3. 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!XLUqAJBt6ISsL4ijpdxZ68emHJa8EMAvwLAq_ZRlZPg
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)

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)

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

How to rework clone KESS V2 green PCB in the correct method?

Because some people are making some good money out of it (rework clone KESS V2 green PCB ), let’s make it free for everyone.

PS: the following red parts are the correct method. 
Transistors to use : 
BCR112
MMUN2113
BC817

Murata filters:
NFE61PT472C1H9L (connect ground for all of them)

Correct method:

Connect MIDDLE PINS MURATTA FILTERS TO GROUND, not the signal

Capacitors:
1uF – 35V
220uF – 10V
10uF – 16V tantalum

Go Follow Picture.
I changed Voltage Stabilizators as well
1 x LM1117 3.3v
1 x PZT2907AT1G
1 x LM2575s 5.0V
all diodes SK14 (not required)
Micro SD Card to better quality if is NO NAME (BLANK on the top) but very carefull, is not easy just copy CONTENT, need generate againb becase another card have diffrent CID so will doesn`t work, if you copy 1:1

Compare with V5.017 Kess China clone green PCB:

BTW, reword has certain requirements on the user’s skills, please be careful. Invest the original one or the clone one will be better.

Thanks to @pocinas from DK forum.

Thanks Laurance editor.

SOURCE:http://blog.obdexpress.co.uk/2019/03/27/how-to-rework-clone-kess-v2-green-pcb/

Kess V2 unlocking Simos PCR 2.1 - connection, wiring, tips&guides

Possible to OBD unlock Simos PCR 2.1 with Kess V2 clone?

Look here: all information can be found here to help you unlock PCR 2.1 using Kess v2 china clone.

Connection:

ECU connection for the bootmode unlocking procedure only!

1. Connect the ECU to the bootloader adapter
2. Power up the bootloader adapter with a stabilized 12v power supply
3. Connect the cable 14P600KT02 to the 14P600BTLR adapter
4. Follow the instructions provided below

Wiring diagram:

1. Solder a wire to the CNF1 pin
2. Solder the 470 Ohm resistor on the two pads
3. Solder the 1K resister on the pad

 

Test:

Basic info:

Tested and confirmed working by me on 4 ecus /cars

only on Chinese clone not reworked unit: ktag 6.070, kess v2 v4.036, ksuite up to 2.15

Tips and guides of tools for use:

pcr 2.1 need to be as you know unlocked before writing .

On this ecu pcr 2.1, ksuite (kess v2 or ktag) seem to be more stable than fgtech on pcr but work too sometimes: i get error with fgtech on one pcr2.1 but no problem with ksuite . 

So if you have both tools , prefer ksuite seem to be more stable & flawlessly and car run ok .

After you get you ecu unlocked in boot mode , with fgtech just remove boot and left pin connection , and read or write on bench .

On ksuite tools , you can’t read or write with ktag , only unlock . (alientech need to work on it…)
with kess it’s ok , BUT , you can’t use the tricore module !

The problem is that the harness is plugged in the tricore module . so you have to build your own bench cable : just get a obd female plug on a scrapyard , and wire +12 gnd and can h/l (kline is not used but you can wire it it will make a universal bench cable) .

The trick to get communication error free on both fgtech and kess cable is to use a strong external psu .

when the tool id or read or write the ecu , the ecu will perform a kind of reset , and the big cap inside the ecu will go charging , causing a drop in voltage if your psu isn’t strong enough to handle it . THAT WILL CAUSE THE COMM ERROR . That’s the only thing you have to take care . 

when i made test with many little psu (like one you get with your tools) i have seen 7 volts drop some time , so the ecu is shutting down and no comm . 

you can use computer atx psu modded to work on bench (green wire plugged on ground to power on ) i think anything that can provide +12v 2A will be ok . i didn’t need more than 12v just a stable 12V . 14v unstable will not be ok 

that’s why on the car you have no problem , car battery can handle the cap charging current .

There is no immo caused comm error on this ecu , psu is the problem !!

So in conclusion : good psu and obd home made bench cable , remove tricore module on kess = 100% tested bench flashing solution for pcr2.1 .

 http://blog.obdexpress.co.uk/2018/11/12/how-to-obd-unlock-simos-pcr-2-1-with-kess-v2/

How to use Kess V2 without “Protocol not compatible with version FW”

I also solved the problem with Kess v2 clone, with error “Protocol not compatible with version FW”. Now the error no longer appears. Cheers!

I am using: Kess v2 clone firmware v4.036 with Ksuite v2.28

The error message: “Protocol not compatible with version FW”

Systems can be: Windows 7 and Windows XP….both OK

Here are the instructions:

Solution for Kess v2 FW protocol error

Here, I would like to show you step by step how to use your Kess v2 without the error “Protocol not compatible with version FW”.

To do this, you first have to uninstall the already installed software and the drivers.

Afterwards we start with step:

1. Disable Internet connection
2. Install the K-Suite 2.06 Full Version including drivers (Microsoft Visual C ++ 2005 SP1 and USBDEVICEDRV 1.00.011). The Kess device is not yet connected to your computer.
3. After successful installation, K-Suite will open automatically (no error message may occur during installation, otherwise you will have to repeat the installation). Select the desired language and exit the program.
4. Now you have to connect the Kess device via USB and wait for the automatic driver installation. (K-Suite not yet opens)
5. Right-click the K-Suite icon to open the file path. (Win-XP: right-click on the K-Suite icon, then open the properties, in the lower left you can open the file path) Marks the entire content in the folder and deletes it.
6. Opens the “Token Reset Folder” and copies the entire contents (it is the data from K-Suite 2.08). Now you change back to the already installed file path (here you just deleted all files) and insert the copied records. In addition, you copy the help folder (can be found on the supplied CD) and also paste it into the already installed file path. Now you can close all windows and start K-Suite.

The Kess device will now be updated. This may take a little time. As soon as the main menu of K-Suite opens, version 2.08 should be visible. The message “Protocol not compatible with version FW” should no longer appear. If everything was successful, you can close K-Suite again and install the updates (2.10, 2.12, … etc) one at a time. The Kess device can remain connected to the computer. The important thing is that you only install the updates. Not the drivers (Microsoft Visual C ++ 2005 SP1 and USBDEVICEDRV 1.00.011).

PS: If the error message “External exception EEFFACE” appears, you must close the program. Now disconnects the Kess device, reinstalls the version at which this error occurred. This time with the USBDEVICEDRV 1.00.011, but without Microsoft Visual C ++ 2005 SP1. After installation reconnect the Kess device and start K-Suite.

I currently have the version 2.32 Ksuite, and it works perfectly.

Hopefully this guide is understandable.

(BIG THANKS to the contributor; good info to share with kess v2 users in obdexpress.co.uk)