RhinoPower Ltd

TechSupport · Guru

RE: 33920-71EC1 1996 Sidekick/Tracker 1.6 16V US AT

Toys-n-joys · Member

I wonder if there's a ols or damos file for this ecu code. Older bosch ecu for audis and vw use a code aswell. Once you crack the code it's easy to modify right?

Mpps v16 or v18 etc has ability to read and flash through obd aswell rewrite Eprom.

Kess v2 with ktag has ability to do alot more even force write onto new boards from what I've heard. If there's a way to tune the older tracker g16 16v ecu or h27a xl7 2003 ecu please let me know. I am going to look into this more. Glad I found this forum

Troubled-1 · Member

Thank you for your response much appreciated, glad yo see you active with the Suzuki ECMs.

I'm.happy to hear it will be supported by rhinoview once repaired.

I have another ecm I'll start a thread on for information. It's for the same year and in good condition although it's construction or manufacture looks different.

I will keep an eye out for when your cables become available.

thanks again

TechSupport · Guru

That ECU will be compatible with the new tool and Rhinoview through the SDL interface, the OBD2 interface I need to experiment with, its quite difficult to get the correct timing unless you use a micro in the interface. I don't have schematics for those ECUs but its fairly straightforward to trace the circuitry back from the connector, if it got shorted to battery volts then its probably just the output transistor although you should check the traces as well.. I am doing repairs again this year although I haven't updated the website.

Troubled-1 · Member

Where would I keep an eye out for your interfaces once complete,? That is if you're going to sell them.

I have attached an image of another ecm (96 two door 5 speed 16v evap2) i'm interested in connectivity,/compatibility with rhinoview with the ecm in the attached image also .

*****tech question******

I understand your not tech support for Suzuki :p however, i do have a question about the board attached in the images, I don't know anyone with your knowledge to ask. If you were still repairing ECM S I'd probably just send it over to you

The ecm fuel pump relay circuit does not function. Pink wire to fp relay shows 12v (instead of supplying ground) when relay should be triggered it shows battery voltage. I'm pretty sure a short in the wiring caused battery voltage to short directly to this driver pin.

The ecm communicates, shows no codes and enters open/closed loop as it should with power direct to the FP via a fused switch. For all intents and purposes the ECM works excellent, aside from the FP relay circuit.

If you're inclined would you mind pointing out the numbers of the transistor, diode, or any other components on the silk screen in for the fuel pump driver circuit I could replace to get the ECM running properly. Pin 5 I believe is pink(fp relay trigger).

If I'm correct km thinking Q119, possibly Q106, are there any other possibly broken parts?

Thank you for your time. I hope you have an excellent new year.

-- Edited by Troubled-1 on Wednesday 2nd of January 2019 02:38:21 AM

TechSupport · Guru

I haven'thad much time to work on the Suzuki stuff over the last couple of years, I'm trying to kick it off again with some new projects. I didn't do much more work on remapping this ECU because there wasn't any real demand. I use a modified SDL interface with Rhinoview when I am working on these, the OBD2 interface is far too slow for real time data. I have just ordered some prototype PCBs for a new SDL interface that will be able to talk to these ECUs via SDL, those should arrive towards the end of this month.

Troubled-1 · Member

I've just come across this ecm, and have it in my possession.

Are you still working on Suzuki ecms?

My current ECM has a bad fuel pump driver circuit. (Standard transmission 96)

This ECM you have posted the information for is for a auto transmission. Although it runs the engine, I'm sure the MAP is wrong and off course it throws codes although I haven't run it enough to see if it's in limp mode .

I have several ecms. I would seriously be interested in enhanced diagnostics and possible reprogramming

Thanks for your time. I've been reading your tech since it seems like 2006.

Appreciate your willingness to share your hobby with us.

TechSupport · Guru

I did a little bit more work on the code for this ECU, interestingly the OBD1 interface has a number of undocumented diagnostic addresses which makes it even more powerful than the OBD2 interface. I have enough data parameters defined now to be able to completely reverse engineer the code although, as always, time is limited as I have a number of other projects on the go.

http://www.rhinopower.org/ECUs/71EC1/docs/ee93.asm

TechSupport · Guru

I did a little bit more work on the code for this ECU, interestingly the OBD1 interface has a number of undocumented diagnostic addresses which makes it even more powerful than the OBD2 interface. I have enough data parameters defined now to be able to completely reverse engineer the code although, as always, time is limited as I have a number of other projects on the go.

http://www.rhinopower.org/ECUs/71EC1/docs/ee93.asm

TechSupport · Guru

I've been looking some more at this ECU. Its something of an oddity, it appears to be an OBD1 ECU with an 'intepreter' built into the software to handle OBD2. The good news is that it has a full OBD1 interface which means that not only does it support live data and fault codes but it is also has immobilser support and its possible to control actuators and to read/write to memory. It uses ISO9141 on pin 7 so it requires a modified SDL tool but I am going to add the ECU definition to Rhinoview to support tuning at a later date.

TechSupport · Guru

I've now run the binary through the disassembler, this is the raw code:

http://www.rhinopower.org/ECUs/71EC1/docs/ee93.asm

TechSupport · Guru

This is an OBD2 ECU for a 1996 Suzuki Sidekick or Geo Tracker. 33920-71EC1 H8/536

The processor is an H8/536 which is very similar to the H8/532 processor used in the OBD1 models but with a few extra tricks thrown in. Its an OTP (one time programmable) device and requires a daughterboard to allow code modifications and remapping. The firmware version is EE93.

33920-71EC1 OBD2 PCB

The binary image from the processor is here:

http://www.rhinopower.org/ECUs/71EC1/docs/EE93.bin