Best upgrade path to 1.1.x

[mattias]

You can use the minimum MAP value to turn off EGO below 30-40 kPa as that is usually the region where you have released the throttle and doing engine breaking.
Given that you run Alpha-N many might not consider that you can still use the MAP sensor for this, many functions still rely on it.

[Benzmac16v]

I am not running alpha-n.

At any rate, adjusting my timing helped most of my hesitation, particularly coming off idle.  However, I still have a fuel cut at 20%... My pw goes directly to zero when I cross it going down the rpm... It's sort of hard to explain, so I'll take a video of it.  I changed my overrun settings as well.  Anything else that would cut fuel?

Jim

[mattias]

I am not running alpha-n.

Huh. Must've mis-read that somewhere.

A lot better than anything else is posting an actual log file.
Zip it  and upload it somewhere, vems.hu has a file upload facility.
http://www.vems.hu/wiki/index.php?page=FileArea

[Benzmac16v]

Here it is.

http://www.rpi.edu/~smithj16/VEMS/v3.3_n001612-2010.06.22-13.11.48.vemslog

The problem is apparent between 4:03 and 4:24

Thanks,
Jim

[Benzmac16v]

My car is a plenum based N/A 4 banger.  It is a 1985 190E 2.3-16v, and outside of the ECU VEMS and needed components for VEMS it is basically stock.

Also, another kind of unrelated question.  I noticed in VEMS tune a wheel speed sensor available, can I just tap into an ABS sensor for this?

Jim

[mattias]

If you got a paper with your ECU with pin designations for the EC18 connector that said "wheelspeed input" on pin 8, then you can connect a sensor there. I'm not sure on the specifics, but it works the best with Hall type sensors.

Your trigger settings are strange, you're running WAY too much timing for a N/A 16v  high c/r engine, and your lambda table doesn't make much sense.
You need to disable input channels that you don't use.
Trigger edge on a VR/inductive sensor is always rising, unless you know what you're doing.

I fixed most of that and you can use this configuration file:
http://media.vems.se/mattias/benz-v3.3_n001612-2010.06.24-12.38.57.vemscfg

When using my config, disable the injectors and strobe the ignition again to make sure you are synched correctly.

At least take a look at  the config..

[Benzmac16v]

I was playing with it yesterday and noticed the ignition map being waay off.  That was the map that came with the ECU and because I didn't have the tools to play with ignition timing (det cans, knock sensor...) I figured it was a conservative table.  Going back to it now (I have learned quite a bit since getting VEMS which was more or less the idea behind it) it is quite obviously very advanced.  I dropped it quite a bit yesterday and general drivability went waaay up.

As far as the lambda map, that was also stock with the ECU.

My hall sensor is a sink to ground sensor, http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail?name=365-1002-ND so I figured it should be on falling edge not rising.

Ill give your set up a try today.

Thanks,
Jim

[mattias]

Do note : Disable the input functions that you don't use.
You had input channels for ALS and something else active!

[Benzmac16v]

Car is running pretty damn good now.  I took your tables and redid them for N/A as your map values went well above atmospheric.  Made all the changes you did as well, using 4 ignition 'outputs' but only cycling between two... what is the point of that? And I turned off the two inputs I had on, which I have no idea how they got turned on.

At any rate, it runs great now, no hesitations or lag or nasty jerkiness, and the 20% TPS fuel turn off thing seems to have gone away too, not really sure what that was all about.  It is lacking a little bit of power in the high end, but the VE table probably just needs to be tuned again.

Thanks a lot for all the help guys!  I know I am a noob at this and some of my questions are... noob questions, so I really appreciate the help while I am learning!

Jim

[rob@vems.co.uk]

This forum is *for* noob questions.

[mattias]

The config I posted contains MAP values higher than atmospheric even though I've used them only on N/A engines, there is simply enough resolution already as it is. People often mistake high resolution for accuracy and good driveability - it's a lot more complex than that, VE modelling and interpolation works great.

The point of using 4 positions in the ignition output table is to define all the events in the 4-stroke cycle, that is a must with the 1.1.x firmware. You are simply repeating the same pattern on every revolution of the engine, since you're using "wasted spark".

The fuel cut and stuff you experience before was related the configure inputs that you never used. Where those settings came from (= enabled) I can't say.