Re: Engine #11 Andy's 1996 GM 3.1L V6 in a 1932 Ford Coupe
Posted: Sat Mar 17, 2012 8:35 pm
Andy, can you tell me the range of timing marks that your pulley has? I ask because we'll need to differentiate between DIS default timing and whatever we do. Ideally we'll need two check points besides the 10btdc marking. If the timing marks go from 0btdc to 20btdc that would be ideal, however 5-15 would also work. We'll set it to 10btdc in the code for the first 1500RPM then X higher than that for the second 1500 (up to 3k), then X lower the rest of the way. This should create a retard limiter effect to keep you safe while testing :-)
Can you please commit your config changes and push them to a temporary branch so that I can tweak them to work with DIS. Do that like this:
You'll need a fork of the firmware on there in order to push like that, and to have it set as your origin in your .git/config file.
Lastly, what is the polarity of the bypass signal requirement? Ideally it would be processor low by default and processor high to enable FreeEMS controlled timing. Same goes for the EST signal too, ie, trailing edge of processor high (processor goes low) = fire. If you used an XOR and those signals match, then it will be straight forward to configure them correctly in hardware.
If we get this sorted out ASAP maybe we can work together on the phone tomorrow to get it running properly right there and then. If you have time after dinner to push the config and answer the questions that'd be awesome, if not, no stress. I'm going out for dinner too and may be in no shape to do any work :-)
Fred.
Can you please commit your config changes and push them to a temporary branch so that I can tweak them to work with DIS. Do that like this:
Code: Select all
cd src
git add .
git commit -m "Temp config commit for Fred." .
git push
Lastly, what is the polarity of the bypass signal requirement? Ideally it would be processor low by default and processor high to enable FreeEMS controlled timing. Same goes for the EST signal too, ie, trailing edge of processor high (processor goes low) = fire. If you used an XOR and those signals match, then it will be straight forward to configure them correctly in hardware.
If we get this sorted out ASAP maybe we can work together on the phone tomorrow to get it running properly right there and then. If you have time after dinner to push the config and answer the questions that'd be awesome, if not, no stress. I'm going out for dinner too and may be in no shape to do any work :-)
Fred.