MK60 ABS long coding for members

[lprot]

Thanks lprot, you are a wizard! The car is 2.0SDI. EDIT: my car is not AWD
It accepts both codes but now I'm left with:

01279 - Longitudinal Acceleration Sensor (G251)
005 - No or Incorrect Basic Setting / Adaptation - Intermittent
Freeze Frame:
Fault Status: 00100101
Fault Priority: 2
Fault Frequency: 1
Reset counter: 209
Mileage: 228535 km
Time Indication: 0


Freeze Frame:
Count: 27
Count: 2
Count: 12800
Count: 212
Count: 50432
Count: 0
Count: 0
Count: 0


01423 - Lateral Acceleration Sensor (G200)
012 - Electrical Fault in Circuit - Intermittent
Freeze Frame:
Fault Status: 00101100
Fault Priority: 2
Fault Frequency: 1
Reset counter: 209
Mileage: 228535 km
Time Indication: 0


Freeze Frame:
Count: 27
Count: 2
Count: 12288
Count: 267
Count: 46592
Count: 0
Count: 0
Count: 0


02085 - Incorrect Control Module Installed
000 - -
Freeze Frame:
Fault Status: 01100000
Fault Priority: 2
Fault Frequency: 1
Reset counter: 209
Mileage: 228535 km
Time Indication: 0


Freeze Frame:
Count: 16415
Count: 0
Count: 8192
Count: 204
Count: 46848
Count: 0
Count: 0
Count: 0


16347 - Control Module - EEPROM Error
014 - Defective
Freeze Frame:
Fault Status: 01101110
Fault Priority: 1
Fault Frequency: 1
Reset counter: 209
Mileage: 228535 km
Time Indication: 0


Freeze Frame:
Count: 16415
Count: 0
Count: 8192
Count: 198
Count: 46848
Count: 0
Count: 0
Count: 0


00003 - Control Module
005 - No or Incorrect Basic Setting / Adaptation
Freeze Frame:
Fault Status: 01100101
Fault Priority: 1
Fault Frequency: 1
Reset counter: 209
Mileage: 228535 km
Time Indication: 0


Freeze Frame:
Count: 16415
Count: 0
Count: 8192
Count: 143
Count: 46848
Count: 0
Count: 0
Count: 0

Let's disable HHC 113B600D49290000881006E8921A0042300000
Did you try basic settings? https://youtube.com/watch?v=w6EiDEjR2rk
Are you sure the unit is BD? Also might be someone reflashed is with incompatible firmware?

[kiropraktik]

Let's disable HHC 113B600D49290000881006E8921A0042300000
Did you try basic settings? https://youtube.com/watch?v=w6EiDEjR2rk
Are you sure the unit is BD? Also might be someone reflashed is with incompatible firmware?

Now it is down to:

01423 - Lateral Acceleration Sensor (G200)
012 - Electrical Fault in Circuit - Intermittent
Freeze Frame:
Fault Status: 00101100
Fault Priority: 2
Fault Frequency: 1
Reset counter: 209
Mileage: 228535 km
Time Indication: 0


Freeze Frame:
Count: 27
Count: 0
Count: 12288
Count: 267
Count: 45056
Count: 0
Count: 0
Count: 0


00003 - Control Module
005 - No or Incorrect Basic Setting / Adaptation
Freeze Frame:
Fault Status: 01100101
Fault Priority: 1
Fault Frequency: 1
Reset counter: 209
Mileage: 228535 km
Time Indication: 0


Freeze Frame:
Count: 27
Count: 0
Count: 12288
Count: 143
Count: 45056
Count: 0
Count: 0
Count: 0


16347 - Control Module - EEPROM Error
014 - Defective
Freeze Frame:
Fault Status: 01101110
Fault Priority: 1
Fault Frequency: 1
Reset counter: 209
Mileage: 228535 km
Time Indication: 0


Freeze Frame:
Count: 27
Count: 0
Count: 12288
Count: 198
Count: 45056
Count: 0
Count: 0
Count: 0

Yes, the unit is BD... as for flashing, it is possible that someone wiped the firmware but I'm not completely sure.
As for basic settings, I can not open the link but if you're referring to these: http://wiki.ross-tech.com/wiki/index...ctronics_(MK60)
I did try them with no luck as the lateral acceleration is stuck at 0.00 m/s:
kj1231872319kadsd91lasd.jpg

