digibum

Still waiting... The service center has been waiting for two weeks now for a reply from the importer (tech support) to finally figure out what the next step will be. Honestly, I'm at my wits' end with them and I'm this close to calling them up and giving them a piece of my mind about why everything moves at a snail's pace.

@Breezy_Pete thank you for your effort! This morning, I ran a scan on a cold engine and got the usual cold-start behavior, and refused to clear: Immediate rescan: I cleared the code (P25AB00) on cold ignition. OBDeleven automatically rescanned the ECU a second later and caught the code again immediately. Checking the Freeze Frame data, I noticed a new timestamp and slightly changed parameters. I retried clearing it twice, and after each clear, a new timestamp and slightly changed parameters appeared. The 60-second delay: After failing twice, I turned the ignition OFF, waited a full 60 seconds, and turned the ignition back ON. Upon scanning, the frequency counter had increased to 2. I cleared the code, and this time it stayed gone! I then drove to work with no faults at all, and the Start-Stop system worked perfectly the entire way. A fresh scan upon arrival at work showed zero faults. I also checked the fuse box in the engine bay — I pulled out and reseated all fuses and relays to ensure good contact. All pins and terminals look completely spotless with zero visible signs of corrosion or oxidation.

Tested the code after letting the car sit for 6 hours (cold engine): Cold Engine (Ignition ON, Engine OFF): The code was static and refused to clear. I tried clearing it 4 times in a row, but it reappeared instantly on every rescan without even starting the engine. Warm Engine: After driving to lunch and back, I cleared the code on ignition—it wiped cleanly and stayed gone. Will check the rest of the suggestions when I come home. And retray to clear fault when the engine is cold.

Could be corrosion or bad connector, where is this fuse box in the bottom of engine bay? I do have aditional fault's that are allways present and i never cleare those. Air Conditioning: Air quality sensor faulty (B10AF04 active). Dashboard: Function restriction due to communication interruption (U111000 static). Multifunction Module: Data bus error value recived (U112300 static). Multifunction Module: Fog mode active (C118E00 static)

DNFE / 2.0 TSI EA888 Gen 4 / 280 hp

I am attaching my full engine details from OBDeleven I'll check the voltages with OBDeleven. I can easily get the resting voltage (ignition ON) and running voltage after start. I probably won't catch the split-second dip during actual cranking due to the app's refresh rate, but I'll log what I can and post the numbers!

It was only a very short time — just a few seconds. Between step 2 and 3, I turned the ignition off, opened and closed the driver's door, and then immediately turned the ignition back on to run the scan. I will definitely try your suggestion of leaving a full 60 seconds (or more) with the ignition off before turning it back on... Yesterday, I replace the N522 valve once again, just to 100% rule out the possibility that the first new valve installed by the dealership was defective. When I replaced the valve, the engine was fully warm. After installing the new valve and clearing the code, I ran multiple tests and the fault code did not return. However, after letting the car sit for 3 hours to cool down, I turned the ignition back on and the P25AB00 code immediately returned. The issue seames to never occurs when the engine/oil is warm. It only triggers when the system undergoes a true "cold boot" with cold engine/oil parameters. During my lunch break, once the engine has completely cooled down again, I will repeat the full test sequence on a cold engine, including leaving 60+ second gaps between ignition cycles as suggested earlier. I will post the cold-start results as soon as I complete the tests!

I just upgraded to the OBDeleven PRO subscription to get full access to Freeze Frame data, and I stumbled upon a very interesting discovery regarding the fault's behavior: The code returns instantly on ignition alone (before even cranking the engine)! Here is exact sequence I tested: Cleared the fault code (P25AB00). Turned the ignition off. Turned the ignition back ON (engine OFF / no cranking). Ran a full diagnostic scan. The fault immediately reappears as soon as the ECU powers up, even without the starter motor engaged or the engine running. The PRO version extracted the raw Freeze Frame values. While I can't interpret these raw numbers (HEX) myself, I have forwarded the PrtSc directly to the dealership service team so their technicians can analyze the exact ECU parameters at the moment of failure. Will keep you updated once I hear back from them!

Hi Alasdair, Honestly, I am not sure whether they cloned the old ECU or flashed it from scratch with default factory software. What I do know is that they performed programing. Regarding the code: since picking up the car from the dealership, I have cleared the fault code twice using OBDeleven. Both times it cleared fine, but as soon as the engine cools down and sits for a while, the exact same static code (P25AB00) persistently comes right back on the next cold start. So whatever data or software condition is causing this, it keeps triggering the fault continuously.

