IssueReports/VemsTune (2011-06-10 15:38:32)

Add issues/bugs to most recent release at the top

Do not forget to mention :

Known issues


2011-06-09 NIGHTLY compile - grave: h[] table is saved wrong to [vemscfg]!

<PRE>

h[8]=01 02 04 08 10 20 40 80

h[8]=00 48 36 24 12 00 00 00

h[8]=68 40 38 48 58 20 20 20

h[8]=00 00 00 08 0C 00 00 00

h[8]=80 80 80 80 80 80 80 80

h[8]=00 00 00 00 00 00 00 00

</PRE>

b table also needs attention.


VT 2011-06-04 flags fake warning

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

[Jamo]


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.