ECU killed and ME7.5 compatibility

Pages: [1] 2

« previous next »

Author

Topic: ECU killed and ME7.5 compatibility (Read 9423 times)

zax

Newbie

Karma: +0/-0
Offline

Offline

Posts: 13

	ECU killed and ME7.5 compatibility « on: June 07, 2020, 11:59:24 AM »

Hello!
I've made a lot of soft experiments with my AUQ/ARY engine in A3.
Somebody wrote, that he even restored ecu when somebody wrote the MP3 as a flash, so what worse can happen? Grin

Most of them are just pushing injectors to the limit.
Twice forgot to checksum, so I had to get the ecu out of the car and make a bootmode Roll Eyes

But my last experiment went so wrong... I've found one bin with NLS which has a correct checksums and the same HW code (06A906032HN).
Car started, made about 10 km's shoot a few times testing NLS. Works fine, but at higher rpm's it cuts off power.
I've parked and tested shooting from exhaust. Two great bangs at about 5000 rpm. At next attempt (probably without clutch pressed) - engine runs even over 7000 rpm. Next attempt, and tachometer gone at 0, engine stopped and "oil pressure" blinked at fis.
Then check engine icon went off and only ESP OFF stay on (same situation as when reading or writing soft).
Now I can't connect with ECU by MPPS or VCDS.
I've pulled out the ecu and tried to bench flashing. I only can see voltage, but still can't connect with the driver.
Normally in the car I heard "clicks" when connecting to the ECU. Now "clicks" are quicker...
What happened?
Immo is normally turning on for a second and gone, so it's not an immo.
Is it possible to kill ecu by soft?

I have also 06A906032FK driver, which is also ME7.5, but for 2,0 NA golf 4. Can somebody tell me from his experience if the physically these two drivers are similar or the same, and is it possible to put the immo and flash from my old driver to this one and start the car?


	Logged

Stoti

Full Member

Karma: +0/-0
Offline

Offline

Posts: 79

	Re: ECU killed and ME7.5 compatibility « Reply #1 on: June 07, 2020, 12:58:41 PM »

Did u try bootmode ? with 10k resistor . i had similar issues after flashing on second or third starting of car wont start till i flash it again. For ecu i have experimented with ALT ecu and runs petfect with 1.8t flash but i dont know witch versions will match . simplest way i found is the colour of pcb . for immo it will work if u swap eeprom to new ecu or do immo off .


	Logged

nyet

Administrator
Hero Member

Karma: +607/-168
Offline

Offline

Posts: 12256

	Re: ECU killed and ME7.5 compatibility « Reply #2 on: June 07, 2020, 01:00:36 PM »

Quote from: zax on June 07, 2020, 11:59:24 AM

I've found one bin with NLS

I confess I stopped reading here.


	Logged

ME7.1 tuning guide
ECUx Plot
ME7Sum checksum
Trim heatmap tool

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex

zax

Newbie

Karma: +0/-0
Offline

Offline

Posts: 13

	Re: ECU killed and ME7.5 compatibility « Reply #3 on: June 07, 2020, 01:06:21 PM »

Quote from: Stoti on June 07, 2020, 12:58:41 PM

Thanks for quick reply.
After flashing non-checksummed drivers I can even run the car. But after turning ignition off and on ESP OFF light goes on and check engine goes off. And driver needs bootmode to reupload the correct bin.

Quote from: nyet on June 07, 2020, 01:00:36 PM

I confess I stopped reading here.

Haven't ever tried? Grin


	Logged

Sandstorm3k

Sr. Member

Karma: +10/-14
Offline

Offline

Posts: 402

	Re: ECU killed and ME7.5 compatibility « Reply #4 on: June 08, 2020, 04:38:05 AM »

Quote from: zax on June 07, 2020, 01:06:21 PM

I believe it has to do with the car not always checking the checksums, only every now and then it will check. So using a NON-checksummed file is always a bad idea.

Just use ME7Sum for checksumming ur files.


	Logged

nyet

Administrator
Hero Member

Karma: +607/-168
Offline

Offline

Posts: 12256

	Re: ECU killed and ME7.5 compatibility « Reply #5 on: June 08, 2020, 08:43:06 AM »

Quote from: Sandstorm3k on June 08, 2020, 04:38:05 AM

Has to do with NLS stomping all over the RSA code in ME7.5


	Logged

Sandstorm3k

Sr. Member

Karma: +10/-14
Offline

Offline

Posts: 402

	Re: ECU killed and ME7.5 compatibility « Reply #6 on: June 08, 2020, 09:25:22 AM »

Quote from: nyet on June 08, 2020, 08:43:06 AM

Has to do with NLS stomping all over the RSA code in ME7.5

How does that work? Is it due to the calls NLS makes which messes everything up?


	Logged

zax

Newbie

Karma: +0/-0
Offline

Offline

Posts: 13

	Re: ECU killed and ME7.5 compatibility « Reply #7 on: June 08, 2020, 10:29:42 PM »

