OBD Auto Doctor OBD2 app for iPhone is now available from the Apple app store!
The app works now perfectly even with the new iOS 8 released just few weeks ago. The very first version of the app had some layout issues with iOS 8 but now all those issues are gone. The app works fine with iOS 7 too but older versions are not supported.
The iPhone version of the app requires separate ELM based OBD adapter using Wi-Fi connectivity. Due to technical limitations of the platform Bluetooth adapters can’t be supported. To get started with the app and adapter setup, please check the Quick Start Guide for iPhone. It will guide you through the first time usage.
The basic app is available for free so that you can evaluate it and make sure it works with your car and OBD-II adapter. The free app has some limitations though. You can unleash all the features and upgrade to the Pro version using in-app purchase. In-app purchasing is convenient way to unlock the Pro features without need to re-install separate app version.
Upgrading to the Pro
Getting the Pro version can be done inside the app using in-app purchase. It’s one time purchase that covers all future feature updates and additions to the app. The purchase is tied to your Apple account. You can get the Pro version back even if you upgrade your phone or uninstall the app by accident. Just install the free app from the app store and it will automatically detect that you already own the Pro version. The only thing you have to do is use the same Apple account in your phone.
Unfortunately Apple doesn’t provide us means to issue refunds of the purchase. Therefore, please try the free version first to make sure there are no compatibility issues with your adapter or car. The issues are very rare but if the free version doesn’t work, the Pro version won’t make the situation any better.
OBD Auto Doctor is coming for iPhone soon! We are very excited about this announcement as we are expanding our OBD2 software to even bigger audience. iPhone will be great addition to our product family that already covers Android, Windows Phone, Windows, Mac OS X and Linux.
We have been busy and working hard the whole summer to implement the best user experience for the app. We hope you like the app or send us feedback on the areas needing improvement. The app will require iOS 7.0 or newer to function. Earlier iOS version are not supported at the moment.
The app release will be announced separately but we are targeting September for the release. The app is basically ready by now but we still want to tweak the user interface and functionality to make it even better. If you want to be part of the early adopters and help us, please join our beta testing group by sending us email to email@example.com.
Here are couple of screenshots of the app. We are very excited about it, how about you?
In the previous app update for Android (version 2.2) and Windows Phone (version 2.0) we added support for multiple control units. The most common and usually the only control unit is the Engine Control Module. However, newer cars are starting to have more than the ECU responding to OBD2 requests. Most cars with automatic transmission have Transmission Control Module (TCM) available for example. There can be also other controllers depending on the manufacturer and model.
Our desktop software has had the support for multiple control units for ages but with the last update we brought the support to the mobile versions too. As with all mobile version updates, this update is completely free for all of our existing customers using the app in these platforms.
In Android, the selection of control unit was added as dropdown spinner in the action bar. The screenshot illustrates a vehicle with three control units available. The selection can be made by opening the spinner by tapping the title and then selecting the appropriate control unit. The selected control unit is visible in every view where it matters and where it can be changed. After changing the control unit, the view data is refreshed from the car and information is shown for the selected controller.
In Windows Phone, the control unit selection was added to the navigation page. The controller can be changed using the list picker on top of the navigation page titled “browse”. To change the control unit, you need to come back to the browse page and do the change you wanted. The screenshot is from the same car as the Android screenshot. The car has three control units and the first one is selected. The acronym of the selected control unit is indicated on top of the view in the title.
Now it’s good time to update your app to the newest version. Remember that as with all the other features, your car needs to support multiple control units for them to show up in the app. If you have only one ECU listed, then your car has only one ECU responding to the OBD2 messages. Happy diagnosing!
An update for OBD Auto Doctor WP8 version was just published few hours ago. The update adds dashboard with some neat gauges to the app. On top of the screen there are speed and RPM meters. At the bottom there are four gauges displaying various information. The gauges may vary a little bit depending on what sensors your car supports. The update is ready for download from Windows Phone Store.
With the free version, only the speed, RPM and Engine Coolant Temperature are displayed. If you want access to all of the gauges, then upgrade to the Pro version.
In addition to the gauges and meters, the update fixes a disconnect issue with some adapters where the adapter closes the connection after certain idle period.
If you still haven’t tried the app, now it’s good time to try it out!
OBD2 Readiness Monitors are simple yet powerful self check routines. They provide insight to the car’s self-diagnostics. This post will explain in detail what the readiness monitors are.
The purpose of readiness monitors is to self-test the car’s emission control systems. The monitors are also known as Emissions Monitors. Like the name indicates, they observe the performance of car’s emission related systems.
Cars may perform up to 11 system tests or routines. These tests are so called readiness monitors. The output of readiness monitors tell you whether the car’s computer has completed the tests successfully.
Readiness Monitor types
There are two different types of readiness monitors: continuous and non-continuous. Continuous monitors are different in design from the non-continuous ones. Continuous monitors are being constantly tested and evaluated while the engine is running. The non-continuous monitors need certain conditions to be met before a test can be completed.
The conditions necessary to run the non-continuous self-diagnostic tests vary. Some monitors require that the car follows a predefined drive cycle routine. Some require two drive cycles because of the need for a cool down and warm up periods between. Each emission monitor can have different requirements for the conditions.
Previously, the OBD2 standard (SAE J1979) categorized each defined monitor as either one. In the latest standard edition, this definite allocation is no longer present for all of them. Thus, OBD Auto Doctor doesn’t follow the categorization anymore either.
Continuous or Non-continuous Monitors
These monitors can be of either type. It’s up to the manufacturer to decide.
Non-continuous monitors are different for spark ignition cars (gasoline engines) and compression ignition cars (diesel engines).
Spark ignition vehicles (Gas)
Evaporative (EVAP) System
Secondary Air System
Oxygen (O2) Sensor
Oxygen Sensor Heater
EGR (Exhaust Gas Recirculation) and/or VVT System
Compression ignition vehicles (Diesel)
Exhaust Gas Sensor
EGR and/or VVT System
Traditionally, the only monitor status was the status since the diagnostic trouble codes were cleared. This readiness monitor status is mandatory for all OBD2 compliant vehicles. It will show the long term status after the check engine light was reset and the DTCs cleared.
As the OBD2 has evolved, newer vehicles can now report emission monitor status also for the current driving cycle. These monitors start from the beginning every time when the monitoring cycle begins. Older cars might not support this feature. In that case, OBD Auto Doctor will mark it as NA or Not Available.
Readiness monitor test result yields the monitor status. Each readiness monitor will have its own output status. The completion status can be:
Complete or ready meaning that the test has been completed. It means that the OBD-II system has checked this emissions control system and it has passed the test. OBD Auto Doctor indicates this by green check mark.
Incomplete or not ready meaning the test is not completed. It means that the OBD2 system has not been able to run this routine or it has failed. OBD Auto Doctor indicates this by red exclamation mark.
Disabled meaning that the test has been disabled for the rest of this monitoring cycle. A monitor can be disabled when there is no easy way for the driver to operate the vehicle to allow the monitor to run. For example, the ambient air temperature might be too low or too high.
OBD Auto Doctor lists all the defined monitors in the software. But the actual status can be reported only for the ones that the car supports too. It is not required for a car to support all the monitors. NA or not available monitor means that the car doesn’t have that monitor. Thus it can’t be tested.
Why is a monitor incomplete or “not ready”
Clearing the diagnostic trouble codes (DTCs) and the Check Engine Light will reset the monitor statuses too. This typically occurs during or after vehicle repair.
Statuses are also reset in case of power failure. This usually happens when the battery has been disconnected. That’s why it is not advisable to disconnect the battery. If you need to disconnect the battery for example to replace it, read further. You will learn how to get the monitors back to complete.
For the current monitoring cycle, or “this drive cycle”, the status is set to incomplete upon starting a new monitoring cycle. It is a normal situation for these monitors to be incomplete when starting the engine.
Depending on your country and state, OBDII vehicle may not pass the annual inspection unless the required monitors since reset are complete. For example, the US Environmental Protection Agency guidelines allow up to two monitors to be not ready for model year 1996 through 2000 vehicles. For 2001 and newer model year vehicles only single monitor status can be incomplete or not ready.
How to get the monitors complete or “ready”?
Because the monitors are self check routines, the best way to get them ready is to drive the car. Yet, monotonic driving will not most likely meet all the needed conditions. That’s why there is so called OBD drive cycle. But before going into that, let’s go through the obvious ones.
First, make sure that the MIL (Malfunction Indicator Light) is not commanded on. Having stored or even pending diagnostic trouble codes active may prevent a monitor from running to completion.
Second, make sure that you have enough fuel in the car. Some monitors, for instance the EVAP monitor, may require the fuel level to be between 35% and 85% to initiate the diagnostic testing.
Third, complete the so called “drive cycle”. About one week of combined city and highway driving is usually enough to allow the monitors to reach complete status. The drive cycle is explained in more details in the next paragraph.
OBD drive cycle
The purpose of the OBD2 drive cycle is to let your car run on-board diagnostics. This, in turn, allows the readiness monitors to operate. And detect potential malfunctions of your car’s emission system. The correct drive cycle for your car can vary greatly depending on the car model and manufacturer. Also, the monitor in question affects the required drive cycle.
Today, many vehicle manufacturers include these drive cycles in the vehicle owner’s manual. Typically, a few days of normal driving, both city and highway, will make the monitors ready. The following generic drive cycle can be used as a guideline if a specific drive cycle is not known. It will assist with resetting monitors when a car specific drive cycle is not available. However, it may not work for all cars and monitors.
The drive cycle can be difficult to follow exactly under normal driving conditions. Thus, it is better to drive it in restricted area!
The universal OBD-II drive cycle begins with a cold start. You should have coolant temperature below 50 C/122 F, and the coolant and air temperatures within 11 degrees of one another. This condition can be achieved by letting the car to sit overnight.
The ignition key must not be left ON position before the cold start. Otherwise the heated oxygen sensor diagnostic may not run.
Start the engine and idle the engine in drive for two and half minutes, with the A/C and rear defroster on if equipped.
Turn the A/C and rear defroster off, and speed up to 90 km/h (55 mph) under moderate, constant acceleration. Hold at a steady speed for three minutes.
Slow down to 30 km/h (20 mph) without braking. Do not depress the clutch if you are running with manual transmission.
Speed up back to 90-100 km/h (55-60 mph) at 3/4 throttle. Hold at a steady speed for five minutes.
Slow down to a stop without braking.
Get ready for inspection
To avoid rejection in the annual inspection, you can prepare your car for the check yourself. You should at least read the readiness monitors and make sure they are ready. This will save you from almost guaranteed rejection.