Menu
Page 14 of 44 [ 658 posts ] Go to pagePrevious1 ... 11, 12, 13, 14, 15, 16, 17 ... 44Next
- Ford As Built Data File Download Windows 10
- Ford F150 As Built Data
- Ford As Built Data File Downloads
- Ford As Built Data File Download 2017
- Ford As Built Data Website
Load ASBUILT data for edit From Ford ETIS by VIN. VIN: From local XML asbuilt file. To program the PCM with As-built information via Ford IDS software: Enter the Module Programming menu in the IDS Select As-built. Aug 12, 2017 The free Ford website listed above does not have this file download option at times. In box F of Figure 1, there sometimes are additional data paths to find As Built data, and sometimes not. Most module As Built data for Ford vehicles from 1999 and forward are available. This is a small program for comparing As-Built files for Ford/Lincoln/Mazda vehicles. The program can compare single.AB (Ford/Motorcraft) files and multiple.ABT files (FORScan As-Built format), as well as UCDS files. The program can also export to.ABT and to UCDS.XML. Mar 31, 2018 This video is for people that need to upload as built data files sent to them. I made this for people that receive my files for the 2018 Mustang digital instrument cluster and SCCM from me.
Posts:24 Joined: 29th Nov 2007 Ride: 2001 F350 Diesel 4x4 Location: McAllen Texas Oustide Australia | The VIN can be entered by hand. The menus list options to enable or disable as well. The last 4 digits are some type of software version info. Here is the file for the 5r29-12a650-ane. HADCEN3. Exhaling the info using the FMP software from the old ECU, all the features will be transferred. If not, you could use the 'As Built Data' if availible from ford. This would program all the features as it came out of the factory. The way the info was changed in previous posts to enable features, is exactly what the as built data does. Its just the bit level info to indicate what features are present. Add .zip and extract.
| ||||
Top |
| |||
Posts:1123 Joined: 7th Nov 2005 Location: Newcastle NSW, Australia | I have some motivation to understand the inhale/exhale bit a little better, but for a different reason. The SX Territory, which is an AWD version of our cars, has a feature called 'Hill Descent Control' that is only available on some models. However the only real difference between those with or without this feature appears to be in the software, as the hardware is the same. The Bosch 8.0 Module without this feature has the code: 3R73-2C405-AA And the Bosch 8.0 Module with this feature has the code: 3R73-2C405-BA So the big question is whether the whole code needs to be reflashed, or whether it's just a matter of loading different 'as-built' data. I only just sent you a PM with some VIN's and PCM codes - one of them is for 3R73 Territory with the 'HDC' feature disabled. I took a bit of a look at your attachment and it's difficult to make out the format of the data or it's application. It's looking to me like we'd need either a decoding miracle, or we'll just have to bite the bullet and get FMP for ourselves for a little while. Lukeyson | ||
Top |
| |||
Posts:1656 Joined: 22nd Jun 2005 Location: Melbourne VIC, Australia | Very interesting read guys , keep up the good work cheers _________________ FS [VIC]: WorkShop CleanOut - Assorted Parts Some New & Chassis Dyno http://www.fordmods.com/ford-parts-for-sale-f17/fs-workshop-cleanout-assorted-parts-some-new-chassis-dyno-t123623.html | ||
Top |
Posts:24 Joined: 29th Nov 2007 Ride: 2001 F350 Diesel 4x4 Location: McAllen Texas Oustide Australia | Ok the SX Territory (3R73) does not appear anywhere in the software. The Falcons do appear, I am in the process to get the 'as built data'. The inhale/exhale process if logged should reveal all that is necessary to read/write the modules. I believe the data is what is written to the module, so unless you read module It means nothing. I believe with a sub and some sniffing you will have what you are looking for. I believe the bosch module has been cracked in the EU area. These bosch modules are not common in the US fords that I am aware of. | ||
Top |
| |||
Posts:1123 Joined: 7th Nov 2005 Location: Newcastle NSW, Australia | I mentioned it before, but the IDS software that you can download from Motorcraft will let you manually type in the PCM code from your car and will recognise what type of car you have. Everything you read back to me in one of your PM's, Hard_ware, appears identical to what I found in the IDS. Interestingly enough, in the IDS, I can enter and locate those two cars - BA Falcon and SX Territory. However, when I enter the PCM codes for the newer models (From about 2005 onwards, the BF '5R29' Falcon and the SY '???' Territory) I can't find them - well for the 5R29 anyway. I might try 8R29 just to be thorough. So some things do seem incomplete in places. I wonder if there's anyone reading this that might have access to an SY Territory of some sort and would be willing to collect and forward us the Code on the PCM? Lukeyson | ||
Top |
Ford As Built Data File Download Windows 10
| |||
Posts:24 Joined: 29th Nov 2007 Ride: 2001 F350 Diesel 4x4 Location: McAllen Texas Oustide Australia | The code on the pcm in the post (3r73) should be good enough to find. The software I was looking thru was the IDS world wide. It lists the mazda US and Japan and European models. I found no trace of the 3R73 code, or Territory name. Spoke too soon I found the info.'The Ford Territory is a crossover SUV built by Ford Australia and based on the EA169 platform of the Ford BA Falcon. It was released in April 2004. Its code name inside Ford was E265'. Model is listed as E265. The file for the 3R73-2C405-BA is a large file 6.4 megs compressed. This exceeds the forum limit. I will send you a P.M. The file name is HAAP9B2 is the AWD, HAAP9A2 is the RWD. I find the 5r29 thru MY06 and the 8r29 thru MY08. | ||
Top |
| |||
Posts:1123 Joined: 7th Nov 2005 Location: Newcastle NSW, Australia | Hmm. BFII is 8R29 perhaps? I'll look into it. The file HAAP9B2 was only 462k - so I'm not sure if I have the same as you have. There's some text at the front of each file that's almost readable. It's a pity I can't make sense of much else yet. These files look like PCM calibrations to me. IDS downloads these as well. However, while the IDS software is downloadable from Motorcraft, the 'Calibration' software that comes on the VCM DVD is not - I've been hoping to get a copy of that at some point, but alas I think it's not to be! I've got to say, I'm not real impressed with that EEPod website (). There's absolutely no mention of the fact that it's a J2534 tool, and looking at it, I can't tell WTF it does. Does it do full J2534 - or some sort of subset? Who can tell? As a customer, I'd hit those guys up for a better website. It is, in all honesty, crap. I would never buy anything based on such a poor level of information. And if it does what you say it does, they'll sell more off your comments than that website...! Lukeyson Last edited by Lukeyson on Sat Dec 08, 2007 10:12 pm, edited 2 times in total. | ||
Top |
| |||
Posts:1123 Joined: 7th Nov 2005 Location: Newcastle NSW, Australia | OK, I need to reconcile a bit. These filenames you've come up with - are they from FMP or the IDS? I'm able to download new calibration files with the IDS, but not older stuff as I just mentioned. So how were you able to figure out the name of the file that we needed? Certainly from the IDS it's not obvious. Or maybe it is and I just don't know where to look? I'll assume for the moment that you got it from FMP until you tell me otherwise. I've done a lot of poking through the IDS and not found the description of the Territory you came up with. And it's dead set accurate. So that one's got me too. While you step in the regions that are unknown to many of us, you make godlike footprints.... Lukeyson | ||
Top |
| ||||||
Posts:24 Joined: 29th Nov 2007 Ride: 2001 F350 Diesel 4x4 Location: McAllen Texas Oustide Australia | The files are downloaded to the FMP software which is the same process as the IDS from what I can tell. The files are found by finding the first reference to the ECU code written on the ECU. Then looking up if a new part number is listed. If it is you repeat the process until the latest part number has no newer part number, then look up the file used. I will try and attach a file to look up the codes. The file is too large to attach. Its 2 megs MS excel format compressed. This has all the data for the Motorcraft software. Ok give this a try change the part1 to .exe and change the last part of part02 to _186.rar delete the _266.xls and run the first file. It should combine and give you a 2+ meg excel .xls file. Here is all the info I have gathered. Post if it works.
Last edited by Hard_ware on Sun Dec 09, 2007 12:38 pm, edited 1 time in total. | |||||
Top |
Ford F150 As Built Data
| |||
Posts:24 Joined: 29th Nov 2007 Ride: 2001 F350 Diesel 4x4 Location: McAllen Texas Oustide Australia | With the excel file, you will have the data I have used to look up the files.Any old files are not availiable, only the latest updates are on the motorcraft site. I was able to get this file from one that was sent to update the WDS/IDS/FMP and I saved, and extracted it. So far the info it contains has been on the server to download. Make sure you keep looking up the new part number until no newer part number is listed. Then cross over to the file name. This still does not solve how to write the data without a sub. I am working on that. | ||
Top |
| |||
Age: 38 Posts:6275 Joined: 24th Nov 2004 Ride: '06 BF GT-P Power: 293 rwkw Location: Canberra ACT, Australia | Found the specs for mine... Code: A_OR_D Model Type SubType Year code CalID Filename strategy PartNum BasePN NewPartNum Catchword Checksum HardwareType RomSizeKb Bit32 CalibrationNumber Comments NotCertified QualifierValueGrpList QualifierValueGrpName QualByCalID Mandatory TSBNum TSBPartNum Calfilelist CalFileGrpName Dependencylist DependencyGrpName BLfilelist BLFileGrpName ModuleDN QualByCalid_new RationaleMngrpname RatMnemonicnames Subfilelist SubFileGrpName U FALCON 4V 5.4L MY06 (CM_CONNECTOR 16PIN) E43E HADCEN3 5R29-ANE 12A650 5R29-ANF A5NE 7F6E ASU-121 1024 TRUE (User-FORDNA1ESAYLOR ChangedData) BF - Falcon GT 6spd Auto - Job1 + 90 FALSE QVG_AUTOVHSCPETREM_O6SBF 3 FALSE - PCM 3 SubFileGrp_610 U FALCON 4V 5.4L MY06 (CM_CONNECTOR 16PIN) E43E HADCEN3 5R29-ANE 12A650 5R29-ANF A5NE 7F6E ASU-141 1024 TRUE (User-FORDNA1ESAYLOR ChangedData) BF - Falcon GT 6spd Auto - Job1 + 90 FALSE QVG_AUTOVHSCPETREM_O6SBF 3 FALSE - PCM 3 SubFileGrp_610 U FALCON 4V 5.4L MY06 (CM_CONNECTOR 16PIN) E43E HADCEN3 5R29-ANE 12A650 5R29-ANF A5NE 7F6E ASU-161 1024 TRUE (User-FORDNA1ESAYLOR ChangedData) BF - Falcon GT 6spd Auto - Job1 + 90 FALSE QVG_AUTOVHSCPETREM_O6SBF 3 FALSE - PCM 3 SubFileGrp_610 U FALCON 4V 5.4L MY06 (CM_CONNECTOR 16PIN) E43E HADCEN3 5R29-ANE 12A650 5R29-ANF A5NE 7F6E ASU-181 1024 TRUE (User-FORDNA1ESAYLOR ChangedData) BF - Falcon GT 6spd Auto - Job1 + 90 FALSE QVG_AUTOVHSCPETREM_O6SBF 3 FALSE - PCM 3 SubFileGrp_610 (table is a mess, but the idea is there) Now of the 4 results, they all appear the same, no difference in part numbers, and (I guess) the checksum (that should show even the smallest change being evident). _________________ 1998 DL LTD in Sparkling Burgundy, daily, 302W, stereo, slow - 97.5rwkw 2006 BF GT-P in Ego, mods. 293rwkw - 12.427@109 - 0-1000m 24.838@221 | ||
Top |
Age: 38 Posts:6275 Joined: 24th Nov 2004 Ride: '06 BF GT-P Power: 293 rwkw Location: Canberra ACT, Australia | Just found something REALLY cool. Look up the comment for catchword B7LA/B7MA/B8NA/B7PA. And then B8LA/B8LB/B8MA/B8MB Thank me later. _________________ 1998 DL LTD in Sparkling Burgundy, daily, 302W, stereo, slow - 97.5rwkw 2006 BF GT-P in Ego, mods. 293rwkw - 12.427@109 - 0-1000m 24.838@221 | ||
Top |
Posts:1656 Joined: 22nd Jun 2005 Location: Melbourne VIC, Australia | Lukeyson wrote: I mentioned it before, but the IDS software that you can download from Motorcraft will let you manually type in the PCM code from your car and will recognise what type of car you have. Everything you read back to me in one of your PM's, Hard_ware, appears identical to what I found in the IDS. Interestingly enough, in the IDS, I can enter and locate those two cars - BA Falcon and SX Territory. However, when I enter the PCM codes for the newer models (From about 2005 onwards, the BF '5R29' Falcon and the SY '???' Territory) I can't find them - well for the 5R29 anyway. I might try 8R29 just to be thorough. So some things do seem incomplete in places. I wonder if there's anyone reading this that might have access to an SY Territory of some sort and would be willing to collect and forward us the Code on the PCM? Lukeyson Lukeyson , try Ferntree Gully Auto Salvage forum sponsor http://www.fordmods.com/forums/ferntree ... e-f24.html I sure they might be able to help with code on the PCM's cheers _________________ FS [VIC]: WorkShop CleanOut - Assorted Parts Some New & Chassis Dyno http://www.fordmods.com/ford-parts-for-sale-f17/fs-workshop-cleanout-assorted-parts-some-new-chassis-dyno-t123623.html | ||
Top |
Posts:1123 Joined: 7th Nov 2005 Location: Newcastle NSW, Australia | Hi FPV_GTP. Yeah, I've dealt with FTG before. Good bunch of blokes. They are pretty busy so I try not to bug them with too much stuff. That xls is a bit of a bonanza. I thought I'd work through many of the model numbers and PCM types. For the Falcons: 3R23 - BA + BAII 5R29 - BF 7R29 - BFII 8R29 - Orion (!!!!) So THAT's what you mean by MY08! (Orion Production starts in April 2008) For Territory 3R73 - SX 5R79 - SY 6R79 - SY Turbo 7R79 - Not sure. I see reference to Thailand and FSA (South Africa) for this, but I also see these references for 5R79. Could this be the new FPV Enhanced Turbo Territory? Each of these have a number of different flash types. This defined by the first letter aftert he 12A650 bit. I'll see if I can figure out the relevant of each letter. For example, 3R73-12A650-A* is the 2WD SX terry, 3R73-12A650-B* is the 4WD SX Terry. It's interesting that the SY Turbo get's it's own model designation. But how about the Orion stuff eh! That's cool. Lukeyson | ||
Top |
| |||
Posts:1123 Joined: 7th Nov 2005 Location: Newcastle NSW, Australia | data_mine wrote: Just found something REALLY cool. Look up the comment for catchword B7LA/B7MA/B8NA/B7PA. And then B8LA/B8LB/B8MA/B8MB Thank me later. My goodness. I was spinning at seeing the Orion in there. I wonder if this is really a GTHO, or if it was just renamed Cobra at the last minute? Do we dare spread the news? Because it might be spurious. Lukeyson | ||
Top |
Page 14 of 44 [ 658 posts ] Go to pagePrevious1 ... 11, 12, 13, 14, 15, 16, 17 ... 44Next
- Dismiss Notice
Holiday Special! - 2 for 1 Elite Explorer sale! Right now you can purchase an Elite Explorer membership for $20 and receive a two year membership! Click Here to start your membership and get rid of the ads!
to owner generated reviews, discussion, tech tips, and more! The #1 Ford Explorer enthusiast resource on the Internet since 1996. We also cover the Ford Ranger, Explorer Sport Trac, Mercury Mountaineer, Lincoln Aviator, Mazda Navajo, Mazda Pickups, and the Aerostar.
Register Today It's free! This box and some ads will disappear once registered!
Discussion in 'Stock 2011 - 2019 Ford Explorer Discussion' started by Exploder82, October 2, 2015.
Ford As Built Data File Downloads
Ford As Built Data File Download 2017
Ford As Built Data Website
We Support Our Troops!