icarsoft i930 cant speak to abs

Hi folks.
Bought an icarsoft i930 a couple of weeks ago for my 2001 td4.
It cleared a mil light that I'd had for well over a year ( which 4 other cheap code readers and the AA's reader couldn't clear ) which was a good start. It also does the srs system no bother.
But it cant seem to connect with my abs system. When I try, the abs, tc & hdc indicators flash on and off so its doing something right but then I get a failed to communicate message on the screen.
I tried it on my dads 2002 td4 ( which has a slightly different abs system ) and it worked fine on all systems.
Bit of a shame as I occasionally have a visit from the 3 amigos which I've managed to fix with new rings & sensors.
could my abs ecu be faulty? Or am i doin something wrong? There are currently no warning lights on the dash. I've emailed diagnostic world where I bought it but haven't had a reply.
Has anyone out there got an i930 which works on a 2001 td4 ?
cheers folks. ...mitch

Are there any new firmware updates for you in i930?

Can you choose which ABS system you try and talk to on the i930?

I have accessed ABS on my 2002 TD4. I think there are 2 different menu options for a 2001 and 2002+. Also, email [email protected] they are very helpful. Check you have latest download as it is a development type tool being improved regularly.

mitchtd4 said:

I tried it on my dads 2002 td4 ( which has a slightly different abs system ) and it worked fine on all systems.

Click to expand...

Yours should be the same as your dads. There is one software module for the early ABS(BOSCH/WABCO) and one for the late ABS(TEVES) in the i930. There are 4 different ABS modulators on the Freelander:

97-00 Bosch/Wabco
01-02 Teves
02-04(05) Teves
04(05)-06 Teves

Maybe you have choosed the wrong software module or i930 have problems with the 01-02 ABS?

01MY Teves is the Mk20 and 02MY on is Teves Mk25 and are different and have different comms setup

I always thought it was as per this:

1998 - 2001 WABCO D ABS
2000 - 2001 TEVES MK20
2002 - 2006 TEVES MK25

Lights on the dash will alter when you go into the abs computer as yer stopping the process logic when you go in.

Thanks for all replies folks. I've tried every abs option on i930 but still no go yet.
I'll check for updates as suggested. My car was built September 01 so could be bosch or teves. Would that info be printed on the abs pump behind the headlight?
I'll also email [email protected].
I'd love to get it workin as its a really handy tool.
Thanks folks.

My WABCO pump clearly has WABCO marked on it. In fact all 3 have had WABCO written on it - not the most reliable of components in my Freelander!

I'm not sure whether the i930 'detects' what model of Freelander its plugged into or whether you tell it - but if you tell it - have you tried telling it you're plugging it into an older or newer spec that you actually are?

Yes, I tried every option regarding age of vehicle. I cant see a manufacturer name on the abs pump, it has a sticker on it with the code srb 000110.
I've emailed icarsoft who said they would be in touch.

Have you checked power, grounds and comms to the module?

As in wiring integrity, module gets 12V, has a decent earth and the comms line isn't open circuit/short circuit?

Do I disconnect the multiplug on the abs pump to check these? Or at the diag connector in passengers foot well ?
Cheers. ...

The i930 won't be talking to the pump - it talks to the ABS ECU, which is located under the passenger seat on my early Freelander.

As the pump is different to your dad's 2002 model, and it doesn't have WABCO written on it - by deduction from Hippo's list it must be using the TEVES MK20. This looks to have had a very short lifespan. I wonder if the i930 is coded to talk tot he WABCO and TEVES MK25 units but isn't for the TEVES MK20? Might be worth asking iCarSoft.

Also found some interesting information in the MK20 datasheet. Is it possible you cant enter diagnosis mode because you have a code that you havent cleared/fixed?

The amber ABS and red brake warning indicator will blink rapidly. If a hard trouble code is present

Click to expand...

