Engine Control Unit (ECU) Login Failed

Hello,

Recently, I installed the entire technology package from a 2003 facelift model into my pre-facelift Audi A3 8L TDI – yes, absolutely everything!

Since the speedometer of the donor vehicle was damaged in an accident, I temporarily installed a different speedometer. The login credentials for the engine control unit (ECU) and the speedometer were known.

Now I have the final speedometer completed and want to connect it to the immobilizer, or the engine control unit. However, the engine control unit is not accepting its login.
If I start the learning process in the KI (interface), I enter all the login details as usual. When I click "Test" in the configuration, the code reverts to the default setting of 32000. While it is possible to accept this setting, it doesn't work – the KI is not learned.

When I try to log in to the engine control unit, I get an error message saying that the login credentials are incorrect.

However, the login information is also displayed when I read the engine control unit, so it is definitely correct.

Does anyone have any advice?

The engine control unit is an EDC15P, and both speedometers are VDO C5 V12 models with CAN bus (part number 8L0920931E).


Here's another point: The login codes were not extracted from a cracked version! Just like for VCDS, I also paid for the rest of the software and am using a legitimate version (the mileage was, of course, also corrected and adjusted to the actual mileage of the car. The mileage of the car should be the relevant figure here, and incidentally, it was also higher than the mileage shown by the engine).

And if you try to enter the normal login, not the one for the immobilizer, for example "12233", or the one to activate a GRA, for example "11463", does the MSG accept these entries, or does it reject them as well?

Is the speedometer to be installed IMMO2 or IMMO3?

What do you use to pull code?

The other codes for connecting to the GRA (presumably a specific device or system), etc., are accepted without any problems.

"This refers to the WFS III."

The software used for reading the data is VAGTacho or VAGdashCAN.

The engine control unit (ECU) and the transponders in the keys are IMMO2 compatible? I'm asking because of potential issues with locked transponders.

And if the regular logins work, can you also use the Dash Can to access the MSG without any control characters being displayed? Is everything clear?
I want to point out that the MSG might be temporarily blocked due to multiple incorrect login attempts. In that state, it doesn't accept any logins at all, not just logins from the Wfs.
Starting with Immo3, blocking periods are implemented.

Use VCDS to access control module (ECM) byte 23, field 2. Does it show a 0? Then, in control module byte 24, you'll find the pairing/authorization times.
They must all be zeros. If there's a "10" displayed, it means leaving the ignition on for 10 minutes until it shows "0". Then, you need to initiate the learning process. Don't turn off the ignition in between, or you'll have to start all over again.

If it still doesn't work, do you have the option to manually copy the IMMO block from the dump of the old speedometer to the dump of the new speedometer? If you succeed in doing that, the pairing process will be bypassed.
It starts up as if nothing has been changed. The original VAG dash can is supposed to work that way too. You don't need to know the offset addresses for it to function.

The MSG is also WFS III. I can also access it without any problems using VAGdash. I've also considered the lock-out time, but according to the diagnostic data, that's not the cause either.

I also had some problems the first time when I tried to pair the transponders. It took me several attempts before everything worked. But then there were no more problems... until now.

I'm not very familiar with Dashcan yet. I've only been using both tools for a short time, and I've only used them occasionally, mostly with VAGTacho.

Unfortunately, there is very little information available online about tachograph dumps and their contents, especially regarding how to modify them. While it's easy to change things like the chassis number or lighting settings in the dump, I haven't yet managed to copy the WFS information .

I'll try to figure out how to do that with Dashcan.

Please check with VCDS in the instrument cluster that is being programmed, specifically in Control Module 23, field 2, and note the number that is displayed there. Also, please check the same in Control Module 23, field 4.

In field "Transponder Status" of MWB 23, the value is 0.
In field WFS-Status of form MWB 23, the value is 6.

However, the AI device is currently on my desk and not installed.

I've double-checked all the lock-out times, and they are all set to 0.

The engine control unit is still not accepting a login.

Mode 6 is the used mode. Mode 4 is the (pseudo) new mode.
The learning procedure is slightly different. Search online for instructions for the used mode and follow them. If that doesn't work, set the speedometer to mode 4 using the Dashcom and try the other procedure. Always keep an eye on the lock-out times.
If it still doesn't work, I would simply copy the IMMO block from one dump to the other. You can do this either manually if you know the offset addresses, or using the Dashcom software.
And before you start, download the current state of the database and create a backup.

But then I'm still left with the problem that the motor control unit doesn't accept a login.

The problem isn't really a problem. Just follow my train of thought.
You copy the immobilizer block, which contains all the anti-theft data, from the data set of the speedometer that is already installed and working in the car, and paste it into the speedometer that needs to be programmed. Then you upload the dump. If this is successful (which doesn't always happen because there are different speedometers with different data sets), then the problem is solved. All that remains is to (possibly) code it, enter the maintenance interval data, and set the mileage.
Okay?

This is also referred to as "cloning the Immoblock." It is sufficiently described in the operating manual and on the Dashcan support pages. It's also the first result you'll find when you search for it on Google.
Anything related to immobilizer systems that goes beyond the standard learning procedure is less of a concern for us here.

Okay, so I'll definitely be able to get the speedometer connected.

I was just wondering why I can't suddenly log in to the engine control unit anymore.

It might become a problem if I need to log in there.

What is the purpose of logging into the engine control unit (ECU) using the WFS PIN? To pair devices, you should go into the instrument cluster (control unit 17).
There is also a lockout period that is activated for the MSG after multiple incorrect login attempts. However, in this state, it will not accept any login attempts at all.

We already clarified that.

Andreas_M wrote:

The other codes for connecting to the GRA, etc., are accepted without any problems.