The Mustang Forum for Track & Racing Enthusiasts
Taking your Mustang to an open track/HPDE event for the first time? Do you race competitively? This forum is for you! Log in to remove most ads.
- Welcome to the Ford Mustang forum built for owners of the Mustang GT350, BOSS 302, GT500, and all other S550, S197, SN95, Fox Body and older Mustangs set up for open track days, road racing, and/or autocross. Join our forum, interact with others, share your build, and help us strengthen this community!
ABS problems.
- Thread starterMichaelTomany
- Start date
This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.
I looked in my reference stuff from when I was messing with modules and the VIN in my 2016 GT350 ABS module is in the first four blocks 760-01-01 to 760-01-04. It's in binary coded decimal converted to hexadecimal, so it's tricky to read. However, the RCM has the same layout in 737-01-01 through 737-01-04. Just copy that from the RCM to the ABS. It might work - here's hoping.
So, am I reading this correctly - Forscan can't read the BCM because of a CAN bus issue? My BCM only counts up to 726-63-02, so where's 87 coming from? Download the as built file for your car from https://www.motorcraftservice.com/AsBuilt/ and open the .ab file in Notepad on your PC. You'll see a sea of letters but there's a pattern there. Search for "726-01-01" and then track along the lines to get to "727-01-01". The last 726-xx-xx is the end of the 726's. If there's no 87, then Forscan needs to be re-acquainted with the car.
I think whatever module starts with '726' has something to do with the the BCM working correctly, because it counts to 87 and all is well. Maybe the issue is module 727 because 727-01-01 is where it seems to stub it's toe?
| 726-81-01 | 0000 | 1E00 | CD | |
| 726-82-01 | 0000 | 0000 | 00B0 | |
| 726-83-01 | 00B1 | |||
| 726-84-01 | 00B2 | |||
| 726-85-01 | 00B3 | |||
| 726-86-01 | 00B4 | |||
| 726-87-01 | 0000 | 0000 | 00B5 | |
| 726-87-02 | 0000 | 0000 | 00B6 | |
| 727-01-01 | 1850 | 3A02 | 4519 | |
| 727-01-02 | 0100 | 0000 | 0032 | |
| 727-01-03 | 0000 | 0000 | 0032 |
I should have been clearer - the 726 series of entries are the BCM codes, and 760 series is the ABS. 727 is the Audio Control Module - essentially the car radio - if it's missing, or for that matter, if something else is missing, that's possibly why Forscan is running into problems. If you don't have some piece of electronics any more, then get Forscan to re-scan all modules when you connect it. It normally comes up saying "I found a profile - should I use it?" If you say no, it'll create a new profile by scanning all the busses looking for modules. Otherwise, it assumes that modules that were there in the past are still there.
When I run Forscan programming I can choose to edit asbuilt data for the abs which has the vin in hexadecimal but also there’s another programming option for the ABS and the vin is plainly listed there and you can change it there.
That's where I'm struggling. The MS CAN seems to not work properly with the Shelby ABS block. It's not recognizing the ABS is even present. It was a nice thought, but it looks like I'm changing back.
that’s odd. Abs is on HS2 I believe. Are all the rest of the modules on the HS2 network showing up?
I don't seem to be having any issues with the HS side, but, by not seeing the ABS at all, I don't really know where I should expect to find it. Regardless, it doesn't seem to be available under any of the modules I can see.
So when Forscan is connecting and finding all modules on the networks it doesn't find the ABS at all?
Exactly. It seems to find everything else, but I've clicked through everything and have yet to find anything relating to ABS. I am getting a CAN error, also, so I suspect the addressing on the Shelby ABS CAN template is different enough from the Mustang that they aren't a swap. I can't play with changing the VIN or anything, because there's nothing to change.
If anyone is a ForScan wiz and wants to TeamViewer into see if there's something they can try, I'll give you the shot. I just don't think it's there. I'm changing it back later in the day, so the clock is ticking.
There is another resource I should have thought of sooner. If you go here: https://www.motorcraftservice.com/Purchase/ViewProduct and sign up for a 72 hour license. It's the full OASIS system (the factory service manual) and it'll have wiring diagrams and service information for every vehicle made in the last decade including yours and a 2020 GT500. From that you should be able to deduce why you aren't getting a response from the ABS module. It could be as simple as the connector pinout is different or something like that.
So, I found a VIN for a 2020 GT500 on a used car site and plugged it into the Motorcraft Service As-Built page and downloaded the file and compared the 760 series ABS code with my 2016 GT350 Track Pack as built. Essentially the same layout with one more variable in the 760-02-02 string. There's no obvious reason it won't work. On that basis, I think that Forscan can't find the module because it's not connected properly - check the wiring (on the OASIS site I linked earlier) and see if there's a missing power connection or something. In fact, it could be even simpler - compare the number of pins in the two module's connectors - often, they leave pins out if they aren't needed. You might find that the GT500 module has more pins than the GT module
Last edited:
there’s something up with your hs can or hs can2 network. Don’t see any of the other modules on that network. PSCM, SCCM, RCM not to mention ABS.
APIM does not interfere with those. All the networks come together at the GWM which I also don’t see listed there.
your tune won’t have an impact there. Do you have an OBD2 splitter that might not be passing through info correctly?
or maybe your elm adapter. Have you tried with a newer obdlink adapter? Older elm adapters have a switch you need to use between ms and hs can networks. Is there a switch on yours?
APIM does not interfere with those. All the networks come together at the GWM which I also don’t see listed there.
your tune won’t have an impact there. Do you have an OBD2 splitter that might not be passing through info correctly?
or maybe your elm adapter. Have you tried with a newer obdlink adapter? Older elm adapters have a switch you need to use between ms and hs can networks. Is there a switch on yours?
TMO Supporting Vendors
