RhinoPower Ltd

Members Login
Username 
 
Password 
    Remember Me  
Post Info TOPIC: 33920-71EE0 1997 Vitara 1.6 16V


Guru

Status: Offline
Posts: 1354
Date:
RE: 33920-71EE0 1997 Vitara 1.6 16V
Permalink  
 


This is what the table looks like in Tunerpro's 2D data viewer:

TunerPro 2D data viewer

Into the hex editor and it looks like the data is in 8-byte columns:

TunerPro Hex Editor

 now switch to the 3D viewer:

TunerPro 3D data viwer

You should download TunerPro RT and have a play with it, it is a very powerful piece of software.

__________________

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.



Guru

Status: Offline
Posts: 1354
Date:
Permalink  
 

I have had to do that too, in the past. Its much easier to spot patterns in the data using TunerPro's 2D data viewer and then switch to the hex editor to determine the lengths of the axis and then the 3D data viewer to examine the shape of the map.

Working from a disassembly you only get the start addresses of tables or data so I still use a hex editor to determine the lengths of the axis with the

 



__________________

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.



Veteran Member

Status: Offline
Posts: 46
Date:
Permalink  
 

are the MAPs and conversion lookup tables in the BIN or in external eeprom/flash ?

example , plotting a 3d table from 09B0 of 8 bytes x 11 rows looks like a nice looup for something..



Attachments
__________________


Veteran Member

Status: Offline
Posts: 46
Date:
Permalink  
 

LMAO..  well..

a hex+text editor, Look at the characters cross eyed, spot pattens, pull out data in groups of 8 , 10 , 12 or 16 bytes, paste into excel, do a hex2dec and then graph it 



-- Edited by zukjeff on Thursday 19th of April 2012 12:06:14 AM

__________________


Guru

Status: Offline
Posts: 1354
Date:
Permalink  
 

The tables and other data are all in the binary. I'm working on an IDAPro script that will automatically seek out the tables based on what I've discovered from analysing the X90 code. I haven't looked at this code yet, other than to note that the code start address is the same as the X90 which leads me to believe that it is probably the same code but with different mapping.

What software package did you use for that? I usually use TunerPro for sniffing out tables if I don't have a good disassembly.



__________________

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.



Guru

Status: Offline
Posts: 1354
Date:
Permalink  
 

I have now copied the binary image from the processor's memory, it is available here:

http://www.rhinopower.org/ECUs/71EE0/docs/EF21.bin

 At first glance it looks very similar to the binary for the 79E50 X-90 ECU. This is to be expected as it shares the same PCB.



__________________

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.



Guru

Status: Offline
Posts: 1354
Date:
Permalink  
 

This ECU uses the same circuit board as the X90 of similar vintage, the firmware is the only difference. The additional board on this one has been fitted to eliminate the immobiliser - the ECU came to me because the company that fitted it made a complete hash of the job leaving the vehicle immobilised.

  This ECU could be remapped using a daughterboard.

71EE0 with immo emulator



__________________

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.

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