In case of bug reports please do not forget to write
- VemsTune version
- V3 firmware version.
- Zip and publish your saved config (vemscfg) and Tools/firmware/config download when appropriate.
- I have the same problem(0.9.85)
- Could it be possible to add a background to the gauges?
- Currently not. Need some implement.
- I think of a simple object like jpg/bmp image? (example Kevlar background)
- If we type in the firing order could the value of injector and ignition table be automatic generated if using standard inj A = cyl 1. inj B = cyl 2 same with ign. nice job -Peter
An installer says: "When a customer has problems I like to be able to send finished mtt files to him, these can then be sent with command line tools or if he has communication problems I help him with bray over the phone"
Finished files make a lot of sense. It was planned that one would send project file, where the RIGHT firmware and/or config can be uploaded with 1..2 clicks (not lost in menu-s).
Note that the vemstune over the network will be very useful in many cases, but dealers still need a way to prepare project / vemscfg files (in a documented way!) that can be uploaded extremely quickly (without using menu-s) by a computer-illiterate child supported over the phone.
- Remote tune over TCP connection feature is in integration/testing phase, planned to work only in newest firmware only with SIPR protocol.
Gauges
- How can I add new gauges (especially knock_cyl_0_knock_val) to VemsTune and how Can I log it? I have tried to put vemsv3.ini, vemstune-v3-1.1.27.ini, GaugeSymbols?.xml but no success.
- __Can I log it?__ I think you mean how can I convert it to csv (*.vemslog contains all raw data).
- To convert it to CSV you have to edit manually the appropriate *.ini (for example: vemstune-v3-1.1.27.ini) and go to __[Datalog]__ section and add new __entry__ to it.
Firmware Version
- Can not find the new function (wheelspeed, wheelspeed-based launch and the new knock-threshold-map) in 1.1.61 non ps2 in VemsTune when i make a new empty project.
- I found a new row in the defaultfirmwareconfig directory in the new 0.10.0 VemsTune called CompileOptions: 0000001B, and loaded into VemsTune, the program showed the Mics Output new settings. I played it with a bit, but not got any logics. With ff it shows the alternate knock settings to. How this varible work???
How do I get 1.0.79 to work with the current version VemsTune?
VT version 2010-07-08 + 1.1.78 FW:
- Ignition map misses remap-button
- Program in general is way too heavy on processor
VT version 2010-07-08 + 1.1.74 FW
- In alphaN mode I can't enter the TPS breakpoints that I want to, ie I can't enter 4 it changes to 3. I can't enter 100 as it changes to 99. It is as if the resolution is larger than 1
- Tune by statistics doesn't work in AlphaN mode (also tried with VT 2010-07-16). The VE table used in it has a Y axis of 0 - 255 and all the data is analyzed at being 100kpa (MAP sensor is measuring baro). Log (with config inside) here http://www.fautley.co.uk/alphanlog.zip
VT version 2010-07-16
- As alpha N mode doesn't work with tune by statistics I am using CSV exporting. CSV export scales TP to between 0-100 whereas megalogviewer expects 0-255.
- Is it possible to modify ini file so that CSV export scales TP to between 0-255? Thanks
VT version 2010-07-19
- fw version 1.1.80 config file: Factory AAN config, driven by c270 signal constans 670RPM. "Tools"/"Analyze/record trigger log" Source is V3. Start trigger signal(from Audacity), Click on "Start v3" button. start to show trigger signal badly, after click on "Stop v3" button VT crashed.
- Can't reproduce it
- fw version 1.1.80 config file: Factory AAN config, driven by c270 signal constans 670RPM. "Tools"/"Analyze/record trigger log" Source is V3. Click on "Start v3" button after start trigger signal(from Audacity) start to draw trigger signal seems well, but draws 3 sectrig puls for 270 primary, click on "Stop v3" button. Clicking to "Show result" button I've got the "Trigger log result window" shows nothink usable only the headers.
- fixed
Analyze Trigger-Log consumed way too much processor and did not work on slower-CPU notebooks. From 2010-08-06, now it doesn't use excessive CPU and useful even with Nx100 MHz slow hosts too.
- fw version 1.1.80 config file: Factory econoseal config, driven by m231 signal with disabled sec. trig. "Tools"/"Analyze/record trigger log" Source is V3. Click on "Start v3" button after start trigger signal(from Audacity) start to draw trigger signal WELL, click on "Stop v3" button. Clicking to "Show result" button I've got the "Trigger log result window" shows nothink usable only the headers.
- fixed
- fw version 1.1.80 config file: Factory econoseal config, driven by m231 signal with enabled sec. trig. "Tools"/"Analyze/record trigger log" Source is V3. Click on "Start v3" button after start trigger signal(from Audacity) start to draw trigger signal WELL, click on "Stop v3" button. Clicking to "Show result" button I've got the "Trigger log result window" shows nothink usable only the headers.
- fixed
- Pressing "ESC" escape key closes some menus, changes focus to main window from others. Would be very helpful and intuitive if escape closed current menu window without sending or burning.
- fixed (2010-08-09 morning)
VT version 2010-07-19
fw:1.1.70, when i wanted to erase the sd card (tools/sd card log/erase) vt crashed. After erasing the sd with on older VT, start, stop, extended overview functions are work.
VT version 2010-08-19
It is impossible to remap MAT/TPS enrichment table with MAT values below zero. X axis negative values are incrasing every time I reopen MAT/TPS table. (fw 1.1.75, 1.1.80, 1.1.81)