Rtek Pocketlogger diagnostics (check engine codes) reporting
07-17-13, 07:01 PM
#1
Pocketlogger diagnostics (check engine codes) reporting
I'm running Rtek 2.x on a S5T2 (N370 ECU). Got a question on how the Pocketlogger software reports CEL (check engine light) codes - is it supposed to report CEL codes that were stored in the ECU, in addition to any currently active/occurring codes?
Here's why I asked. The other day my car started bucking, and CEL light came on - something threw it into limp mode. With the engine still running, I tried to use the diagnostics function of the Pocketlogger SW to read the CEL code; no codes showed, but I assumed that was normal because I didn't have a jumper wire handy to jump that 1 pin check connector to ground. Ended up shutting the engine off, restarting, and everything was running fine from that point on, no lit CEL light.
When I got home, I jumped the check connector to ground, and read the CEL codes using the CEL blinking light method per the FSM. Result there was I had a code 27 (MOP) and 38 (AWS solenoid). The code 27 is what threw me into limp mode, and there may have been an intermittent connection issue with the MOP. I would add that I don't have my MOP functionality disabled via the Rtek 2.x.
When I used the Pocketlogger to read CEL codes, it only reported the code 38 (AWS), which is normal for my car because my AWS is removed and that circuit is always open - error is always present, but it didn't show the code 27 (MOP). So what I gather is happening is the Pocketlogger can't report CEL codes that were *stored* in the N370 ECU (the intermittent code 27 in this case); it can only report actively occurring CEL codes. Is this a bug or normal operation?
Here's why I asked. The other day my car started bucking, and CEL light came on - something threw it into limp mode. With the engine still running, I tried to use the diagnostics function of the Pocketlogger SW to read the CEL code; no codes showed, but I assumed that was normal because I didn't have a jumper wire handy to jump that 1 pin check connector to ground. Ended up shutting the engine off, restarting, and everything was running fine from that point on, no lit CEL light.
When I got home, I jumped the check connector to ground, and read the CEL codes using the CEL blinking light method per the FSM. Result there was I had a code 27 (MOP) and 38 (AWS solenoid). The code 27 is what threw me into limp mode, and there may have been an intermittent connection issue with the MOP. I would add that I don't have my MOP functionality disabled via the Rtek 2.x.
When I used the Pocketlogger to read CEL codes, it only reported the code 38 (AWS), which is normal for my car because my AWS is removed and that circuit is always open - error is always present, but it didn't show the code 27 (MOP). So what I gather is happening is the Pocketlogger can't report CEL codes that were *stored* in the N370 ECU (the intermittent code 27 in this case); it can only report actively occurring CEL codes. Is this a bug or normal operation?
07-17-13, 07:27 PM
#2
I know the S4's don't store codes. I thought that was true of the S5's as well. The codes you have are "realtime".
Now I do know that there is some wacky stuff that goes on when the MOP driver is bad. Many of the ECUs we get in for the NO MOP option don't clock out any codes on the check connector. The blown driver seems to affect the ECU's ability to blink lights. Since you already got thrown into limp mode, I assume something is going bad on your MOP driver and you will find yourself in limp mode again soon.
Now I do know that there is some wacky stuff that goes on when the MOP driver is bad. Many of the ECUs we get in for the NO MOP option don't clock out any codes on the check connector. The blown driver seems to affect the ECU's ability to blink lights. Since you already got thrown into limp mode, I assume something is going bad on your MOP driver and you will find yourself in limp mode again soon.
07-17-13, 08:37 PM
#3
Yes, the S5's do store CEL codes in memory. You clear the stored codes on S5's by disconnecting the battery or just pulling the 60A BTN (Back To Normal) fuse.
Like I mentioned, I'm not using the Rtek to disable the MOP functionality. Also, a simple "reboot" (shutting the engine off & just restarting) cleared the limp mode condition. I've tested the MOP pump per the FSM procedures, and all the electrical components check out OK - stepper motor & position sensor, harness wiring continuity & voltages, etc. This has happened a couple of times before, but it is very infrequent and random. When it has happened before, the ECU will store either a code 20 (MOP position sensor) or 27 (MOP stepper motor).
Like I mentioned, I'm not using the Rtek to disable the MOP functionality. Also, a simple "reboot" (shutting the engine off & just restarting) cleared the limp mode condition. I've tested the MOP pump per the FSM procedures, and all the electrical components check out OK - stepper motor & position sensor, harness wiring continuity & voltages, etc. This has happened a couple of times before, but it is very infrequent and random. When it has happened before, the ECU will store either a code 20 (MOP position sensor) or 27 (MOP stepper motor).
Thread
Thread Starter
Forum
Replies
Last Post
