| Home  Blogs Help Search Login Register  
« previous next »
Pages: [1] Print
Author Topic: Engine (and other) ECU codes read success (1999 V6 24V)  (Read 27026 times)
José V. Gavilá
Full Member
***
Posts: 96


1999 Espace 3.0 V6 24V


WWW
« on: February 21, 2010, 12:56:41 pm »

Hello!

It has been some time since I last wrote a message in this nice forum. This time is about the ECUs on my 1999 Espace V6 24V

I bought an AUTEL Maxidiag JP701 reader to get some info from another of my cars, a 2000 Mitsubishi Carisma 1.8 GDI. Well, success with it was not great, as I only got the 'no error codes stored' message, while I know there are some!

So today I have checked the unit with my brother's 2008 Honda Jazz. Wow, what a difference!. I could even get real time measurements. My next (used as always) car will be OBD-II compliant, for sure  Shocked  Shocked !!!

Then I have decided to try luck with the Espace. Yesterday night I had read several messages on this forum abut it and was not really too confident. But as I saw that the Espace had a CAN bus controller (it says so in the electronics box besides the fuses), I wanted to give it a try.

First thing I had to do was to hack my JP701 reader, which is intended for Japanese cars (the one needed was the FR704) to add Renault cars as well. I found the info and it is just a matter of adding, by USB, another file to the unit. Pretty neat and easy  Cheesy !!!

So I have connected the reader to the OBD connector and have tried first autoscan with OBD-II/EOBD modes, which in turns check all kind of interfaces, from KWP-2000 to several CAN systems, to ISOs and so on. But no luck, as expected.

Then I have entered the Renault menu for non-OBD-II cars and have found that there was an Espace model selectable and also two Espace IV models (one of them Phase II). So I have selected Espace and then Petrol engine... and, yes, it has connected to the car bus  Shocked  Shocked

So I have tested then Engine ECU and have got three errors, one current and two stored. And they make some sense, I think, as two of them relate to O2 sensor loop while the other is a configuration error (which could be due to a battery disconnect some time ago). Then I have tried ABS ECU and it has also connected, giving no errors. And then I have checked AIRBAG ECU and have got some open circuit errors in a couple front lateral sensors, which could be just real. The only ECU which has refused to talk is the AT ECU (transmission). For the three ECUs I have got also some info (model codes and such)

All in all, I have had no guts (yet  Roll Eyes ) to clear errors, just in case I fried something  Grin. But it seems that the communication and decoding is done nicely. What do you think?

Best regards,

JOSE
« Last Edit: February 23, 2010, 05:35:25 pm by José V. Gavilá » Logged

JOSE V. GAVILA
La Canyada (Valencia)
SPAIN

http://jvgavila.com
BrianM
Sr. Member
****
Posts: 321


« Reply #1 on: February 21, 2010, 11:19:54 pm »

Don't worry about clearing codes. I use the 704 all the time on mine. especially the o2 sensor fault. It is a good unit to have as it reports the code details. It does not do the auto transmition on any that I have tried. I also have a chinese clone 'Clip' this works great as it is a copy of what the dealer uses. But the 704 is great as it is so fast, ot having to have to boot up a computer. Good luck Smiley
Logged
José V. Gavilá
Full Member
***
Posts: 96


1999 Espace 3.0 V6 24V


WWW
« Reply #2 on: February 22, 2010, 09:21:22 pm »

Hi Brian,

Don't worry about clearing codes. I use the 704 all the time on mine. especially the o2 sensor fault. It is a good unit to have as it reports the code details. It does not do the auto transmition on any that I have tried. I also have a chinese clone 'Clip' this works great as it is a copy of what the dealer uses. But the 704 is great as it is so fast, ot having to have to boot up a computer. Good luck Smiley

Please, could you elaborate a bit about this comment ?

Quote
I use the 704 all the time on mine. especially the o2 sensor fault

