red8812 / android-obd-reader Goto Github PK

What steps will reproduce the problem?
1.Induce Check Engine Light via disconnect of MAF (Engine Light On) 
2.Configure Reader 
3.Trouble Codes 

What is the expected output? P code for MAF and Air Temp 
What do you see instead? No output (Clear Codes Works)


What version of the product are you using? Latest Available
On what operating system? Android 2.2

I would reccomend Mode 13 - Pulls all codes including history and pending.


Please provide any additional information below.

What steps will reproduce the problem?
1. Switching to imperial units
2. Not sure if the issue is impacting calculated 
values such as mpgs done by manifold pressure

What is the expected output? What do you see 
instead?
See 50mph when going 30

What version of the product are you using? On 
what operating system?
1.1 on nexus one cyanogenmod.

Currently, we have from command description to menus and labels hard-coded.

This must be amended to comply with development best-practices.

without the bluetooth admin permission wont not work on some devieces

What steps will reproduce the problem?
1. mvn clean compile
2. copy the apk file to the phone and install it
3. run the app

What is the expected output? What do you see instead?
One expects the app to run, but instead it crashes with ClassNotFoundException.

This is a packaging problem.

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.

What steps will reproduce the problem?
1. Starting the App 

What is the expected output? What do you see instead?
I cannot see the valid current fuel consumption and the litres per kilometer. 
It's always zero. I added a plain ObdFuelConsumptionCommand with a TextView to 
the code and getFormattedResult() always returns the initial value of -1.0.

What version of the product are you using? On what operating system?
1_3
Android 2.2.3
Bluetooth Adapter ELM327 from E-Bay
Kia Picanto 1.0 

Please provide any additional information below.
With Torque Free, the current fuel consumption and also the average is 
displayed, so this is not an issue with the car.

What steps will reproduce the problem?
1. Either start the app and go to start live data or run any command from the 
command menu.
2.
3.

What is the expected output? What do you see instead?
The expected output is the result of the command or NODATA.

Regardless of the command, the preamble sent before each command "ate0\n\r" 
will lock-up the adapter as a '>' will never be received but only the partial 
'ate0\n\r' answer. This will end up in the readResult function waiting forever 
to receive a '>' confirmation.

What version of the product are you using? On what operating system?
Latest at April, 2011 on Android 2.2.

Please provide any additional information below.

It seems that some adapters (sorry, I won't name which one as it is a well 
known brand from which I just happened to have one) are really fussy about what 
they receive.
I had more success receiving an answer from the adapter by removing the '\n' 
character appended after each command and leaving just the '\r'. According to 
the ELM specs any command is interpreted when the '\r' character is 
encountered. Thus the '\n' might confuse the adapter and even lock it up. To 
make my particular adapter even more stable I also had to add additional sleep 
periods 100-200ms in various places but I have not yet discovered the minimum 
required periods.

Please note that with some other adapter that I own (cheap elm v1.2 clone), the 
above issues are not present.

I tested the application using ELM327 bluetooth dongle with honda city 2008 but 
got the error. the error photo is attached. Please help me out. 

Dear authors,

I'm experiencing troubles with running your application.
When I run the application, an error message box appears:
"The application OBD II Reader (process eu.lighthouse.obd.reader) has stopped 
enexpectedly. Please try again."

Here are my steps:
1.I've cloned your repository:
  git clone https://code.google.com/p/android-obd-reader/
2.Runned in cmd: mvn clean install
  Compilation was succesfull.
3.Installed aplication on Android 2.3 Gingerbread.
4.Tried to run application.
5.Error appeared.

Could you give me some hint please?
What did I do wrong?



Yours Sincerely,
Lukáš Kubík

The android manifest has the target as 'android-6'. However this API 6 is now 
been flagged as obsolete in the SDK manager and does not support Linux and 
MacOS flavors. 

Is there a reason to stay on API 6?. 
Thanks
Greg R

"These commands control whether or not space characters are inserted in the ECU 
response.
The ELM327 normally reports ECU responses as a series of hex characters that 
are separated by space characters (to improve readability), but messages can be 
transferred much more quickly if every third byte (the space) is removed. While 
this makes the message less readable for humans, it can provide significant 
improvements for computer processing of the data. By default, spaces are on 
(S1), and space characters are inserted in every response."

One shall implement this enhancement for faster application response times.

What steps will reproduce the problem?
1. Get codes
2. Set Country to Finland, or some else where used decimal separator is ',' 
instead of '.'
3. Build with maven

What is the expected output? What do you see instead?
- Code compiled and apk created
- Testing fails in assertion because values are separated with ',' instead of 
'.'

What version of the product are you using? On what operating system?
- Downloaded available ones with Git 6th of February 2013.
- Win7 Enterprise SP1 (6.1) / Amd64 / jdk1.6.0_39 / Maven 3.0.4


Please provide any additional information below.
Could also be metric/imperial issue?

