I am unable to activate the Automatic VE feature on the two different versions of WinTec4 I have used (4.5.17, and now 4.5.25). When I open the "Tools" pull down menu, the "Automatic VE" option is not selectable (it appears like the picture attached below). I cannot activate Automatic VE either while the engine is running or after importing a datalog.

Does anybody have any suggestions to fix this problem? I'm quite frustrated that this feature has never worked with my TecGT. Between this problem and all of the "Autorun Error 6: Overflow" errors that have rendered countless .bin files uneditable, I'm growing very sorry I ever traded in my Tec2 for this TecGT.

Hooray. Reloaded the firmware for 4.5.25 and Automatic VE finally is available when the engine is running.

Still no love for running Auto VE from a datalog. Is this even a feature? If not, will this be available on the upcoming release of WinTec4?

But wait! It doesn't do anything *sigh* The red dot just sits in one cell and stays there, regardless of the RPM or MAP. And the EGO correction isn't working either

[Eric Cartman] I hate you guys. [/Eric Cartman]

Update (not like anybody really cares...):

So, I finally got the EGO corrections working. I had to save the .bin file under a new name and reprogram the Tec-GT; it appears the EGO correction cannot be activated/deactivated via onfly.

However, Automatic VE still does not work. The red dot still freezes on the same MAP/RPM cell as when I turned Auto VE on. EGO correction works fine throughout all of this, but WinTec4 is not logging the changes in the VE table. I have seen the thread over in the Tec-GT forum where another user had this same problem. His solution was to turn on the overlay, but this has no effect. Nothing happens.

Is my laptop the culprit? Not enough memory or processor? Comm problem? Any insight?

it might be hard to find a solution on here if youre the only one with the issue.

have you called EM and talked to anyone there?

I've spoken with Fred...e-mailed him my .bin file and a datalog last week.

It's hard to find a solution anywhere. My best bet is to hope that somebody else has experienced the problem and came across the solution. Between here and efi101.com, there's a couple hundred people...the odds don't look good.

You mean to tell me we have a forum now that has Electromotive Tech's on board, and you can't even get a response... that's sad!

For some reason I thought I had responded to this quite a while ago, sorry!

The AutoVE is WinTEC 4.5.25 is a little flaky. It frustrated me for quite a while because people would complain, I would try what they did and it worked fine for me. I think I have it working much better now. The new release (with TEC3 support as well) will be out very soon (I know I've been saying that but really, it will be very soon) and will have the AutoVE working much better.

Just a quick comment. I have found the new AutoVE in WinTEC4 to be much more accurate than WinTEC3. I recently had started a whole new VE Table and got it dialed in close in just a few driving sessions. I do not use AutoVE for tuning above 100kPA (on boost) It's hard to spend enough time in the cells to make a correction. Minimum is 5 occurrences which would land me in jail for reckless driving. Above 100kPa I make VE changes based on my datalog.