I don't know if you want to say that it is not important to get an O2 sensor fault or it is the cause for you to use the 704  Wink

Thanks and best regards,

JOSE
Logged

JOSE V. GAVILA
La Canyada (Valencia)
SPAIN

http://jvgavila.com
renaultbiler
Sr. Member
****
Posts: 418



WWW
« Reply #3 on: February 22, 2010, 09:40:46 pm »

The 02 fault is "always" present on the Espace 24v, probably more a software issue than a real life problem.
Logged

1980 Alpine A-310 w/GTA 2.5 V6 Turbo
2000 Grand Espace V6 24v Initiale: http://www.renaultbiler.no/forum/viewtopic.php?id=2529
2000 Scenic RXi 2.0 16v IDE aut DP0: http://www.renaultbiler.no/forum/viewtopic.php?id=3751
1982 R20TX 2.2
Service Online: www.servicehefte.net/servdata/?cid=qqkX
José V. Gavilá
Full Member
***
Posts: 96


1999 Espace 3.0 V6 24V


WWW
« Reply #4 on: February 23, 2010, 09:10:39 am »

Hello!

The 02 fault is "always" present on the Espace 24v, probably more a software issue than a real life problem.

OK, thanks a lot!!!. I was wondering how it didn't trigger the engine error light  Wink!!!

Now I am more confident in my car  Grin

BTW, Airbag ECU reported also some problems. I will check them and comment here, just in case you coud help. I recall they were about open circuits in lateral sensors or something similar.

Best regards,

JOSE
Logged

JOSE V. GAVILA
La Canyada (Valencia)
SPAIN

http://jvgavila.com
renaultbiler
Sr. Member
****
Posts: 418



WWW
« Reply #5 on: February 23, 2010, 09:25:48 am »

"Always" the connectors under the front seats causing open circuit problems. No need to clear faultcodes, just fix the connection and the bag ecu selftest checks it out ok.
Logged

1980 Alpine A-310 w/GTA 2.5 V6 Turbo
2000 Grand Espace V6 24v Initiale: http://www.renaultbiler.no/forum/viewtopic.php?id=2529
2000 Scenic RXi 2.0 16v IDE aut DP0: http://www.renaultbiler.no/forum/viewtopic.php?id=3751
1982 R20TX 2.2
Service Online: www.servicehefte.net/servdata/?cid=qqkX
José V. Gavilá
Full Member
***
Posts: 96


1999 Espace 3.0 V6 24V


WWW
« Reply #6 on: February 23, 2010, 05:37:07 pm »

Hi Tom,

"Always" the connectors under the front seats causing open circuit problems. No need to clear faultcodes, just fix the connection and the bag ecu selftest checks it out ok.

OK, thanks!. Will do as soon as possible.

It has been a great help  Cheesy !!!

Regards,

JOSE
Logged

JOSE V. GAVILA
La Canyada (Valencia)
SPAIN

http://jvgavila.com
Anders Dinsen
Administrator
YaBB God
*****
Posts: 2822



WWW
« Reply #7 on: February 24, 2010, 06:07:57 am »

Hi José, great to hear from you here again! Smiley

I've got the same experiences Tom is mentioning: O2 fault code is "always" there (the software developer who put it in probably has a brother in law or something with shares in an O2-sensor production facility! Wink ), and the side airbag connector under the seat always gives problems.

It's the brown connector in this photo:



And the way to fix it:



/Anders

« Last Edit: February 24, 2010, 07:39:43 pm by Anders Dinsen » Logged

'82 Murena 2.2 prep 142
'01 Grand Espace 24v
'08 Smart Fortwo 0,8 cdi
george
Newbie
*
Posts: 16


« Reply #8 on: February 25, 2010, 08:09:26 am »

O2 sensor fault will always show up as the engine is not running.
If you can check the ECU with the car running you will find the fault is not there anymore.
Logged
Pages: [1] Print 
« previous next »
Jump to: