Like many car owners, we love our Skoda Yeti, but there are times when the dashboard lights up like a disco, and not in a good way. When those fault lights decide to stay illuminated, the initial charm wears off quickly, and thoughts drift towards browsing for new vehicles. However, before making any rash decisions, a bit of investigation can go a long way, and that’s where the Foseal Obdii Fo-01 scanner comes into play.
Our Yeti, a 2015 diesel model, comes with the joys of AdBlue to meet emission standards. This means regular top-ups to keep things running smoothly. Early on, after purchasing the car in 2019, we faced weeks of frustration with the AdBlue warning system. It wrongly indicated a critically low level, threatening to immobilize the engine. The garage eventually resolved it, though the exact fix remained a bit of a mystery. Since then, proactively topping up the AdBlue before the warning light appears has seemed to keep this issue at bay – fingers crossed.
We also experienced the dreaded yellow engine icon light a couple of years back, diagnosed and resolved (we think) by the dealer replacing a NOx sensor. This light, commonly known as the emissions control light, can be quite concerning.
Recently, the emissions light reappeared. This time, armed with my Foseal OBDII FO-01 gizmo, I plugged it into the Yeti and it flagged up the error code P20EE. While information on this code was scarce when it first appeared, thankfully, online resources like https://obd2pros.com/dtc-codes/p20ee/ now provide insights. In essence, the P20EE code points to a “SCR NOx Catalyst Efficiency Below Threshold” malfunction. Common causes often relate to the DPF Filter Element and DEF Fluid (AdBlue) issues. This diagnosis aligned with our past experiences and the nature of diesel engines, which, as our salesman hinted, prefer longer, higher-speed journeys to maintain optimal performance.
Our Yeti had been primarily used for shorter trips recently, which might have contributed to the error. Since the engine seemed to be running normally, I decided to use the Foseal FO-01 to clear the error code. And just like that, the light disappeared!
Finding the OBDII Connector with Foseal FO-01
For those unfamiliar, the OBDII connector is essential for plugging in your diagnostic tools like the Foseal OBDII FO-01. In the Skoda Yeti, accessing it is quite straightforward. Position yourself upside down in the driver’s seat, head towards the pedals, and you’ll find the connector located above the throttle pedal.
Navigating the Foseal OBDII FO-01 Interface
Once connected and the ignition is turned on, the Foseal FO-01 springs to life. The home screen is user-friendly and intuitive.
Navigating to the ‘Diagnostic’ menu (option 4 out of 7 in this version) allows you to delve into error checking.
From here, you can read and, if you feel confident, clear error codes. The Foseal OBDII FO-01 also includes a DTC Lookup screen.
While the DTC lookup is present, it’s worth noting that its utility might be limited compared to online databases for detailed error code information.
Since clearing the code, we’ve driven a few hundred miles, and so far, the dashboard disco lights have stayed off. With longer journeys planned, we’ll be keeping a close eye on whether the emissions control light decides to reappear. The Foseal OBDII FO-01 has proven to be a handy tool for understanding and addressing these minor car hiccups, offering a bit more control and insight into our Skoda Yeti’s occasional dashboard dramas.