Quote from: Sandstorm3k on June 08, 2020, 09:25:22 AM

How does that work? Is it due to the calls NLS makes which messes everything up?

Hello again!
Now that's going weird. Yesterday the ecu started to connect with mpps normally. What happened?
Soft uploading required to turn off and on ignition a few times and failed for a first attempt, but at second attempt it got a soft normally... Today I'll try if all is right.


	Logged

nyet

Administrator
Hero Member

Karma: +607/-168
Offline

Offline

Posts: 12256

	Re: ECU killed and ME7.5 compatibility « Reply #8 on: June 08, 2020, 10:42:34 PM »

Quote from: Sandstorm3k on June 08, 2020, 09:25:22 AM

How does that work? Is it due to the calls NLS makes which messes everything up?

Yes. I can't stress how bad the publicly available NLS script is. And make no mistake, 99% of the binaries with NLS have had this script (or variants) run on it, and nobody has solved the RSA issue (afaik) w/o just disabling RSA completely. You really think anybody did this themselves?


	Logged

zax

Newbie

Karma: +0/-0
Offline

Offline

Posts: 13

	Re: ECU killed and ME7.5 compatibility « Reply #9 on: June 09, 2020, 12:13:47 AM »

Ok, today I've put ecu back to the car.
But car still won't start, esp off light is on and check engine light is off. I can't connect to the ecu by vcds neither mpps.
In mpps I can connect to the ecu on the bench, it normally connects, read, write...
What else can happened?


	Logged

adam-

Hero Member

Karma: +123/-33
Offline

Offline

Posts: 2179

	Re: ECU killed and ME7.5 compatibility « Reply #10 on: June 09, 2020, 12:45:55 AM »

Write stock file, fix death code in EEP.


	Logged

zax

Newbie

Karma: +0/-0
Offline

Offline

Posts: 13

	Re: ECU killed and ME7.5 compatibility « Reply #11 on: June 09, 2020, 02:57:59 AM »

I've wrote the stock file.
I haven't an idea about death code in eeprom.
Is it possible to get and write the eeprom in this state by vcds or mpps cable?
I've found the topic where @adam suggested the same and somebody removed two 33 hex values to 0's. But I haven't found another informations about it.

My question is: which soft and cable should I use to download 95040 eeprom and rewrite it if I have only VCDS and MPPS cables?


« Last Edit: June 09, 2020, 07:06:52 AM by zax »	Logged

K92

Full Member

Karma: +0/-3
Offline

Offline

Posts: 137

	Re: ECU killed and ME7.5 compatibility « Reply #12 on: June 09, 2020, 11:24:03 AM »

Quote from: zax on June 09, 2020, 02:57:59 AM

I am using INPA BMW cable. And when i need i convert it to galleto.


	Logged

d3irb

Full Member

Karma: +134/-1
Offline

Offline

Posts: 195

	Re: ECU killed and ME7.5 compatibility « Reply #13 on: June 09, 2020, 12:00:10 PM »

Quote from: zax on June 09, 2020, 02:57:59 AM

argdubs me7_95040 should work with your VCDS cable in VCP mode. otherwise get an FTDI KKL for a few $.


	Logged

zax

Newbie

Karma: +0/-0
Offline

Offline

Posts: 13

	Re: ECU killed and ME7.5 compatibility « Reply #14 on: June 10, 2020, 10:07:16 AM »

Quote from: adam- on June 09, 2020, 12:45:55 AM

Write stock file, fix death code in EEP.

Actually I can read and write via MPPS when the ECU is on the bench. But when I put it to the car and connect I can't connect via MPPS. Should I check the fuses or cables, or is it normal when death code is in the driver?

I still can't connect and download 95040.
I've tried version 1.40 with OBD and bootmode:

Code:

C:\Users\laptop>"C:\Users\laptop\Desktop\chip\me7 eeprom\me7-eeprom-1.40\ME7EEPR
OM.exe" --OBD -r -p 1 95040.bin
ME7_EEPROM v1.40
COM: 1, Baud Rate: 10400
Opening COM1 ... OK
Initiating communication ... FAIL. (error=0x21007)
Closing COM1

and 1.31 version both with bootmode and OBD mode:

Code:

C:\Users\laptop>"C:\Users\laptop\Desktop\chip\me7 eeprom\me7_95040_v1.31\me7_950
40.exe" --OBD -r -p 1 95040.bin
Ver: 1.31
Com Port: 1
Baud Rate: 10400
Opening COM1 ... OK
Initiating communication ... FAIL. (error=0x07)
Closing COM1

I have a vagtacho cable which is K+CAN and set as COM1. If it's the problem, I still have to find the cheap KKL cable.


	Logged

Pages: [1] 2

« previous next »

Jump to:

Navigation

Personal Tools

November 16, 2024, 06:35:42 PM

Welcome, Guest. Please login or register.
Did you miss your activation email?

Navigation

Personal Tools

Search