Kess V2 Harware Rework - FREE SOLUTION!

**pocinas** · 22nd April, 2019, 05:34 AM

I looking the code parts of U13 , U15 and U17.
Have problem.with kess " Connection estabilished"
I changed Nxp (thinking is broken) .. i changed FDTI and programmed with correct data. Still the same problem. U13

**elmer9** · 22nd April, 2019, 11:21 AM

Originally Posted by mandriao

Its is true refer. I see the manual SMD and have info of 33 value. More is "33a". Now see the correction. Thanks...

I think I found the suppressor
https://www.mouser.it/ProductDetail/...SAAEgJDuPD_BwE

suppressore.jpg
PCB green ori kees, PCB violet EU kess

link datasheet full
https://www.st.com/resource/en/datasheet/sm6t.pdf

press thanks if I helped you

**Jupiter199** · 22nd April, 2019, 12:17 PM

Originally Posted by pocinas

I looking the code parts of U13 , U15 and U17.
Have problem.with kess " Connection estabilished"
I changed Nxp (thinking is broken) .. i changed FDTI and programmed with correct data. Still the same problem. U13

" Connection estabilished" is when Ksuite not see FTDI or wrong data in FTDI.
Did you program data in FTDI after replacement?
If NXP can't answer for message Ksuite error is "EEFFACE"

**pocinas** · 22nd April, 2019, 05:29 PM

Originally Posted by Jupiter199

" Connection estabilished" is when Ksuite not see FTDI or wrong data in FTDI.
Did you program data in FTDI after replacement?
If NXP can't answer for message Ksuite error is "EEFFACE"

Computer detect KESS, after replacment FDTI yes i programmed (have another working 5.017 so i used MProg and saved DATA FDTI from working Unit, and programmed New replacment FDTI)

i do it test, solder working FDTI chip from working unit in this broken pcb and the same problem.. so..think is somwhere problem... NXP chip is works as well because soldered from working unit as well. What i see, i compared some resistans value, and see very low resistans on the one capacitor (this middle close FDTI chip and between SD SOCKET CARD) have 75 ohm when working unit 15k ohm...

i desoldered U13 because one of this signal going to U13 but resustance is still LOW, will measured circuit i try find element which made me low resistance

**pocinas** · 22nd April, 2019, 08:20 PM

Originally Posted by Jupiter199

" Connection estabilished" is when Ksuite not see FTDI or wrong data in FTDI.
Did you program data in FTDI after replacement?
If NXP can't answer for message Ksuite error is "EEFFACE"

Thanks a lot, this little helps

Kess work.

Was 2 problems
1) Broken U17 74hct125 (after connect usb cable and wait couple second chip was warm and wormer) this is why was low reistance on this Capacitor, actually on the 5V line
2) Programmed content FTDI was wrong, strange because i take and save from working unit, (this working EPT i found on the internet from package 4.036)

**elmer9** · 23rd April, 2019, 10:04 AM

to empower the k-line change transistors and L9613,
to empower the can-line which integrated change?

**toreddu** · 27th April, 2019, 07:41 PM

Can you tell me which is the model with the red and green led that goes under the light guides? Can you also confirm me that the light guides are the right ones?

**elmer9** · 28th April, 2019, 12:48 PM

Originally Posted by toreddu

Can you tell me which is the model with the red and green led that goes under the light guides? Can you also confirm me that the light guides are the right ones?

I am fine 1206 (3216) led

**Jerak** · 1st May, 2019, 02:03 AM

Originally Posted by Jerak

So the ad said:
- The left upper corner and the lower right corner notch size is not the same
- WF = Infineon, BCR112 NPN Digital Transistor
- 27E = ON Semiconductor NUP2105LT1G
- 6DW = NXP BC817,215 NPN Bipolar Transistor
- A6c =MMUN2113LT1G / MMUN2113LT3G
- K5B = BC807-25-7-F PNP Bipolar Transistor
- Using imported Japanese Murata filter NFE61PT472C1H9L

