General 1G E931 XDF file for Tunerpro?

[notsofastdsm55]

does anybody know where I can get xdf files for the e931 ecu code????? image and bin would be greatly appreciated.

 

[Jeff_Ciesielski]

try the dsm-ecu yahoo group

 

[i1nk83]

you can also contact steve on here, he burns chips for guys and might have what you need

 

[notsofastdsm55]

thanks guys, also is steve his member name???

 

[steve]

The base E931 ecu file for tunerpro is in the Files > *** Official Releases *** > 1G > Standard E931 folder on the yahoo dsm-ecu group. You have to join the group to download from the files.

I don't use tunerpro so I can't help you.

Steve

 

[i1nk83]

steve^^ ftw yet again

 

[notsofastdsm55]

thanks steve, by the way tunerpro is nice, and you can still use hex if you want, it just makes changing the fuel maps really easy as well as gives you graphic pictures for the fuel and timing curves. also changing deadtime as well as injector comp, idle, airflow correction for mafs, basicly everything you can do with hex just in a nice easy windows type package.

However I was looking at a extended fuel and timing tables map and the map looks horrible with a peak afr of 9.03 to 1!!!! it looks like the maps were just doubled and the fuel curve just keeps going richer!!! and by looking at it looks like you'll lose some drivability. what do you think about it. also the timing table on the extended maps goes really low in the top rom peaking at 13 degrees which is bad for cast parts(then again if you in that high part of the load table you might already...should be using forged internals!!!)

ummm.....basicly what do you think of the extended timing and fuel maps code. (it looks like it needs alot of adjusting but that might be just the source that I got it from)

 

[Zenja]

No, the extended maps keep basically the stock AFR and timing advance. You have to realize that the highest load level row in the stock maps is only halfway up the table in the extended maps. If you look at that, you'll see that the stock air fuel ratio and timing advance is pretty much the same in the extended maps.

Once you do get past where the highest load point on the stock maps is, then the extended maps just extends the trend of less timing advance and richer AFR as load increases. You have to realize that you'll have to be running like 35psi to hit the top map in the extended maps. It is up to you to adjust the maps to your liking though.

The timing advance on the stock maps seems ok, but the AFR is quite rich at the highest load point on the stock maps. Just like you'd want to change that in the stock maps, you could do so in the extended maps, and change the points on the upper levels too. The extended maps are actually better for driveability in theory as they're smoother than the stock maps, but they try to still keep the levels about the same. I was a bit hesitant about using the extended maps, but after I switched to them, I noticed no ill effects and everything is working great.

 

[notsofastdsm55]

wow thanks for the info, and yeah after doing a little math you are right about needing to be at high boost to reach that load level. I gues I'll start editing the the extended map.

Zenja, do you use tunerpro? or just edit using hex??? cause the definition file that I have for the fuel map just goes from low,1,2,3 to high(in the load axis) without giving any indication where vacuum stops and boost begins..I mean I kind of have an idea where it is but looking at where the afr start to get rich but it would be nice the know exactly which row 100kpa (atmosphere pressure..right where boost would start to climb after that point) is.

 

[Zenja]

Yeah, I use tunerpro. The load maps don't correspond directly to any boost level so you can't tune for different boost levels just going by the load rows.

There is a great way to tell what load row you're hitting though. If you change a couple of bytes in the code, you can get the "air volume" (or any other one basically, but this is a good one to use) variable in the logger to log the internal load value instead. This way, when you're datalogging the car you can tell exactly what load row you're on at any point by looking at the logs. The number logged is from 0 to 255. There is also a table that will let you directly translate this number to a load row. Or, you could do what I did which is change the load row numbers from low, 1, 2, 3, etc to be just that 0-255 number. So you would change the labels for the rows to be 32, 48, 64, 80, 96, 120, 144, 168, 192, 216, 240, 264, and these numbers will directly correspond to the number logged on the datalogger.

This is the table for conversion:

Row: 		1	2	3	4	5	6	7	8	9	10	11	12
Internal (log):	32	48	64	80	96	120	144	168	192	216	240	264
stock g/rev:	0.25	0.38	0.50	0.63	0.75	0.94	1.13	1.31	1.50	1.69	1.88	2.06
ext g/rev:	0.50	0.75	1.00	1.25	1.50	1.88	2.25	2.63	3.00	3.38	3.75	4.13

You can find everything you need about this on the dsm-ecu yahoo group. I use this and it works great for tuning.

 

[notsofastdsm55]

forgive me I am kinda new with xdf files, but how would I go about changing the load row values???? do I have to open the xdf file seperately and change the values in there??? I am confused!!!


nevermind found it!!!!