matts85vet

i need a step by step on extending my spark table to 6400rpm. i am using tunerpro rt $6E 165ecm. thanks in advance!

dan0617

I took some time searching and researching, and here is what I found and did, and I think it worked, but SOMEONE CORRECT ME IF THIS IS WRONG.

Open the .bin you are using. Save it as a different name, so if anything screws up, you still have your good .bin file.

Open your hex editor. If using TunerproRT, go to tools, advanced, hex editor. Go to location 0E97. (Scroll down till you find 0000E90. Then, count over 8 places (which is bit 7 since the first location in that row is bit 0). You will see it is number 58. Put the cursor in front of the 58, and type 59. The 59 will be red. Close the hex editor, save it when it asks.

Scroll down to your Spark Advance Table RPM vs LV8. Right click it, then select "Edit Item XDF Info". Click on the "Rows" tab. Click in the first row. You will see it is 400. Make it 0. Make row 2 400, row 3 800, etc. Keep increasing by 400 till you get to the last row, which will be 6400. Click apply, then close the window. Go to the XDF tab on the main page, then select Save XDF as, and save it under a new name. Go open the main spark table, and you will see it goes up to 6400. You will need to change your spark numbers as they will be the same as they were in their cells, but the rows rpm labels have changed therefore the spark has changed at many of the rpms.

Again, I did this and it seems to have worked but someone please tell me if I'm missing something that will keep this from functioning properly.

dimented24x7

iTrader: (2)

Dan,

The size of the spark table is something thats intrinsic to the ECM. It cant be changed in tuner-pro. TP only formats the data into something easy for humans to interpret. Making changes in TP only causes the values to be stored incorrectly in the bin, so its usually a bad idea to play with the XDF unless you really know what your doing.

To increase the size of the spark table would require that you make changes to actual code in the binary that operates the ECM. Its not a simple "click this" operation. Instead it requires some programming. Not too hard if you know assembly, but usually something that would be over the head of your average tuner.

RBob

iTrader: (1)

Looks like it'll work. Instead of using a by 200/400 RPM variable, uses the by 400 RPM variable. So instead of every 200 RPM per row at first, the whole table is every 400 RPM per row.

Loss of resolution, but extends the RPM range higher.

RBob.

matts85vet

thanks for the responses!
its seems easy enough.
i think i'll try it and see if i can get it to work.

dan0617

If you get a chance to throw it in the car and see if it works let me know. Only thing I know to do is to actually test it in car and datalog the timing at certain rpms to see if it is putting out the timing that it is supposed to according to that rpm in the timing table.

dan0617

This is something I found in old threads by tequilaboy. It is for sure over my head to develop something like this. It was almost over my head to get it installed in my software since it was never really spelled out step by step how to get it installed. I think changing the bit 58 to 59 makes it use the 400 rpm resolution table the whole time instead of the 200, then 400 table, as explained by rbob.

matts85vet

it works!

i followed your instructions. i changed the 58 to 59, re-labeled the spark table, updated the values in the table.

i burned a new chip with the new extended spark table bin and drove the car. it drove fine no problems.

no data logs yet- i was having issues with my autoprom.

i'm hoping to data log tomorrow.

dan0617

After you datalog look and see that it is showing the spark in the datalog that it is supposed to be getting according to the main table and adder tables at some different rpms. That way we can see if we just relabled the table and now made it innacurate, or if changing the 58 to 59 actually made it quit using the 200 rpm resolution table at low rpms, like we are expecting it to.

I'm in the snow here now so no driving and datalogging for me for a little while.

matts85vet

did some data logging today- IT WORKS! as far as i can tell, the advance above 4800 rpm corresponds to the table. i'll send you a copy of the log, the bin and the mask. hope you have tunerpro rt.

dimented24x7

iTrader: (2)

Your right, my mistake. I misread your post. I thought you where just changing the TP settings.

hellz_wings

iTrader: (2)

Wow this is amazing guys I just found this thread! Somebody should upload this BIN somewhere (basically a stock 6E bin with this mod).

So, you would, I presume, have to adjust the spark table accordingly or would all your spark values still remain the same at the right spots?

dan0617

You have to adjust the spark table after you do this. The same values remain in the same cells, but the rows labels changed therefore the timing the motor sees is changed. I used the compare feature of TunerproRT and compared to my old .bin, then changed the new .bin to make it match the old up to 4800. Some of the rows in the old .bin are no longer used so just ignore those.

EagleMark

Here's a $6E XDF and bin file with spark to 6400 RPM.

It was in my 6E folder, I do not know where it came from or who did it or it's acuracy but it does have a data log with it too. Hope it helps but use with caution!

usc iroc

Worked like a charm. Thanks for posting this info.