IssueReports/VemsTune (2012-08-21 23:10:45)

Add issues/bugs to most recent release at the top

Do not forget to mention :

Known issues


Vemstune 1.3.1 2012.07.30

Problem with Editor after saving a certain view.

It will add more instances of the same channel, this has been

a problem on many older versions as well, I donĀ“t think any version has ever not had this problem.

editorproblem.jpg

Also just to note :

As discussed with Emil it would be nice if the whole view could be saved as a single file for export to customers, this means gauge views and multi graphs all saved into a single file.


Vemstune 2012-30-01

Using firmware 1.1.98 Y axis values are wrong after upgrading to this firmware.

Also bug after uploading firmware is that the ecu is stuck in

safety mode after firmware update. Tested back in 2011-12-21 and no problem there.


Vemstune 2011-15-11


Vemstune 16/6/2011

firmware 1.1.88

Vemstune is unable to load any config and brings up a message of SQlite unable to load database. i have already reported this through the report error module of vemstune.

it cannot load any config or log. I turned back to 20/1 version.

latest vemstune seems to work fine on windows XP


Old firmware trouble

Tried this on VT 06-04. If connecting to an old ECU which lacks an ini-file, then you should at least be given the option of downloading config and upgrading firmware. It was not able to connect to 1.0.71 to even enable any kind of upgrade path with VemsTune.

Here is a video of the problem : [27 MB download]

I used the old bat-scripts of 1.0.73 from MegaTune packages to upgrade to 1.0.73 and then up to recent firmware with VemsTune.


VT 06-15

With older firmware, I tried 1.1.64, config validation complains about invalid output chosen for VVTi. This symbol doesn't exist until more recent firmwares.

Also got a config from a guy running 1.1.64, who on config validation not only gets the above (VVTi) but also a warning about too high cranking enrichment values, but the table looks ok ?

[screenshot] and [vemscfg]

Try loading the default configs that come with VemsTune, many of the older firmwares fail the validate config test. Some, like the above are bugs and others are "INVALID" values.


Config different with 05-27 vs 06-04

The config files are here : [05-27] and [06-04]

Can't really explain any of it, and I'm not there to oversee it.

[Mattias]


FIXED: VT 2011-06-04 flags fake warning

For the Audi trigger divide by 3 setup (default VemsTune/QuickStartAudi ) show a warning on validate.


In vemstune/config/include page-config-[version].ini

change sdcard_choice sdcard_choice = bits, U08, 149, [1] , "INVALID", "INVALID", "INVALID"

In to

sdcard_choice = bits, U08, 149, [2], "Disabled", "Enabled"

I don't know if its good but it works getting your knock working again in channel 0.


VemsTune 2011-05-27

(report by Mattias)

Upgrade scenario

Done on a workstation with real serial port (COM1) running Windows XP (32 bit).

1. Install 2011-05-27

2. Start application

3. Enable comms, pick COM1, detection works straight away, ECU comes online and uses firmware 1.1.70 [config here].

4. Firmware validation complains about :

5. Now upload new firmware 1.1.92. Some observations.

6. When the new config is uploaded to the ECU, the application hangs.

Second attempt. Ok. Restart VemsTune, now running 1.1.92 firmware after failed config upload, use the upload advanced (to A and B) function in the file menu, picking the latest 1.1.70 config file, conversion and upload goes well this time. Still, validate config fails on these points :

Detection issue

Hard to understand exactly what happens. I did this on my Lenovo T61 laptop using a fresh install of 05-27.

Graphics issue

Still in 05-27, due to slow graphics on some laptops - it's a known problem but still worthwhile to bring up a scenario. Bringing up a simple table, like "warmup enrichment table" or "idle reference duty cycle", can bring graphics display to a complete halt in the active gauge group in the background. This needs to be fixed, wxWidgets must have some means of drawing all elements of the application without being interrupted, before continuing to make the next redraw. It seems only a few elements are redrawn, then interrupted by some kind of timer (too short time) and the redraw starts over, which leaves some elements never seing an update (most gauges).


INVESTIGATING: 2011-05-27 sometimes crashes before (or after) firmware upgrade (in same usecase, 2011-04-26 worked well)

DONE: Issureport ergonomy improved after 2011-04-26, more userfriendly in 2011-05-27

VemsTune 2011-01-20


Fixed items

May not appear until next release.