Forum Fordtransitconnectforum

@Don Ridley, I was able to go and setup an account, enter the VIN, and get factory as-built data from Motocraft just now. Might try again if you previously hit a roadblock in your own endeavors.

Don, Thanks for more to consider. It is possible to pull some as-built data from the vehicle computer via Forscan, which is what I'm asking forum users to potentially share. I'm not completely following your statement about the Motocraft site with factory as-built data. Can you expand on that? would this have been additional info beyong what we can pull ourselves with Forscan? If there is any line of editable data in any computer that corresponds to a wheel diameter, rev/mile, etc, that is what most of the forums (across F150/250, Gen2 TC, focus etc) point towards sometimes being able to manually override. That's my goal to attempt. I hear you on AI - but it's another tool I'm using. But, every week it is growing in capabilities faster than we can comprehend, so though unlikely, I'm not ruling out that it somehow is combing information that you and I cannot access. Unlikely, but not impossible.

I had the fronts put on last fall at 100,000ish miles. Replaced the 2 front half shafts at the same time and its like a new van.

Get the van washed after snow events with an underbody wash. My 2016 with 116,000 miles is clean as heck underneath. And I live in northern Indiana an hour from Michigan. (snow)

THey aren't "needed". They are there to keep the pad from rattling against the rotor. Use them if you have them. No biggie if they are gone.

Those are nastier than mine were for my first brake job at 9 years and 103,000 miles. Seriously.

One thing to keep on mind, Ford only wrote programming to support options they defined for a product line. The Gen 2 TCs have a short list of tire options Forscan can choose from. These are likely the tires the factory would have supplied on varions versions of the van. Due to the computer acthitecture, these are the only options we can reverese engineer. Other Fords like the F150, F250 trucks have a wide range of tire options. These trucks have a different computer architecture and users can input a large range of tire sizes once they have converted the tire size to a hex number. Even this has limits based on the max tire size Ford designed the softeare to handle (probably due to factory tire options). Finally, as of today the Motocraft site used to download factory as built data has been locked down by Ford. It is not working and you now need an account to even get to the proper page. Ford appears to be preventing users from reverse engineering the as built coding. I don't know how/what you are using for AI, but nothing that is accessible to normal users can accurately solve these types of problems. AI currently relies on forums like this for information and unfortunaly, there is a lot of misinformation on any forum and the information is not properly documented for a specific application (model, year, trim level, country etc.)

@windguy Great suggestions, I have not gotten that far due to time. I do have some clues - and i'll share an abridged update on findings thus far: I am going to be painfully clear on van model/etc for clarity for all future readers Gen2 TC is somehwat well documented elsewhere in this forum and Forscan forums on selecting/modifying screen menues as well as manual modificatino of as-built wheel size data. I've read extensively on that. I've used Forscan on my Gen1, there is no immediate tire size selection. Further, as as far as I can tell, As-built data is not revealing any obviuos lines of hex data that would correspond to a wheel size. I believe the wheel size data, or revolutions/mile data for speedo is stored in PCM in Gen1 TC. Forscan (thus far from my experiernce) cannot read PCM on Gen1 TC. Hoping maybe i'm doing something wrong. PCM on my van (2013 United States), according to Chat GPT across broad cross searching, is the same make PCM used in 2010/2011 Focus. I've also learned perhaps the software ELMconfig can read PCM data, but I have yet to find a reliable download source for this software to try it. Also, there is vague reference that my AI has found that suggests a Ford Dealer may be able to read/write PCM module from Ford Focus 2010/2011, and thus might translate to being able to the same my 13 TC Gen1. I haven't gotten further on this lead. My ask above for someone else to corrobrate their data from their van (from a non US variant) is an a third parallel effo

@drum_buster Just some random thoughts to help get your question answered. Have you tried posting your question on the FORSCAN forum? I have a Gen2 TC. I'm vaguely aware that the TC shares some similarities to the Ford Focus. Not sure about the Gen1 TC, but perhaps that too is similar to the Focus or another Ford model. If so, perhaps there's a Focus forum you can post your question on as well. Keep us posted. Good luck!

Still searching for answers here: If anyone in UK has a gen 1 Transit Connect or Tourneo, and can use forscan to send me a screenshot of your IC, VSM, and GEM As Built, as well as your factory tire size, that would be appreciated. I'm having AI reverse engineer to identify if any of these as built data corresponds.

Good update. Seemed like it was happening regularly and now it's not, so you may be right on the reset fixing the problem. It was a strange problem to begin with. Forscan is such a great tool. Glad you were able to use it effectively to solve your problem.

Thank ya Sir! I found a PAM at the local wrecker for $150 but oddly enough, this issue has not reoccurred since it left me stranded last time. The last time it happened I reset the PAM w FORScan so I’m thinking maybe it just needed to be rebooted, I dunno but it hasn’t happened in a few weeks and this van logs at least 150 mi/day in the same conditions that triggered the first incident.