Author Topic: VE Tune by statistics, calculating Lambda delay  (Read 22329 times)

Offline Pet

  • Full Member
  • ***
  • Posts: 121
  • BHP: 7
Re: VE Tune by statistics, calculating Lambda delay
« Reply #15 on: October 09, 2010, 11:54:35 am »
VT is alot better then megatune or tunerstudio for live tuning.

a whole lot better then alot of tuning programs even.
The log review side just needs more work.
Maybe better, but why to remove *.VEX table export/import support ?? I think it's nothing difficult to add/keep this feature into VT and everybody will be happy.

Offline GintsK

  • Hero Member
  • *****
  • Posts: 1257
  • BHP: 50
Re: VE Tune by statistics, calculating Lambda delay
« Reply #16 on: October 09, 2010, 07:56:57 pm »
VT is dual software. It implements lot of valuable things. But at same time drops many good points from old package.

Today I worked with wide screen laptop on dyno. And gauge design not adopts for it like it was on MT. Few gauges was not visible. Designer mode crash VT... So no way... :(

MSQ import works for 1.1.74, but not for 1.1.80/81. On last ones import for tables do not work also from vemscfg.
 
I can't even count how many times I was forced to restart VT. Mainly due to communication problems. FTDI. But also due csv tool, trigger logger, hangs after firmware updates. Communication re-establish takes ages. And each time after powerup VT start undesired new datalog....

In 3D VE mode Alt-B, Alt-W do not work! I lost my work few times before catch it.

Currently it is very hard to use this software. It requires a lot of patience. I am patient. So I hope some day VT will be beautiful piece of tuning software with rock stability and fast response like old package had.

Offline Jamo

  • Full Member
  • ***
  • Posts: 129
  • BHP: 6
Re: VE Tune by statistics, calculating Lambda delay
« Reply #17 on: October 09, 2010, 08:58:30 pm »
Where can be the mess: last point - import from msq do not work for me (at least on previous VT 2010-09-08 version)? In worst case it just smash table. In best - do nothing. I tried both: drag and drop and Import button in VE table.
What VT works for that?

It works I've done it twice this weekend from 1hour drive logs and tune I'm using 2010.10.01
« Last Edit: October 10, 2010, 12:13:22 am by mattias »

Offline mattias

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1075
  • BHP: 41
    • Sävar Turbo Site
Re: VE Tune by statistics, calculating Lambda delay
« Reply #18 on: October 10, 2010, 12:12:58 am »
In 3D VE mode Alt-B, Alt-W do not work! I lost my work few times before catch it.
This was a known problem when 09-08 was released, it's fixed in 10-01 (10 days ago).

Offline GintsK

  • Hero Member
  • *****
  • Posts: 1257
  • BHP: 50
Re: VE Tune by statistics, calculating Lambda delay
« Reply #19 on: October 10, 2010, 08:32:01 am »
Ouch! I still use old VT from August. With reliesed label....
This is one more problem - no any history of changes. In addition it is usual - new VT=new bugs :( Mentioned Burn problem is one of fresh ones. :(

I will try October version. On August version table  importing works on 1.1.74, but didn't on 80/81 (msq and vemscfg).

Offline mattias

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1075
  • BHP: 41
    • Sävar Turbo Site
Re: VE Tune by statistics, calculating Lambda delay
« Reply #20 on: October 10, 2010, 01:52:28 pm »
This is one more problem - no any history of changes.

Sure there is history of changes :
http://www.vems.hu/wiki/index.php?page=VemsTune

I have no idea of which August version you are talking about, what does "release" mean to you?
« Last Edit: October 10, 2010, 01:54:47 pm by mattias »

Offline GintsK

  • Hero Member
  • *****
  • Posts: 1257
  • BHP: 50
Re: VE Tune by statistics, calculating Lambda delay
« Reply #21 on: October 10, 2010, 05:32:47 pm »

Sorry, Mattias. Not August, September:
Quote
VemsTune 2010-09-08 has been released:
- this is what I used yesterday. I usually read dates in opposite direction...

Where is history of changes? Since 2009 summer about 30 different VT versions comes out. And many times it was necessary to install these together with new f/w versions. Is somewhere changelog and known bug lists? It would help a lot to keep user in the knew what happens with this delicate software.

Offline mattias

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1075
  • BHP: 41
    • Sävar Turbo Site
Re: VE Tune by statistics, calculating Lambda delay
« Reply #22 on: October 10, 2010, 10:46:20 pm »
It would be nice with more information, but this is what we have. I can see the developers changelog, but it's far too technical for most and I don't have time (or get paid) to update you about it. Needless to say, it gets better with each version. If you have a known bug, report it in the Wiki or discuss it in a new thread pertaining to the version you are using.