Well, first CEL in my new to me 03 spider. Wanted to create this thread to document my troubleshooting efforts. Check Engine Light after driving for ten mins. Used the Autel AP200 to read it. Error code P0442. First thing I did was re-tighten the fuel cap (it did move a tiny bit) and clear the error. Image Unavailable, Please Login A week later CEL showed up again. Same error code with the AP200 but then later used the Thinkdiag +. Error codes: 020D1000 and 020E1800. Image Unavailable, Please Login This is my current status. Will add more details as I go about it. Image Unavailable, Please Login
As I mentioned, I have used both the Autel AP200 and the Thinkdiag scanners Note: I also have the Autel MK900, a more refined scanner, and I got it from Amazon. Beware though, this one won't work for Ferraris despite the listing saying it does. Unfortunately I found out about it months after getting it and can't return it. Also, I called Autel and they told me that Amazon is not an authorized reseller/distributor so they won't help you much if you have any issues with any of their devices ordered from Amazon. So here is where things get interesting: I drove it again and, as expected, got the CEL again. I checked with the Thinkdiag and, surprise, it told me there were no errors. I then connected the AP200 and it showed me the P0442 message. I cleared them, went for another ride, and got the CEL again. And the results were the same. AP200 told me P0442 while Thinkdiag said no codes found. Obviously these are under $100 scanners, but I was surprised about the discrepancy on the results. Especially after the Thinkdiag had given me a more detailed report earlier (see first post). I guess the saying A man with a watch knows what time it is. A man with two watches is never sure. certainly applies here...
OK, looking at the specifics of the Error codes: 020D1000 and 020E1800, one of the cool features of the Thinkdiag is that it has an AI chatbot that seems to look for details on each of the codes, and they look like this: 020D1000 The fault code 020D1000 for a Ferrari 360 Modena is related to the *Lambda (02) sensor* on Bank 1 Sensor 1). This code typically indicates an issue with the oxygen sensor's signal or performance, which can affect the engine's air-fuel mixture and overall performance. Image Unavailable, Please Login Image Unavailable, Please Login 020E1800: The fault code 020E1800 for a Ferrari 360 Modena typically relates to an issue with the *Lambda (02) sensor* on Bank 1 (the sensor located before the catalytic converter). This code indicates a problem with the sensor's signal or its circuit, which can affect the engine's air-fuel mixture and overall performance. Image Unavailable, Please Login Image Unavailable, Please Login and it has like 8 steps on how to address it. Yep, cool to me. The interesting part is that both error messages look identical. And again, the worst part is that I was not able to read the errors again even though the CEL was on and the AP200 did report the P0442... oh well.
Another interesting thing I mentioned before was that I got once a phantom code... Image Unavailable, Please Login And, nope, still can't replicate it... it says there is an error code and then it says there are no error codes... go figure. Also, if you noticed the first report, there was another code: 020D037F ### Steps to Fix Fault Code 020D037F: 1. Check the Battery Voltage: - Low battery voltage can cause communication errors in the CAN system. - Ensure the battery is fully charged and in good condition. - Check the alternator to ensure it's charging the battery properly. 2. Inspect CAN Wiring and Connectors: - Look for damaged, corroded, or loose wiring in the CAN system. - Check the connectors at the ECU and other modules for proper seating and corrosion. - Repair or replace any damaged wiring or connectors. 3. Scan for Additional Fault Codes: - Use a Ferrari-specific diagnostic tool (e.g., SD3 or similar) to check for other fault codes that might point to a specific module or component failure. Image Unavailable, Please Login
OK, things now got more interesting... Recap: I was getting a P0442 error code. Then later I was getting the CEL on the dashboard but both OBD readers (AP200 and ThinkDiag) were saying there were no errors. Well, what I realized is that I may have two separate issues. When I did the read the times when I saw the CEL but got no error codes, it was immediately after coming back from a drive. After inspecting both readers, I realized something: I am not seeing the right bank anymore, just the left side. I tried it again the next day and the ThinkDiag still could not read the right bank, but the AP 200 did see it. This is what the ThinkDiag showed me when I scanned the systems for availability: Image Unavailable, Please Login Note I can see the "Recovery" but not the "regular" right bank system, while both Left bank showed up. I ran the diagnostic again with the AP 200 and, voila, the right bank did show up and the error codes showed up right away: Image Unavailable, Please Login Here are the error codes in the AP200: Image Unavailable, Please Login So, a few questions and conclusions I have so far: 1. Why is there a Recovery for each bank? Is that a safety mechanism in the ECUs? 2. Why is the ThinkDiag not reading the bank side system but it is reading the Recovery one for the right side? 3. If the ThinkDiag can see the Recovery, why is it not showing the error codes that the AP200 is seeing? --reminder: the CEL is on so something is happening. Also, why is the AP200 seeing the right bank now, but it wasn't yesterday? is it because it was hot yesterday? what does that tell me? 4. Do I have 2 separate problems then? 4.1 error 1: the P0442 is real and I need to check the evap system for a small leaking somewhere 4.2 error 2: is there a communication error with the right hand side ECU? Is it a cabling issue? is the ECU letting me know it is going to go kaput soon? how do I even diagnose that? 5. I checked for videos on how to test the evap system for a 360 but did not find anything specific... I do have a smoke testing machine so I need to figure out where to put it to perform the test. In theory is a simple problem to diagnose and, depending on the location of the leak, it could also be a simple fix. But, if I am not mistaken, this won't be a major issue for now and still can enjoy some joy rides while the weather is good. 6. I likely will need to find somebody with a more advanced scanner that lets me check for the error messages and see if I can find more specific information about these two issues. In any case, I will continue adding my notes here so I document for myself what I am seeing and what I am doing with this sexy beast.
All the issues you are having is because the scanners cannot communicate correctly with the ECU most likely due to immo been on or the sequence of how you connected to car - Autel is better getting thru vs the Launch I would concentrate on P0442 and once fixed scan each module independently even with car running
Makes sense. The thing is that they used to communicate before, but you are correct; regardless, the P0442 is real and will focus on that one ASAP. Thanks.
P0442 is coming from RHS bank, its an Evaporative emissions leak. Check tubing and evap valve as well as charcoal canister. Might need to smoke test it for leaks.
Thanks. Yes, planning to do so. Never done a smoke test for evap, only for intake, so need to figure out where to connect the machine to complete it. Will update the thread when done.