OBDScope User's Guide
OBDScope User's Guide
Table of Contents
1 Introduction...........................................................................3
2 Installation and activation.....................................................4
3 Connecting to the vehicle.....................................................5
4 Diagnosing the vehicle.........................................................5
5 Managing diagnoses............................................................8
6 Using gauges........................................................................9
7 Data logging........................................................................22
8 Settings...............................................................................26
9 Calibrating the Fuel Economy reading...............................30
10 Advanced features............................................................31
Appendix A: Supported parameters.......................................32
1 Introduction
OBDScope is a vehicle On-Board diagnostics software for
Symbian S60 smartphones. The software uses Bluetooth to
connect to an OBD-II interface which is connected to a
vehicle. The software then uses the OBD-II interface to
access the data available on the ECU of the vehicle. The data
can be monitored in real-time or it can be logged to a file for
further analysis.
System requirements
● Symbian S60 3rd, 5th or Symbian^3 edition smartphone.
○ Most of the recent Nokia handsets.
● Bluetooth OBD-II interface.
○ ELM327 Bluetooth OBD-II Wireless Transceiver Dongle.
○ DIAMEX DX70 Bluetooth.
○ OBDKey Bluetooth.
○ OBDLink Bluetooth
○ ElmCanII-Bluetooth-Interface
○ Any Bluetooth OBD-II interface with ELM compliant chip may
operate.
● Vehicle supporting OBD-II.
○ Most of the passenger cars model 2001 -> with petrol engine.
○ Most of the passenger cars model 2005 -> with diesel engine.
Warning:
Never use OBDScope while driving!
You should never attempt to use OBDScope while operating a
moving vehicle. If you need to monitor sensor information
while driving, it is strongly recommended that you have a
passenger to operate OBDScope. If you don’t have a helping
passenger, use OBDScope's Data logging feature so that you
can analyse the collected data once you have safely parked
your vehicle.
Test is completed
Example:
C0245 Wheel Speed Sensor Frequency Error
5 Managing diagnoses
Saved diagnoses can be managed by selecting Saved
diagnoses from the OBDScope main menu. A list of previous
diagnoses is displayed with the time of diagnosis, DTC count
and MIL status as summary as seen in Picture 6. One
example diagnosis with four example DTC:s comes with
OBDScope installation. The example diagnosis is dated
22.02.2010 and it contains two current and two pending
Troubles.
6 Using gauges
Gauges are for viewing live (almost real time) data from the
vehicle. List of gauges, as seen in Picture 7, can be viewed by
selecting Gauges from the OBDScope main menu. The
content of the list varies with different vehicles. Open a gauge
by pressing enter key. Switch to list of favourites by switching
tab. An example of a gauge is displayed in Picture 8.
Gauges can be monitored in background. By monitoring a
gauge it is possible to get the monitored gauge activated even
if the gauge is not visible at the moment of monitor is
triggered. Monitor triggers when the value of the gauge gets
over Alert high setting or the value gets below Alert low
setting. For setting alert boundaries see page 17. Monitor is
Picture 7: List of gauges. not triggered when one of the following views is active:
● Troubles
● FreezeFrame
● Diagnosis
● OBD Tests
● Lambda Tests
● Data Logging
● Settings
2
1
3
2 3
2
3
1
4
5
2 3
4 5
3
1
4
5
2
6
3 4
5 6
4
2
5
1
6
3
7
2 3
4 5
6 7
2 6
3 7
1
4 8
5 9
2 3
4 5
6 7
8 9
7 Data logging
Data logging is for creating CSV formatted files from the data
available from the vehicle. Files can be viewed with any text
editor or spreadsheet application. Data can be sent to a
remote server as well. Data logging can be done by selecting
Logging from OBDScope main menu. Data logging view can
be seen on Picture 12.
8 Settings
Settings can be opened by selecting Settings from OBDScope
main menu. Setting views are presented in Pictures 14 - 19.
Following settings are available:
General settings
Gauge settings
● Gauge backlight – Keep the phone backlight on and
disable screensaver while viewing a gauge.
● Alerts – Determine the type of alert. Visual only or
Sound and visual values are available
● Monitors – Enable or disable background monitoring
of gauge.
● Main color – The main color used in gauge. Color
setting are set with a RGB view as seen in Picture 17.
● Normal background – The background color used in a
Picture 16: Gauge settings. gauge while an Alert is not activated.
● Alert high background – The background color used
in a gauge while high Alert is activated.
● Alert low background – The background color used in
a gauge while low Alert is activated.
Vehicle settings
10 Advanced features
Shell (Options – Shell) is for applying low level commands
directly to the OBD-II interface, see Picture 21.
There are two ways to open the Shell:
● Connecting: If the Shell is opened while there is no
connection established beforehand, the connection is
then opened but no initialization commands are
executed. Closing the Shell will disconnect.
● Interfering the current connection: If the Shell is
opened while OBDScope is already connected, the
current connection is then used for the Shell. This way
it is possible to interfere the current connection by
Picture 21: Shell applying commands with the Shell. Closing the Shell
will not disconnect.
There are two types of commands that can be applied:
● OBD-II interface commands. For more information, see
interface (IC, chip) manufacturer documentation.
● OBD-II protocol commands. For more information, see
OBD-II protocol specifications.
To save the content of the Shell window to a file, select
Options → Save to file. To clear Shell, select Options → Clear.
Note: It is not recommended to apply any commands unless
you you are absolutely sure what you are doing.