Ford As Built Data Deciphering

[tractmec]

help me, code abs used information.
I'm not getting it on the site.
can anyone get it for me?
VIN 9BFZB55P4D8808773

Did you try here?: https://www.motorcraftservice.com/AsBuilt I just found it for the VIN you posted above! You can also get to this Data from the https://www.motorcraftservice.com home page by opening the "Free Resources" tab and "Quick Guides" link and scroll down to the "Module Build Data(AsBuilt)" link!
Fill out the VIN information field and the Security Check field and you will get a page that you can print with the browsers print button command(easiest to read and the ABS module are the 760 address's) or download as a text file with the Download button as a <YourVINNumber>.ab file which will open in Notepad or any text editor but it is harder to decipher!

The Load Factory AsBuilt button in the FORScan Configuration(AsBuilt Format) section will also go out and do this for you(computer must have a valid internet connection while connected to the vehicle for this)!

Hope this helps?

[Expat_Zach]

Is there any way you can make this program work with Australian vehicles? I’m having to poke around in the dark to figure out what’s what and I don’t wanna just go bit flipping on a hunch, ya know?

[oldtinfords]

Is there any way you can make this program work with Australian vehicles? I’m having to poke around in the dark to figure out what’s what and I don’t wanna just go bit flipping on a hunch, ya know?

ALL requests for additional functions have to be made directly to FORScan support. They don't monitor all forum posts.

You also have to remember, Ford Australia only implemented small amounts of options that can be changed & like most changes that aren't normally available, it takes lots of hours by users to find additional settings. You could start by logging CANbus messages & reverse engineering the messages or comparing asbuilt from a similar vehicle with the feature you want to enable on yours.

Also keep in mind that asking for additional features on an old vehicle with a small market share & almost zero demand is going to be a very low priority, as it should be. Keeping up with the much larger worldwide market of new vehicles is priority 1.

[Expat_Zach]

Is there any way you can make this program work with Australian vehicles? I’m having to poke around in the dark to figure out what’s what and I don’t wanna just go bit flipping on a hunch, ya know?

ALL requests for additional functions have to be made directly to FORScan support. They don't monitor all forum posts.

You also have to remember, Ford Australia only implemented small amounts of options that can be changed & like most changes that aren't normally available, it takes lots of hours by users to find additional settings. You could start by logging CANbus messages & reverse engineering the messages or comparing asbuilt from a similar vehicle with the feature you want to enable on yours.

Also keep in mind that asking for additional features on an old vehicle with a small market share & almost zero demand is going to be a very low priority, as it should be. Keeping up with the much larger worldwide market of new vehicles is priority 1.

Mate, I was asking about the as built decoder program, not FORScan. It would be nice to have at least a basic database if what data block does what.

[vesemir]

It would be nice to have at least a basic database ....

That is the point!

This is really hacking work, from binary data figure out what is what. The biggest problem is that many times it is not just one place, many bits are related, change in place is not enough.

There is one guy, Livnitup "The Forscan guy" (great regards) who takes decoding from Ford software or some leaks. Certainly it is not "guessed"! His spreadsheets are great, unfortunately he does not bother about outside America. He does no do this for any EU cars, even US Escape (Kuga) is not in his repository. Even though, his spreadsheets are very useful! Sometimes, I just look for a feature to see how it is implemented, what are the options, asbuilt is not compatible but at least I know that some settings are there. They are very helpful.

My way to find settings, is to compare large number of asbuilts. I group them in two graups: with and without a feature I'm looking for. Then, filter unchanged bits in groups and finally compare the groups against each other. I have a tool for that. This gives lot of changes since many times features comes in a bundles, but helps to spot places to look for a change. This way I have figure out LED headlapms conversion for Focus MK4, wide view for camera, rear keyless handles and many others.

I have also created a browser tool to store "feature" changes in form of a ready to apply "recipe". Same as UCDS does, marks changes in multiple places. This tool is free to use, online or offline, recipes can be shared or keep privately. No more hassle with bits, bits calculations, silly descriptions with ambiguities. The tool takes stored asbuilt from forscan, makes changes and generates asbuilts to load back with forscan.
https://www.formod.eu/asbuiltcalc.php?id=rvcwide

[Expat_Zach]

It would be nice to have at least a basic database ....

That is the point!

This is really hacking work, from binary data figure out what is what. The biggest problem is that many times it is not just one place, many bits are related, change in place is not enough.

There is one guy, Livnitup "The Forscan guy" (great regards) who takes decoding from Ford software or some leaks. Certainly it is not "guessed"! His spreadsheets are great, unfortunately he does not bother about outside America. He does no do this for any EU cars, even US Escape (Kuga) is not in his repository. Even though, his spreadsheets are very useful! Sometimes, I just look for a feature to see how it is implemented, what are the options, asbuilt is not compatible but at least I know that some settings are there. They are very helpful.

My way to find settings, is to compare large number of asbuilts. I group them in two graups: with and without a feature I'm looking for. Then, filter unchanged bits in groups and finally compare the groups against each other. I have a tool for that. This gives lot of changes since many times features comes in a bundles, but helps to spot places to look for a change. This way I have figure out LED headlapms conversion for Focus MK4, wide view for camera, rear keyless handles and many others.

I have also created a browser tool to store "feature" changes in form of a ready to apply "recipe". Same as UCDS does, marks changes in multiple places. This tool is free to use, online or offline, recipes can be shared or keep privately. No more hassle with bits, bits calculations, silly descriptions with ambiguities. The tool takes stored asbuilt from forscan, makes changes and generates asbuilts to load back with forscan.
https://www.formod.eu/asbuiltcalc.php?id=rvcwide

Bro! Thanks for this link! I’ll deffo try playing with it!

[Goz1]

Yes I second that thankyou......, some great information U have disclosed to us.