RhinoPower Ltd

Members Login
Username 
 
Password 
    Remember Me  
Post Info TOPIC: Error codes 81 & 83 on Grand Vitara 2.0 D Mazda RF engine.


Guru

Status: Offline
Posts: 1211
Date:
RE: Error codes 81 & 83 on Grand Vitara 2.0 D Mazda RF engine.
Permalink  
 


The dealer tools require a password to use the immobiliser functions, passwords only last 24 hours and are only available to dealers. My interface can be used for key matching but when the codes are faulty then the codes in the ECU and immo must be replaced by removing and reprogramming the memory chips.



__________________

1984 Suzuki SJ413K pick up, 1.6 16V Baleno engine
2000 Suzuki Vitara 1.6 8V, many mods
2004 Suzuki Ignis 1.5VVT 4Grip
2006 Suzuki Jimny 1.3VVT JLX+
and many more.



Newbie

Status: Offline
Posts: 1
Date:
Permalink  
 

Hi guys,

Sorry for re-animate this old topic :P

For that car with that engine (rf-turbo) which will be the best tool for Immobilizer jobs? Denso Intelligent Tester with SDT or Vetronix (GM-Tech2) console ?

Thanks ;)

__________________


Newbie

Status: Offline
Posts: 2
Date:
Permalink  
 

Hello Rhinoman I'm writing because I have the same problem with my Vitara TD engine mazda rf. I test and give me the code error 83 (serial data link), I read in difflock forum that the ECU denso can turn off the inmobiliser and read about some people there that can resolve the problem. I appreciate it if you can tell me a solution send me a private mesaje. THanks!

__________________


Member

Status: Offline
Posts: 5
Date:
Permalink  
 

Sadly, not that close, Andover.

Let me try a few things first & if I still have problems we can sort something out.

I have still got use of the Jag for important trips with "she who must be obeyed" and my old Pinto based Mk3 Corttina Eagle RV kit car, almost as thirsty as the Jag!

Thanks very much for the offer, what ever the outcome we can try your kit.

Ross

 

 

 



__________________


Guru

Status: Offline
Posts: 1211
Date:
Permalink  
 

Whereabouts  are you located? If you are local I could drop over and try my tool out.



__________________

1984 Suzuki SJ413K pick up, 1.6 16V Baleno engine
2000 Suzuki Vitara 1.6 8V, many mods
2004 Suzuki Ignis 1.5VVT 4Grip
2006 Suzuki Jimny 1.3VVT JLX+
and many more.



Member

Status: Offline
Posts: 5
Date:
Permalink  
 

Just done a CEL and get Code 12 - Normal, to be expected because the Glowplug light isn't flashing, so the engine will start.

I will find ECU numbers & let you know, hope your design will work.

Will also get model type of friends Launch tool to see it can be confirmed compatible. Will then use it to see if any error codes.

When this starting problem occurs, if I ignore the flashing Glowplug light & turn key to crank the engine, it does fire a few times. Repeating this gives the same results.

If we ignore the diagnostics, I would assume there was a fuel problem, low flow or pressure.

Funny thing, the problem occurs immediately after or soon after refuelling.

In the olden days I would have checked for blocked fuel tank breather, crud in fuel filter (recently changed), or faulty pump (now incoveniently fitted in the tank).

As the ECU or some other part of the system knows or thinks there is a problem and flashes the Glow lamp, I assume there is a transducer that gives an out of range output, perhaps fhe fuel pressure.

What do you think, are there any simple, mechanicle or electrical checks I can make? Like stick a pressure guage on feed from tank.

I have no desire to let a main agent near the car again, the car isn't worth it in monetary terms.

I see you are in the Swindon area, perhaps we should meet for a beer one day. I assume you drink, I've never met a racing diver who doesn't whether active or retired!



__________________


Guru

Status: Offline
Posts: 1211
Date:
Permalink  
 

I've been trying to find out some more details on exactly which Launch tool works with the OBD1 Suzukis. If you can borrow it then you can hook it up to the PC simulator and extract all the addressing info from it.

