I've just bought the 2nd generation iCarsoft LRii diagnostics scanner to use on my Freelander 1 (2003 1.8 petrol) but it doesn't seem to be able to communicate with my engine ECU (mems3). It will communicate if I use it in generic OBDII mode but obviously you then have some limitations.

The manufacturer claims that it should work according to their advertising.

Has anybody here successfully used one?

What limitations do you have in Generic ODBII mode? Is it not just that you 2003 model is standard ODBII whereas previous models needed specific, non-standard, comms protocols?

There are a few things that are outside of the industry standard OBDII scope which are not picked up by a generic scanner. The other problem is that it is limiting on the data streams that I can monitor. Even basic things like 'is the ignition on' are not detected correctly.

Zigzagsky said:

There are a few things that are outside of the industry standard OBDII scope which are not picked up by a generic scanner. The other problem is that it is limiting on the data streams that I can monitor. Even basic things like 'is the ignition on' are not detected correctly.

Click to expand...

When you say "not detected correctly" can I assume it has the option to do this or at least displays the option, but the status of the ignition is displayed incorrectly? Don't mean to split hairs... I find this sort of thing intriguing.

As part of the diagnostics you can set it to monitor what the manufacturer refers to as 'data streams'. So you can see stuff such as manifold pressure, fuel pump flow, water temp which are analogue and some digital streams such as whether the ignition is on or off, which doors are open, is the rear wiper activated, which doors are locked etc. The problem is that it's not monitoring most of these. The only modules it seems to be correctly communicating with are the ABS and a couple of others.
I've emailed iCarsoft but they have yet to offer a solution hence I was wondering if anybody else has used this successfully