Obd2 diagnostics

[intheozone]

Please forgive me as I am sure some of these questions have been asked before but I don't seem to be successful at using search on my iPhone.

I am trying to diagnose a misfire and rough running on my 2001 4.6 p38. I have a obd2 cable for communicating with the EAS. Can I use the same cable and some software (free or not too expensive) to get other fault codes from the engine and other sensors. Or do I need to shell out and get a nanocom

I saw in a post a while ago about a tablet app that could display things from a obd2 Bluetooth adaptor. Where is that post? How successful was the app. I see from eBay obd2 Bluetooth devices are not too expensive as are some code readers, will they work with the brains of the p38?

Thanks


Steve

[Pete38]

The EAS lead is different and only works for the EAS. You can buy an ELM327 style bluetooth device and that will work. Can't remember the suggested software for OBD 2 stuff but believe most of the software works. But there are limited functions available but believe most of the engine stuff is generic, but no HEVAC, gearbox, ABS etc. Worth the $20 delivered though I guess.

Edit: Software is EasyOBDII but is limited

[RR P38]

Pretty sure the new Nano com can do all functions with one lead, or its under development? The Nano is fairly expensive. The other option is one of the Black box solutions units or you can go for the Hawkeye;
http://www.bearmach.com/downloads/Diagnostic/Hawkeye_v3and4_GB.pdf

Im selling mine in markets, ATM.

[Pete38]

Yeh my Nanocom does it with one lead but that lead doesn't work with a pc or laptop. I have yet to see a cheap diagnostics unit, although my Nanocom could pay itself off with one failure in the bush... Touch wood it hasn't happened yet.

[davidsonsm]

I have the Torque app on my Samsung, along with an ebay sourced Bluetooth device and that reads fault codes. Works pretty well.

Funnily enough, I'm getting an orange "check engine" dash light at present, which is associated with fault 1179 - MAF related I understand.

I'm another P38 owner who won't be using a K&N oiled filter ever again. I'm back on the paper filter in readiness for the snorkel fitment.

I'm hoping a new MAF won't be needed.

[clubagreenie]

The P38 uses (by comaprison to the D2) quite a few connections (7 by memory ad some run paired with another) for the OBD data (the D2 only has 12v, 2 x earth & 1 x data). That's the first issue in getting something non brand or model specific to work with the whole system.

[OffTrack]

Might have been the Launch X431 iDiag? It's probably midway between a generic code reader and something like a Nanocom or Hawkeye in terms of pricing and capability. I haven't used on a P38 so I cant comment on coverage beyond the spec sheet.

Generally the iDiag seems to be slightly older versions of the Launch software sold to workshops so gives most of the available diagnostic information, reading clearing codes, live data display, testing actuators, ECU version information.

I tend to use it in preference to the Nanocom on my Td5 D2 for anything that doesn't require changing settings.

For the 1999-2002 P38 the coverage lists:

V8 - DTC, Data display, action test, version information, reset adaptations
Gearbox - DTC, Data display, action test, version information, reset adaptations
ABS - DTC, Data display, action test, version information
SRS - DTC
HVAC - DTC, Data Display

The hardware is about $120 but requires android or iOS device, and a $66US per year unlock. The unlock covers all supported systems on LR vehicles made between 1996 and 2011 in the current software version. The pro versions have coverage to 2014 models.

cheers
Paul

[Hoges]

Please forgive me as I am sure some of these questions have been asked before but I don't seem to be successful at using search on my iPhone.

I am trying to diagnose a misfire and rough running on my 2001 4.6 p38. I have a obd2 cable for communicating with the EAS. Can I use the same cable and some software (free or not too expensive) to get other fault codes from the engine and other sensors. Or do I need to shell out and get a nanocom

I saw in a post a while ago about a tablet app that could display things from a obd2 Bluetooth adaptor. Where is that post? How successful was the app. I see from eBay obd2 Bluetooth devices are not too expensive as are some code readers, will they work with the brains of the p38?

Thanks
Steve

a relevant post is http://www.aulro.com/afvb/p38a-range-rover/172248-high-long-term-fuel-trims-why.html for examples. App is Torque (pro) ~$5, plus Elm327 bluetooth OBDII plug (~$23 Ebay).
LR uses standard OBD2 codes plus a number of proprietary codes.

Highly probable that the cause of the miss is being stored in the engine ECU memory as a "generic" trouble code and will be listed on the Torque app.

As a first thought, running rough and missing maybe a coil block issue and /or a failing crankshaft position sensor...

EDIT: see also post #9 in http://www.aulro.com/afvb/technical-chatter/184520-persistant-misfire-idle-stalls-idle-gear.html

[RR P38]

I have the Torque app on my Samsung, along with an ebay sourced Bluetooth device and that reads fault codes. Works pretty well.

Funnily enough, I'm getting an orange "check engine" dash light at present, which is associated with fault 1179 - MAF related I understand.

I'm another P38 owner who won't be using a K&N oiled filter ever again. I'm back on the paper filter in readiness for the snorkel fitment.

I'm hoping a new MAF won't be needed.

Yep, K & N filters are bad news if you love your engine.
They are not designed with 4wds in mind.
Terrific if you are on a race track and want more power, but in dusty conditions they are a big fail.

[TheTree]

HI

I used a generic ELM327 wi-fi dongle from fleabay with DashCommand from Palmer Performance.

It gives me all the engine codes and was able to give me an ECU box fan failure P code, but it didn't know what it meant.

All in all, a few bucks well spent, but no substitute for a proper diagnostics kit

The Launch stuff sounds interesting, but $66 a year will soon add up:eek:

Steve