seanjordan20

The error you're getting has nothing to do with coding or programming. Something isn't right with the mechatronic. If it were a coding issue you would have multiple errors not singling out a lockup on solenoid 3.

Question? Did you check the codes before doing the work? What were they if you did?

I can't find the proper sequence on coding because everyone who's done it said all they needed to do was reset the adaptions. The pairing comes in when you separate the TCU from the mechatronic so you can skip that step. As for why INPA is not seeing it correctly may be because it needs to be updated

mimi174

The error code was the reason i changed the Mechatronic unit. After changing everything i reset the adaptions. Been driving the car since and i am getting an 4F96 error and issues downshifting. My thinking is maybe need to pair the TCM to the car.

seanjordan20

The TCM/TCU is the black part on the mechatronic. You said you used both from the donor car so there is no need to pair. Now you have to figure your code out. That code is a shifting code. I would recheck to make sure the fluid is correct first by taking the fill plug out and making sure some fluid leaks out. then take cover off and redo it. It's either a fluid issue or something is not mate correctly.

How many miles did the loaner car have on it? You can't dismiss that the one you purchased is bad?

seanjordan20

Check your code again are you sure it's a 4F96 you are currently getting

seanjordan20

What type of fluid did you use?

mimi174

The Donor car had 96k miles(might be bad). I just ran the codes again and now am getting 4F96 and 4F85. I used Pentosin ATF for the transmission fluid.

mimi174

I ran WinKfp again and read the uif...Below is waht it pulled up...

Entries of the user info field:

--------------------------------------
Entry 1:

Vehicle identification number: WBANV13569C155956 (Donor CAR)
Date: 29.01.2009
Change index: DA
Software number: 7592113
Office number: 0000000
Assembly identification number: 7592112
Seral number: NFS01
Program number: 0479SA0T641Z
Kilometer: 0
Dealer number: 000240

--------------------------------------
Entry 2:

Vehicle identification number: C134035 (MY CAR)
Date: 21.05.2020
Change index: DA
Software number: 7601461
Office number: 0000000
Assembly identification number: 7601460
Seral number: 12345
Program number: 0479SA0T641Z
Kilometer: 153000
Dealer number: 011111


--------------------------------------
End of user info field

seanjordan20

The only thing I could see was your module having newer software. If you were able to read yours in INPA then the donor shouldn't have an issue.

What programs do you use to code? Since WINKPF can read the module then you should be able to code it. You should be able to first write the VIN then do an update. I assume you have the updated sp-daten files

mimi174

I have Sp-daten V67.1. I thought the Assembly identification numbers were different on both cars..donor 7592112 ....My car 7601460. I have ISTA D, ISTA P, Winkfp, NCS Expert, Tool32 Plus INPA

seanjordan20

I don't look at the assembly number. It's only there for you when you need to program it. When you pull up NCS do you find the donor ZB number in the list to code it. If so code your car VIN to it then code it to the car using the same ZB number. You should only need NCS expert for the VIN then use Tool32 and NCS for programming. After that you should be able to see the correct ZB number in INPA