_______ 
(_____  )
     /'/'
   /'/'  
 /'/'___ 
(_______)
         
         

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

 _______ 
(  ____ \
| (    \/
| (_____ 
(_____  )
      ) |
/\____) |
\_______)
         

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

         
|\     /|
( \   / )
 \ (_) / 
  ) _ (  
 / ( ) \ 
( /   \ )
|/     \|
         

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 at least''': * board version, serial Nr. * '''firmware version''' * '''MegaTune version''' (when MegaTune is used at all) * intended config.txt (possibly commented) * '''mcd.txt''' (captured output of Manmcd 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 ---- '''Firmware:''' * Is it known limitation of 95rpm on 4cyl (3.17Hz 50% PW feed to trig1) for ignition to work with coil-type setup? Under this freq injection works fine but ignition doesn't work at all. Wondering is there such limitation with multitooth (couldn't tabletest myself) that could cause flood with sloow cranking engines@winter? Shouldn't flood situation be avoided even with coil-setup? * DONE: (fixed in svn) If throttle is released while RPM is above config.overrun_fuelcut, fuel is cut by definition of overrun_fuelcut. So fresh air rushes through the engine. Therefore EGO closed loop is switched off until TPS is again pressed more than config.iac_tps_thres (or RPM drops under overrun_fuelresume). Of course EGO is off while fuelcut is active, but it doesn't switch back on even after RPM drops to idle (ego_min_rpm < RPM < overrun_fuelresume). Used firmware was 1.0.53 How could/should this be different ? Just to mention, because it is #1 in the required things list ;) * DONE: (fixed in svn scheduled for next release) Firmware v53: PWM is not working correctly eg. when injpwm=7F pwm should be 50% when batt_cal is correct? I measured (injpwm=7F) 16V 62%, 12V 82%, 10V ~100%! This was kinda same before v53; injpwm6 added more pwm% @14-16V when it really shouldn't!, pwm dc calculation was limited at 19v, which obviously should have been 14v - DB * DONE: (fixed in svn scheduled for next release) Misc output boundries were not included in range selection, therefore making for instance switch from 20 to 100% tps impossible - DB * DONE: check ALS and Launch at the same time (it is reported by Roland that their on patch on 1.0.23 worked OK, but the (well, actually another car with) 1.0.38 (but no ALS related change between 1.0.36 and at least 1.0.43) ALS worked, and Launch also worked, but not at the same time - verified to work properly * DONE: '''double-check operation''' at "> 100% injector duty" ** I made several experiments near (and above 100% injector duty), that is when injector pulsewidth > cam period (engine cyle lenght). I coulnd't find any problem, but I could make a stupid injpwm config that demonstrates the effect that resembles the rumours. See [http://www.vems.hu/files/Firmware/config/stupid_injpwm_config_100_percent_injector.zip RPM-sweep mp3 file and config]. Note the comment text at the top of the config.txt file. * NOTED: '''Newest WinAVR''' can't compile 1.0.28 firmware direct from distribution correctly. ECU hangs and need to be jumpered into the bootloader. Downgrading WinAVR to 20050214 release solved the problem. Reported by RagnarB. Shouldn't this be reported to winavr instead ? '''Use of pre-compiled releases or winavr-20050214 is recommended''' ** This is also seen using the latest avr-lib release. Some incompatibility must've been introduced. ** is this the same as the previous report commented as "the ALS": Compiling latest svn firmware with ALS makes VE go all over the place, even with the same values in the whole ve table. Compiling without -D ALS it works fine. This is typically a '''compiler error that we cannot fix''', we have seen it before: AtMega/AvrGccFAQ * DONE: (in mainstream. freq was double) 1.0.30 [VemsMT1.0.30rc3.zip] the dualpwm iac doesn't seem to give fast iac-valve actuation. Tried iac_speed=06,07,08,09 (actually set in MegaTune, tested with mdi commands => as a result PID was untunable) GergelyLezsak's old code was good. More on it, and SOLUTION at MembersPage/GergelyLezsak/IdleControl/Firmware. * DONE: A low temperature (lower than -40degC) showed as 76 degC with old EasyTherm generated table. This was a known feature, we dropped it. * DONE: we should also make sure to include properly calibrated tables for the NTC sold in webshop 2200_287 (for v3.3) * NOTED: Compiling (with what compiler version?) latest svn firmware (revision?) with ALS makes VE go all over the place, even with the same values in the whole ve table. Compiling without -D ALS it works fine. '''Use of pre-compiled releases or winavr-20050214 is recommended''' ---- '''Tuningprogram (Megatune):''' * 2006-07-29 primary_trigger upper bits cannot be changed or even checked. Bit6 (nissan-trigger) and bit7 (currently not used, but still should be added) should be added, and if possible, a numeric field so the whole primary_trigger config value can be set or verified easily in one step (=> less chance for error) '''done''' ** note that this can confuse the unaware who doesn't care to dump his config and check a few values manually or publish mcd/mct so others can help * 2006-02-26 naming: INJGROUP or FETGROUP or similar would be the right name for selecting inj-channel. The "group" suggests that it's not a direct output and the group needs to be configured elsewhere '''done, renamed to INJOUT''' * 2006-01-31 [VemsMT1.0.30rc3.zip] looks like lambda bargraph is not working under VE-tuning (no dots at all) '''fixed from 1.0.36''' * 2006-01-21 [VemsMT1.0.30rc3.zip] seems to show 40 degrees "spark angle" instead of 20 degrees (as on LCD, and in reality) '''fixed from 1.0.36''' * 2006-01-19 rumours has it that knock-advance enable/disable in megatune (r28?) is reversed. Unverified '''fixed''' * 2005-09-21 iac activation flag is inverted (Fero reported on phone): not sure which one, the (ON/OFF vs. PWM-stepper - likely) or ignition advance based idle active/OFF * 2005-09-02 ** EGT display (range) is bad, the gauge displays upto 256C (the digital display is good, but the gauge rails out) '''fixed from 1.0.53''' ** injector duty cycle... is this fixed already ? '''fixed in 1.0.36 at least''' *2005-10-23 ** In alphaN-mode, at 22% throttle (VE, lambda or ignadv table) 56 kPa (255 * 22%) line is used. However MegaTune shows 117 kPa ( 512kPa * 22%) and places the dot at a different place, '''Tunable, but very confusing''' ** Ini file -> vemsv3_v13_r021.zip or up to mt-r027 ** firmware -> 1.0.13 .. 1.0.18 .. 1.0.22 ** possible solutions: *** '''fixed in next release: when reporting load, in comm.c '''A''' command offset 4 and 5, <<2 used instead of <<3 from 1.0.23'''. User must still be aware that MAP gauge only shows MAP when RPM > hybrid_rpm_m and load otherwise *** in the future, firmware might report load and kpa in different positions (the dot should always move according to load, MAP gauge always display MAP) *** If you are running alpha-n only and not hybrid mode, its possible to modify vemsv3.ini to show TPS in the realtime tuning, write here or memberspage if you need help. ** thanks for the info. I'm useing Alpha-n only, yes I need details how to modify vemsv3.ini *Megatune Accel wizard display shows current TPS instead of changespeed of TPS. ----
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.