You are absolutely rightGood, that you made a review - I didn't focus on that, and on top of that I also made another mistake. Unfortunately yours will not be accepted as well, there is still an incompatibility due to the change from BC to AD. And also something that needs to be changed if the car is not a DSG, which I think it isn't, cause it is a US car and it's rather old. But requester should confirm that to make the coding accurate and accepted without trouble codes.
So at workshop: is the car DSG or not?
Yes, that's always good to take a look at the same puzzle in four eyes
I will try to give some extended answer on this case.
1. BC coding is 17 byte long. One byte longer than the coding AD fw accepts. So we just strip the last byte of existing BC coding before writing to ABS block with AD firmware. By the way it's better to update AD to freely available CD version.
2. If we take into consideration the scan of the car that is posted here https://forums.ross-tech.com/index.php?threads/32807/ we can see it got AQ250 transmission.
When you see this, I beleive you would like to leave bit 7 of byte 16 enabled but the thing is, automatic transmission is NOT always an indication that enabling bit 7 of byte 16 is a must!
The bit depends not on the DSG itself but on the type of ESC system. So to code this correctly you either need to take a look at the sticker in the trunk or decode VIN to see PR-codes.
If there is 1AS code, you need to enable bit 7 on AD fw. If 1AT or 1AZ then the bit should be off:114B400C492300FD880B02E8921A00413600
3. We also need to consider, that byte 4 (break system config) on the BC firmware was 49. I am not sure if AD firmware supports that value but know that CD firmware definately does
Don't know why, but I prefer such kind of elaborations instead of simply coding block 3.
The approach that currently happens here leads to that workshop mechanics code something into the ABS block of their customer without taking into consideration anything and then that poor guy just drives the car with not correctly coded braking system.
Last edited by lprot; 18th June, 2022 at 12:04 PM.
Correct. That is something I missed earlier in a hurry.
You hit the point, one thing is about that bit. But you never set it unless in some rare cases with DSG (take care: it is not about automatic at all as you say, only DSG affected). It was set in his BC software because it has a different meaning there. Still you didn't take care of another incompatibility that is caused because meanings changed from AD to BC, which is why solution above is going to be rejected from what I see. You kept an option that doesn't exist in AD but did in BC. But a feedback from requester would be nice to have a confirmation, though.Even though it seems he isn't that much interested anymore as there is no feedback in the meanwhile...
Don't worry about that. Has to be copied over. Though it doesn't contain the brakes...
That is absolutely my speaking and hits what I tried to teach pretty often in this thread. It is not about getting the ABS accept a coding so that in can be made operable at first sight and lamps are off. The parameters that you cannot see to be wrong mostly affect the regulations of the system and if these are not correct this may lead to very dangerous situations. Where you will only notice something is wrong when it is too late. Other things may be coded wrong - you will notice that things are wrong by DTC (mismatch to other codings and setup) so that's not that much of a problem. As soon as I see people offering more than one coding to go try and error gives me the creeps and I can only recommend to immediately be careful in case someone does that...
Last edited by r4nd0mize; 18th June, 2022 at 01:03 PM.
Greetings gents,
Please i need the abs long coding for VW Passat
VIN# WVWAR7A39FC001439
ABS MODULE# 1k0907379BM
Well I was blind and forgot that SET RDW/RKA button on MFA+/MaxiDOT cannot be handled by AD and that's why bit 1 of byte 16 should be disabled too. So taking into consideration all the nuances (1AT code, AD version, no HHC possible, no RDW/RKA SET button handling possible) the proper coding is: 114B400C492300FD880B02E8921A00413400
I wonder will flashing to CD add compatibility with SET button?
I also beleive you underestimate importance of break system config in byte 4 that configures suspension type etc. I do not mean brake discs config is stored in this byte. There are alot of cases when firmware does not accept correct coding because of mismatch between the value you want to set with the hardcoded fw value. I beleive reflashing to the latest fw version solves that.
Last edited by lprot; 18th June, 2022 at 02:46 PM.
Workshop2 (20th June, 2022)
Hello friends, I still have this problem, can you help me please. Audi A1 2011 VIN:WAUAYA8X4BB089287 number: 6R0907379BB reference number of hardware:6R0907379AH This can be used to get the long code? I thank you very much for the help.
:wink
correct code
it works well
thanks
Please anyone can help?
You need to provide photo of the sticker from the trunk or decode your VIN. To know L0L or L0R, ESC type 1AT or 1AS, brakes diameter 1Z*, 1K* codes. Also scan of the car will help to understand which options needed to be enabled in bytes 16-18. Blindly coding random codings will keep you busy with eliminating errors or not accepted coding endlessly and your customer will return to you complaining brakes do not work properly.
Last edited by lprot; 19th June, 2022 at 05:49 PM.
Getting correct ABS coding is simple:
1. Get a photo of the sticker with PR codes from the trunk spare wheel or decode VIN https://carinfo.kiev.ua/vin
2. Get VCDS scan
3. Post the info above on the forum and please also describe where steering wheel is located (LHD/RHD), presence of Start-Stop system, buttons: TPMS/RKA, ESC/TCS/ASR off
Good to know: without option's list/current car scan/details about driving side etc, the proper coding is not possible in 99% of cases!
Bookmarks