Ford As Built Data Deciphering
-
ClockWorK
- Posts: 139
- Joined: Sat Mar 05, 2016 11:29 pm
- Vehicle: 2015 Taurus SHO pp
- Location: Detroit Area
- Contact:
Re: Ford As Built Data Deciphering
I think you did everything right. I think the two vehicles have very different BCM modules.
2015 Taurus SHO (pp), AWD Gauge Enabled, Engine Hours Enabled, DRLs Enabled, Sync2-to-Sync3.
AsBuilt Compare Tool: http://www.compulsivecode.com/Project_A ... mpare.aspx
AsBuilt Compare Tool: http://www.compulsivecode.com/Project_A ... mpare.aspx
Re: Ford As Built Data Deciphering
If I get more samples will that help? Basically trying to find the same BCM with one that honks and one that does not would be the key?ClockWorK wrote:I think you did everything right. I think the two vehicles have very different BCM modules.
-
ClockWorK
- Posts: 139
- Joined: Sat Mar 05, 2016 11:29 pm
- Vehicle: 2015 Taurus SHO pp
- Location: Detroit Area
- Contact:
Re: Ford As Built Data Deciphering
I think that will be your best bet.
2015 Taurus SHO (pp), AWD Gauge Enabled, Engine Hours Enabled, DRLs Enabled, Sync2-to-Sync3.
AsBuilt Compare Tool: http://www.compulsivecode.com/Project_A ... mpare.aspx
AsBuilt Compare Tool: http://www.compulsivecode.com/Project_A ... mpare.aspx
Re: Ford As Built Data Deciphering
I have two more that don't honk: https://www.dropbox.com/s/cp02piq8yozpg ... ns.ab?dl=0
https://www.dropbox.com/s/e0muh8wsauzky ... 11.ab?dl=0
Sorry I just don't know what to look for. I started searching part numbers and comparing the code used on the F150 to point me in the right direction. It seems like every other ford, this code has been found, the Fiesta remains illusive.
https://www.dropbox.com/s/e0muh8wsauzky ... 11.ab?dl=0
Sorry I just don't know what to look for. I started searching part numbers and comparing the code used on the F150 to point me in the right direction. It seems like every other ford, this code has been found, the Fiesta remains illusive.
Re: Ford As Built Data Deciphering
I'm trying to turn on the hour meter in my 2013 Explorer XLT.
I tried running VINs through AsBuiltExplorer. Got VINs off of eBay. When I run it, it identifies 9 vehicles with the feature, and 11 without, but it doesn't give me the 'perfect bits'. It's just blank. When I try to load modules, it does nothing. Any suggestions?
I also tried, using the info above from the Taurus/PI, but no luck. I ran my 720-01-02 through a hex to binary converter, changed the bits marked, and converted it back, but it didn't work. I tried various configurations of them, and the only thing that changed, that I found, was the DTE calculation; I went from 332 miles to empty, to 339, and 999.
One thing I noticed is that it changed the last digit from what I entered, to a value one higher or lower, i.e. 9024 to 9023 or 9025. I'm not sure if that's just a check digit. There was one attempt that I got an error saying the vehicle wasn't equipped.
My 720-01-02 is F42C 0842 9024.
I tried running VINs through AsBuiltExplorer. Got VINs off of eBay. When I run it, it identifies 9 vehicles with the feature, and 11 without, but it doesn't give me the 'perfect bits'. It's just blank. When I try to load modules, it does nothing. Any suggestions?
I also tried, using the info above from the Taurus/PI, but no luck. I ran my 720-01-02 through a hex to binary converter, changed the bits marked, and converted it back, but it didn't work. I tried various configurations of them, and the only thing that changed, that I found, was the DTE calculation; I went from 332 miles to empty, to 339, and 999.
One thing I noticed is that it changed the last digit from what I entered, to a value one higher or lower, i.e. 9024 to 9023 or 9025. I'm not sure if that's just a check digit. There was one attempt that I got an error saying the vehicle wasn't equipped.
My 720-01-02 is F42C 0842 9024.
-
ClockWorK
- Posts: 139
- Joined: Sat Mar 05, 2016 11:29 pm
- Vehicle: 2015 Taurus SHO pp
- Location: Detroit Area
- Contact:
Re: Ford As Built Data Deciphering
Do you know where to look for the Hour Meters in the instrument cluster? I took me a while to actually find them. They are buried in the menus. On my car, they are under Information, System Check, scroll to the bottom. Also, I don't know if the Explorer uses the same IPC, or if the same bits will apply.
As for the deduction part, I would recommend starting with a narrower search by limiting the search to a single year.
Worst case, PM me the VINs you have and I will try it when I've got a bit of time.
As for the deduction part, I would recommend starting with a narrower search by limiting the search to a single year.
Worst case, PM me the VINs you have and I will try it when I've got a bit of time.
2015 Taurus SHO (pp), AWD Gauge Enabled, Engine Hours Enabled, DRLs Enabled, Sync2-to-Sync3.
AsBuilt Compare Tool: http://www.compulsivecode.com/Project_A ... mpare.aspx
AsBuilt Compare Tool: http://www.compulsivecode.com/Project_A ... mpare.aspx
Re: Ford As Built Data Deciphering
I went through every option in the menu. I saw you mentioned the system check, so I made a point of looking there.ClockWorK wrote:Do you know where to look for the Hour Meters in the instrument cluster? I took me a while to actually find them. They are buried in the menus. On my car, they are under Information, System Check, scroll to the bottom. Also, I don't know if the Explorer uses the same IPC, or if the same bits will apply.
As for the deduction part, I would recommend starting with a narrower search by limiting the search to a single year.
Worst case, PM me the VINs you have and I will try it when I've got a bit of time.
I did try limiting it to 2013, and got the same result; nothing.
pnuticus on the Explorer forum tried some and got:
Perfect Bits:
720-01-01 bit 12 val 1
720-01-01 bit 31 val 1
720-01-01 bit 36 val 1
720-01-01 bit 39 val 1
720-01-02 bit 11 val 1
720-01-03 bit 12 val 1
720-01-03 bit 14 val 1
720-02-01 bit 1 val 1
720-02-01 bit 3 val 1
720-02-01 bit 5 val 1
720-02-01 bit 9 val 1
720-02-01 bit 11 val 1
720-02-01 bit 14 val 1
726-22-01 bit 21 val 1
726-22-01 bit 29 val 1
726-25-01 bit 5 val 1
726-25-01 bit 6 val 1
726-25-01 bit 9 val 1
726-26-01 bit 13 val 1
726-43-01 bit 14 val 1
727-01-01 bit 0 val 1
727-04-01 bit 14 val 1
733-01-01 bit 7 val 1
733-02-02 bit 22 val 1
737-01-02 bit 22 val 1
760-01-02 bit 22 val 1
7A5-01-01 bit 16 val 1
Assuming 720-01-02 is still the correct location, my bit 11 is already 1, which in my very limited understanding of binary, means on.
Thanks for the help!
-
MayTheFordBeWithYou
- Posts: 37
- Joined: Sun Mar 19, 2017 9:24 pm
- Vehicle: Ford Mondeo MK4 Early Facelift 09/2010
Re: Ford As Built Data Deciphering
I think i've read all posts in the twelve pages of this thread, but still don't get it. I understand the concept of node-IDs and know many of them. I also know that they are used for reading/clearing DTCs and resetting the module (maybe to call more functions the module provides).
But, can somebody please explain the map of bytesequences in CCC-hexdump to CCC-functionality settings? Where do i find what?
If i change CCC to use "door autolocking" this will even be a flag, a single Bit, somewhere in the CCC dataset. But where?
Also, i don't get what the extra numbers behind the node-id are good for? 720-01-02 means what?
But, can somebody please explain the map of bytesequences in CCC-hexdump to CCC-functionality settings? Where do i find what?
If i change CCC to use "door autolocking" this will even be a flag, a single Bit, somewhere in the CCC dataset. But where?
Also, i don't get what the extra numbers behind the node-id are good for? 720-01-02 means what?
-
ClockWorK
- Posts: 139
- Joined: Sat Mar 05, 2016 11:29 pm
- Vehicle: 2015 Taurus SHO pp
- Location: Detroit Area
- Contact:
Re: Ford As Built Data Deciphering
This will take a little time. I'll probably need to grab between 50 and 100 Explorer and PIU VINs.
You may have to flip more than one bit. In my Taurus, it's 720-01-02, bits 30 and 31 I believe.
You may have to flip more than one bit. In my Taurus, it's 720-01-02, bits 30 and 31 I believe.
2015 Taurus SHO (pp), AWD Gauge Enabled, Engine Hours Enabled, DRLs Enabled, Sync2-to-Sync3.
AsBuilt Compare Tool: http://www.compulsivecode.com/Project_A ... mpare.aspx
AsBuilt Compare Tool: http://www.compulsivecode.com/Project_A ... mpare.aspx
-
anarchyx34
- Posts: 5
- Joined: Sun Mar 12, 2017 2:31 pm
- Vehicle: 2016 Ford Fiesta SE Ecoboost
Re: Ford As Built Data Deciphering
I've read all the pages of this thread and I'm a little confused. I'm trying to see if it's possible to enable fog lights on my '16 Fiesta. I grabbed the AB file for my car, and another one factory equipped with fogs, and ran them through AB-Compare, but I don't think I'm seeing what I want.
I also ran the deducer, and while it does show a difference between the two vehicles (one having the feature, and the other not) it doesn't seem to show any bits.
However if I look at the AsBuilt editor at http://ford.xtlt.ru/ab/, it shows it at byte 18.
Mine has the value at 01 for without foglamp, and the other vehicle shows value 03 which is labeled as "unknown", and not 02 for "foglamp"
I tried editing my XML file to "02" using this site just to see the difference it made. "03" isn't an option it seems, even though that's what the other vehicle's AB file had. I ran it through a diff tool and here's the change.
Changed to:
I'm stuck at what to do next. I'm not convinced the "02' value will work.
I also ran the deducer, and while it does show a difference between the two vehicles (one having the feature, and the other not) it doesn't seem to show any bits.
However if I look at the AsBuilt editor at http://ford.xtlt.ru/ab/, it shows it at byte 18.
Mine has the value at 01 for without foglamp, and the other vehicle shows value 03 which is labeled as "unknown", and not 02 for "foglamp"
I tried editing my XML file to "02" using this site just to see the difference it made. "03" isn't an option it seems, even though that's what the other vehicle's AB file had. I ran it through a diff tool and here's the change.
Code: Select all
<CCC_MODULE>
<CCC_NODE1> 720</CCC_NODE1>
<CCC_NODE2> 726</CCC_NODE2>
<CCC_DATA> FCE3630001013A010401110100020010000200010000010102010004020000030002010100020000020000030201010001000000960A000200000301010000090100000003121176420002010601000100000100010001000102020000001100000100000100050000000701000013020116020001020200000100000204010201000007020200020002000000000300010202000000020000000004000008000000000000000000000000050003000001000002000000000401000102000001000100000000000000000100020000000001001902000003000300020300000100010000000000000000000001000000020000000000010000000000454A</CCC_DATA>
</CCC_MODULE>Code: Select all
<CCC_MODULE>
<CCC_NODE1> 720</CCC_NODE1>
<CCC_NODE2> 726</CCC_NODE2>
<CCC_DATA> FCe4630001013A010401110100020010000200020000010102010004020000030002010100020000020000030201010001000000960A000200000301010000090100000003121176420002010601000100000100010001000102020000001100000100000100050000000701000013020116020001020200000100000204010201000007020200020002000000000300010202000000020000000004000008000000000000000000000000050003000001000002000000000401000102000001000100000000000000000100020000000001001902000003000300020300000100010000000000000000000001000000020000000000010000000000454A</CCC_DATA>
</CCC_MODULE>- Attachments
-
- VirtualBox_Windows 7 Starter_21_03_2017_16_45_18.png (171.51 KiB) Viewed 12770 times