ECUflash First Flashed DSM ECU! (98/99 Flashing FAQ)

PieEyedPiper · Apr 10, 2012

CurtC said:
This is what I have done in order to get Evoscan to run on Windows 7. Another thing to try is to create a folder on your C drive called Evoscan and try installing the software to that directory, rater than the Program File(s) directories.

Does anyone know the setting in ECU flash that switches the boost gauge back to stock, rather than knocksum?

My curiosity has been piqued.

Why?

CurtC · Apr 10, 2012

PieEyedPiper said:
My curiosity has been piqued.

Why?

Why about the separate folder or gauge :confused:

colbyc · Apr 10, 2012

CurtC said:
Why about the separate folder or gauge

Pretty sure he means the gauge. Copy your stock rom then go look for the codes to the gauge, if you can't I'll do it when I get home.

ed1380 · Apr 10, 2012

The stock gauge will be in the ceddy settings or the periphery bits

CurtC · Apr 10, 2012

colbyc said:
Pretty sure he means the gauge. Copy your stock rom then go look for the codes to the gauge, if you can't I'll do it when I get home.

Ok, I'll try taking a look when I get home as well but last I checked the definition that I had set in my folder for ECU flash wouldn't open the stock rom that I pulled from my ECU. If you feel like taking a look, I'd appreciate it.

As for why, I'd just like to switch mine back now that I'm done tuning and eliminated knock. I'm usually logging with my tactrix plug and theres the CEL on knock sum setting as well.

rkcstr · Apr 10, 2012

I have EvoScan/ECUflash running without issue on Win7 Professional 64-bit. Just make sure you don't install the programs in the Program Files folder, just install in its own folder on your hard drive. Also, make sure you're not doing something unusual like having your user folder or Documents folder encrypted or something, as that's where log files go. Try running the program as an administrator (right-click the file and select Properties, under compatibility tab and there's a checkbox) and see if that changes anything. You shouldn't have to do that, though.

Hakmak · Apr 10, 2012

I did it off a fresh install...I acquired the laptop for the sole purpose of tuning my vehicle....I Performed all of the above except one thing....my install was a 32 bit... so I believe you're onto something rkcstr....If I were you nuclearr, I would try with a 64 bit install b4 going to xp...

Actually,my bad, I didn't even ask what ver of 7 you where on 32 or 64bit?....

nuclearr · Apr 11, 2012

Hakmak said:
I did it off a fresh install...I acquired the laptop for the sole purpose of tuning my vehicle....I Performed all of the above except one thing....my install was a 32 bit... so I believe you're onto something rkcstr....If I were you nuclearr, I would try with a 64 bit install b4 going to xp...

Actually,my bad, I didn't even ask what ver of 7 you where on 32 or 64bit?....

I am on a 64 bit version of w7 home

as far as comatibilty mode tried it thats a no go also installed onto the c drive under evoscan thats a no go adjusted the file preferences thats a no go. W7 pro has special support to run xp programs put out by Microsoft.

HadesOmega · Apr 13, 2012

For the record I installed it on a W7 64bit computer as a 32bit program. I doubt they have a 64 bit version it doesn't really need to be. There are 2 program file directories one for 32 bit programs and 64 bit programs and it is installed in the 32 bit one.

The version of ECUflash I installed on this computer is 1.43.3172

nuclearr · Apr 14, 2012

well I went out and bought an old xp computer from a friend. I can now log but for some reason evoscan will not check my dtc's. I am running 2.8

Ok I have been playing with my car finnaly trying to get the injectors dialed in properly. All my fuel grins stay at 0% when at idle and while driving and crusing. Also I am in sure of the proper way to adjust latency. I know the injectors I have have a .315-.330 ms. But what do I do with that number. Ceddys says to adjust the ms at the idle voltage for me that is 13.5 Closest one on the chart is 14.5 or so.

colbyc · Apr 15, 2012

You need to add the .330 to every value in the latency table.

Zack Huffman · Apr 16, 2012

Before you do ^ that, check to see if you're in closed loop learn mode in your logs.

All must be true: said:
Coolant temp >= 180F
Intake air temp < 133F
Baro >= 22.9 inHg
Baro <= 31.6 inHg

Also keep in mind too high TPS values seen by the ECU or a front O2 sensor not oscillating around 0.5V for more than 128 seconds will cause you to enter open loop.
If you're in closed loop, the fuel trims are all close to zero and the front O2 sensor's voltage is oscillating between 0.2-0.8 volts, then your deadtime is already pretty close. You want to reach LTFT of +-2% and STFT bouncing back and forth between positive and negative values. Increasing deadtime adds fuel and causes fuel trims to trend less positive.

For what it's worth, I have had numerous issues with both 2.7 and 2.8 on my old tuning laptop. Granted, part of it is probably just me not taking time to figure out the issue, but 2.6 already does everything I need it to so I've just stuck with it.

Hakmak · Apr 16, 2012

nuclearr said:
well I went out and bought an old xp computer from a friend. I can now log but for some reason evoscan will not check my dtc's. I am running 2.8

Ok I have been playing with my car finnaly trying to get the injectors dialed in properly. All my fuel grins stay at 0% when at idle and while driving and crusing. Also I am in sure of the proper way to adjust latency. I know the injectors I have have a .315-.330 ms. But what do I do with that number. Ceddys says to adjust the ms at the idle voltage for me that is 13.5 Closest one on the chart is 14.5 or so.

Shout out to dboyle23...he helped me out ALOT with this post...

http://www.dsmtuners.com/forums/articles-tuning-ecu/407715-how-get-basic-tune-ecuflash.html

nuclearr · Apr 16, 2012

colbyc said:
You need to add the .330 to every value in the latency table.

