Sequencer update/ code 3.430 release
Posted: Fri Jan 22, 2010 12:08 pm
The sequencer is ready to go into production, EXCEPT for processors. These have become impossible to get except in small spurts, and we have to use these to keep production going for current products. The earliest we expect to get any is end of Feb, and we will need those for current products. I have a ton of processors on order, but it doesn't matter, Freescale will only allocate them piecemeal to the distributors. I have tried the black market and no hits there. We are planning to grab 12 or so of them so we can at least make a few for test purposes.
Meanwhile, I have been busy enhancing the code, so I thought this would be a good time to do a release, since the code will work perfectly well on a microsquirt. BUT, this code can NOT be loaded on an MS2 because the downloader that is in it won't handle the expanded code size. The microsquirt, since it is newer, has a bootloader that will handle it. The existing Sequencers also can NOT use this code because the Router cpu (which has no serial port) would have to be reflashed with a BDM dongle, and it is not worth doing this at this time. The main reason for releasing it is for people who want to use MAF and get more out of it than possible with the current 2.890 code. This new code is meant for sequential engines, which are only possible with microsquirt and Sequencer (unless you use extra code).
The links to the download and documentation and ini files are:
code: http://www.megamanual.com/files/code/Mo ... 30.abs.s19
ini: http://www.megamanual.com/files/ini/meg ... .ini.3.430
revisions: http://www.megamanual.com/ms2/revisions.htm#latest
user inputs: http://www.megamanual.com/ms2/betacode.htm#userinputs
Sequencer differences: http://www.megamanual.com/seq/seqsetup.htm#differences
There are several things I would like to emphasize:
1. This code only works with TS because it has table download functions which are not supported in MT. I have tested the MAF table download and it works. There is a default file into which you can load a 1024 point file and a loader that will allow you to put in shorter files is in the works (it is actually there, just need someone to test and document the process.)
2. There were major changes in inputs and outputs and so you should manually change the settings (except tables can be imported) rather than use an old msq. Once you are satisfied, save it. Also, don't change default settings unless you really understand them. Note that the outputs are now 130 instead of 112 bytes, and include map as calculated from maf and rpm, and the VE that is needed to make them match. These are datalogged.
3. The above links include documentation of the inputs, but it is pretty technical. A wheel setup program is in the works to help with that and there is a good link at the very end of microsquirt.info that defines and illustrates the concepts.
4. The injector Start input is somewhat complicated (nearly impenetrable if you nhave odd fire) so leave this as 0 until you have the car up and running, then you can test if this makes a difference.
5. The first model-based concept we want to test is manifold cylinder filling which enhances acceleration fueling. X-Tau took care of the fuel wetting part, this option takes care of the air part. This has NOT been tested in a running car, but an early version was tested on a dyno engine and worked well there. So, DO NOT start out with this, get evreything else working, then you can give it a try, but be careful.
Meanwhile, I have been busy enhancing the code, so I thought this would be a good time to do a release, since the code will work perfectly well on a microsquirt. BUT, this code can NOT be loaded on an MS2 because the downloader that is in it won't handle the expanded code size. The microsquirt, since it is newer, has a bootloader that will handle it. The existing Sequencers also can NOT use this code because the Router cpu (which has no serial port) would have to be reflashed with a BDM dongle, and it is not worth doing this at this time. The main reason for releasing it is for people who want to use MAF and get more out of it than possible with the current 2.890 code. This new code is meant for sequential engines, which are only possible with microsquirt and Sequencer (unless you use extra code).
The links to the download and documentation and ini files are:
code: http://www.megamanual.com/files/code/Mo ... 30.abs.s19
ini: http://www.megamanual.com/files/ini/meg ... .ini.3.430
revisions: http://www.megamanual.com/ms2/revisions.htm#latest
user inputs: http://www.megamanual.com/ms2/betacode.htm#userinputs
Sequencer differences: http://www.megamanual.com/seq/seqsetup.htm#differences
There are several things I would like to emphasize:
1. This code only works with TS because it has table download functions which are not supported in MT. I have tested the MAF table download and it works. There is a default file into which you can load a 1024 point file and a loader that will allow you to put in shorter files is in the works (it is actually there, just need someone to test and document the process.)
2. There were major changes in inputs and outputs and so you should manually change the settings (except tables can be imported) rather than use an old msq. Once you are satisfied, save it. Also, don't change default settings unless you really understand them. Note that the outputs are now 130 instead of 112 bytes, and include map as calculated from maf and rpm, and the VE that is needed to make them match. These are datalogged.
3. The above links include documentation of the inputs, but it is pretty technical. A wheel setup program is in the works to help with that and there is a good link at the very end of microsquirt.info that defines and illustrates the concepts.
4. The injector Start input is somewhat complicated (nearly impenetrable if you nhave odd fire) so leave this as 0 until you have the car up and running, then you can test if this makes a difference.
5. The first model-based concept we want to test is manifold cylinder filling which enhances acceleration fueling. X-Tau took care of the fuel wetting part, this option takes care of the air part. This has NOT been tested in a running car, but an early version was tested on a dyno engine and worked well there. So, DO NOT start out with this, get evreything else working, then you can give it a try, but be careful.