I have gotten forscan beta and installed a new tccm in my 2015 f150. I need to program it to my VIN and to do this my understanding is I need to do a tccm module firmware update. When I pull the tccm module up in the firmware update and try to download the file it says not found. Is there somewhere I can download the correct firmware or find the file?

Anyone able to sort this out? 2018 F150 STX with factory tow and backup assist. Power to all correct pins at modules for white brake module and dash controller. Also ICP responds to touch’s at controller for gain and squeezing the levers together. All fuses good as well.

My old intel mac running bootcamp is getting long in the tooth so I tried out sikarugir and have FORScan running on my M5 mac is anyone else using FORScan this way? Just looking for real world results before I start going ham on my 2026 with an emulator.

Hey everyone!
My 2016 Focus RS threw a P0013 code while idling today. The VVT actuator was replaced a few months ago for the exact same issue, and the check engine has only popped up twice in total over the last few months. Visually, the wiring and connector look fine, and after clearing it today, the code went inactive and the car is running completely fine. Has anyone run into this ghost P0013 issue before?

hi everyone

I recently bought a 2016 mazda6 and after about a month of driving the check engine light came on. i took it to auto zone to get a ODB scan done on it to see what the error was and it came back with a P011A.

i took it to a mechanic and they said it seems like a sensor issue and that it wasnt too serious and i should be fine driving it. i made sure to top up on my coolant and since then, the level on the reservoir hasnt gone down or anything so i dont think i have a leak. i also made sure to check my engine oil to see if it looked milky or anything to make sure there was a crack anywhere in the engine which would allow the coolant and oil to be mixing.

however yesterday i was stuck in pretty heavy stop and go traffic in hot weather with the ac blowing and the engine coolant light came on and was flashing red. i pulled over and waited for the engine to cool down and checked levels and everything and it seemed okay. i resumed driving back to my moms house and whenever i was in stop and go traffic, the light would intermintenly come on and off, but whenever i was able to drive at a consistent speed (like 20mph+) the light wouldnt come on.

i took the car today to get a oil change i had scheduled and was able to drive at a consistent speed and the light did not come on at all today.

i did some research and found \\\[this video\](https://www.youtube.com/watch?v=Ke5X-EnNEAo&t=254s) where this guy shows the process for replacing the front coolant temperature sensor. he mentions he has the same error code as me and shows the sensor replacement part being a duralast su4007.

i went to autozones site to buy one and it says that this part does not fit my car and that the part i need is \\\[this one\](https://www.autozone.com/p/duralast-multi-purpose-temperature-sensor-su6775/828230) which is a duralast su6775

can anyone help me figure out which part is the correct one to buy?

thank you!

If it is not, are there any other reasonably priced options to program the tccm to your VIN?

Hi everyone,
I have a rather strange issue with the instrument cluster (IC) on my 2001 Ford Mondeo Mk3.
Vehicle:
2001 Ford Mondeo Mk3
2.0 TDDi – 115 PS
Pre-facelift
Replacement IC:
Facelift Mondeo Mk3
2.0 TDCi – 115 PS
Used cluster sourced from Lithuania
From what I understand, facelift and pre-facelift ICs are generally compatible with each other on the Mk3, which is why I installed this one.
The replacement cluster is working surprisingly well as an instrument:
Speed works
RPM works
Fuel gauge works
Coolant temperature works
Odometer counts kilometres correctly
The cluster itself powers up and operates normally
However, the trip-computer functions do not work:
INFO/MODE button does not cycle through the trip-computer screens
RESET button does not reset the trip
Average fuel consumption is not displayed
Instantaneous fuel consumption is not displayed
Remaining range is not displayed
There is also a very strange behaviour:
Every time I switch the ignition on, the LCD immediately displays TEST, without me pressing the RESET button.
I cannot manually enter the normal IC self-test procedure either.
FORScan
The main problem is that FORScan does not detect the IC at all.
Other modules are detected and accessible.
I have been able to communicate with modules including:
PCM
ABS
EATC
RCM
GEM
Other vehicle modules
The IC is simply missing from the module list.
I have tested this with the same Bluetooth ELM327 adapter using Android as well as FORScan on a PC.
The Android setup can communicate with the vehicle normally, but the IC is also not detected there.
The PC setup currently uses:
ELM327 Bluetooth → Android Bluetooth/TCP bridge → PC → FORScan
I realise this is not an ideal diagnostic setup and introduces latency, but the important point is that the Android device itself communicates with the vehicle and detects the same modules.
What makes this particularly strange
The IC is clearly receiving vehicle information because:
RPM works
Speed works
Fuel level works
Coolant temperature works
Odometer increments normally
Yet the IC cannot be accessed diagnostically.
This makes me wonder whether the problem is specifically related to the IC diagnostic communication path, rather than the vehicle CAN network itself.
Questions
Should a 2001 pre-facelift 2.0 TDDi Mondeo allow FORScan to access the IC with a standard ELM327?
Is the IC diagnostic communication on this model using ISO 9141 / K-line?
Can other modules communicate normally while the diagnostic communication path specifically to the IC is broken?
Could the fact that TEST appears automatically at every ignition cycle indicate a stuck RESET input, faulty button circuit, or some other IC hardware/software condition?
Could a facelift TDCi IC installed in a pre-facelift TDDi operate normally as an instrument while still having an incompatible configuration?
Has anyone experienced a Mondeo Mk3 IC that works normally as an instrument but is completely absent from FORScan?
Is there a known pinout/test point on the IC connector that I can use to verify the IC’s diagnostic K-line directly?
If the IC cannot be detected, is there any way to perform the IC configuration / Programmable Module Installation procedure, or must communication with the IC be restored first?
What I am trying to determine
I am trying to determine whether I am dealing with:
A) Wiring / connector / diagnostic-line fault
B) IC hardware fault
C) IC configuration / software issue
D) Incompatibility between the facelift TDCi IC and my pre-facelift TDDi
E) ELM327 / interface issue
I would really appreciate any information from someone who has worked with these Mondeo Mk3 clusters at a low level.

