The engine management firmware has quite a number of parameters, these are daunting to a newcomer, but vital if you want to extract the best performance from your engine.
[[Manual: Basics.Install.Upgrade]]
Config File
[[Manual: Detailed.Central.Firmware.Config]]
[[Manual: Detailed.Central.LCD.Config]]
[[Manual: Detailed.Output.EDIS.Config]]
[[Manual: Detailed.Output.Fuel.Config]]
Mik's Example files
Note that even this configuration might work for Mik, it might destroy your engine.
You must know what you are doing, that's very important.
See also GenBoard/MenuSystem for
- how to use these files (make mtt and send the mtt files with SoftwarePage/TerminalProgram) and
- how to save your config and tables into files like this (mcd and mct commands and cutn'paste)
- or how to quickly set individual parameters in the ECM SRAM and EEPROM (without files involved, in the mtt menu, mcs needed to copy to EEPROM)
Eric
Question:
I was trying upload config.mtt with bray terminal and by mistake I've selected config.txt instead of config.mtt end send it to ms avr's eeprom and receved strange signs in terminal. Ather that I've uploaded config.mtt and everithing worked fine. Now I am wondering if config.txt that I have sent is going to make some trouble, do I need to erese my eeprom and upload config.mtt and tables again, and if I do how can I do that?
Answer:
Verify if your flash is what you used to write in (vems.hex: bootloader prog.pl verifies it in a sec or or avrprog in a minute...). The problem is that if you happen to activate the bootloader (mcbffmcb) with the dummy strings you send to AVR, there is some chance you can hurt the flashcontent (atmel used very simple commands in the protocol...). The chance is very small, but still there. So verify. If you don't have the vems.hex, which you uploaded (you made another mistake there too, then!!) just upload a new.
Got tired of doing HEX-conversions and figured, that others felt the same.
Created a small Win32 app to do it for me (Yeah, I know i'm supposed to do a nifty Perl-hack, but thought that the not-so-nerdy-ones should have a go at it too...).
Get it here: http://80.196.115.45/install/InitialTables.zip
/Nolan
I improved bin/make_table.pl so anyone can use decimal numbers and even real-world units in the tables.txt file, after\n
numberformat=10 or numberformat=real
- You can switch numberformat after each line if you like
- Default (everything in the file before an explicite numberformat=.. statement) is numberformat=16 (which is for hexa) so old tables.txt files are not broken.
- numberformat=real multiplies by 4 n (ignition) table values, so the crankdegree unit is converted to ECM's internal 1/4 degree representation. numberformat=real gives undefined result (don't use) for j and l tables
TODO:
- support other number-system (eg binary: numberformat=2)
- add same to config.pl
- allow 0x.. and %.... format even if default is decimal (to input hexa or binary numbers without changing back and forth)
TODO: this page should be splitted to sections:
- PortInjected (injection parameters)
- DummyIgnition or EdisIgnition, (IgnitionPage)
- IdleControl
- WideBand, NarrowBand
- GenBoard/LcdFaQ
- GenBoard/KeyBoard
Misc...
Following some complete docs structure (Autronics?) would be a good idea. Mostof these are started, but unorganized. Finally all these texts will be integrated into jtune, the new experimental tuning software (so it must be splitted to individual parameters and flags)...
See also
- GenBoard/Manual is the new matrix that we use for explaining config parameters. Please move config parameter info into the page referred from Config column (make up the link and even the page if needed, try to reuse existing pages)