V1.1.74 Firmware

[lugnuts]

Ran the race car today on 1.1.74FW. The car ran and drove well during slow driving.
But it ran very pooorly under high load.

No time to diagnose so I switched back to the 1.0.78 ecu for the night, and it ran great.


When I was able to look into the details, I found that the Target Lambda is going very very rich and taking the Lambda with it.

Below is a log, you must change the ".rtf" to ".vemslog" (I changed it to get it to upload to vems filearea)

http://www.vems.hu/files/KevinBlack/Copy%20of%20v3.3_n002889-002-SDCard-2010.04.30-20.18.07.rtf


Look at 2:14.00 timestamp, the Target Lambda is .66, in the configuration it is set to .78 to .80.

I'm not sure if that is all that is wrong, hopefully so. The car sounded awlful coming out of the burnout, bogged bad in first gear, and would only rev to 6400 rpm in second gear.

One note is - the Launch Control input is set to "6 inverted". The regular Launch Control worked fine (7,200 rpm)  I was planning on using the Rev/Speed Table but I set the rpm values to 8500 to try to see if it fixed the problem.

Any insight would be appreciated.

[gunni]

I see alot of what seem to be missifires when the lambda goes to 0 around that area.

I can also see that your EGT goes to 1199 and in your config you have

10.1% added fuel for every 100C° above 1000C° so at 1199 you have 20% added.
which at that point turns 0.79 lambda into 0.658 lambda

[lugnuts]

You're right. In my haste I glanced over the safety settings, I knew the boost reductions were set to "disabled" but the fuel addition is not disabled. The EGT sensor is bad so that egt was incorrect anyway.
That's what you get for doing things in a big hurry .

The engine did misfire badly. I'm not sure if it was only the fuel that is causing it.

The Lambda going to "0" is something I haven't seen before. It definitely appears to go to "0" instead of a high number, because you can see it at 2:15.400 when the decel fuel cut is active.

 

[Sprocket]

*als_iacpos;// iac position when ALS active (0 disables)

Cool

[messer]

The Lambda going to "0" is something I haven't seen before. It definitely appears to go to "0" instead of a high number, because you can see it at 2:15.400 when the decel fuel cut is active.

From Wiki:
Note: 1.1.53 uses a different lambda (runtime vars, offset=10) value above 1,0, (eg. not compliant with 20.9 reading at 20.9% O2). Higher resolution around 1.0 though. Likely we're forking 1.1.53 and 1.1.54 vemstune.ini and vemsv3.ini to make it work with both.

That mumbojumbo = high and low values shows up as zero, but you have better resolution 0.7 -1.2, I dont need or like that, but someone do.

[mattias]

That mumbojumbo = high and low values shows up as zero, but you have better resolution 0.7 -1.2, I dont need or like that, but someone do.

I fully agree with you here, the resolution is ok but there should be more to it. I used to tune intuitively faster based on where the "needle on the gauge" went, if it was locked to lean or rich. Now it just falls to zero and makes  it harder to guess what has happened. You can't spot a rich mis-fire as easily, or tune acceleration enrichment the same way.

[lugnuts]

Back on the 1.1.74 as of last night. Did a few pulls on the street, the car is running well again with the added fueling disabled. Forgot to say "thanks" to you gunni.

[[email protected]]

One gripe that tuners have mentioned to me is that disabled features are not always disabled.  It would be nice if idle, boost and other features could be switched off to allow tuning to take place without some other seemingly random feature interfering with the tuning process.

[mattias]

Rob: I think your "feature fear" comes from the old firmware with ALS interfering easily.  Really, the only thing you might want to disable while VE mapping by hand is the EGO correction, unless you can't cope with it on and watching the % correction gauge.

It's also a question of the order of tuning the features, never complicate a situation by enabling things that are not fully tuned/tested. Make a working VE map without the majority of the creature comfort features turned on. Then enable one by one as you go.

[lugnuts]

I am happy with the firmware, I just screwed up and missed the value in the egt fuel setting.

There is a bug in the wheel speed/rev limit set-up, with the "disable" box. I have documented this and sent it to the webshop.

Ran the car again yesterday, the fueling is correct and the car ran very well to a certain point. But a mechanical problem prevented us from making full passes.

[GintsK]

 
I had some problems with stepper when migrating from 1.1.53 and 1.1.63 to 1.1.70. It simply did not works for some reason.
Any ideas wat could be the problem. Both subaru 6wire steppers.

Gints

[lezsi]

Hi!

I've tried to upgrade my 1.1.56 to 1.1.70, have reviewed all the forms in vemstune after upgrading, still somehow the engine is apparently very-very lean (stuttering, stalling and so) -with same injection/VE values.

I had nice idle with lambda ~0.95 using 1.1.56, but cannot get it to stay running (idle) above lambda ~0.80 with 1.1.70

I've got configs and logs here : http://quasar.dynaweb.hu/~lezsi/vems/vems-1170-upg.zip

More details at http://www.vems.hu/wiki/index.php?page=MembersPage/GergelyLezsak/FirmWare

Any ideas appreciated! 

[gunni]

Look at the Gair compensation in .56
it´s not there in .70

It´s 10% during load.
That however doesn´t really explain fuel mixture at any other point.

[NOTORIOUS VR]

LCD? How do you even read that jumbled mess?

hehe... I honestly don't even use it, but the "gearheads" that I've installed VEMS into love the LCD since it give a lot of info at a quick glance... at least it did with 1.0.x FW when there was no lag.

That said, I don't push the LCD anymore, mainly because it's finicky connection wise and due to the lag now.

It's nice to see the round only gauge coming down in price, I will probably get them to upgrade to that if they really want to keep an eye on things.

[mattias]

That said, I don't push the LCD anymore, mainly because it's finicky connection wise and due to the lag now.

This has had no effect for you? (from release notes 1.1.74 http://www.vems.hu/wiki/index.php?page=GenBoard%2FUnderDevelopment%2FFirmwareChanges )

• LCD updates are synchronized to LCD refresh (when lambda changes from 1.00 to 0.99, 1.99 should not be intermittently displayed).
  Disable "forced goto" in LCD menu for higher refresh rate