[lprot]

Yes, the unit is BD... as for flashing, it is possible that someone wiped the firmware but I'm not completely sure.

Try to update it to 1K0907379BH_0120.sgo https://dropmefiles.com/U0I0D
Then do basic settings https://cutt.ly/WLloil7
IMPORTANT! Before flashing 1K0907379BD with 1K0907379BH_0120.sgo backup adaptation list of block 44 (steering). It may happen they will get changed after the reflash.

[r4nd0mize]

Now it is down to:

01423 - Lateral Acceleration Sensor (G200)
012 - Electrical Fault in Circuit - Intermittent
Freeze Frame:
Fault Status: 00101100
Fault Priority: 2
Fault Frequency: 1
Reset counter: 209
Mileage: 228535 km
Time Indication: 0

Unfortunately it really looks like what the DTC says - seems like a hardware failure in your unit, regarding the lateral sensor. The longitudinal DTC you had earlier was caused having HHC on, but a BE unit does not have that sensor so that makes sense. Iprot turned that off so that is ok.

00003 - Control Module
005 - No or Incorrect Basic Setting / Adaptation
Freeze Frame:
Fault Status: 01100101
Fault Priority: 1
Fault Frequency: 1
Reset counter: 209
Mileage: 228535 km
Time Indication: 0

Also what is says, some basic settings not done. But could also be a follow up DTC because of that lateral sensor DTC... and I really think that's what it is...

16347 - Control Module - EEPROM Error
014 - Defective
Freeze Frame:
Fault Status: 01101110
Fault Priority: 1
Fault Frequency: 1
Reset counter: 209
Mileage: 228535 km
Time Indication: 0

This is something that really underlines something is superweird with your unit or it really is defective. If you have something like that a dealer would replace the unit. If you have some freedom to play around the only thing I could suggest to do is do factory reset by diagnosis (reset to factory settings) and then get the unit back by writing coding and doing basic settings. If this DTC is then still present, I don't think you can fix it with regular, diagnostic tools :-/

Yes, the unit is BD... as for flashing, it is possible that someone wiped the firmware but I'm not completely sure.
As for basic settings, I can not open the link but if you're referring to these: http://wiki.ross-tech.com/wiki/index...ctronics_(MK60)
I did try them with no luck as the lateral acceleration is stuck at 0.00 m/s:
kj1231872319kadsd91lasd.jpg

Havin later acceleration stuck at 0.00 m/s is another hint, hardware really is broken.

Indeed you can flash your unit to BD without any doubts, but if it really is a hardware failure you won't fix anything with that. Good luck though and let us know how it turned out...

[atd]

Car Has no ABS coding because of damaged immo on cluster. I've repaired whole immo, car starts but coding is lost and i'm having problem to code it. Whole sticker is attached.
A3 8p, 2010year, 2.0tdi CBBB, manual trans, LHD, only esp button. Vin is on the photo of sticker.
1k0907379AH
Thank you in advance.

[r4nd0mize]

Car Has no ABS coding because of damaged immo on cluster. I've repaired whole immo, car starts but coding is lost and i'm having problem to code it. Whole sticker is attached.
A3 8p, 2010year, 2.0tdi CBBB, manual trans, LHD, only esp button. Vin is on the photo of sticker.
1k0907379AH
Thank you in advance.

Done. Check you PM box...

[lprot]

Car Has no ABS coding because of damaged immo on cluster. I've repaired whole immo, car starts but coding is lost and i'm having problem to code it. Whole sticker is attached.
A3 8p, 2010year, 2.0tdi CBBB, manual trans, LHD, only esp button. Vin is on the photo of sticker.
1k0907379AH
Thank you in advance.

1142601209260002880F06E490210042380800

[r4nd0mize]

1142601209260002880F06E490210042380800

Check his PR sticker. 1ZA = your brake booster setting is wrong... Still some improvements, young padawan Rest is ok...

[lprot]

Check his PR sticker. 1ZA = your brake booster setting is wrong... Still some improvements, young padawan Rest is ok...

