General Chip Modding: XTG file for TunerPro?

[Dred]

Can anyone tell me if there's an XTG file for TunerPro for our ECU's? I've been trying to find one at DSM-ECU but had no luck thus far. I found something close (an .ecu file) but it doesn't really do anything, maybe I should rename it or smthn. But when I compare the .xtg file that came with tunerpro and the .ecu I found, they have totally different syntax. If anyone has a clue what I'm talkin about, please help

Thnx in advance.

 

[GVR4592]

I was having the same problem with tuner-pro and I couldn't get a straight answer from anybody. Do you mean .xdf? I haven't heard of .xtg Most of the guys on the dsm-ecu group are pretty tight lipped. I think the guy that write the tunerpro software is working on the problem though.

 

[Dred]

Yah I did mean the xdf and I figured out how you do it. Ge the 32k .ecu file from the Files section in there, and in TunerPro go to XDF--->Import---->Import from ECU. Select the .ec file, and then it lets you save the "Imported" file as an xdf. Make sure that you will be using a 32k bin file after so that the offset is correct tho, otherwise it will be wrong.

Also, I have a question. When I do this, some of the values are what they should be, but the tables (fuel and octance etc) seem to be all at 0 or -10.0. Only thing that is close to what it should be are the constants (Rev limit, fuel cut, etc). Anyone have the same prob or could tell me what I'm doing wrong would be appreciated.

 

[GVR4592]

Yeah I got about as far as you did, I am having the same problem with the fuel and timing tables being 0 and -10. I can't wait for dsmap to be finished.

 

[Dred]

DSM Map or xdf?
I have a finished .bin file, and it's still not reading the table properly, yet when I look through hex editor it seems to check out fine. There's a complete guide (only one I've found so far) t hat has remapped air/fuel/timing/octane maps, if you want I'll give you a link.

 

[huafist]

I was having the same problem with tuner-pro and I couldn't get a straight answer from anybody. Do you mean .xdf? I haven't heard of .xtg Most of the guys on the dsm-ecu group are pretty tight lipped. I think the guy that write the tunerpro software is working on the problem though.

The DSM-ECU group isn't tight-lipped at all. What you're asking about doesn't fall into the scope of the group, so it's ignored. The DSM-ECU group isn't there to help people with modding chips and stuff like that. The purpose of the group is to disassemble and understand 100% of the code in the DSM ECUs.

 

[Dred]

That is also my purpose. When I asked for some links I got the link the "Links" section in the group. 50% of them were dead, and pretty much the only one that was extremely useful was the DSM-ECU Hacking link. Also, huafist, you're not helpin by posting this. I can relate to what GVR is saying mainly because I find the whole message board thing a little weird, even tho it has search. If you cannot provide any helpful info on the subject, please don't post at all, that's just not helpful what you said right there.

 

[huafist]

That is also my purpose. When I asked for some links I got the link the "Links" section in the group. 50% of them were dead, and pretty much the only one that was extremely useful was the DSM-ECU Hacking link. Also, huafist, you're not helpin by posting this. I can relate to what GVR is saying mainly because I find the whole message board thing a little weird, even tho it has search. If you cannot provide any helpful info on the subject, please don't post at all, that's just not helpful what you said right there.

I'm simply correcting an erronous statement. Saying things like "they're tight-lipped," because you ddin't ask a question pertaining to the purpose of the group isn't fair.
At any rate, I'm out. There's nothing more to say on this subject.

 

[Dred]

I'm simply correcting an erronous statement. Saying things like "they're tight-lipped," because you ddin't ask a question pertaining to the purpose of the group isn't fair.
At any rate, I'm out. There's nothing more to say on this subject.

How do you even know whether or not the question was off the subject?

 

[tmizer]

jeezuz... there's a *.xdf file in the files section of the group if you just look. It's a E931 file which will work also with EA01 chips. If you need a a EA02 file I made one you can have... but I should probably upload it to the group. Other bins you'll be outta luck and you'll be on your own. E931 works with most ECU's.

I agree with the point that the Yahoo Group structure is horribly arcane and difficult to search, but you really need to spend some time and poke around. The answers are there.

EDIT: Okay, I "reread" this thread. The XDF file should work just fine if you have version 4.x of TunerProRT. Fuel and timing tables should come up fine. Load the *.xdf and then load your *.bin file. The 3D plots of both should look similar to the surface plots in Excel. If you edit the *.xdf item, are the starting addresses for the items in question matching up?

Ok, I feel like a heel. I cannot for the life of me find the *.xdf file that I swear I downloaded in the file section.

So, email me if you want the file and I'll reply back with the *.xdf file I use for E931.

 

[Freudie1]

Yeah I got about as far as you did, I am having the same problem with the fuel and timing tables being 0 and -10. I can't wait for dsmap to be finished.

Just grabbed a copy of TunerProRT and the 32K image and ecu file from the mailing list.

Do the following:

1. Use the import option under the XDF dropdown menu to select the ecu file.
2. Hit ctrl-f2 and put 8000 in the Bin Size (hex) section.

Ouila......values in the tables make sense.

Damn I'm smuuurt