@ETangooo thanks for answering my clearly foolish question. Such a shame. My 14 forester xt had had zero issues for 236k miles and now I have to drive around with a Bluedriver scan tool in my car to reset the codes at least once a day until I can pick up a new vehicle. Just not worth spending 3500 for Subaru to do this repair (and from what I understand replace the ecu) for a vehicle not worth much more than that. It's a shame that it's not a sensor or the wiring but it never seems to be ( and I have tested everything) Thanks again
@@Samlol23_drrich $3500 seems excessive. Get another quote. It's maybe 8 hours of work and a few parts (mainly the sprocket). Subaru should cover the ECU. My XT had this problem at 40,000 miles.
@stan916 wow. 40k? It would make that the last subaru I would own. At 240k there's no way tbey are going to cover the ecu and it's a shame it needs to be changed and can't just be reprogrammed. In the mean time, until the inspection is due I'm driving around with a Bluedriver bluetooth code reader plugged into my odb2 and when it codes I open the app on my phone and clear it as I'm driving. Sometimes it's once per trip and sometimes it's no times per trip. Sucks. Thanks for the advice!
@@Samlol23_drrich there is a way to clear the hard coded memory now. You need a specific scan tool that can access special function once you put your car in service mode. Thinkdiag2 scan tool can do that. There a RU-vid video a guy walking through it on a forester
