I have two more that don't honk: https://www.dropbox.com/s/cp02piq8yozpgwz/2014%20TB%20FiST%20no%20options.ab?dl=0
https://www.dropbox.com/s/e0muh8wsauzkyh1/3FADP4GX7FM137911.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 ...
Search found 4 matches
- Tue Mar 14, 2017 8:51 pm
- Forum: Configuration and Programming
- Topic: Ford As Built Data Deciphering
- Replies: 286
- Views: 398709
- Tue Mar 14, 2017 8:42 pm
- Forum: Configuration and Programming
- Topic: Ford As Built Data Deciphering
- Replies: 286
- Views: 398709
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.
- Tue Mar 14, 2017 8:36 pm
- Forum: Configuration and Programming
- Topic: Ford As Built Data Deciphering
- Replies: 286
- Views: 398709
Re: Ford As Built Data Deciphering
The two AsBuilt files appear to have very different BCMs (726-XX-XX). Which is why that particular section does not show pairs of values when comparing. One file simply lacks 726-18-01 thru 726-49-04.
Both files were created using the same website, is there a different way to create the AsBuilt ...
Both files were created using the same website, is there a different way to create the AsBuilt ...
- Tue Mar 14, 2017 5:06 pm
- Forum: Configuration and Programming
- Topic: Ford As Built Data Deciphering
- Replies: 286
- Views: 398709
Re: Ford As Built Data Deciphering
I don't really know what I'm doing and could use some help. 6 months into the 2014 Fiesta ST build Ford added a double honk if the key is outside of the car while running. I have two as built files, both 2014, both with the same options, one honks, one does not. Can anyone help me figure out what I ...