Useful features?

[PeepPaadam]

I've been thinking about some simple additional features that would be really useful and maybe not too much for the programmer guys. Here they are:

* Coolant temp dependant rpm limit. Great safety feature.
* Coolant temp dependant boost limit. Both soft and hard boost limit.
* Oil pressure dependant limiter (rpm, boost, fuel cut). Might save you an engine on the track.

What do you think of these things guys?

[lugnuts]

These sound great, but these I think are much more important:

MAT and EGT Boost Reduction/Cut
Improved Acceleration Enrichments
MAT vs. TPS Table
Display only Round gauge
SD card Datalogginig
Gear Gased Boost Control
14x16 Tables

And, critically:
- Everything on one firmware!
- Everything works!
- Dont lose any existing features!

[PeepPaadam]

I don't know about everyboady else but I'm using 16x14 tables for nearly two years now?

And we've kinda have already these:

Improved Acceleration Enrichments
MAT vs. TPS Table
Display only Round gauge
SD card Datalogginig
Gear Gased Boost Control
14x16 Tables

[gunni]

The best useful feature would be a working Software package .
i.e vemstune.


I´ll rather live with frequent upgrades to the software rather then
undocumented firmware upgrades.

[lugnuts]

Yes I have the 16x14 on my 1.0.73 firmware, is just dont want to lose them!

I do not wish to change firmwares multiple times. I'd like to pick one firmware and go with it. I'm hoping to get most of the above features in one firmware.

So do you know which firmware has the most new features?

Also, yes I agree it has to work 100%. I like the Megatune for now. The VEMSTune I use is from Sept 2008, the newer versions cause problems for me. I know I need to document these problems better - but there are so many! 

[lugnuts]

Andrey   (http://www.vems.hu/wiki/index.php?page=MembersPage%2FAndrey)  seems to be doing a lot of experimental work. I'm trying to contact him and anyone else that can help me.

I'm willing to pay someone to help me get the features that I want - with support.

Kevin
Lugnuts9@msn.com

[Sprocket]

Where firmware is concerned, you should only upgrade if the new firmware resolves a particular issue that the previous firmware suffers, or it has a feature not available on the firmware you are currently using.

I agree, more work is needed to get a working Vemstune WITH a help file

[GintsK]

What missing me from above is widened coolant temperature range.
I live with Megatune (with adopted .ini), bat scripts and Megalogwiever and I am happy without vemstune.
Megatune is fast and reliable. Yes it is a bit tricky these drop down menus with unclear values. But Vemstune has not any step forward in this. What my tuning package miss is capability of graphical analyzing of desired values against each other. e.g. MAT/egoC/Rpms for proper construction of MAT table.

But firmware is much improved since 1.0.73!

[lugnuts]

One thing I am happy to do in Megatune is clean things up.

Example - I changed the "coolant bins" to normal non-geek numbers (100,90,80 deg C) and then went into the vemsvs.ini file and disabled the coolant bins line altogether (by putting a ; in the beginning of the line)
Who the hell wants a coolant setpoint at 71 deg C or whatever it is.... annoying!

Example #2 - I make sure the graphic tables such as boost vs rpm have "normal" values , like 1000-2000-3000-  etc.

Some of the values and text in the tuning windows/graphs are just dumb.

I have also organized and renamed the functions the way I like them.


I'll trade vemsv3.ini work for firmware work with anybody!

[GintsK]

Again!
 Somtimes LSU fails. We need to stop Ego correction to zero.
Today I had phone call from race service park. Crew has some problems with WBO2 sensor. La shows ?? on LCD all the time, but egoC fluctuates +/- close to max allowed range. And I has no way to help to solve this issue. It was leading crew

Gints

[rob@vems.co.uk]

Again!
 Somtimes LSU fails. We need to stop Ego correction to zero.
Today I had phone call from race service park. Crew has some problems with WBO2 sensor. La shows ?? on LCD all the time, but egoC fluctuates +/- close to max allowed range. And I has no way to help to solve this issue. It was leading crew

Gints

Sambas tells me that 1.1.4x has the freeze EGO feature.

[MWfire]

Again!
 Somtimes LSU fails. We need to stop Ego correction to zero.
Today I had phone call from race service park. Crew has some problems with WBO2 sensor. La shows ?? on LCD all the time, but egoC fluctuates +/- close to max allowed range. And I has no way to help to solve this issue. It was leading crew

Gints

Sambas tells me that 1.1.4x has the freeze EGO feature.

I can confirm. Once i disconect one wire of lamda sensor, and lambda was 2.1 and ego=0.

[GintsK]

It is good news! I will try!
They use 1.1.47
It would be more safe if egoC freezing on zero automatically if no real AFR feedback for prolonged period (closed loop is damaged). Not all drivers watch on LCD.
More good news - crew was fastest anyway

Gints

[z0tya]

Can be possible to use speedsensor from auditrigger vr input?
(If there is the 2nd lm chip to signal processing but not for triggering)

[ASSA]

Waiting for 1.1.51 package with megatune. Found a lot of useful things in this build.