Mitsubishi ASX 1.8 2014 DENSO 4N13 ECU KTAG 2.25 CAN READ?

[Panathaole]

Hi

I have to read an ecu from mitsubishi asx 1.8 2014 model with denso 4n13 ecu,

As i can see in kess 2.25 is not available, it exists only in ktag, have anyone read it in bench
With ktag clone?

Thanks....

[Panathaole]

I tried to read it, at 26% I lost communication and since then I can not reconnect with the ecu, fortunately in the car I have a check,

how else can i read this ecu?

[chucky69]

Flex bench mode without problems.

[eculevel]

I tried to read it, at 26% I lost communication and since then I can not reconnect with the ecu, fortunately in the car I have a check,

how else can i read this ecu?




only genuine tools, DFB do this in fullmode from pinout

[Panathaole]

Pcmflash works on that ecu?

[Panathaole]

Today trying with dimsport, it read it once with errors, and can't connect any more.....(fortunately ecu work fine)...

Is this ecu so hard to read? (R4F70580SV)...

[beltronics]

Ktag 7.020 works well this ecu

[Panathaole]

Ktag 7.020 works well this ecu


have you ever try?

(i had read denso ecus with kess and with ktag without a problem in the past...)

the ecu have this chip

755697

[beltronics]

I did that ecu 3 or 4 times

755707

[Panathaole]

I did that ecu 3 or 4 times

755707


yes, i use that protocol, ktag make identification and start reading, and at ~30％ it lost connection, i resoldering better the wires, and try again, but this time no communication with ecu....i send it to read by a dimsport, they use adapter, manage to read one time with errors, and that's it, no more communicate with ecu.....

755726

fortunately the car starts..... no damage to dump....

[beltronics]

Your ecu will be wrong, I did work without problem.

[Panathaole]

Ecu works fine on car, as i see the protocol for pajero is from 2006, maybe this one have different chip, as it is 2014 model, i had read many denso ecus without problem,
I don't know what is going on....

Even ori dimsport couldn't read it....

[volorucinski]

Ecu works fine on car, as i see the protocol for pajero is from 2006, maybe this one have different chip, as it is 2014 model, i had read many denso ecus without problem,
I don't know what is going on....

Even ori dimsport couldn't read it....

That ecu has corrupted mcu. Like those z17dt denso opel or like z19dt opel bosch bulsh*t... it works on the car but cannot communicate, or viceversa.

[Panathaole]

Car goes to a know in my country tune company, they try to read ecu obd, and guess, they did not make it, (they say to owner that i destroy the ecu, that's why they can't read it....)

Official mitsubishi diagnostic tool connect correctly with the ecu........

Is any change to read it?????

[volorucinski]

Uhhhh... your #10 post shows that ktag cannot see all details of the ecu. Or is happening for an internal mcu issue, or becouse is not the propper protocol to read it. Did you try galletto or mpps, or some other tool?

[Panathaole]

a company tried to write it from obd, they did not succeed and said that I have damaged the ecu (good pro....lol), they tried again, and finally they managed to read it and write it from obd ...

I do not trust galetto, it is very aggressive tool, mpps, no I did not use ...(i have eu clone purple..)

I probably did stupid things by solder the cables not by scratching the pads but at the ends of them ....

ktag may have seen bad communication and would not let me re-read the ecu so as not to ruin it ... maybe .....

thanks mate...

[volorucinski]

Well.... sometimes the mcus are having badsolder joints and need reball, or just become corrupted and are communicating ok just when they want. I am wondering if after a while, the customer will tell you that ecu has the same issues :)

[Panathaole]

the car had no problem, the problem arose when the ecu needed to be read, most likely it will never have a problem "ever" ....