RhinoPower Ltd

pszemeke · Newbie

33920-64E10 Swift GTI (I2)

Agostino95 · Newbie

Hi guys , i'll try to remap the ECU swift i mounted in my samurai . I tryed to download the "I2 TunerPro definition File (.xdf)" but there is a servere error , could someone send me via E-mail a copy of that file ? thanks a lot !

TechSupport · Guru

Most of those files are quite out of date. The latest files for the Swift GTi are for the F5 and those are available here:

www.rhinopower.org/TunerPro/F3_serial_mod.zip

I am looking to update those files again, but I need some feedback from someone running a vehicle. I have been working with another person and we will be looking at better defining the acceleration enrichments come the spring.

-- Edited by TechSupport on Thursday 10th of February 2022 12:41:54 PM

joshy182 · Newbie

Hello, I'm currently searching for some XDF files, the links that are on this page are no longer working, can you please upload those files again?

chiptuner · Newbie

can you please share the link files:

www.rhinopower.org/ECUs/64E10/64E10.html

www.rhinopower.org/TunerPro/Bin_definitions/swift_I2.xdf

likaon · Newbie

Hello, i'm looking for .xdf for I2 and F5 ecu.
I've downloaded .bin files from my I2 and i can't download Swift_I2.xdf from site.
Where i can find it for my ecu ?

sag · Newbie

Hello i´m from argentina.
i have a Swift GTI and would have put the original ignition maps and fuel.
I need the .bin files and .xdf of I2 and F5 ecu , to combine with the maps currently have, the car no longer works with maf and would like to build maps to work with map .

Some I could provide these files?
then I share what I could achieve

Teeth · Member

I am glad you're still working on this--my car is on the road again, so I may be able to help real-world verify things, though I now have an I4 Cultus ECU in the car.

I am succesfully tuning with an Ostrich and I have made some minor updates to a version of the I2 .xdf you released earlier. I've changed the addresses so I can use a 16k.bin so that it is convenient to compare code across all the Swift GT/i ECUs, however.

I'd be happy to share my .xdf and other files, if you have a preferred method of getting it to you.

Also, I am very interested in the relationship between the tables at 48E0 and 4900 and the scale factors for the maps, as these seem to change how the rows correspond to rpm in the fuel and ignition tables respectively.

I also have several tuner .bins for the GT/i and Cultus ECUs that I am willing to share, though that's a bit of a touchy subject (or maybe not) as I'm pretty sure some folks considered these things valuable intellectual property at some point, but none of them are currently available on the market either, so who knows--we can correspond via PM on TeamSwift if you like.

Regards,

Seth, aka Teeth

TechSupport · Guru

I've done some more work on the I2, I've found an issue with reading RAM addresses which I have a work around for and I'm now getting some sensible results. The rev limiter is at 7500rpm, as stated in the FSM. The maximum rev limit is 8500rpm (0xDC) after which the RPM reading becomes unstable so a safe limit is probably around 8200rpm. I intend to spend a few more hours on this to try and produce a more comprehensive xdf file.

Teeth · Member

Would you be interested in updating a 16k XDF file with your changes? I like to be able to quickly compare across all the available programs.

Is there a good reference anywhere on how to come up with an .xdf file? I'd like to learn more.

Teeth · Member

The fuel table should be proportional to AFR but these tables usually have a scaling factor applied that will allow the best possible resolution, most of the AFR tables that I've seen are fairly flat under mid loads for stoich.

That's just it--the table isn't very flat at times when the ecu would want to tune to stoich using closed loop, if it is enabled.

This is the part of the map used for lift throttle, load neutral, and part throttle cruise where AFR's are running very close to stoich, yet there's more relief (range) on that side of the map.

F3 Fuel Map

TechSupport · Guru

The fuel table should be proportional to AFR but these tables usually have a scaling factor applied that will allow the best possible resolution, most of the AFR tables that I've seen are fairly flat under mid loads for stoich. Now I know that the RPM scaling is correct I will look for the switch to another table.

The table at CC20h is related to ignition timing and the idle switch, it may be ignition timing at idle but I suspect that its the ignition correction during deceleration and below 12MPH.

Teeth · Member

My problem is that I have to wait until I fix the transmission before I can do any more road testing cry

I do have a wideband, and I've had good results tuning with the Ostrich--running between 12.5 and 13.0 at WOT all the way up and the engine feels strong. I know that fuel tables are usually expressed in terms of AFR somehow, but I'd then expect to see a lot of numbers corresponding to stoich in the table, particularly in near neutral-load, part throttle, and cruise, and I don't see that.

Looking forward to see if you can figure out what those two tables that are always altered with the rev limiter do--running off the scale for tuning at 6500 rpm doesn't sound so great, though my car runs fairly well. It seems like the ECU starts richening the mixture without respect to the maps 500 rpm before the limiter, so that still sounds correct for stock but I could swear it's the same at 7500 when the rev limiter is changed.

I have I4, I3, and F3 .bins FYI.

TechSupport · Guru

I need to repair my I2 as it failed due to a short. I'm thinking that there is another table that handles fuelling at high load, I will look through the code for that. Have you got a wide-band sensor? the problem with trying to relate the tables to AFR values is that you need to know all the tables and corrections that are being used. Now you are getting some results I will do some more work on this and between us we can improve the definition, confirming the RPM is a big step forward.

Teeth · Member

Well, that corresponds closely to what I'm seeing in real-world testing running the OEM tune, so that's probably correct.

I am interested in what happens to the maps when the rev limiter is increased.

