So who wants their ECU's "Chromed"?

[Chris@Rvengeperformance]

Berry true, Brett is awesome.

Quick question, will the write up explain injector, and maf setup in detail? Orrrr, should I get to researching like a mad man?

all of that info is in this thread. The injector setup is simple:

Put in approximate latencies and injector size. Car *should* be drive able if you put half way sane numbers in. Drive it around town for 10-15 minutes. Check the fuel trims.

The latencies have about twice the effect on the low trim as the med trim because the injector pulse width is so low at idle. So, for example.

Low Trim -10%
Med Trim - 5%

Then you need to REMOVE some injector latency so the ecu will open the injectors for a shorter period of time. Log it again until low and med are close to the same. For example:

Low Trim -5%
Med Trim - 4%

Now ADD 5% to your injector size to REMOVE 5% fuel.

That's pretty much it. Once the trims are good do some wastegate pulls and see if it goes lean. If the afr is safe you can then start tweaking the fuel map if you want.

[Greg E]

I'm in contact with him but this is the first I'm hearing about this particular issue, I'll bring it up to him. If you were to make an educated guess, would this be the primary problem, or do you believe the front and rear o2's are still crossed as well?

I could tell you if the harness is correct just by looking at it... Rather not make guesses.

I am 100% confident the cause of the starting issue is the ignition coil driver.

[Jesters Deadd]

@ Vishnu
You can check the o2 outputs in evoscan 2.9.
Can you describe your starting issue in more detail?
What inj settings do you have?
What inj do you have?
What rom are you running?
What maf?
Your car is a 95?

[Vishnu]

@ Vishnu
You can check the o2 outputs in evoscan 2.9.
Can you describe your starting issue in more detail?
What inj settings do you have?
What inj do you have?
What rom are you running?
What maf?
Your car is a 95?

I'll check the o2 outputs tomorrow in evoscan 2.9,

Here's a video showing what my starting issue sounds like to me. I'm using my remote starter, but imagine me holding the key in the choke position for as long as I want, occationally it may crank up, but usually it just sounds like this the entire time. It's been tested that the stock 95 fed spec ecu makes the car fire up with no problems at all.

Vr4 choking - YouTube

Injector settings are stock.

Injectors are stock.

Maf is stock

Car is 95 Fed spec. Basically the car is 95% stock. I have an intake and exhaust and EBC which is set to 12psi. everything else is stock.

[mjannusch]

Vishnu, I'd probably try to verify the pinouts for the coil triggers on your conversion harness. Sounds like it may be trying to fire on the wrong cycle or wrong time or something along those lines.

[Jesters Deadd]

I'll check the o2 outputs tomorrow in evoscan 2.9,

Here's a video showing what my starting issue sounds like to me. I'm using my remote starter, but imagine me holding the key in the choke position for as long as I want, occationally it may crank up, but usually it just sounds like this the entire time. It's been tested that the stock 95 fed spec ecu makes the car fire up with no problems at all.

Vr4 choking - YouTube

Injector settings are stock.

Injectors are stock.

Maf is stock

Car is 95 Fed spec. Basically the car is 95% stock. I have an intake and exhaust and EBC which is set to 12psi. everything else is stock.

If after your car cranks and finally starts then runs fine, then I agree with Greg. Don't worry about checking anything I asked.

[Vishnu]

If after your car cranks and finally starts then runs fine, then I agree with Greg. Don't worry about checking anything I asked.

It runs fine after starting, with the exception of the WBo2 showing that it's running rich under cruise and idle conditions. Physically the car feels fine under any kind of (stock level) boost I throw at it. On inspecting what the shop did when they installed my wbo2 gauge, I saw that they plugged the sensor into the rear secondary slot instead of further down where it's supposed to be. Once that's corrected, I should be able to get a better reading as to what's going on down there.

[Toni]

So after a couple days of testing I feel comfortable releasing my Evoscan to Logworks log file converter.

evoscan2logworks - Convert Evoscan logs to Logworks logs - Google Project Hosting

Check it out and see what you think. It is beta so it's currently not tolerate of many things but a standard 2.6 evoscan logfile will work fine and the output will work in Logworks. I'm obviously not a vb(yuck) developer but it was quick, works, and needs nothing extra to be installed (I think).

Let me know if you have any troubles!

Uploaded a minor fix today after using the tool over the weekend. I adjusted the lower scaling so graphs that don't go to 0 won't hang on the bottom of the chart making it appear as if it goes to zero.

[Kx1984]

Not sure if I missed it but any word on the evoscan 2.9 file

2.6 will not work for me :/

[vr4whore]

Hey guys,

If I gut the stock maf, what would be the limit on it? I'm aiming for 450-500 awhp on a conservative dyno, I know the evo maf is a much better option.

Thanks