Has anyone seen lambda readings in a log file, but no ego correction happening?

[Tony C]

right, coming up with this now Rob,
WARNING: giac_ign_slope in config.txt not found in global.h
WARNING: did not find a value for iac_ign_slope in config.txt
config.mtt generated with 0 errors and 2 warnings,


BUT if i go back to using the config with the ego_conf set at 06 again its fine, any clues?

[Tony C]

found it looking at what i just posted was a type error,
i must of put the letter g in front by accident,
now the modded config with the ego_conf value changed to 07 has generated fine will upload to ecu tomorrow,
phew, im getting there slowly,

[Tony C]

Rob, David,
right uploaded the new config to the ecu, went to start ran like a bag of spanners, (you will see on datalog)
uploaded the .msq again and ran good again,
downloaded config to make sure the values were the same still and they were,
did a datalog and it looks like its still not working on the fuel correction side of things, and ego_conf is now at 07,
http://www.v-8.org.uk/zipfiles/log14_03_08.zip
towards the end of the log is where i started giving it death if you want to check the WOT fueling,
also there is a log when on nitrous i did also today for you,
did a practise 1/4 mile run,

[rob@vems.co.uk]

That makes no sense...
Especially as uploading the msq and downloading the config showed no difference between the one you generated and uploaded.

But I dont doubt what you're saying, just can't figure out why

[Tony C]

Rob my ego settings,
settings>ego settings

lean limit is 19%
rich limit 5%
step size 1%
speed limit(or PID kp) 64
engine cycles before changing correction 1

they correct?

[dnb]

They're good settings.

[Tony C]

Cheers Dave,

Rob,
i know your a busy person,
BUT is there any progress with help from the wiki regarding this ego fault???
as i want to get this sorted as its not worked from day one by the looks of it,
once its sorted i can then move onto sorting out going wasted spark, but want to complete one thing (ego) before starting to do the ignition
cheers mate,

[rob@vems.co.uk]

The general consensus from the team is that there are bigger problems with all those trigger errors that need to be cured before the EGO correction is worried about.

[Tony C]

did they give any clues to help me what could be causing them high triggers?

and did they have any ideas what is causing the ego fault too?

[mattias]

Disable all acceleration enrichment, then give the EGO correction a try.

[Tony C]

anyone localish to me that would like to try my ecu to see if they get these ferkin spikes and ego problem on there car?

[Tony C]

in settings>primary trigger settings,
there is an advanced filter, you recon it may help these spikes if it was turned on?
just a thought?

[rob@vems.co.uk]

Those trigger filters are designed to cope with strange happenings with VR triggers Hall is too clean a signal for them to have much effect.  Those spikes tend to come from a loose connection in power, ground or some other area injecting noise into the ECU.

[Tony C]

its defo not a ground mate as you checked the loom 
and it is fixed to the passengers head via a ring terminal on the o/e ecu earth point,
i will check the relays, fuse box and fusebox terminals this week to see if that is all ok, failing that im as lost as every one else. 

one thing that is confusing, on the log the spikes is not on going is it, there is a blip where there are 2 large blips possibly a couple small ones then its fine,
i have noticed though, the spikes are bigger if the laptop is plugged into the cars battery as power,

[rob@vems.co.uk]

I checked continuity of the earths on the loom, but that's only half the story as is written in the User Guide there are plenty of oppotunities for noise to get inejcted into any number of places.

The thing with EGO correction is that its a software feature, the lambda values that the system are reading are sensible, so the VEMS should be correcting.  For some reason its not.  EGO correction does not work when the engine is in a transient state, so thats why mattias suggested turning off the acceleration enrichment to see if the software starts compensating.

If you set your Acceleration Bins in Settings->Acceleration Enrichments
to 255 (make a note of their original values so that you can reset them after the test).
You will not be able to achive TPS speeds of 255 so the VEMS will never enter into an acceleration state - which means that EGO stays on.

BTW mattias is one of the development team.