CBB9M
23 year Ranger veteran
Joined: Sun Oct 22nd, 2017
Posts: 371
Name: Bill ... Occupation: Interests:
Reputation Points: 371
|
If it were me and if it were my problem to fix, I'd go out to my garage like a boss, armed with my lappy (no, not my phone which has FORScan Lite) that's running Windows and has the latest version of FORScan, and using the OBDLink MX already plugged into the OBDII port on the vehicle I'd scan for codes. By doing this I know I'd be scanning all codes but especially the extended/proprietary to Ford codes, not just the generic OBDII codes that all vehicles built in 1996 and up need to make available to consumers, techs, the kids at Autozone (that are virtually guaranteed to NOT have a scan tool capable of pulling the extended codes), people who use Torque and Torque PRO, you get the picture. If FORScan didn't kick up a code(s?) I'd be posting the situation over on the forums at FORScan, where the highly motivated staff (in my experience) would most likely work with you on this. First question would be confirmation and peace of mind that FORScan can see codes pertaining to TC operation (IMO, I'd be surprised if it didn't).
I would also get my hands on the FSM (ONLY the FSM) for your vehicle if you don't have that already and do some reading. If you don't know how TC works, there is probably a section titled something like, "theory of operation". Read it. I'd next move on to diagnostics and/or look for the procedure for diagnosing the code you found using FORScan. Anyhow, food for thought in all this.Last edited on Wed May 2nd, 2018 08:51 pm by CBB9M
____________________
-Bill
04 Ranger FX4 Level II, several mods
|