I've noticed that the 1-row tables at 48E0 and 4900 are always also modified when the rev limiter is increased when tuning. I've speculated that these tables "stretch" or assign different rpm load points to the fuel and timing maps. I believe I see this in real world tests, but I may be imagining things (also working with a partner watching the address tracing--not sure if he sees what I see). I am also confused in that there doesn't seem to be a logical or linear way to relate the changes in the table to real-world numbers. Is it possible to double check this with your "arbitrary waveform generator"? I could send you a modified .bin or you can use these values:

table values		RPM
OEM	8500	OEM	8500?
20	28	500	800
30	38	750	900
40	47	1000	1000
50	63	1250	1500
60	78	1500	2000
70	94	1750	2500
80	110	2000	3000
90	125	2250	3500
100	141	2500	4000
120	156	3000	4500
140	172	3500	5000
160	188	4000	5500
180	203	4500	6000
200	219	5000	6500
224	234	5500	7000
255	250	6500	7500

TechSupport · Guru

I did a little more work on this, I have programmed the crank waveform into my arbitrary waveform generator to run the I2 ECU. Running through the fuel map I get the RPM load points as this:

That should be correct unless my maths is wrong. The table should be AFR but I haven't determined the scaling factor.

-- Edited by Rhinoman on Sunday 23rd of February 2014 10:11:52 PM

TechSupport · Guru

Teeth wrote:
Thanks--this is much better.
All the values appear more or less as they should.
Just a few more quick questions: You've confused me with the new hex addresses you list as "real addresses" Perhaps it is simply a limitation of the hex editor in Tuner Pro, but I still see the relevant addresses as 503C and 503E--the last address in the file is 7FFF and the actual program begins at 4000. Is there a way to see the "real" addresses in the Hex editor?
I also still can't commit changes to the RPM values by using the scalar, but I can change them manually using the Hex editor to DA and DB. The values then change to 8512 and 8551 respectively. I am glad I can set this, but I still don't understand what's going on there.
The closed loop parameter is read as 129 which is what should actually be set to disable closed loop correct? Default value is 26 hex? AT least changes to this value are saved from the dialog box. What values should I actually use to enable or disable close loop?
Just trying to get a .bin with some obvious changes to burn as a test when I can find some hardware to run the burner.

I don't think that you can see real addresses in the hex editor, it something that should be asked on the TunerPro forum I think.
I'll check the temperature scaling, I need to create a conversion chart for that anyway to be be able to cross reference the sensor voltage with the actual' temperature.

Teeth · Member

Thanks--this is much better.

All the values appear more or less as they should.

Just a few more quick questions: You've confused me with the new hex addresses you list as "real addresses" Perhaps it is simply a limitation of the hex editor in Tuner Pro, but I still see the relevant addresses as 503C and 503E--the last address in the file is 7FFF and the actual program begins at 4000. Is there a way to see the "real" addresses in the Hex editor?

I also still can't commit changes to the RPM values by using the scalar, but I can change them manually using the Hex editor to DA and DB. The values then change to 8512 and 8551 respectively. I am glad I can set this, but I still don't understand what's going on there.

The closed loop parameter is read as 129 which is what should actually be set to disable closed loop correct? Default value is 26 hex? AT least changes to this value are saved from the dialog box. What values should I actually use to enable or disable close loop?

Just trying to get a .bin with some obvious changes to burn as a test when I can find some hardware to run the burner.

TechSupport · Guru

The first check to do is to ensure that the file length is correct, the bin that I am using is 32k which is for a 27C256 EPROM. I've just checked the xdf that I have and the offset was not specified correctly for the fuel cut values, the EPROM is actually mapped from 8000h to C000h so in my TunerPro definition, which now uses real addresses, the addresses should therefore by D03C and D03E. I have just completed another run through the xdf adding all the tables although most are not yet assigned.

http://www.rhinopower.org/TunerPro/Bin_definitions/swift_I2.xdf

Edit:

The fuel cut limits are at D03B and D03D if they are, more correctly, defined as 16-bit values

-- Edited by Rhinoman on Wednesday 15th of May 2013 01:36:30 PM

Teeth · Member

At your suggestion, continuing the mess I started here

http://rhinopower.activeboard.com/t37509007/tunerpro-xdf-files/

The only files I can get to load successfully were downloaded from the page linked below. I downloaded a second copy today to see if these had changed. The .bin file I get currently doesn't seem to be in sync with the .xdf-- It is populated with values, but they are all scrambled. The .bin I thought I downloaded from the same link earlier still works fine, but only has the fuel cut off scalars. I also can't seem to save changes to the fuel cutoff to the .bin.

I am new at this but I think this is the line that should contain the information for the fuel cut off constants, at 503C and 503E as referenced in the .xdf.

The values are FA (250) and FB (251) respectively. Which would make me think that those values would be near the top of a scale with 255 (FF) as the maximum value. So then I would expect that there should be a way to convert the hex values to rpm--I would expect something like X*29+ some number, but this thread on TeamSwift says it must be reduced to DA and DB for cut off at 8600? http://www.teamswift.net/viewtopic.php?f=4&t=45878&hilit=hex+address+temperature&start=25#p345669

The conversion in the .xdf is 1864200/X?

Also, I can edit the values manually in the hex editor, but not by changing the values in the scalar dialog. I tried to define my own scalar for the open loop value, but I am having the same trouble as with the fuel cuts for editing.

Thanks for your help--hopefully I will be able to add an I6 .bin to the repository soon.

TechSupport · Guru

I wrote a script for IDAPro to search out all the table start addresses, the results are here:

http://www.rhinopower.org/ECUs/64E10/docs/table_finder.txt

There are a total number of references of around 100.

TechSupport · Guru

The information for this ECU has been provided to me. I have the source code and the locations of the fuelling tables and (the only) ignition table is known.

http://www.rhinopower.org/ECUs/64E10/64E10.html