3.2 ABS DIAGNOSTIC TROUBLE CODES
The Teves Mark 20e Antilock Brake System (ABS) module may report any of the following diagnostic trouble codes: • BUS System Communication Failure • CAB Internal Failure • Cluster Lamp Failure • Left Front Sensor Circuit Failure • Left Front Wheel Speed Signal Failure • Left Rear Sensor Circuit Failure • Left Rear Wheel Speed Signal Failure • Pump Circuit Failure • Right Front Sensor Circuit Failure • Right Front Wheel Speed Signal Failure • Right Rear Sensor Circuit Failure • Right Rear Wheel Speed Signal Failure • System Over Voltage • System Under Voltage • Valve Power Feed Failure Diagnostic trouble codes are retained in memory until erased using the DRBIIIt, or automatically erased after 255 key cycles or 3500 miles.

3.2.1 SYSTEM INITIALIZATION System initialization starts when the key is turned to “run”. At this point, the CAB performs a complete self-check of all electrical components in the antilock brake systems. The ABS and brake warning lamps will illuminate for 4 seconds with ignition on. At 20 km/h (12 mph) a dynamic test is performed. This will momentarily run the pump/motor. If dur- ing the dynamic test, the brake pedal is depressed, the driver may feel the test through brake pedal pulsations. This is a normal condition. If any component sets a trouble code during system initialization or dynamic check, the CAB will illuminate the ABS warning lamp.

3.2.2 DIAGNOSTIC MODE For a Mark 20e system to enter diagnostic mode, vehicle speed must be below 10 km/h (6 mph) and no ABS condition present. If vehicle speed is not below 10 km/h (6 mph), a “no response” message could be displayed by the DRBIIIt. The following are characteristics of diagnostic mode:
• The amber ABS and red brake warning indicator will blink rapidly. If a hard trouble code is present, such as a CAB Power Feed Circuit diagnostic trouble code, the indicator will be illuminated without blinking until the diagnostic trouble condition is corrected. • Antilock operation is disabled.

I've had no reply from icarsoft since yesterday so will try again tomorrow.
I'll ask them about the teves 20 as suggested.
Cant see any ecu under my seats, but there is a black box mounted on the front of the abs pump. Could that be the abs ecu?
Regarding any stored trouble codes preventing communication, this could be the case but dunno another way to clear them. I wonder if a hawkeye would do the job. Would be an expensive nightmare if that had same issue as i930.
It's a bit frustrating as although there are no warning lights lit and abs is workin fine just now, I'm pretty sure the 3 amigos will strike again.
thanks for all your help folks.
much appreciated.

Hippo said:

I always thought it was as per this:

1998 - 2001 WABCO D ABS
2000 - 2001 TEVES MK20
2002 - 2006 TEVES MK25

Lights on the dash will alter when you go into the abs computer as yer stopping the process logic when you go in.

Click to expand...

Info from micro cat May 2014:

SRB100800 = up to vin YA999999 (I assume it's WABCO D ABS)
SRB000111 = vin 1A000001 to 1A999999 (I assume it's TEVES MK20)
SRB000201 = vin 2A000001 to 5A428027 (I assume it's TEVES MK25)
SRB500250 = vin 5A428028 onwards

Web says SRB500250 superceeds SRB000201. I guess this is the same TEVES MK25 but with a slight update?

mitchtd4 said:

...
Regarding any stored trouble codes preventing communication, this could be the case but dunno another way to clear them. I wonder if a hawkeye would do the job...

Click to expand...

I've used my Hawkeye on mk20 and mk25 and they both work. The TEVES MK25 option has different wiring so it needs the BA5077 adapter added in series with the normal Hawkeye cable.

Update on i930 issue
After emailing icarsoft 3 times over 3 weeks I received an answer from their engineer.
which reads



Thank you for your email.

Engineer said as it need security verify to test your car,
I'm afraid i930 can not test ABS system of your car .
Sorry about that.

Needless to say I'm very dissatisfied with icarsoft. They should state clearly that for certain models of car the unit will not work for on a specific module. If I'd known this I would have put the hard earned 90 quid to a hawkeye.
so if you're thinking of buying an i930 for a 2001 td4 please think again. You'll be as p*^@ed off as I am.
works great on a 2002 td4 tho to be fair.
hope this helps anyone who's looking for a code reader for a td4.
Thanks to everyone who offered advice on this thread.
cheers.....mitch

It's strange they say they need a security test. You would think someone who makes the product wouldn't have added the option if they knew it wouldn't work. Unfortunatley readers which cover many vehicles don't always get tested on every vehicle, with every option. Writing and supporting all that software will take a lot of time unless it's nicked.