Spark Advance Table Generation
Posted: Sun Feb 15, 2015 7:48 pm
Hello all!
I am currently planning a EFI conversion of a '72 Opel GT and as a result have been digging through every piece of documentation from the MegaSquirt sites, aided by my trusty Heywood and Blair textbooks.
I don't have a specific motivation other than really as a learning event (I am a college student studying combustion), but I am interested in the more specific rules which are being used to create the spark tables here: http://www.useasydocs.com/theory/spktable.htm
I noticed when a different table size is selected and no other modifications are made to the input variables, very odd and unexpected behavior in the construction of the spark tables can occur. I would expect to simply see finer granularity, however what I end up seeing sometimes is a complete loss of the 'curve' idea and a simple shortcut to max advance at max rpm.
I would really like to be able to see the code which is generating the tables so I may more specifically see how the 'rules' are driving the table. I understand there is a version of these rules here: http://www.useasydocs.com/theory/advrules.htm. However there seem to be additional constraints coming in to play in the auto-generating table code.
Does anyone know how I might be able to view the math going on behind the scenes in the spark advance table generator?
Thank you for any input you may have!
Jay
I am currently planning a EFI conversion of a '72 Opel GT and as a result have been digging through every piece of documentation from the MegaSquirt sites, aided by my trusty Heywood and Blair textbooks.
I don't have a specific motivation other than really as a learning event (I am a college student studying combustion), but I am interested in the more specific rules which are being used to create the spark tables here: http://www.useasydocs.com/theory/spktable.htm
I noticed when a different table size is selected and no other modifications are made to the input variables, very odd and unexpected behavior in the construction of the spark tables can occur. I would expect to simply see finer granularity, however what I end up seeing sometimes is a complete loss of the 'curve' idea and a simple shortcut to max advance at max rpm.
I would really like to be able to see the code which is generating the tables so I may more specifically see how the 'rules' are driving the table. I understand there is a version of these rules here: http://www.useasydocs.com/theory/advrules.htm. However there seem to be additional constraints coming in to play in the auto-generating table code.
Does anyone know how I might be able to view the math going on behind the scenes in the spark advance table generator?
Thank you for any input you may have!
Jay