News:

When asking for technical help at the very least let us know the version of firmware you are running.
Cliff's Calibration (Mapping) Guide is a MUST READ: http://www.vemssupport.com/forum/index.php/topic,97.0.html

Main Menu

VemsTune graphics problems (gauge update speed)

Started by mattias, April 13, 2011, 12:14:55 PM

Previous topic - Next topic

mattias

If you experience "lag" and display problems with gauges and buttons in the menu, you can change a variable in a text-file.

"rtMinRefreshInterval" is the variable, in number of milliseconds between screen redraw.
You find it in the installation directory under config/v3gui.cfg

Check the CPU usage of the VemsTune process, press shift+ctrl+esc and the process manager appears. If the usage is at 100% for the process when online to the ECU then you have issues. Edit and replace the number with a high enough number so that it flows well on your computer,  setting it to 200 would be 5 Hz  = 5 redraws/second. By mistake this is set too low in some releases.

It's not useful to have any faster redraw than the update rate you get from the ECU, which is usually 15-25 Hz.

This can help a lot on some old laptops that have really crappy ATI chipsets with poor 2D acceleration where the CPU has to do the dirty work, which is not nearly as efficient. Obviously if you get a high update rate from the ECU and have this variable set too low (short interval between redraws) then the computer won't keep up. At the moment the redraw is interrupted which can cause graphics glitches, the developers are working to fix that - if it wasn't for that I wouldn't tell you about the variable, so this problem is probably solved by the next release.

lugnuts

Thank you so much for this information!

Setting the "rtMinRefreshInterval" to 100 instantly fixed my issues.

The easy way to replicate this problem, is to go to ADC CAL or RAW display.
My test bench harness has ADC7 on a trim pot, and my screen just would not refresh any change to the value - UNTIL I clicked on any of the drop down menus, then it would refresh perfectly.

Why was this not sent out in the auto updates? Seems an easy way to fix the issue instantly (set to compromise value of 50-100 to suit all pc's) My value was set to "10" by the way in 3-24-2011.

I don't know about you guys, but I always use an old computer for tuning, suince they get the crap beat out of them anyway.

I have a Dell C400 laptop, with an Intel 82830M Graphics Controller.

I'll try the new 4-26-2011 vemstune as-is and report back.

mattias


It's set to 60 ms in the 4-26 release, should work out better on most computers, but older laptops will have issues.

GintsK

Is somewhat changed during this period? My 20.07.2011 VT keep CPU loaded heavily (yes ATI on T43p with 1600x1200 screen)! But changing of mentioned value seems has no any influence on gauge update rate. Tried 100, 200, 1000 and 10000.  Yes, I resaved file and restarted VT fter changes.

Gints

mattias

Gints: Make a report about it, use the built-in tool in VemsTune.

z0tya

Quote from: mattias on September 06, 2011, 11:45:43 PM
Gints: Make a report about it, use the built-in tool in VemsTune.


Is it works? I have sent two report some weeks ago about ve analize but no any response yet.

mattias

Join #vems on EFnet (www.efnet.org IRC) or mail [email protected] to get things rolling a bit..