Printable View
Would it be posible to modify the 16188051 to run with a (Northstar DIS, 60* V6 DIS, Quad 4 DIS, etc) instead of the optispark module? Is there anything specific with the 16188051 hardware that will cause it not to work with a DIS? Looking at the possibility of using the 16188051 to use in place of the ECM's on DIS motors.
i don't see why it couldn't work. the code is expecting to see 90 pulses between 4X reference pulses. i don't see why that section of code couldn't be removed and simply run it as a "low" res 2, 3 or 4X system.
it's the rest of the code that would bother me on a completely new application.
The 4x being different wouldn't be a problem? I could be wrong, but I though the 4x out of the DIS modules had symmetrical waveforms vs the long/short of the optispark.
I would imagine adding a separate cam sensor for a SFI system would be a small feat. Timing for SFI would already there, just based on the asymmetric 4x sensor.
How so?Quote:
Originally Posted by RobertISaar
the signals from the normal DIS modules are about 50% duty cycles... but the PCM only watches for the falling edge IIRC. it SHOULDN'T matter because of that, but it would be hard to tell if it will cause a problem until it is built.
not that i care for SFI, but yes, it is all there. how well code intended to only ever be used on an 8 cylinder application works on a 4 or 6, no idea. the code does check the firing cylinder # in quite a few places, just need to make sure it will reset after the final cylinder fires rather than count up to 8 and reset. stuff like that would bother me. it's hidden pretty well in the algorithm a lot of the times.
Yea, I have a thing for SFI; its not fully rational and I admit it. I had a 94 LQ1 I switched over to 93 $DF, stock all the way around and went from 32mpg to 29mpg. The 94 $2e also ran smoother but that could have been a MAF vs MAP thing.
That makes sense. My understanding of things is going on half a decade of neglect, but would it alright to assume that once the cylinder counting is taken care in its various spots of and it works thats the end of it? eg, there wouldn't be other hidden spots that only get called under certain circumstances?
good question.
no idea.
the only experience i have with the 8051 is disassembling the BINs and somewhat making sense of them. i would ASSUME when cylinder count is dealt with in calibration and in the couple of spots i remember seeing it hardcoded in the algorithm, it will work as if it were built to run anything that gives it reasonable signals. obviously stuff like cylinder size and 4X signal offset would need to be dealt with, but that is a given.