Torque

Forums

Forums

Won't display CEL c...
 
Notifications
Clear all

Won't display CEL codes, but will clear them, 1995 Volvo 850

6 Posts
2 Users
0 Reactions
763 Views
(@wheelsup)
Posts: 3
Active Member
Topic starter
 

I have an HTC Incredible (Verizon) with the Android 2.1 I believe.

ELM327 bluetooth dongle with the latest updated hardware (just received it).

1995 Volvo 850 OBDII

I can connect to the car, it gets all the data fine. My CEL is on due to an O2 sensor. When I ask for the codes, it says none are stored or pending.

When I clear codes, it clears the CEL no problem (light went off).

I pulled the connector off my MAF sensor, and the CEL illuminated. Attempted to get codes, but still no codes are found.

Did the same to my wife's 1998 VW Jetta and it found the correct code (P0102).

I understand technically 1995 vehicles aren't OBD2 but mine is OBD2 compliant. I have had no issues pulling the codes with the el cheapo Autozone generic code readers.

Also, when connecting, the status bar says something to the effect of, "cannot connect, retrying" and on the second attempt connects fine.

Thoughts?

Neat program, using the freebie right now, if I can get this sorted out I will pay. I actually bought my phone with the intention of buying this app believe it or not, as I was in the market for a code reader but this is so much better and cheaper.

 
Posted : 10/08/2010 5:44 pm
(@admin)
Posts: 6550
Member Admin
 

Can you try again then send me a comms debug log (accessed from the menus) - it could be a bug, but as the function works on many other vehicles I suspect at the moment the ECU isn't supplying the fault codes when asked using the generic commands.

 
Posted : 10/08/2010 8:55 pm
(@wheelsup)
Posts: 3
Active Member
Topic starter
 

I believe I sent it correctly. Also I noticed when it doesn't connect first off to the ELM327 is says something about "trying an alternate connection". This is able to connect. It says that on both my 1995 Volvo and 1998 VW. Also none of the other OBD apps connect to my cars (either of them) so your program is already leaps and bounds better than the rest.

Could you shed some light on why it's not connecting correctly? If its the ELM327 I will send it back and get my money back, as this isn't your issue but an issue on my end. And then I'll buy the 0 one. I want this to work correctly, although I am (slightly) afraid of spending 0 just to not have it work either. Seeing as though others have no issues with these ELM327s.

 
Posted : 14/08/2010 11:05 pm
(@admin)
Posts: 6550
Member Admin
 

Got it, thanks. The 3 interesting bits are snipped from the log below, these are the responses to the commands to fault code requests. Unfortunately it looks like your Volvo doesn't allow access or does not support the fault code request outright on the standard diagnostic commands

1281825128456 --> NO DATA
1281825139326 --> NO DATA
1281825148606 --> NO DATA

I have some other documentation from the SAE which might cover this (at the moment quite a few pages to browse through) so if there is any other way to get extended fault info (I know there is, but it is down to volvo if it is implemented or not) I'll see what I can do.

Unfortunately I am quite busy at the moment with WinterSun (another upcoming android app) so it may be a week or two before I release another update

 
Posted : 15/08/2010 7:56 am
(@wheelsup)
Posts: 3
Active Member
Topic starter
 

Thanks for writing back! I find it odd that you can connect/pull with a standard OBDII scan tool but that it doesn't like this program. Not knowing much about programming, just a smattering of PHP/MySQL, I find it interesting but sometimes exceedingly frustrating!

I took a video of the MAF/code clearing experiment if it helps, fast forward to 1:50

http://www.youtube.com/watch?v=SoozilyKwBA

Also not sure if you need any help with this stuff but I am more than happy to do any grunt work/research if needed, especially when it comes to this Volvo stuff. I'm on a Volvo board and we are looking forward to your program being compatible with our cars.

 
Posted : 20/08/2010 1:27 pm
(@admin)
Posts: 6550
Member Admin
 

Hi, thanks for the video

Basically it confirms what I currently suspect is happening - the trouble codes are not available in the standard OBD2 specification that the ECU should be compliant to.

However it may be possible to list them in some extended version of the protocol - I have the documentation for that and hopefully will get to read through it properly next week

 
Posted : 22/08/2010 12:11 pm
Share:

  Follow me on twitter