Thats what I thought I just cant get it to add .330 I will have to play with it some more.

delta448 said:
Before you do ^ that, check to see if you're in closed loop learn mode in your logs.

Also keep in mind too high TPS values seen by the ECU or a front O2 sensor not oscillating around 0.5V for more than 128 seconds will cause you to enter open loop.
If you're in closed loop, the fuel trims are all close to zero and the front O2 sensor's voltage is oscillating between 0.2-0.8 volts, then your deadtime is already pretty close. You want to reach LTFT of +-2% and STFT bouncing back and forth between positive and negative values. Increasing deadtime adds fuel and causes fuel trims to trend less positive.

For what it's worth, I have had numerous issues with both 2.7 and 2.8 on my old tuning laptop. Granted, part of it is probably just me not taking time to figure out the issue, but 2.6 already does everything I need it to so I've just stuck with it.

I see I might be in open loop. The issue is I am simulating front o2 so I also know the voltage does not oscillate. I checked the values posted and all are good except for bario mine is logged to kPa not hg its flat lined at 100 kpa

Hakmak · Apr 17, 2012

nuclearr said:
Thats what I thought I just cant get it to add .330 I will have to play with it some more.

To add .330 to all the latency values, select the "intjector batt vol latency comp" grid->(click on the first value then drag down to select all) or Click Edit->choose "select all"->Click edit again->select "add to data"->input .330->hit enter key and you're done. Hope this helps you.

nuclearr · Apr 17, 2012

Hakmak said:
To add .330 to all the latency values, select the "intjector batt vol latency comp" grid->(click on the first value then drag down to select all) or Click Edit->choose "select all"->Click edit again->select "add to data"->input .330->hit enter key and you're done. Hope this helps you.

Thanks I had a brain fart. I figured it out before I saw your post LOL

On another note my o2 is working fine voltage is good. But I still have 0 LTLF but my STFT is bouncing between +&-

I after some research my inHG is correct is there a way I can change evoscan to logg inHG instead of kPa?

As far as I can tell I am in closed loop

Zack Huffman · Apr 17, 2012

nuclearr said:
I after some research my inHG is correct is there a way I can change evoscan to logg inHG instead of kPa?

To convert from kPa to inHg, you multiply by 0.2953.

Go to the "Logging" drop down menu and select "Edit Data Item List" in EvoScan. Select the sensor you want to read inHg with, and change the "Eval:" field so that the formula already there is multiplied by 0.2953. You may also want to change the gauge max and chart max values.

re-rx7 · Apr 18, 2012

Got cable, ecu flash, i can retrieve the stock code(binary) but i cant see the maps? I have not dl ceddy yet. Is this wats causing the problem? After downloading it where do i put it?

colbyc · Apr 18, 2012

re-rx7 said:
Got cable, ecu flash, i can retrieve the stock code(binary) but i cant see the maps? I have not dl ceddy yet. Is this wats causing the problem? After downloading it where do i put it?

You have to have ceddy mods to edit. Save it as stock rom then flash with the ceddy mods.

Zack Huffman · Apr 18, 2012

You have to have ceddy mods to edit.

You can edit anything that you have properly defined. You don't need a modified ROM if all you want is to edit the fuel and timing maps. All you need is the definition file for the ROM you want to work with.

If you want big maps, SD, launch control or any other custom coded features, that's when you'd need to have a modified ROM and definition file.

re-rx7, AFAIK there isn't a publicly available definition for the 2363 ROM, which should be the ROM version your ECU originally had. If for some reason your stock ROM is 2055, 2056 or 2364, then you can download those definitions from ceddy site.

colbyc · Apr 18, 2012

delta448 said:
You can edit anything that you have properly defined. You don't need a modified ROM if all you want is to edit the fuel and timing maps. All you need is the definition file for the ROM you want to work with.

If you want big maps, SD, launch control or any other custom coded features, that's when you'd need to have a modified ROM and definition file.

re-rx7, AFAIK there isn't a publicly available definition for the 2363 ROM, which should be the ROM version your ECU originally had. If for some reason your stock ROM is 2055, 2056 or 2364, then you can download those definitions from ceddy site.

I'm sorry I worded that quite wrong. Its more logical in sense to have the modified rom.

re-rx7 · Apr 18, 2012

i have downloaded ceddy mods. I just dont know how to put it in Ecu flash to let me read maps. My car has a tune on it from a shop. I do not want to lose it.

PieEyedPiper · Apr 19, 2012

re-rx7 said:
i have downloaded ceddy mods. I just dont know how to put it in Ecu flash to let me read maps. My car has a tune on it from a shop. I do not want to lose it.

Then fire up ECUFlash and save your current rom.

white92talontsi · Apr 22, 2012

I have a silly question, I have been battling trying to get my new engine to run right.

I was looking through my settings tonight and happened to notice that I had the Base timing feature enabled and set to 5*.

I remember seeing a post Ceddy posted a while back saying that it was OK to leave it enabled but to me it seems like it would try to lock the car at 5* all the time.

Could this be causing any issues?

ed1380 · Apr 22, 2012

The base timing setting in ceddymods is what timing you want the engine to run while the base timing mode is activated in evoscan.

The Top DSM Community on the Web

ECUflash First Flashed DSM ECU! (98/99 Flashing FAQ)

PieEyedPiper

CurtC

colbyc

ed1380

CurtC

rkcstr

Hakmak

nuclearr

HadesOmega

nuclearr

colbyc

Zack Huffman

Hakmak

nuclearr

Hakmak

Attachments

nuclearr

Zack Huffman

re-rx7

colbyc

Zack Huffman

colbyc

re-rx7

PieEyedPiper

white92talontsi

ed1380

Similar threads

Latest posts

Build Thread Updates

Vendor Updates

Latest Classifieds