That 304 / 293 figure you gave - it's power at the crank right?
I think my tune is similar to the one you did and I get 293 ft-lb crank.

 

----

 

----

 

Interesting thread. I used to be able to make great power on the XEDE, I just couldn't get any driveability out of it on my current setup. These days I'm pretty much getting the same power _and_ I've got 90% of my driveability back with ECUflash.

So far the only thing I haven't been able to eliminate with ECUflash is my phantom knock - something that I could do to some degree with the XEDE. Hopefully Bez, or someone that can understand what he did, can implement some of the knock routine findings in a way that bloke like me can understand...

l8r)

 

----

 

Strange that you would say 16* at 7k rpm is pushing it. Most people aim for 20* on 93 and more on 100+.

NJ, I am going to be hitting you up soon. I need help translating the XEDE values over to the ECU values....same approach you took.

Does anyone have a non-vendor generic map for a cammed stock turbo EVO? I'm looking for a starting point that I can tweak from AND compare it to my stock map.

 

I'm in the same boat Jeff..

I can log with logworks and open port 1.3 but not with the xede addin. the adding starts logging but somehow logworks does not pick up the xede. For this I'm using a serial port(com1) and 2 usb. I may need 3 usb ports?

I can log with evoscan but it will recognise the LC-1. I've used 2 usb and combination 1 serial 1 usb. hmmm it may be the white connector?

 

I use ecu flash in my evo. I am still trying to get ride of a brand new UTEC because i went with ecu flash instead. It is a way better program in my opinion.

 

You will need THREE usb ports or a combination serial/usb ports. Basically three cables need to run into your lap top:

1. From ECU port to the laptop for tactrix cable
2. From LM-1/LC-1/XD-16 to laptop
3. From xede to laptop.

 

-----

 

I run them as listed, xede plug in connects to xede, but logworks does not collect the data, all I get is blanks

I can connect to xede with xmap...

 

Jorge why not just use ecuflash without xede? By the way I met you before at a carwash about 2 yrs ago on richmond.

 

What do I need to do to get my LW pwr/tq working like yours?
I entered all the correct stuff in the formula,
and since I have no g - meter used:

1. # acceleration i g

a = slope(RPM) *pi*td4.3153245*10^-5/(gear_ratio*finaldrive)

2. # speed in ft/sec

v = (RPM *R * piu) / (gear_ratio*finaldrive)



and all the other stuff but can't work it.

Can you screeshot what your using for "Enter formulas here" or whatever I need to use besides the stuff I already have e.g. gear ratio's, weight, temp, and tire size.

Thanks dude

 

I want to use ECU flash to tune AFR, but would like to see if I can keep the XEDE to control boost and timing, and have maps for 93 and 104.
We need to meet up again!

Was it at the carwash on Richmond and Tanglewilde(Gessner)?

 

That is the one, I no longer live over there though. I would think ecuflash would be your better option for timing, but I remember you mentioned you had some tunes in xede and I guess you may not want to lose them. Do you have evoscan or mitsulogger to datalog. I am sure you can make those maps in ecuflash and have more direct control of timing, since xede is a piggyback.