- For experienced users only. Remember, experimental FW is easy way to kill engine.
- Read carefully my_make (if present) file to know what features needed to set. If you forget at least one output (warning beep/light for example) you flood engine.
- I sometimes use simple injector deadtime table instead injector opening model (INJECTOR_DEADTIME_SIMPLE in my_make), small xls spreadsheet could help convert values.
- I always use MT, so forget about SD logging and other VemsTune features. Terminal commands (mct, mcd etc) could not work too.
- MT have limit for dialogs, if you see VE table instead RPM limiters or EGT calibration, unset EXPERIMENTALS in settings.ini for a moment.
- I use AFR values instead lambda, make changes to settings.ini if you need lambda.
- Do not see on base FW build, it could be different from actual, because there is some delay beetwen FW builds and sending my codes to svn. I make names only to prevent mess.
- Make notes about FWs if you tested if, "work" or "broken" is enough
- I havent source codes for most this FWs (I use last SVN rev), it is only immediately builds, it could not be recompiled with other options, and if any FW not work it should be removed.
- Pakages are light versions, some consist MT but without exe, some only files.
- I use sometimes other aim equations for more precise showing values on my rounds, if you have bad readings, know that lamdaRaw=147 => afr=14.7 (lambda=1.0), mapRaw=100 => map=100kpa, egtRaw=900 => egt=900, speedRaw=100 => speed=100
- Some FW could contains temporary hacks, so if FW not work as expected describe problem.
http://www.vems.hu/files/MembersPage/Andrey/ExperimentalFirmwares/1.1.46.01.zip 1.1.46.01, compiled for speedsensor request, found in e-mail history, 12x12, only .hex and MT config.