I have the SDT but I think it only goes back to 2001, if you get the 4 digit ECU ID I will try it on that tool as well.



-- Edited by Rhinoman on Saturday 3rd of December 2011 06:07:55 PM

__________________

1984 Suzuki SJ413K pick up, 1.6 16V Baleno engine
2000 Suzuki Vitara 1.6 8V, many mods
2004 Suzuki Ignis 1.5VVT 4Grip
2006 Suzuki Jimny 1.3VVT JLX+
and many more.



Member

Status: Offline
Posts: 5
Date:
Permalink  
 

Sorry, forgot about the year, it's 2000 on a W.

Will knock up the interface and try it. It won't be till next week but will let you know the outcome.

A good friend and small garage owner has a very expensive Launch code reader. It does appear to read the codes and reset them. I will try to borrow it and see if the same error shows as some time ago.

Can't remember the number but it said something to the effect of

"o2 sensor bank? sporadic fault" and it is certainly a sporadic failure to start!

I will also check the flash codes.

Will be home tomorrow. Have been lent a Jag XJ8 SE. A tad thirsty but very nice to drive.

Thanks for your help



__________________


Guru

Status: Offline
Posts: 1211
Date:
Permalink  
 

The interface should communicate with any Suzuki ECU prior to 2001, I'm not aware of anyone who has tried it on a diesel model though. If you have the FTDI kit then you could easily put together an interface and see what you get.

Have you had a look inside the ECU? you may be able to read the memory which would help to determine what the data is at each address. It should be a Denso unit and is probably HC16 based. What year is the vehicle?



__________________

1984 Suzuki SJ413K pick up, 1.6 16V Baleno engine
2000 Suzuki Vitara 1.6 8V, many mods
2004 Suzuki Ignis 1.5VVT 4Grip
2006 Suzuki Jimny 1.3VVT JLX+
and many more.



Member

Status: Offline
Posts: 5
Date:
Permalink  
 

Well, including the transporting of the car and the main agent restting the immo, the cost was £270.

What a pity they then read the error codes AFTER they had rebooted the system! They said there were no errors & everything was fixed.

I knew that was crap because they had done nothing about the original problem of the starting difficulty - glow lamp continually flashing.

So I was not in the least bit surprised when the problem reoccured on Friday night. I was lucky this time, after leaving the car for about 10 mins I tried aggain and it started, so I drove it straight home.

There will be fireworks on Monday!

Will your diagnostic unit and software work OK with this car, see Subject line?

I'm an electronics design engineer and have an FTDI development kit plus enough bits to build the unit.

Look forward to hearing from you



__________________


Guru

Status: Offline
Posts: 1211
Date:
Permalink  
 

There is a definate issue with the immobiliser and jump starting, perhaps a strongly worded letter to Suzuki GB might have some effect. They must be aware of this issue.



__________________

1984 Suzuki SJ413K pick up, 1.6 16V Baleno engine
2000 Suzuki Vitara 1.6 8V, many mods
2004 Suzuki Ignis 1.5VVT 4Grip
2006 Suzuki Jimny 1.3VVT JLX+
and many more.



Member

Status: Offline
Posts: 5
Date:
Permalink  
 

I really can't believe there is any logic behind the fact that a lost keycode in the ECU stops a vehicle from starting, and the only way to fix this is by towing the vehicle to the nearest dealer (in my case 20 odd miles) so that at considerable expense the ECU can be reprogrammed.

And furthermore, what a crap piece of hardware design that allows the addition of a boost battery to cause the ECU to 'forget' the keycode. This was done by the AA when they tried to work out why the vehicle failed to start in the first place.

So even when the keycode is sorted, the original problem has to be diagnosed, £86 for said dealer to connect his code reader!

My other car has a Ford Pinto engine on a carburretor with points and a coil, it's the reliable one. Maybe it will tow the GV.

I'm not happy!

 

 



__________________
Page 1 of 1  sorted by
 
Quick Reply

Please log in to post quick replies.



Create your own FREE Forum
Report Abuse
Powered by ActiveBoard