Here's a somewhat rhetorical set of questions:
How does a PC-* retard ignition timing? That'd be easy; merely hold on to the coil signal before passing it along.
How does a PC-* advance ignition timing? That'd be easy; merely hold on to the coil signal until just before the next time.
In either case, I wonder just how this affects the functionality of the Ion Sense output polling by the ECM which is surely perusing it a fixed time after sending the spark signal...
PC has it's own coil drivers and does it's thing based on what the HD ECM timing signal is.
ION sense adds fuel - PC won't defeat that
ION sense retards timing - PC will simply do it's thing on top of HD ECM.
I'm aware the PC has its own coil drivers. My point is that if you're retarding spark 2° somewhere, it's easy-enough to do the math and say that'll be 1/180 of a crank revolution, wait until then after intercepting the signal, and send the new signal. But if you're
advancing spark 2° somewhere, there's no way predict how to send the signal 1/180 of a crank revolution
before the ECM sends
its spark signal, so what you'd have to do is hold onto the timing sent from the ECM
this time, and send your own signal 359/180
later. Obviously this would leave out a spark
this time, so maybe the spark timing is always delayed by one full engine cycle from when the ECM sent it.
Now if you consider
http://delphi.com/manufacturers/auto/powertrain/gas/ignsys/ionized/ you'll see that the Ion Sense circuit is passive and always functions immediately after a spark event. The ECM "listens" to that circuit output and the ECM knows that what it's looking for is going to be happening a fixed time after the spark event was initiated. So here we'd have a situation where the ECM is sending a spark signal, then listening, but the actual spark event didn't occur when the ECM thought it did (and the ECM has absolutely no way of knowing why this might be or to expect or even consider the possibility). How can the Ion Sense system work properly under these conditions? It's a crap-shoot at best.
So not only with a PC-* are you disabling closed-loop operation (if you had it) but you've just about got to be "dicking" with the Ion Sense system as well. I would not consider this a cost-effective measure. Saving a few bucks on a system to address fuel and spark timing, but also wasting monetary value already possessed.
I guess that's the
main point I was getting at...