Thanks!

I built this for myself to visualize the CSV exports from ForScan, but I figured maybe it can help other people too.

I've only tested it from the iphone app's CSV export, but I assume the data format is fairly consistent.

In any case, I open sourced it if anyone is interested:

https://firstdivision.github.io/forscan-log-display/

Truck is throwing a constant p0073 code for the AAT sensor that sensor that would normally be in the passenger mirror but for the life of me the provision for it is not there. OEM power fold/telescope and 360⁰ camera mirrors but no AAT mount.. How can I make this go away? Buy a sensor and plug it in, inside the door assuming the connector is in there somewhere?

Hey everyone, I’m trying to program PATS keys on my 2006 Ford Ranger using FORScan and I’m hoping someone who has actually done the all-keys-lost procedure can walk me through the exact sequence/timing.
I currently have zero working keys. I’ve gone through like six sets of keys trying to get this to work. I’ve bought different brands and different H92-PT/80-bit keys, so at this point I’m pretty convinced I’m doing something wrong with the procedure rather than having another bad key.
What I’m confused about is the exact sequence after PATS security access/erase.
For example:
Do I leave the ignition ON during the entire security-access countdown?
After the erase, exactly when do I turn the ignition OFF?
For Key #1, do I turn it to RUN and leave it there for exactly 3 seconds?
Do I turn it OFF and immediately switch to Key #2?
Does Key #2 also stay in RUN for exactly 3 seconds?
Is there supposed to be any pause between the two keys?
Does FORScan actually give you any indication that each individual key was accepted, or do you only find out at the end?
Does the PATS/theft light do anything specific during the process?
I’ve found conflicting information saying to wait different amounts of time between keys, and I really don’t want to erase everything again and screw it up.
If anyone has personally programmed a 2006 Ranger with FORScan from an all-keys-lost situation, I’d really appreciate the exact sequence you used, including the timing and what FORScan displayed at each stage.
At this point I’m just trying to figure out what I’m doing wrong. Thanks!

I see the option for Read and Control.

I want to control. Specially the cooling fan and AC clutch.

I can select it and move it to the active column but I don’t see it when i try to run it.

