IssueReports (2012-06-20 06:58:49)

Here you can link your report issues with your Genboard V3, firmware, tuningprogram or hardware problems.

Make your report on your MembersPage, and place link in the relevant section (with a "title", so it can be remembered easily). If you dont know the section, put it under "Unknown".

In the report, include a short entry and description + URL to your page, where the page contains:

The report, to be considered, must contain ALL necessary info. Without the necessary info, question-answer iterations are needed, so solution is delayed in the best case. If there is not enough info to reproduce, the report is neglected (especially if it contradicts experience). Re-post with the necessary info if you believe it holds.


Hardware: - usually wiring. These are normally answered even if you only use your MembersPage, but if you insist...


Config: please use your MembersPage where the full setup (engine, triggers, whatever related) is described


Vemsdisplay 2.0 - fail to start on android 4.0, logcat says application not found gauge table in gaugegroups.db. Seems to compatibility problem, with 2.3.5 works fine.


1.1.98 onwards (1.2.00) - 2nd WBO2 calibration and free air/ O2 display. How to calibrate?. Sprocket


Somewhat is broken in 1.1.96 classical Auditrigger. Cranking before first sparks prolongs approximately twice more blank revolutions. I note that on two cars. and today downgraded last one to 1.1.95 - it clearly improves situation to common. GintsK

Confirmed, 1.1.96 cranks much longer than 1.1.95 with the same config file. KeithJ

Confirmed again, 1.1.96 takes noticeably longer time before starting compared to 1.1.95. Mattias S.

This is fixed in 1.1.99, but instead serial communications drops all the time. This makes tuning rather difficult. Everything is the same except for firmware version, switching back to 1.1.95 makes it work fine. KeithJ

Something is still up with Auditrigger. Lots of misfires on 1.1.99+ for a config that works perfectly with 1.1.95. It acts like there is a rev limit way below the set point, and misfires really easily even at low RPMs.


1.1.95 now and running ok. However i see that the knock sensor features that were on 1.1.88 are now completely missing. Is there any options for knock sensing and updated settings that can make VEMS use the knock sensors adequately?

thanks

1.1.95 - No menu options for wheelspeed running latest nightly VT 7-12. Checked Firmware Parameters and it lists a 1 for PS2. I then downloaded both 'wheelspeed' & 'ps2' firmware to vems and neither of them showed a 0 for ps2.


1.1.94 - solved: use non-PS2 if wheelspeed is needed

THANKS> im going to go with 1.1.95 now. I thought i was supposed to use PS2 and not non-PS2(dont understand the difference). I would also appreciate if you could point out where to look for knock sensor settings for audi, as well as speed sensor settings for audi 5cyl engine. Thanks, Vasilis


Firmware:


1.1.88 knock_chan setting of 168 resulted in an increase in spark advance. vemslog and additional data here: http://www.vems.hu/wiki/index.php?page=MembersPage%2FMarcSwanson%2FFirmwareBugs


1.1.81 anytrim for boost do not work as expected. Boost target is boost dependant. Here is deeper description + real life and bench test .vemslog http://www.vemssupport.com/forum/index.php/topic,1490.0.html GintsK

Thanks for the Error report, problem found and fixed in Fw 1.1.86


1.1.75 and up

Trying pure alpha-n without using map signal. It was believed an VE (TPS/RPM table) interpolation problem:

http://cosworth.hu/misc/alphan/alphan_test_1.1.75.v3.3_n003420-2011.08.06-12.02.13.vemslog

http://cosworth.hu/misc/alphan/alphan_test_1.1.96.v3.3_n003420-2011.08.06-12.18.12.vemslog

http://cosworth.hu/misc/alphan/alphan_test_acc_1.1.96.v3.3_n003420-2011.08.06-12.19.18.vemslog

more info here:

http://www.vemssupport.com/forum/index.php/topic,1774.0.html

Solution: Dynamic VE table in group

Dynamic VE table means automatically change the Y axis based on current config Speed-density or Alpha-N.

To use it in a group properly you have to select Edit Mode and add Super table or Super Table 3D instead of Table and Table 3D


Problem with sd logging in 1.1.85. The Rpm and map values logged corruptly with sd log, when normal VT log seems fine:

sd log file:

http://cosworth.hu/misc/king_1gb_v3.3_n003420-001-SDCard-2011.09.19-21.59.35.vemslog

vemstune log file:

http://cosworth.hu/misc/king_1gb_v3.3_n003420-2011.09.19-21.58.42.vemslog