1.1.80 firmware

[MWfire]

If you don't absolutely need the injection angle function I suggest to go back to 1.1.78.
There's a problem with TPS refreshing in 1.1.79 and 1.1.80, not a fatal problem in my experience, but sometimes it makes the engine jerking a bit.

http://www.vems.hu/wiki/index.php?page=MembersPage%2FGergelyLezsak%2FFirmWare

Backs up your findings, I'm waiting until this is fixed in a later version. TPS refreshing would be an issue for me, is this going to be fixed in the next release?

in "new" 1.1.80 is tps problem fixed.

[Jamo]

Ah good info, so the one in vemstune date 2nd August is the new one?

Notice 1.1.81 is available in vemstune now as well!

[Kamuto]

and how is it? knock works?

[lugnuts]

I had a strange issue, I'm not sure if it was the 1.1.80 firmware or not.

VemsTune 8-11-2010, 1.1.80 fw.

I uploaded the 1.1.80 to an ecu, and the MAP sensor would suddenly not respond to vacuum/pressure.
I put it back to 1.1.70 or 1.1.74, and the MAP sensor works again.
1.1.80 again, no response from the MAP...... 
install 1.1.74 - MAP works and I sent it out the door.

And I just sucessfully put the 1.1.80 on another car and tuned it for 2 days before that...
and that car is running well at the track today.

[mattias]

lugnuts : I noticed that too and it's fixed in 1.1.81.

The MAP sensor value was only updated with input from the primary trigger (engine running).

[BigD]

Not sure what it was but my engine wouldn't start with .81. Can't say I gave it a really solid effort to find the reason but I looked through the basics (well I could smell fuel out the pipe so I was mainly looking for ignition problems), everything seemed right. Reverted to .80, fired right up.

[lugnuts]

lugnuts : I noticed that too and it's fixed in 1.1.81.

The MAP sensor value was only updated with input from the primary trigger (engine running).

- Thanks for the reply. That change was a big problem for me, I had just noticed it the day i was trying to send an ECU out the door. I changed the fw back and forth and ended up going back to 1.1.74 for that unit. Cost me a couple of hours.

- I notice that every new fw version brings new bugs. Is this unavoidable, or is it "tinkering"?

[Jamo]

lugnuts : I noticed that too and it's fixed in 1.1.81.

The MAP sensor value was only updated with input from the primary trigger (engine running).

- Thanks for the reply. That change was a big problem for me, I had just noticed it the day i was trying to send an ECU out the door. I changed the fw back and forth and ended up going back to 1.1.74 for that unit. Cost me a couple of hours.

- I notice that every new fw version brings new bugs. Is this unavoidable, or is it "tinkering"?

IMO from my experience this is way of software, it's unavoidable no matter how hard you try. I did software testing and programming for living in my early years and the you find that code you thought was working correctly isn't actually until you write more new code!

In terms of Vems because a lot of features are continually been put into it, until it stablises on a version with no new features and one that concentrates on solely refinement of existing features it will be in this status.

[Sprocket]

*Feature request*

since 1.1.80 now has injection angle and individual injector trim, could there be a possible progression to perhaps replace the fixed injector trim per channel with an 8x8 table (injector channel x rpm x trim) This would satisfy my needs for siamease port injection :D Everything is there except for the RPM variable

A similar table for injection angle would wholey compliment the above and truelly turn VEMS into a versatile system Edit* what is there should actualy do the task as I think more about it :)

I do not care for the second wideband anymore, as I can simply use a Vems WBO2 round to display both Vems Gen3 aim lambda and the WBO2 round lambda on the one display ;) I think that it would be a rather neat solution to that which other shall not mention systems have to use :D

[Jamo]

*Feature request*

since 1.1.80 now has injection angle and individual injector trim, could there be a possible progression to perhaps replace the fixed injector trim per channel with an 8x8 table (injector channel x rpm x trim) This would satisfy my needs for siamease port injection :D Everything is there except for the RPM variable

A similar table for injection angle would wholey compliment the above and truelly turn VEMS into a versatile system Edit* what is there should actualy do the task as I think more about it :)

I do not care for the second wideband anymore, as I can simply use a Vems WBO2 round to display both Vems Gen3 aim lambda and the WBO2 round lambda on the one display ;) I think that it would be a rather neat solution to that which other shall not mention systems have to use :D

I'd love to able to use narrow and wideband input in parallel

[AVP]

has the ability to control boost with gear or speed depended been dropped on 1.1.80 and upwards? if so, why? is it because it can be adjusted through anytrim?

[Jamo]

Both are in 1.1.81

[AVP]

yes, but on 1.1.74, when i pressed to use either, another plot came up. WHen i do that on 1.1.80 they dont come up at all. As if not allowed to specify values on a table.

[Jamo]

Might be a vemstune issue as it's there in 1.1.74 as I was running that before upgrade

[AVP]

i used the one before the latest vemstune version (august 18 i think) and when i upload 1.1.74 firmware it does come up, but when i upload a 1.1.80 vemsconfig it doesnt!