I bought a OBD2 adapter that same to the one(the last row in the Working 
adapters table) in the web site(http://torque-bhp.com/wiki/Bluetooth_Adapters), 
and this adapter works well with my Ford Tdci (2010) with your Torque app. It 
is very amazing work for me.
I wanna try to develop a customized app with obd2 information, but encounter a 
code problem. Would you give me some hints to solve the code problem shown 
below briefly:


protected BluetoothDevice dev = null;
protected static final UUID MY_UUID = 
UUID.fromString("00001101-0000-1000-8000-00805F9B34FB");
protected void startDevice() throws IOException, InterruptedException {
        sock = this.dev.createRfcommSocketToServiceRecord(MY_UUID);
        sock.connect();

.....
}



But I always get the error messages on this line
sock.connect();
:~~~, 




please help me escape this hell, please!! thank you very much.

I am really new to MAVEN.  I get the error below when I do a "MVN clean 
package" I am not sure what the error below means. Any input into this would be 
great.

I am using maven 3.0.4.

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.
3.2:compile (default-compile) on project reader: Compilation failure
[ERROR] \android-obd-reader\obd-reader\src\eu\lighthouselabs\obd\reader\activity
\ConfigActivity.java:[52,30] error: package R does not exist

Running the trouble codes command 03 for a know MAF failure returns only 5 
bytes of data after the 43 response when it should return 6.

For example, I unplugged the maf on a 2008 Mazda3.  The codes set are P0102 and 
P0113  When I run the 03 command the response is:
43 02 01 02 01 13 \r\r

It should be:
43 01 02 01 13 00 00

Or something like:
43 01 02 01 02 01 13

ANy idea why it would do this?

What steps will reproduce the problem?
1. Start the application.
2. Watch the screen and try to tell if your phone can actually talk to the OBD 
reader.

What is the expected output? What do you see instead?
I would like to have a status message (e.g. in the main window) telling me 
whether an OBD reader has been found and the app can talk to it - in a way that 
is clear even to new users of the application.
Instead, I see a notification saying "ODB Connection has started". However, I 
get this on every app start, even when there is no OBD reader anywhere in 
sight, and the notification disappears as soon as I press "Start Live Data".

What version of the product are you using? On what operating system?
Currently using version 1.3, installed from f-droid.org. OS is CyanogenMod 
10.1.0 on a Nexus S, with a generic ELM327 reader, in a 2005 Audi A4.

Please provide any additional information below.
Testing a successful connection with the OBD reader could be done by sending a 
universally supported PID (e.g. Mode 01 PID 00 - list supported PIDs) and 
checking for a valid response. Connection status can be:
- Connected - if we got a valid response
- Invalid response - if we got a response but it doesn't look like a valid 
response to the PID we sent (e.g. for Mode 01 PID 00, if the response length is 
not equal to 4 bytes).
- OBD device not found - if no Bluetooth connection to the selected OBD device 
could be established
- No device selected - if no device has been selected in Settings

We must split the code in order to easily maintain this project functionalities 
and at the same time fasten new developments.

An API should be extracted from the current code. Also, it should be a pure 
Java project with no Android dependencies, whatsoever. With Maven this is 
peanuts :-)

"When receiving responses from a vehicle, the ELM327 has traditionally waited 
the time set by the AT ST hh setting for a response. To ensure that the IC 
would work with a wide variety of vehicles, the default value was set to a 
conservative (slow) value. Although it was adjustable, many people did not have 
the equipment or experience to determine a better value.
The Adaptive Timing feature automatically sets the timeout value for you, to a 
value that is based on the actual response times that your vehicle is 
responding in. As conditions such as bus loading, etc. change, the algorithm 
learns from them, and makes appropriate adjustments. Note that it always uses 
your AT ST hh setting as the maximum setting, and will never choose one which 
is longer.

There are three adaptive timing settings that are available for use. By 
default, Adaptive Timing option 1 (AT1) is enabled, and is the recommended 
setting. AT0 is used to disable Adaptive timing (so the timeout is always as 
set by AT ST), while AT2 is a more aggressive version of AT1 (the effect is 
more noticeable for very slow connections – you may not see much difference 
with faster OBD systems). The J1939 protocol does not support Adaptive Timing 
– it uses fixed timeouts as set in the standard."

One shall implement this enhancement for faster application response times.

What steps will reproduce the problem?
1. Open App
2. Try and connect with android 4.2.1 or higher
3. It wont connect when executing socket.connect();

What is the expected output? What do you see instead?
Should connect.

What version of the product are you using? On what operating system?
Android 4.3
I have tested on multiple devices. Worked on all devices lower than android 
4.2.1

Please provide any additional information below.
I'm thinking this is actually a bug with android, however, apps like torque 
still work on the new versions of android.

I think the command is incorrect:

It is: super("10 51")
Should be: super("01 51")

Thanks

PVS

hi
i'm developing an android application for OBD. Your source code has been very 
useful for me but i`ve got some problems when i execute it.
Firstly, explain I usually use Eclipse for running and create the .apk and I 
don`t know if this is a problem. the cuestion is that when i run the 
application in the phone without error in the code appears and select any menu 
item appears me
"the application OBD II Reader has stopped enexpectedly. Please try again." and 
finish.
Could you help me in this question???
Is very important for me resolve this problem cause is essential for my proyect

thanks very much

my mail is [email protected]

When we test an ObdCommand instance that stores some value as a member, always 
remember to reset those members before next test or risk to have your tests 
borked.

A good solution is to get a new ObdCommand instance on each test.