Results 1 to 14 of 14

Thread: U201A code in ABS after swapping from MT82 to 6R80

  1. #1
    Tuner in Training
    Join Date
    Apr 2017
    Posts
    21

    U201A code in ABS after swapping from MT82 to 6R80

    Has anybody been involved in 6R80 swaps? I have a 2014 GT I swapped from the MT82 to a 6R80 and everything went smooth except for the ABS. I have a hard fault U201A code I cannot get rid of along with ABS, traction control, and advance track lights on. I tried to do PMI on my original module with no success. Was told that you had to replace the module with a new blank one and do PMI and that would fix it. Replaced module to no avail. Any help would be greatly appreciated.

  2. #2
    Senior Tuner
    Join Date
    May 2015
    Posts
    1,908
    do you have the abs module from the vehicle the 6r80 came from? That seems to be the fix, for some reason lots of guys could never resolve the issue with a new or their existing ABS module.

    Get donor ABS, pmi PCM to donor VIN, clear DTCs, and should work.

  3. #3
    Tuner in Training
    Join Date
    Oct 2015
    Posts
    12
    Hi just read my review mt82 to 6R80 step by step with pics | SVTPerformance.com
    https://www.svtperformance.com/forum...h-pics.921639/

  4. #4
    Tuner in Training
    Join Date
    Apr 2017
    Posts
    21
    Bob. Read through your post on SVT and it still did not really answer my question as to what exactly needs to be done to fix the ABS issue. My car and the auto car I used the VIN from call for the exact same part # for the ABS module. So, I'm not exactly sure where I went wrong with programming the new blank module to end up with the same problem.

  5. #5
    Tuner in Training
    Join Date
    Oct 2015
    Posts
    12
    You need ids to prog module... maybe module have wrong prog it is not difficult to prog.. be sure your ecu have matching strategy with donor car also to match abs

  6. #6
    Tuner in Training
    Join Date
    Apr 2017
    Posts
    21
    Correct. I have IDS. My PCM was a new blank one that I sent to Matt at Lund Racing and he programmed it with my VIN and the calibration from the donor VIN. I tried as-built and PMI on my original module with no success. I figured I would at least try to program mine since it calls for the same one. Didn't work and Matt said the only way he has got them to work is with a new blank one. He said to do a manual ID with IDS and the donor VIN and then do PMI. Only problem is, to do a manual session with IDS, it opens the session based on PCM part #, tear tag #, or calibration # and not VIN. When you start a session that way, all module programming is disabled. So I started a session allowing IDS to pull my VIN and then did the PMI. When it asked to verify the VIN I entered the donor VIN and ended up with the same result. Maybe by telling it the VIN was incorrect and entering the donor VIN is where I went wrong.

  7. #7
    Senior Tuner
    Join Date
    May 2015
    Posts
    1,908
    Why would you program your PCM with your VIN and the new ABS module with the donor VIN??

  8. #8
    Tuner in Training
    Join Date
    Oct 2015
    Posts
    12
    i did the same way as this video except i enter vin donor vehicule in section abs( instead 016A as show in video) and i took my old module to reprogram..... https://www.youtube.com/watch?v=5POPyjOuxwU&t=46s

    the abs software should be matching ecu strategy..

    https://www.motorcraftservice.com/AsBuilt

    in this is exemple i enter a random vin the last line is abs strategy this case 066f

    Module Address Instructions
    Body Control Module B Inst
    BCMB 7B7-01-01 1162 4480 F7
    BCMB 7B7-02-01 0500 0000 C6
    BCMB 7B7-03-01 0100 0000 C3
    BCMB 7B7-04-01 8500 0000 48
    BCMB 7B7-05-01 253A 0C00 2F
    BCMB 7B7-06-01 6400 0000 29
    BCMB 7B7-07-01 1101 0101 DA
    Accessory Protocol Interface Module Inst
    APIM 7D0-01-01 0004 4000 001D
    APIM 7D0-02-01 0155 5300 0083
    APIM 7D0-03-01 0000 0000 00DB
    Instrument Cluster Module Inst
    ICM 720-01-01 E388 FF61 F4
    ICM 720-02-01 F000 0000 1A
    Generic Electronic Module Inst
    GEM 726-01-01 0A0A 43
    GEM 726-02-01 03C0 2323 0039
    GEM 726-03-01 0140 72
    GEM 726-04-01 0A3C
    GEM 726-05-01 040C 43
    GEM 726-06-01 0000 34
    GEM 726-07-01 2505 5F
    GEM 726-08-01 1305 0A58
    GEM 726-09-01 C000 F7
    GEM 726-10-01 8008 0000 00C6
    GEM 726-10-02 0000 0000 003F
    GEM 726-10-03 0000 0000 0040
    GEM 726-10-04 0000 41
    GEM 726-11-01 1400 53
    Audio Control Module Inst
    ACM 727-01-01 2140 8D29 80C7
    ACM 727-01-02 0888 00C1
    ACM 727-02-01 2E5F
    ACM 727-03-01 1446
    ACM 727-04-01 0000 2D0C 1F8B
    ACM 727-04-02 062D 67
    ACM 727-05-01 1246
    ACM 727-06-01 0D42
    ACM 727-07-01 0007 2F57 5B1E
    ACM 727-07-02 76AD
    ACM 727-08-01 000A 3335 5C05
    ACM 727-08-02 649C
    ACM 727-09-01 000A 3335 5C06
    ACM 727-09-02 649D
    ACM 727-10-01 080E 3C01 16A8
    ACM 727-10-02 1F01 161F 4BE0
    ACM 727-10-03 090D 090D 329F
    ACM 727-10-04 7308 0ECB
    Power Steering Control Module Inst
    PSCM 730-01-01 033C
    Restraint Control Module Inst
    RCM 737-01-01 315A 5642 50B3
    RCM 737-01-02 3846 4636 427D
    RCM 737-01-03 3531 3633 3849
    RCM 737-01-04 3833 AE
    RCM 737-02-01 C700 0000 08

    Anti-Lock Bake System Module Inst
    ABS 760-01-01 066F


    i am not a ford tech sorry
    Last edited by bob450; 06-29-2017 at 04:54 PM.

  9. #9
    the module for the abs wont help lol been there done that. it was hell getting those damn lights and errors off the dash but its def not the module. I even tried a new one w same results. its something to do w the as built data. ive only found 2 diff as builts. its almost as if the ids isn't actually programing it at all. I ended up pulling the abs connector in the middle of the process and then it failed and I reconnected it and it finally took the diff as built. I just pulled a ton of oasis on auto gts from 13 to 14 to find the two diff as builts. idk why its like that but do not waste money on the module. I even got one from a auto gt aaaannnd it did the same shit. I also think it has something to do w the ic, if you have the track apps in your ic but the ecu is from a base that's where I had the problem happen every time. ive done 24 of these swaps and 5 were a pain in the ass w the errors from abs. I wonder if eric could just set it up to disable the codes for the abs for those faults?
    GOD HELP US ALL....

  10. #10
    Tuner in Training
    Join Date
    Apr 2017
    Posts
    21
    Thanks for the info. I got the same feeling from messing with it. It definitely seemed to me like the info wasn't getting to the module too. My car has track apps and according to the info in OASIS the donor VIN I am using does as well. I'll mess with it some more this weekend. I finally found the special function codes for IDS again, so hopefully with that, I can get this thing to program. I have added NAV to vehicles with my ford touch and it wasn't this big of a pain.

  11. #11
    Tuner in Training
    Join Date
    Apr 2017
    Posts
    21
    kaineoutlaw, any other insight on this that you can share? Spent hours trying to get this thing programmed last night with no success. On the swaps that you did, what did you do for programming on the PCM? Do the cars that you did have their original VIN programmed into them or did you just program them with a donor VIN? I have found 4 different as-built codes for the ABS on auto cars, 056E, 016A, 026B, and 066F. None of them make a difference. Thanks

  12. #12
    I used forscan to fix this on my 2015. I had to change the line of code that had the VIN code n it the auto VIN

  13. #13
    Tuner in Training
    Join Date
    Apr 2017
    Posts
    21
    I have forscan as well. Which module are you referring to? My ABS module only has one line of code in the as-built.

  14. #14
    send me a email, [email protected] and ill give you my number so we can talk and not have to go back and forth emailing.
    GOD HELP US ALL....