Dear all,

I bought an iCarSoft i930 diag tool. Everything is working well (I can scan every modules) except the Engine Control Module which shows a message like "Fault in communication with vehicle ECU" ... I search on this forum and I saw I'm not alone but I didn't see any solution or workaround.

The weird thing is that I'm able to read the data stream ! Coolant temp, battery, short trim fuel, ... So my ECM is working fine and the data bus (CAN ?) too ...

So a question : must I have the i930 for every modules and and ELM327 for the ECM ? Are they serious ? I do not have the OBD2 menu on my device.

Thank you,

Laurent

 

I had the same problem with my i930. Wouldn't read the ECM on my STR or XF. Answer: Update the unit on their website. It's supposed to come fully up to date, but some do & some don't. I updated mine & it works fine now.

 

 

I'll have a look tomorrow as it's 10pm here. Can't recall about the OBD2, but I'll be able to find out. Do you have the Jaguar specific model ? What car do you have ?

 

Read down this thread a bit, as others have had the same issue with the ECM you have:

​​​​​​​

 

Mine is v12.10. OBDII is there in the opening menu. Interestingly, it failed to read the ECM (STR) in manual mode, but scanned it successfully in auto.

 

When I ordered my i930 a little more than two years ago, my understanding was that it can be programmed from the iCarsoft website to read the engine modules OR all the other modules, but not both at the same time. You have to decide what you want it to do. I chose to leave it in the format it came in, which was to read all of the modules EXCEPT the engine modules. I use a $40 generic OBDII code reader from Harbor Freight whenever I need to read or erase any engine modules. That strategy has worked well for both of our Jaguars....

 

@Jon89 I missed that part, re: reading one or the other. I'm going to go on their website & read up. Fortunately, I too have generic OBD reader as a back-up. But it does scan the ECM on auto, but not in manual.

 

Since I see no details on what year ST is being looked at, I'll just give you the quirk that I ran into with the i930:

I have a 2002 model that has a build date of 5/2001. The i930 reads everything EXCEPT the PCM. I have to select the 2001 model year for it to communicate with the PCM.

Could you be running into a similar problem, where you have to select a different year to read an individual module?

 

I also tried mine as 2003 model, the MY, & made no difference. I will try it with 2001 entered.

​​​​​​​Update: Didn't work on 2001 setting. 2002-3 setting is combined.

 

I have a 2004 2.5 V6 and had this drama: ..... Ordered I carsoft i9300 through a reputable dealer and that finished up with me returning it (as it didn't want to connect) despite the seller telling me it was good for my model....I contacted them again and they couldn't help... suggested i get in touch with the manufacturer in the US. I did that and they said the i9300 wasn't compatible and I needed an LR 2 Model. I sent it back to dealer and got refunded. Very confused at this point and pretty hacked off too.
So, I then ordered the LR 2. although 30% more expensive than the i9300 it was supposed to do more...Really i said...i just want to clear the faults!... Once the LR 2 is connected it still has similar issues where it says "it cannot always connect with the ECU" although it will still clear faults.