As previously mentioned, Bruce has taken to showing me the CEL just like Roxy did. As you can see above, that is the error code I am currently getting. A search on the internet tells me this could be something simple like making sure the car has oil (it does) or something bad like OMGWTFBBQWEAREALLGONNADIE. I really <3 the internet.
I’m not a big fan of self-diagnosis and I am not a mechanic. I’ll get him in to have it checked out before too long. I’m keeping fingers crossed for sensors that have gone caput, but who knows.
You guys are probably wondering about the fancy screen shot above too. I’m sure you already thought “my code reader doesn’t look like that”. Being the nerd that I am, I am using a device called Automatic. Plugs into the ODB port and connects to my personal computing device via bluetooth. I’m currently testing the device with it’s default settings and full nanny mode. Configuration changes will be coming shortly.
I got this device because, not only does it read engine codes and tell me where I left my car and how far my last trip was and how much fuel I used on my last trip (you are getting the idea), it also ties in with the nerd machine, ifttt.com. You can have it save CEL codes to your Evernote. Tag drives for business and save them to your Google Docs or DropBox. Have it turn on your Nest or Hue lights when you get home. All kinds of things.
I’ll have a full review coming in another week after I have spent some time with it. In the meantime, if you have any questions, the comments are open!