Exists in current SVN, constants window, EGO Type has been there for a long time, Load multiplication, now renamed to MAP multiplication is in recent files.This seemed to have been missing for a long time (or is it hidden somewhere?) config13=06 # CONTROL_STRATEGY bit2=1 will disable MAP multiplier for all RPM bit1=1 is WBO2 enable.
MEGATUNE CONFIGURATOR MANUAL
Script for re-generating a new config.xml when all scaling is done, or manual generating after May 15.Could maybe be done without touching firmware.Misc inputs (currently 3 spare inputs, Is there easier way to configure scaling of these? Currently.Temperature sensors (Configurable scaling, not compile time).I had no idea that knock was working at all, if someone helps me with the firmware part, i'm ready to make a new megatune + firmware release on monday, who can write a simple knock config howto ? //Emil Rob is working on a knock setup section in MembersPage/PhatBob/UserGuide.So i think megatune Knock Gauge would be necessary. During tuning, i always watching the knock diff characters in the LCD, but lcd IS TOO SLOW to correctly realize knock. DONE: make a "knock gauge" in megatune, it would be very helpfull in tuning.Does MT support colums like hardcoded std_constants? Not actual bug but config pages lines are limited to 20, keep this in mind when editing inis.So if you set 70 Kpa boost than the boost target will be 140 Kpa. DONE: "Boost solenoid off below this pressure", and the boost table boost bins are divided by two.Check my page at MembersPage/GergelyLezsak/MegaTune DONE: the firing sequence during cranking is not right too (in megatune?) in firmware this is believed 2b fixed.DONE: the Kpa readings doesn't work good if i use kpafac and kpaoffset - possible solution below - DB.the "controller voltage too low for flash-burning" is annoying (at low VBatt), our eeprom (flash is not used for config) can be written even at only 4.5V.Fortunately this shouldn't bite anyone in real life. Lambda values should be limited in config. setting beyond extreme (leaner than 1.28 or richer than 0.56) lambda values overflow (at least in 3D view).Also firmware fix for unitialized variable in table reading committed to both branches. fixed MT ini used incorrect page reading lambda table. DONE: Lambda table does not work good.strange looking boost vs rpm table, this will stay this way.Prime pulse in config is changed when altering boost vs rpm table -MS.do we know any case when rpmk "RPM constant" is not 12000 / ncyl ? If it's always 12000/ncyl, we can calculate it in firmware (just define RPMK_AUTO doesn't take much cycles, and frees 2 config bytes too).This isn't a bug, but can the RPM constant be calculated by the number of cylinders (12000/ncyl) in the constants window? This causes trouble for some V6 or V8 people.Write your name here when you are actively working on the files
0 kommentar(er)