This is the first thing I checked. 1ZA=312mm 1KD=rear drums. That gives us byte2 = 60.
Brake booster aka byte 4 = 09 I met it even when the brakes in byte2 = 80
Does Yoda really know something I'm missing?

[atd]

Okey guys... i've tested both....
Iprot coding ABS module has accepted. I will try on the road in few minutes. I'm having doubts from where you know that 6th byte is 88 and 16th byte is 38 ?
My calculator doesn't show it.... :/

[lprot]

Okey guys... i've tested both....
Iprot coding ABS module has accepted. I will try on the road in few minutes. I'm having doubts from where you know that 6th byte is 88 and 16th byte is 38 ?
My calculator doesn't show it.... :/

I bet you meant byte 8th but not 6th. It is binary mirror of byte 0.
Byte 16:
bit3 ESC off button installed
bit4 I know that it should be 1 on AH firmware. But I do not really know what it means. I would appreciate if you disable it and tell which error in which block it forces.
bit5 ACC disabled

I would also like to see the coding that was not accepted.

[atd]

I'm using this shitty calculator which gives you coding from Vin and allows to modify equipment. Everything was the same without 8 and 16 byte so that i asked for that.
Firstly i hoped that this will be my coding:
14426012092600FA280F06E490210042380800
And when it was rejected i was combined between those and result of mine calculator .

[r4nd0mize]

Let's not get too confused. Iprod's coding he posted initially from his side for you is absolutely fine. You can can live with that perfectly. Do not play around if you get that one written to the unit! There's only the 1ZA thing that does not match and it affects byte zero,... and another byte according to that. But now that you say that is not accepted suprises me,... since it is part of what is not checked by the unit while writing the coding. Could only explain, that this older unit does not know this parameter set, even though your PR number points to it. Probably it didn't exist in this software... weird to me.

Anyways. Before starting struggle here, use Iprots coding please, as it is super accurate in terms of everything else. Do not modify it. Just use it as it is. It's only that one thing not quite clear, and in my opinion, doubtable case I mentioned. But you or whoever drives the car can live with that as the effect should be rather small.

Would still be a nice move to check again whether the coding I sent you can be written and was just rejected due to some other unforseen things.


Aaaaand my two cents besides that: me using a smiley together with a little friendly joke, means it is a friendly joke Wink wink Just don't wann be misunderstood.

[lprot]

Let's not get too confused. Iprod's coding he posted initially from his side for you is absolutely fine. You can can live with that perfectly. Do not play around if you get that one written to the unit! There's only the 1ZA thing that does not match and it affects byte zero,... and another byte according to that. But now that you say that is not accepted suprises me,... since it is part of what is not checked by the unit while writing the coding. Could only explain, that this older unit does not know this parameter set, even though your PR number points to it. Probably it didn't exist in this software... weird to me.

Anyways. Before starting struggle here, use Iprots coding please, as it is super accurate in terms of everything else. Do not modify it. Just use it as it is. It's only that one thing not quite clear, and in my opinion, doubtable case I mentioned. But you or whoever drives the car can live with that as the effect should be rather small.

Would still be a nice move to check again whether the coding I sent you can be written and was just rejected due to some other unforseen things.


Aaaaand my two cents besides that: me using a smiley together with a little friendly joke, means it is a friendly joke Wink wink Just don't wann be misunderstood.

You surprise me with associating 1ZA with the value of byte0. Do you relize that byte0=14 is for "Sport" version of the cars? The given car is neither quattro nor S-line!
Why are you talking about other nuances like "one more" thing is not correct? What is not correct from your point of view? Which PR code are you talking about?
I guess 1N3 and because of that you made byte4=49? It does not work like that.
Please don't create myths out of nothing

[atd]

Firstly i've tried coding from well known calculator and every one was rejected. Then i tried r4nd0mize coding and also was rejected. Then i was trying to play with r4nd0mize values in coding and also was bad. Iprot coding was accepted for the first time and i left it as it was and gave the car to customer back. Maybe something was manipulated with abs previously? I don't know. Somebody wanted to stole the car, whole immo was empty, i had to work on new pair of dumps for micronas and c32. Maybe it was the problem with coding acceptation?