Hi everyone, Can anyone point me to the exact physical location of the Piston Cooling Oil Control Valve (N522) on the 2.0 TSI engine (280 hp)? The VAG part number for the valve is 06K115243L. I know it's located somewhere on the engine block near the oil pump module, but is it accessible from the top, or do I need to drop the undertray and get to it from underneath (front side of the block facing the radiator)? A photo/description of where to look would be hugely appreciated!

Just a quick update to the thread, both to keep this documented for future reference and in case someone has a fresh idea or a similar experience to share. Since my last post, the dealership went ahead and replaced the Engine ECU. The result? Absolutely no change. I picked up the car yesterday, turned the ignition on, and immediately got the Start-Stop error. Within two ignition cycles, the Check Engine Light was back with the exact same static code: P25AB00 (Piston Cooling Oil Control Circuit High) on a cold start. To recap, the entire chain is now 100% brand new OEM: New Oil Control Valve N522 (06K115243L) New Engine Wiring Harness New Engine ECU If anyone has any new insights or has seen this happen on Superb 2022 2.0 TSI 280HP, please let me know. I'm completely baffled.

This morning, I performed a cold start, and a Start-Stop system error appeared immediately (though the Check Engine Light / MIL remained off). After a 15-minute drive, I stopped at a gas station to refuel. The vehicle was stationary for about 5 minutes. Upon restarting, I drove 10 meters to the main road and stopped; the Start-Stop system engaged correctly, and the engine stalled/shut down as intended. After another 10 minutes of driving, I stopped in a traffic queue, but the engine failed to shut down. I checked the vehicle status menu, which displayed a Start-Stop error. Five minutes later, I cycled the ignition (turned the car off and on) about 100 meters before my destination. The start-stop error cleared, and upon reaching the parking spot, the engine shut down automatically. After the car sat for 5 hours, I took a short trip (under 5 mins), and the Start-Stop error reappeared instantly. Following a 30-minute soak time, the error persisted on the return trip. Again, I cycled the ignition shortly before parking; the system reset, and the engine shut down normally at the destination. Scanning the vehicle with OBD11 revealed the old P25AB00 Piston Cooling Oil Control Circuit High. Toward the end of the day, the Check Engine Light (CEL) illuminated, and the Start-Stop system became permanently disabled. The service center is currently in contact with Škoda’s technical support for consultation. They are awaiting a response. They've also double-checked the bypass and used a cleaner spray on the contacts. Interestingly, the fault did not reappear at the service center after they inspected the car, cleared the codes, and performed a 40 km test drive with over 20 ignition cycles. During their testing, the car reached full operating temperature. In contrast, when I'm driving, the error occurs very quickly—usually after just a few trips. Will report back :)

Thank you D402, but I don't think the recent bypass is the culprit. The issue was already present before it was installed and has persisted since. I’ve recently noticed that the fault resets itself if I cycle the ignition about 3 times once the engine is at operating temperature (100°C+). Between each cycle, I drive a short distance of approximately 100 meters and reach a speed of 50 km/h. When starting from a cold soak, the Auto Start-Stop error triggers immediately, followed by the Check Engine Light (CEL) after the third cycle. However, repeating these short 100m drives and ignition cycles while the engine is hot seems to clear the fault.

Hey everyone, I’m looking for some insight regarding an issue with a 2022 Skoda Superb Combi 2.0 TSI 4x4 (280hp). The car has 130,000 km on the clock and was imported from Germany. The Issue: The Check Engine Light (CEL) is on. Upon startup, the dashboard also displays a "Start-Stop System Error." Diagnostics: Using OBDeleven, I pulled the following fault code: P25AB00: Piston Cooling Oil Control Circuit High What has been done so far: Solenoid Replacement: The dealership technicians first replaced the valve associated with this code—if I’m not mistaken, this is the N522 valve, which regulates the oil flow for piston cooling jets. This did not fix the problem. Wiring Inspection: They spent about two weeks troubleshooting the wiring harness between the N522 valve and the ECU. They eventually found a potential fault and performed a wiring bypass for a specific cable. After this, the error disappeared. Current Status: Two days later, the error returned. The symptoms and the fault code are exactly the same. It triggered in the morning immediately after a cold start. I cleared the code, but it came back after about three drive cycles. The service center has now contacted technical support and sent over the diagnostic data to see if they have any further guidance. Driving Behavior: Aside from the warning light, the car drives perfectly fine. Oil temperatures reach about 105°C during normal to spirited driving. Has anyone dealt with this before? Any opinions on what else we should check? Thanks a lot for your time and help!