I didn't get the PCB with the different corners but it is dated 2017.4.1.

The components are WF, 27E, 6DW, A6c and K5B but I don't know if these are the actual ones stated in the ad.
Anyone know if this is legit?

I tried this unit out with bootloader mode but couldn't find the protocol???
I need the EDC17 CP44 282 protocol that shows in the first page.
kessProb01.jpg
It doesn't show in the next page.
kessProb02.jpg
If I select the CP44 P268, I get wrong protocol with TOOL > ECU DATA.
I think that 1268 is for KTag.
This is KSuite 2.47, am I missing files?
Thank you.

**toreddu** · 1st May, 2019, 02:21 AM

Originally Posted by elmer9

I am fine 1206 (3216) led

can you show where to buy it?

can you show where to buy it?

**pocinas** · 1st May, 2019, 08:32 AM

Originally Posted by Jerak

I tried this unit out with bootloader mode but couldn't find the protocol???
I need the EDC17 CP44 282 protocol that shows in the first page.
kessProb01.jpg
It doesn't show in the next page.
kessProb02.jpg
If I select the CP44 P268, I get wrong protocol with TOOL > ECU DATA.
I think that 1268 is for KTag.
This is KSuite 2.47, am I missing files?
Thank you.

Dont have now laptop in hand now to confirm this what i write below but

Tried with ksuite 2.32?

On the internet is 2 diffrent cracked 2.47 ksuite. One with all protocols shows (including grey which doesnt work anyway) and 2nd without grey means all this grey protocols is deleted, you can check example in BMW F series. If exist Fxx series they you will see model and all cars but protocols is grey and when you click.somw.cars will.have messagw Protocol cant find.... or another version ksuite.exe is when F series dont exist because dont work anyway so.

The diffrent is just ksuite.exe file..rest should be the same.

**elmer9** · 1st May, 2019, 11:48 AM

Originally Posted by toreddu

can you show where to buy it?

can you show where to buy it?

https://www.mouser.it/ProductDetail/...EEkrWnfTiYIw==

https://www.mouser.it/ProductDetail/...EEkrWnfTiYIw==

press thanks

**elmer9** · 1st May, 2019, 11:53 AM

Originally Posted by pocinas

Dont have now laptop in hand now to confirm this what i write below but

Tried with ksuite 2.32?

On the internet is 2 diffrent cracked 2.47 ksuite. One with all protocols shows (including grey which doesnt work anyway) and 2nd without grey means all this grey protocols is deleted, you can check example in BMW F series. If exist Fxx series they you will see model and all cars but protocols is grey and when you click.somw.cars will.have messagw Protocol cant find.... or another version ksuite.exe is when F series dont exist because dont work anyway so.

The diffrent is just ksuite.exe file..rest should be the same.

what is the best version?

**Jerak** · 1st May, 2019, 10:03 PM

Originally Posted by Jerak

I tried this unit out with bootloader mode but couldn't find the protocol???
I need the EDC17 CP44 282 protocol that shows in the first page.
kessProb01.jpg
It doesn't show in the next page.
kessProb02.jpg
If I select the CP44 P268, I get wrong protocol with TOOL > ECU DATA.
I think that 1268 is for KTag.
This is KSuite 2.47, am I missing files?
Thank you.

Okay, I got this figured out!
The KSuite pdf literature says that my ecu needs the 282 protocol, but at the top of the software it calls this the "Family".
Inside the software, instructions have a link to my hardware and there it also shows a 268 protocol. Easy to miss when you are not familiar with it.

I need Family 282, Protocol 268, which this software has.
I don't know why it would report wrong protocol.

**pocinas** · 4th May, 2019, 11:28 PM

Maybe you ecu was updated software and is latest or newer which was released after release 2.47 ksuite... so for support you ecu.need some kess supported 3.x ksuite.

Dont sure this, is just my suggestion