Tunerpro, xdf, bin - unexpected error closes

[eficker]

When i open tunerpro rt (registered), and then load both the xdf i have and the bin i have for a bmw, and then try to view a map, it closes and xp informs me that tunerpro has encountered an error and needs to close.

Here is a link to my xdf and bin:
http://www.provoscooter.com/images/evo/413.xdf
http://www.provoscooter.com/images/evo/413.bin

I'm sure its something i screwed up. I copied the xdf from a forum into a text file then saved it as an xdf.

Thanks in advance.
Erich

[dfddfd2]

The BinSize in the xdf is set to 0xFFFF, but the bin is only 0x8000. Try that change.

Cheers,
Dave

[Mangus]

What Dave said, although it shouldn't crash. I'll make sure that's fixed for the next major release.

[Six_Shooter]

I had something similar happen. I'll have to find the file again, but I know I started with a known good file (one that opens fine in TP RT), made a change to a table, saved it, and the would crash everytime I tried to open it.

If I find that file again, I send it your way Mark to see if there is something that causes this.

[eficker]

Tried changing the bin size to 0x8000 and no change. still get the error. I will try installing tp on my desktop and see if i can open it there in case there is something else interfering, but i am still getting the same error.

Thanks for the quick replies!

Btw, dave, your car is pretty nutty! Very clean install too.

[dex]

In addition to what Dave said, you also need to alter the xdf header to have the 'Base Offset' subtracting 0x8000 as your parameter addresses are in the 0xE974 to 0xF02F range.

Also, either those addresses are wrong or the bin is corrupt as that area of the bin is full of null data.

[eficker]

The addresses could be wrong. I doubt the rom is corrupt, read it in myself from the factory chip. It matched the rom chip when i read it in.

Even if the addresses were wrong, it should just open with bad data, right?

Even with the base offset set properly, it still gives the error and closes.

[Mangus]

It should not crash - that's the bug. However, you do need to change the base offset for Bosch/Motronic if you're using the "raw" addressing.

[dex]

With the bin size and base offset correct I am not getting any problem. I have tried it on 98Se and XP Home machines. Which version of TunerPro are you using (I used v4.14.0381.00)?

[eficker]

Hmmm. I'm using

4.14.0381.00

I'll have to test it on my desktop, still haven't had a chance.

Does it open with good data, or is it bunk?

The top of my xdf now looks like this:

%%HEADER%%
001000 FileVers =""
001005 DefTitle ="Stock 413 Definitions"
001007 DescSize =0x0
001006 Desc =""
001010 Author ="me"
001030 BinSize =0x8000
001035 BaseOffset =0x8000
001200 ADSAssoc =""
001225 ADSCheck =0x0
001300 GenFlags =0x0
001325 ModeFlags =0x0
%%END%%

Is that correct?

[dex]

Are you editing the xdf by hand? I ask because this is what you should be seeing for the base offset;

001035 BaseOffset =-32768

It is better to edit the xdf through TunerPro rather than using a text editor to avoid these kind of problems.

The table addresses indicate areas of the bin that just contain 0xFF.

[eficker]

Well, let's see, moron is here (pointing to my own forehead).

Yeah, thats probably why it states in yelling all caps, DO NOT EDIT BY HAND!! lol.

Okay, well now i am seeing what you are seeing. I think its just a matter of finding the right offset to see the maps. Or maybe changing the addresses, i'm not sure. I know that the maps move around from different versions of the dme.

Thanks for all your help!

[dex]

I am always grateful when I find it's a simple thing to fix

There is what looks like data at 0x5000 to 0x67D0.