megatune is old, use VemsTune tuningsoftware
EVERYTHING BELOW is OLD ... Downloadable megatune and firmware matched and packaged releases
Some windows freezes when logging 62 bytes blocks of realtime data (D command, that 1.1.12-1.1.27 uses) instead of 56 bytes (A command, that 1.1.1 uses below). This is a bug in the pl2303 usb-adapter windows driver (or operating system). If that happens, 1.1.1 can be used for logging (the difference in dialogs between 1.1.1 and 1.1.27 is small anyway, ve and igntable should work well).
IMPORTANT: new megatune vemsv3.ini must be released with 56 byte realtime logging (A command), the extra data (D command that also contains per-cylinder performance data) must be optional (eg. available with high-boost 12x12 choosable at startup).
Changelog
- [VemsMT1.1.47alpha2]
- Check included changelog!
- Also GenBoard/UnderDevelopment/FirmwareChanges for details on changes pre this release
- [VemsMT1.0.79alpha]
- Check included changelog!
- [VemsMT1.0.78rc2]
- Working bat files
- Updated makeconfig app that handles extended configurations correctly.
- New makeconfig binaries for extended configurations available here [makeconfig.zip]
- [VemsMT1.0.73_20080901.zip]
- Upgraded bat-scripts for easier maintenance with the tools (firmware upload, temperature sensor calibration).
- Those who handle 1.0.78 package in SVN could incorporate the scripts to make things easier to handle. One "config" bat-file for communication port settings, also made table-size as arguments to the scripts. Available here: [vems-bat-scripts_1.0.zip]
- [VemsMT1.1.27beta2.zip] is a quick workaround hack to revert from "D" to "A" command for runtime datalog
- See the adapter cable windows driver bug on IssueReports that made the serial driver unstable with certain windows/notebook when the 62 byte datablock was queried with "D" command
- TODO: use an uptodate vemsv3.ini file for a proper "D" => "A" conversion (using ifdefs), this is a hack (deleted nonrelevant parts and apparently from older vemsv3.ini, the high-boost_12x12 seems usable, low_boost_12x12 pretends as if it was highboost and the 16x14 unknown)
- [VemsMT1.1.23rc] - Full package with firmware 1.1.23 both 12x12 and 16x14 table support.
- since the 1.1.23 is only for InputTrigger/AudiTrigger, use 1.1.18 (or whatever suggested by GenBoard/UnderDevelopment/FirmwareChanges for your setup), but this megatune can be used for 1.1.18 as well (no major changes). The h[2] "ignition output sequence" must be set when engine is off (of course) and verified with mct before starting (make sure you have proper fuses, it's easy to make a config error that blows the coil or the fuse. The good way is if the fuse protects the coil, not the other way around.
- [VemsMT1.1.1-pre0.zip experimental prerelease]
- TODO: test [V3GUI] : a GUI-tool (zip for windows, but also available on linux, ask if you need it). This will replace .bat scripts. Hopefully now contains the dlls so it should run on all windoze (note that previous also ran fine on a few windowses they were tested on - likely the dlls were there for some other reason. Test means "test"; it's for testers and advanterous users; but getting better all the time and now seems useful). Functions:
- Upload/Verify firmware
- Upload/fetch config/table files
- Generate trigger wav sound files
- based on user-input parameters
- based on trigger.ini pointed by the user
- or based on trigger.ini file found in the dir of the config file when/which the user chooses to upload (TODO: do this automatically)
- user can choose coolant/air temperature tables (EasyTherm - hexpatch way) for firmware upload and verification; Very handy. Test if it works for you. Note that you can save (and load) firmware sessions that remembers these settings.
- DONE: GenBoard/Manual/MatRetard (actually, firmware change without any megatune aspect)
- DONE: appear "MAP(load) mult" at another place where one would expect (at hybrid...RPM settings)
- DONE: h[1]
- DONE: ALS and launch input selection
- TODO: h[2] almost OK, but make sure MT resets bit0:2 and bit7
- maketables.exe should examine h[2] upper nibbles: if all are 0, than swap upper and lower nibbles to gracefully migrate to new h[2] semantics, where i259 outputs are 0x00,0x10...0x70 and s259 outputs 3..6 (stepper A..D) can be used for ignition with bit[1]>0 eg. 0x38,0x48,0x58,0x68)
- done ? merge changes in stable1_0 vemsv3.ini (curve-editor?)
- TODO: drop makeconfig.exe (and maybe all the .bats?) makeconfig.exe should not write unspecified vars as FF (done in svn, just need to be compiled)
- TODO: drop sh.exe
- [ VemsMT1.0.65-pre0.zip] has stable1_0 firmware (with recent stable1_1 changes merged)
- minor TODO: get rid of VEMS2 undefined (vemsv3.ini L326) error
- TODO: test [V3GUI] : a GUI-tool (zip for windows, but also available on linux, ask if you need it). This will replace .bat scripts. Hopefully now contains the dlls so it should run on all windoze (note that previous also ran fine on a few windowses they were tested on - likely the dlls were there for some other reason. Test means "test"; it's for testers and advanterous users; but getting better all the time and now seems useful). Functions:
-
[VemsMT1.0.73] - Full package with firmware 1.0.73 both 12x12 and 16x14 table support. The vems.co.uk zip has an error in the vemsv3.ini for the ignition outputs (h23 = h22), fixed in this vems.se zip.USE WITH CAUTION- NOTE: if upgrading from 1.0.53 or older you will need to type this in by hand
- Manttg20h00g21h00g22h00g23h00g24h00g25h00g26h00g27h00mcsbye
- [VemsMT1.0.69.zip] - Full package with firmware 1.0.6
- Now includes generate-configWithWBO2Defaults.bat which ensures that the factory recommended wideband settings are correct. Does not effect unit specific (pump_pw_zero, nernstdc_target and wbo2_calibration) settings.
- NOTE: if upgrading from 1.0.53 or older you will need to type this in by hand
- Manttg20h00g21h00g22h00g23h00g24h00g25h00g26h00g27h00mcsbye
- [VemsMT1.0.53.zip] - Full package with firmware 1.0.53
- Warmup wizard does not save changes for certain variables and writes other over the VE table. USE WITH CAUTION!!
- [VemsMT1.0.36.zip] - full package with firmware 1.0.36
- [VemsMT1.0.30rc3.zip] Renamed the full package for less confusion
- Lots of improvements in megatune, Curve editor (boost vs rpm table), plugins (Tools / Vemslogger Viewer), nicer Table Editor
- It is now possible to inactivate profiles according to your own taste, check the Profileactivation folder in the zip.
- Notifies user of which code is chosen
- temp calibration upload script
- readme.txt file
- improved .bat scripts
- minor changes in megatune dialogs
- please report errors on the IssueReports page
Instructions to make it work:
- download complete package above
- unzip to a directory of your liking
- use "download_config.bat" to fetch your current config from ecm or copy your existing config.txt and tables.txt to VemsMT-xxxx/config
- update your config (if required) with the config changes that may be there between the firmware version you currently used and the version you are about to upgrade to, see GenBoard/UnderDevelopment/FirmwareChanges for details on changes. YOUR CAR MIGHT NOT START OTHERWISE OR YOU MIGHT GET UNWANTED BEHAVIOUR !
- issue a "generate_config.bat"
- closely inspect the generated log files (config.log and tables.log) too see if you missed anything
- flash firmware your v3.X using "upload-firmware.bat" from the directory
- optionally run "tempsensor_upload.bat" to configure your temperature compensation tables (default is clt and iat = 2252).
- upload your tables.mtt and config.mtt to ecm using upload-config.bat"
- Reboot the ECM (cycle power)
- browse to the VemsMT-xxxx/MegaTune2.25 dir and execute megatune.exe
- select the profile that matches your firmware
- start tuning your engine
Megatune and firmware for old genboard v2.x
Several v2.2-s are running, installed and tuned years ago. It is recommended that install specific data including docs,wiring,versions,config,firmware,megatune,tools etc) is kept (and backed up) safely, and passed along if ownership changes (please be nice to the new owner: the advantage of a self-tunable system is gone immediately if access to this info is hard, and it can turn into a blackbox nightmare).
MembersPage/SamiKorhonen has some v2.x firmware compiled from recent code, and megatune he uses for it.