MR2 Check Engine

-
Shown here is the 1991 Toyota MR2. Thanks to the mechanical skills of a family enthusiast, it purrs, growls, and turbo whistles like a dream.
 
My hardware ability doesn't go much further than oil changes. Rather, my expertise is in software, and I wrote an Android App (iOS version is in progress) to diagnose the flashes of the check engine light.

This second generation MR2 predates the OBD2 connector, a standard used to diagnose engine, transmission, and emissions problems quickly and easily. Instead, we have a flashing check engine light which needs some deciphering, followed by a lookup in the service manual.

Basically, you count flashes to arrive at fault code number. A short pause (~1.5 seconds) indicates the start of the next digit. A medium pause (~2.5 seconds) indicates start of the next fault code. And a long pause (~4.5 seconds) means the sequence has ended and will repeat.

The video below corresponds to the codes 41 and 51.


Using the the MR2 Check app and selecting the 3S-GTE engine:



we learn that 41 indicates a problem in the throttle position sensor signal, and that 51 indicates a switch condition signal.

There are two ways to enter the codes. The first is to enter them (separated by a space) using the NUM PAD:


The second way is to use the BLINK PAD. Match the blinking pattern by first tapping START, followed by the BLINK button for every flash. You don't need to match the flashes precisely; rather you just need to match the rhythm.  Also, going through two sequences helps improve the accuracy.  Press STOP when you are done with the sequence.



As an Easter egg of sorts, use the NUM PAD and enter 100 to see all the codes for the selected engine.

MR2 piston heads already know that to get the flashing check engine light you need to jump two pins on the diagnostic port in the engine bay.  I've added photos to help new owners:


Diagnostic Port in Engine Bay


Jump pins TE1 and E1

As per Toyota, prior to jumping:
  • Battery voltage needs to be 11V or more
  • Throttle valve full closed (throttle position sensor IDL points closed)
  • Transmission in neutral position
  • Accessories switched OFF
  • Engine at normal operating temperature
Then turn the ignition switch ON, but do not start the engine. Now ready to jump pins.

For the bit heads, this app was written on a Mac, using Android Studio and Kotlin. The iOS version uses Xcode and Swift.

MR2 Check is currently available on Google Play for $1.99.  Think of it as buying me a cup of coffee. Or about a half gallon of gas.




Comments

Post a Comment

Popular posts from this blog

Bookshelf: UNIX A History and a Memoir

-
Image
  A man page will give you, in black and white, specific information about UNIX. Brian Kernighan's new book adds color and depth about UNIX you won't find anywhere else. I'm not a gray beard (yet), but I imagine they would plow through the book knowingly, but at the same time, learn a few things. Those new to UNIX -- recent college grads or those experimenting with Raspberry Pi -- would be better off starting with Chapter 8 which describes more relatable events and the descendants of UNIX, including Minux and Linux. It's when they start to ask questions like "Where does UNIX come from?" and "Why is Gamora grep?" that they should start from the beginning: Bell Labs, 1969. Kernighan opens with a birds-eye-view of Murray Hill New Jersey, zooms in on the buildings, the offices, the significance of Center 1127, and offers a brief look at some of the key players there. As I progressed through the book, the two factors that made UNIX not just possible, bu
Read more

Bookshelf Classic: The C Programming Language

-
Image
My first job had me programming in Microsoft BASIC for the IBM PC (DOS).  BASIC worked well enough, but its limitations were clear.  The language was interpreted and therefore slow.  More importantly, it wasn't a modern structured language, and instead, relied on line numbers and the GOTO statement.  Anyone who has read Dijkstra knew  GOTO was a bad thing . Having learned a structured language in college ( PL/I ), using BASIC felt unnatural.  When a C compiler became available for the PC, I saw a chance to improve and modernize our software.  The problem was selling the idea -- a problem made harder because I wasn't fluent in C. "It would be a staffing problem.  Not many people know C, but we can find a lot of programmers who know BASIC," noted one manager. The argument was strong as my knowledge of C was weak.  But I knew that C, by design, was a small language and thus easy to learn.  "It has about 30 keywords," I proffered to another manager. U
Read more