=== Mega Tunix === (in irc shorthand: "mtx")
This has been dropped. Not supported for years now.
Mega-Tunix is tuning software written for Linux and Mac that uses the GTK+2 libraries. It has been also compiled for Win32.
MegaTunix is highly configurable to support different firmware data-mappings.
Note that new 0.7.1 [megatunix (sourceforge project page)] has some fixes (in interrogation files) that helps VEMS. It might be much better than above data-mapping: I think Dave Andruczyk started from above configs (otherwise warmup enrichemnt will read/write other config variables, so you'll see if you watch). Please test and write your results here.
GenBoard firmware running on GenBoard/VerThree or GenBoard/VerTwo with MSNS defined, but MS_COMPATIBILITY not defined in my_make (as it is in released firmware from GenBoard/UnderDevelopment/FirmwareChanges).
Tune (3D or 2D)
- VE table
- Lambda table
- Spark table (ignition advance)
- Cranking pulsewidths
- Afterstart enrichment parameters
- Warmup enrichment parameters
- and Take datalogs and view them
Starting it up
Start it from a command window (eg. cmd from win)
- cd _directory_where_megatunix_version_xxx_ was installed (different versions can be installed to different directories)
- check below for slight tweak for nonstandard (not 250kPa) MAP sensor range
- megatunix.exe 2>mtx.err
- check that your serial device (eg. COM1 or /dev/ttyS0) is selected properly
- test ECU communications
- Interrogate ECU - this should find out your firmware type if the above configuration and firmware is used.
Starting megatunix with standard-error redirected to a file is better than starting by clicking a megatunix.exe icon on the desktop, because you can see mtx.err (that has megatunix log) file (with a text editor, such as notepad). Logging can be made more verbose with selecting debugging options (eg. Serial read, Serial Write, interrogation) in "General". Especially useful
Other tweaks and notes - should not be needed
It works without MSNS in my_make (with minor tweaks in interrogation profile: remove CMD_UPPER_I=95 - this is the bytecount in the interrogator profile for I command) but it will not read nor write the spark table. Even if you don't compile your firmware yourself, you can check the my_make in the released directory.
If you try the firmware/doc/megatunix configuration from the CVS head (should not be needed, try the above easily downloadable zipped config directory), make sure to remove CVS/ directory from all subdirectories (not just the main directory, there is a CVS/ dir in all directories).
More info - Installation is platform specific
Both versions are still in Beta.
- New home page [http://megatunix.sourceforge.net/ ]
Communication protocol: MegaTunix/Protocol
Megatunix author: David Andruczyk
Developers - everything below this point
- MegaTunix/ToDo - what's needed of MegaTunix to make it GenBoard compatible. both strategy and short term todo
- A Linux based Live CD might be worth investigating. MegaTunix/LiveCD
Relatively Old News
Megatunix recognizes a Genboard. :)
What to do:
There is still work to be done. This does prove MegaTunix works with Genboard though. The 'S' command and '?' command should be completed sometime. The data in the tables should also be tested to be sure it updates the firmware memory correctly before you try tuning a car with this!
I think there's a LOT of optimization left with the Profile and Gui. Help Wanted so to speak. :)
Download the source with CVS:
setenv CVSROOT :pserver:firstname.lastname@example.org:/cvsroot/megatunix
cvs co MegaTunix
just run "./autogen.sh" as it does all that...
Q: Who is working on the datamaps for MTX so we can get a button and screens for MTX? I'm going to be home all day tomorrow and if anyone need me to help them just give me a holla on mIRC. I don't know much about programming or anythign but would love to help
There's a bug with the way that Megatunix does interrogation, and the 'v' command. Megatunix's interrogation of the genboard will only work if the current page happens to be 0 (either after a powercycle, or because it happened to be set that way). A quick fix to this, is to change Megatunix's interrogation tests to always reset the current page to 0. This is a huge hack, but it means you can keep using an existing Megatunix binary without running into the issue.
[interrogation_tests] total_tests=13 [test_00] raw_cmd=p cmd_length=1 multipart=TRUE cmd_int_arg=0 cmd_desc=Reset ECU to page 0. store_data=FALSE
... and renumber all subsequent tests appropriately. A properly modified version of the tests file can be found here:
We are experimenting with MegaTunix.
The log is very nice and useful, you just have to turn on log for serial reads and writes and check the stderr output.
- the above "tests" file from Alexander
- in the "~/.MegaTunix/Interrogator/Profiles/Genboard?_8x8.prof" I had to adjust the VerNumber?=30 (from 20)
- defining MSNS in my_make (MS_COMPATIBILITY not defined) seems like a good idea, it just adds a few new commands. However we had to add CMD_UPPER_I=95 to the bottom of the interrogation profile.
- comm.c mt_config_var lookup table is bypassed, which means megatunix tried to read/write variables to the bad location. We changed the warmup...datamap to have the proper offsets.
Quick fix for kpa reading for nonstandard (not 250kPa) MAP sensors
Needed to get good mapkpa reading (correct moving-dot position) for sensors other than the standard 250kPa sensor. Eg. Marcell's kpafac=34 (52 decimal, that is 104 kPa / 5V) sensor:
Change the dl_conv_expr and ul_conv_expr in derived_17 section like this:
[derived_17] .... dl_conv_expr=(x*1000)/403 ul_conv_expr=(x*403)/1000 is_float=FALSE ....
Note that "ul_conv_expr=x*0.403" will not work, so just edit the 403 that is proportional with your sensor range: bigger for higher than 104 kPa MAP sensor). This makes it possible to use other MAP sensors as well, not just 115kPa and 250kPa.