_   _ 
 | | | |
 | | | |
 | |_| |
  \___/ 
        

 _______ 
(  ____ \
| (    \/
| (__    
|  __)   
| (      
| )      
|/       
         

         
     ##  
     ##  
  #####  
 ##  ##  
 ##  ##  
  #####  
         

  ______
 |___  /
    / / 
   / /  
  / /__ 
 /_____|
        
        

      _ 
     | |
  _  | |
 | |_| |
  \___/ 
        

IMPORTANT: enter the case-INsensitive alphabetic (no numbers) code AND WRITE SOME SHORT summary of changes (below) if you are saving changes. (not required for previewing changes). Wiki-spamming is not tolerated, will be removed, so it does NOT even show up in history. Spammers go away now.


Visit Preferences to set your user name
Summary of change:
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''': * '''.vemslog or .vemscfg is absolutely essential''' to reproduce ** any report without these will be deleted. Add .vemslog or .vemscfg ** and besides these, (especially if a trigger problem, with new firmwares like 1.1.81) also '''a triggerlog''' (so the team can get a chance to reproduce and help to resolve the case). ** Note that newer firmwares have new trigger-settings in config bits that were previously "don't care". Bad settings of these will simply prevent triggering, so carefully check after uploading an 1.0.x or 1.1.7x or older config to a new 1.1.8x firmware) * board version, serial Nr. * '''firmware version''' * '''MegaTune version''' (when MegaTune is used at all) * intended config.txt (possibly commented) * '''mcdmct.txt''' (captured output of Manmcdmct command.) This is the '''live config'''. Very important, since in a bad case it can be different from the intended config (if you used a global.h from a different firmware version; or there is a MegaTune configuration problem, etc...) * description of the problem * your investigation so far * any ideas to proceed '''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 ---- 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''' * went from 1.1.88 to 1.1.94 as recommended and using vemstune 16/6/2011. ** '''Speed sensor feature is completely missing from my saved config and i am not allowed to see it from base menu'''. ** '''Likely you selected PS2 firmware that does not have wheelspeed sensing''' (the PS2 clock uses up the 1st wheelspeed input). * Other users do not have this problem. ** yes, just '''Choose non-PS2 firmware''' ** actually, Sami reported that his noisy (mechanical reed-relay type audi transmission) wheelspeed sensor reading is not stable with 1.1.94 when input prells at 450 km/h period (he provided suitable triggerlog to see this) and in 1.1.95 we implemented a more advanced wheelspeed filtering that fixed that sick case: you can use 1.1.95 non-PS2 also. 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:''' *v3.1 #56 & #57, 1.1.70 I have a problem with new firmware on 3.1 board. It only works in limphome mode. ** using latest Vemstune (2010-03-08 and 2010-02-05). The problem is that '''after startup spark angle stays fixed on 10° all the time''' ** similar situation with stepper IAC valve. When I turn on the engine it goes in max closed position and stays there ** 3.1 boards are still supported. It's a bootloader problem. Was the bootloader upgraded (or atmega changed) on these boards ? This "limphome" protection was implemented by Andrey, ment for a batch of pirate boards (most in Bulgaria and Russia). If your board is "genuine" (even if old), contact through WebShop (so you can receive a new bootloader, or other solution). Write the original Order-ID or other details (date of purchase) ---- 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
Optional: Add document to category:
Wiki formatting: * is Bullet list ** Bullet list subentry ... '''Bold''', ---- is horizontal ruler, <code> preformatted text... </code> See wiki editing HELP for tables and other formatting tips and tricks.