History of MegaTune/ErrorNew
Older Newer
2006-09-07 11:55:53 . . . . MembersPage/DaveBrul [cleanup, issue report should go to apropriate pag]
2006-03-29 15:01:09 . . . . EmilLarsson [als offset]
2006-03-29 06:17:46 . . . . MembersPage/MarcellGal [spark advance in megatune or LCD ? report useless w/out mcd dump]
2006-03-28 15:09:40 . . . . dsl51B7889F.pool.t-online.hu [MT shows BAD spark adv. values,log also affected]
2006-03-22 02:32:45 . . . . MembersPage/DanaScott [example of error]
2006-03-22 01:42:23 . . . . 212.149.207.208 [timing.c missing]
2006-03-21 07:19:37 . . . . MembersPage/MarcellGal [internal temp note]
2006-03-15 01:27:35 . . . . DanaScott [MT coolant fan settings]
2006-03-14 22:04:54 . . . . MembersPage/DanaScott [MT coolant fan settings]
2006-02-21 00:43:17 . . . . MembersPage/MarcellGal [report is useless without mcd, mct dumps]
2006-02-16 10:10:02 . . . . 68.33.119.91 [beta reports on 1.0.34]
2006-02-16 03:35:11 . . . . MembersPage/GrmRacer [Beta Testing methodology & reports 1.0.34]
2006-02-13 10:47:15 . . . . MembersPage/GrmRacer [r028 & r030 error reports... beta testing at its best..]
2006-02-13 09:47:06 . . . . MembersPage/GrmRacer [VemsMT1.0.30rc3.zip report]
2006-02-13 09:43:45 . . . . MembersPage/GrmRacer [VemsMT1.0.30rc3.zip error report..]


Changes by last author:

Changed:
1.0.36

will not show more then 23deg ignition (MegaTune or LCD?), though in Spark Map/table there is significantly more.Log shows also bad 23 degs all the way.Looks like real spark advance is changing above 23deg,but still have to check that with strobe...//

Remember that an mcd dump is needed to reproduce behaviour. Nanassy.Peter

A: You most likely have a huge (40 degrees) ALS offset, which steals from maximum advance. Change this to some reasonable value, like 20 instead. As marcell writes, impossible to know without a config to look at, but this is a good guess //Emil

-----

VemsMT1.0.30rc3.zip

----

timing.c missing from zip.

----

Mar-14-06 - reported by Dana Scott

In Fan,Water and Fuelpump settings. If I set Coolant fan start temperature to 70 degC, the config value on my LCD value changes to C6. 71 degC gives LCD C8.

This is correct, since the internal format is still degF+40 (71 * 1.8 + 32 + 40 = 200 = 0xC8) unless the tables changed by the tuner (eg for wider range. In this case LCD and megatune with default vemsv3.ini will read fake, eg. 10C lower than reality)

* All documents I can find [this one for example, line #405] call for units in degC .... where? are they about the internal values? note that there are plans to change this for wider range anyway: GenBoard/UnderDevelopment/FirmWare/CoolantTemperatureRange

* Clicking on either 'Fetch from ecu' or 'burn to ecu' will send the value to the ecu.

* The hysteresis value is off by one. MT 8 gives LCD 7

----

First pass at this has the following results

* Unzipped, flashed with supplied firmware

* Deleted /config/*.mtt

* generate_cofig.bat ran -- no errors

* upload_firmware.bat -- reports: Precompiled version 12x12 Standard Boost

* upload_config.bat -- reports

** config.mtt @2049 char sent

** tables.mtt @ 4017 char sent

* Ran Megatune selected 12x12 standard boost

** VE, Spark, lambda table all report 8x8 in megatune

r028 complete package, with 1.0.23 firmware

* used standard flash and attempt to install technique.

* Initial Firmware flash looks good

* Initial generate config / table _.mtt looks good

* Upload_config looks odd, config is ~17char

** found that WinTools\makeconfig is not working correctly

This is the generated output

<code>

Mantt

mcs

bye

</code>

Ran r30 \Tools on r28 distribution it at least reported errors ( complained about shiftcut)

-----------------

Currently under Beta test for emil_

VemsMT1.0.34-testingonly.zip

emil_ provided a download place for me to test.

Givens:

* I have several versions of MegaTune installed.

* I am pretending to be a user for installation and use

* I will not be compiling anything -- only precompiled firmware

* To test I need a complete zip file that has everything where it needs to be already.

* /config with contain default config.txt and tables.txt

Proposed Check sequence

Steps to be checked

* Unzip file

* delete /config/*.mtt

* run in the following order

** upload-firmware.bat

** generate-config.bat ( check for valid table.mtt & config.mtt )

** upload-config.bat

** start provided MegaTune and ensure communication

** run megatune review mode

* report errors

** any errors during any of the (3) batch files

** any errors during boot-up and review mode of MegaTune

** any precompiled (8x8 or 12x12) / MegaTune table errors

Configuration changes from MegaTune

* change primary trigger setup to 60-2 VAG wheel

* change injector output to batch

* change ignition output to wasted spark

* check redline

* check fuel pump control output ( INJ fet and S259-5 )

* Trigger unit and make sure it reads values

* WBO2

** Check pump_zero

** Calibrate o2%

** Breath test

* Output configuration

** INJ change to 2 or 4 bank outputs re-arranging combinations of outputs ( firmware people should suggest combination checks )

** ING change 2 or 4 wasted spark setups (ie. wasted spark COP or is this the dual_ign mod??)

------------------------------

Test Results:

* using 1.0.34 combo.

* VE in realtime display

* MAP is constant (= ?), RPM varies (from .. to ?).

* Set VE to 131 in all RPM position in particular row (#3 up from bottom)

** full mct dump ? (ve and k and r tables too)

* VE varied from 128-133

* Set VE in table to 131 in all positions

* from Row#1 -- Row #5

** VE in RT display varied from 129-130

* Full mcd dump ? Particularly, kpa_conf is interesting. With wrong kpa config unit, the experimental megatune might say "20 kPa" for a line which is in fact for 40 kPa

Basic results:

* deleted *.mtt files in \config

* generate_config.bat reports 2 errors

** iac_integral_speed in config.txt not in global

** did not find launch_rpm in config.txt

** generate_config.bat made *.mtt files

** upload_firmware.bat reports: Precomiled version reports 12x12 standard boost

** flash successful

** turn off advanced filtering and works fine.

All new MegaTune profile or profile firmware combination errors and/or issues should be reported on IssueReports page
Added:
See also: MegaTune