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

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

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

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

   ____  
  / __ \ 
 | |  | |
 | |  | |
 | |__| |
  \____/ 
         
         

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:
'''Firmware''' I've made some experiments with 1.1.50 non-PS2 (gear-boost in theory) Firmware was uploaded and verified by latest vemstune, settings, logging were made in megatune for 1.1.50 (hacked to support 16x14 which is the only supported fw I guess) ---- So first I tried to use boost_channel only (the PID based one), boostalt was disabled all the time. Still, alternate boost's "mode" setting seems to alter the PID boost_channel's general behavior. - And it seems it has nothing to do with gearboost yet?? Strange to me. OK, so my test-cases: '''1. Absolute boost''' there's no change of boostDC excepting a very slight decrease at extreme high map [http://quasar.dynaweb.hu/~lezsi/vems/fw1_1_50/absoluteboost.zip Config and logs] '''2. Relative boost''' there's no change of boostDC excepting a very slight decrease at extreme high map [http://quasar.dynaweb.hu/~lezsi/vems/fw1_1_50/relativeboost.zip Config and logs] '''3. Simple closed loop boost''' boostDC seems to follow closed loop reference from boost refDC table (rpm/map based), however boostDC gets lower than it is specified in the table's reference values. One more interesting thing is when boost target is getting close, boostDC gets down to zero (it's fine) but after MAP has passed the target slightly, it jumps back to some higher value. [http://quasar.dynaweb.hu/~lezsi/vems/fw1_1_50/simpleclosedboost.zip Config and logs] '''4. Simple open loop boost''' there's no change of boostDC excepting a very slight decrease at extreme high map [http://quasar.dynaweb.hu/~lezsi/vems/fw1_1_50/simpleopenloop.zip Config and logs] above the target MAP level boostDC jumps back to around refpos (from zero). annoying. ---- Another tests have been made using BOOST ALTERNATE only (no PID boost_channel used here) with 1.1.50 PS2 firmware. '''5. BoostALT relative''' Generally it works, boostref table kPa-scale is annoying, I tried to convert it to the -155..+100kPa range (not sure it was correct). Later I realized, that it changed SPARK ADVANCE bins also! My boost-build characteristics were as expected, excepting that target somehow seemed to be ~180kPa instead of the 230kPa set (and 224(why?) in logs). [http://quasar.dynaweb.hu/~lezsi/vems/fw1_1_50/boostalt_relative.zip Config and logs] '''6. BoostALT absolute''' It works fine, just like in 1.1.4x firmware. For both boostalt setting, I was really missing some boostaltDC variable in logs, and gauge in megatune, as boostDC is for PID-boost only(?) [http://quasar.dynaweb.hu/~lezsi/vems/fw1_1_50/boostalt_absolute.zip Config and logs] ---- '''Obsolete''' '''2006.04.18.''' Finally went to firmware 1.0.38 which controls BMW idle solenoid nice. (Previous used versions were 1.0.14rc, 1.0.30rc2 - both hacked for iac) Upgrade was not easy as car was going like shit (very weak) thanks to new ALS variables, which I wasn't able to disable completely, and retarded my ignition to hell. I suggest to everyone to double-check changed new-old variables with comparing mcd outputs, and don't expect that FF always means disabled, like I did... Now it seems ok. ---- '''Obsolete 2''' Since I need to have customized code for IAC, tried to compile new firmware. This is not so easy in windows. There's a great howto at MembersPage/JohanEriksson/VerThreeFirmForDummies but I had problems When I tried "make all" from cmd.exe: ... make (e=2): The system cannot find the file specified. make: *** [vems.o] Error 2 I get the same from cygwin's sh.exe, and in sh.exe from unxutils '''I've found that it was nothing to do with the shell and make.exe, but with avr-gcc.exe which wasn't found. '''(Since it was not in path) I've found that spaces are not welcome in winavr's path, and Marcell said that if 'lib' environment variable is set (to anything) that confuses make.exe, so I made a batch file which sets the environment before I can say "make all". It is like: set lib= set path=%path%;D:\VEMS\winavr\bin\;D:\VEMS\winavr\utils\bin\; After that I was able to compile the firmware succesfully. Thanks for the ideas Cell and Ben. ---- About setting prog.pl under win32: * Had an ActivState perl installation * Had to download SerialPort.pm, it's in Win32-SerialPort-0.19.tar * Had to download and install win32-api pm, which was in Win32-API-0.41.zip. This one really need to be installed not just having copied into lib directory. **To install: > ppm **>add repository name_of_the_package_folder **>install win32-api
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.