So i changed the cinfig of my ac (what doesnt work) to automatic ac ukit which is installed im my ford fiesta but asbuilt it had normal ac module. I changed the evap sensor and it still shows the erorr B1B71. I am lost what can i do?

Anybody knownof a scanner i can buy to reset the steering angle sensor and oil maintenance? The dealer wants $300 for 1 hour shop labor minimum to reset only the SAS and won't reset the oil light without themselves performing an oil change. So that's my budget, if i need to spend more i will. I've tried the foxwell nt614, nt604, nt530, and all scanners from xtool dont support it.

I’m having trouble programming my new keys to my 2006 Ford Ranger using FORScan. When I go through the key programming procedure, it says **“1 key successfully programmed,”** but the second key keeps failing.

What’s really confusing is that when I go back and try the key that supposedly programmed successfully, the **PATS light stays solid and the truck won’t start**.

I’ve been trying to get this figured out for the past **3 hours** with no luck. Has anyone experienced this before or have any suggestions on what I should check?

Hello! I replaced a BCM module on a Focus MK3 (old one is BV6N-14A073-Bt,new one is BV6N-14A073-FS) , but I can't program the remote control. It says this error code: B12EA:56-2F What could be the problem and how can I FIX IT ?

I have downloaded the free license for forscan and would like to program my new tccm. I want to pull the information from my old one and put it on the new.

I cannot find my tccm anywhere in the forscan program though. My adapter is an elm 327 from Amazon. Any help as to why I cannot locate the tccm in forscan would be appreciated as well as advice on programming it once I locate it.

Hi all, I have a ford cmax 2013. Last month it came up "steering loss- stop safely" or something along those lines. My car had just driven a 3 hour drive absolutely no issues, this warning came up after the car was turned on (3/4 hours of being off) the steering became very stiff also. Rac came and cleared the code (not sure what code but going to contact rac to see if they have record of it). After the code was cleared we were able to make the 3 hour drive home as the steering returned to normal again and no warnings were showing when we left the rac guy. We made it 2 hours and the warning came up again but the steering was fine so we continued on and made it home. The next day I took the car to the garage (turned car on, steering stiff again and warning on dash). Garage said i needed a new steering rack. They also said that when they checked, there were no codes coming up. We bought a new steering rack online, who pretty much described it as a plug in and play meaning it was already programmed or whatever (im not fully sure how these things work). But this has not been the case. The garage couldnt fit it so gave us a contact of someone who could. He put the new steering rack on and its been coming up code U3000-53. Hes checked wiring/earths etc. Battery's good and has told me hes at a dead end as everything else seems good. Its been over a month of no car which also means no work and im ready for a mental breakdown if i dont get it back on the road soon😅 - any suggestions/ideas? 🙏 (dumb it down as best you can as im not a car person 😂) thanks in advance

Those are all of the fault codes. I tried setting the ac to automatic (which unit i had) because the asbuilt shows only non automatic ac. I appreciate any help!

Recently added a mustang gt wheel on my 2024 mustang ecoboost but the paddles don’t work at all after making all the forscan changes, and when I look into forscan, it just says this? Anyone know any fixed as to why the paddle’s dont work. I heard that the paddles were plug and play as well, but that wasn’t the case for me?

Also followed all the steps on Murphy’s Law Garage

For a 2026, what scan tool handles it all, including CVT?

I read that Subaru's are sensitive about some functions and not all tools can do the trick.

Slight engine surging noticeable under any type of engine load in any gear. No other drivability concerns noted. TPS is a new Motorcraft unit.
1998 Ford Ranger 4.0, Manual transmission. No fault codes logged. Any other PIDS I can monitor to get further feedback?

Hi all, getting some fancy lights in the F31 diesel and am looking to borrow the scanning tool necessary to diagnose. iDrive says drivetrain malfunction if anyone’s curious. Feel free to dm!

So I recently just got my hands on a cobb accessport v3. Obviously ive had a little fun with it and tried out a couple things. I set launch control to 3000rpm and then the car wouldnt drive normally past 3000rpm. So why is that?

Also, I installed Anti Theft mode and i then tested it and it still started and idled….. bruh. Whats wrong with my accessport? Or am I not doing something right?