Toolman said:
Okay, my ECT is not working right. Keeps throwing code 118, ECT @ -40 or something. This sensor and it wires are very close to my DP gasket, and it blew last year and melted a few things in the vicinity, so I have a feeling the wiring harness was damaged right here. My fan does not come on when it should, so something is amiss.
Given the fact that both V6 SHO strategies utilize ECT sensor readings for a good number of their functions and tables (many of which are not yet accessible with the existing version of CalEdit), I would highly recommend that you repair and replace both your ECT sensor and it's harness as soon as you possibly can, Tim. Proper ECT sensor readings are crucial when calculating proper fuel and spark delivery under many different scenarios, something which isn't possible if your ECT isn't reporting the correct voltages and a point which becomes doubly important when discussing a boosted application.
That said, I would recommend that you set your 'WOT Spark Advance vs ECT' function to a value of 0 across the board until such a time when you are able to repair your ECT sensor harness and verify that the correct readings are being fed back to the EEC (via CalCon).
Toolman said:
There is a 'spark advance rate vs RPM' function as well as a 'WOT spark advance vs RPM' function.
The 'Spark Advance Rate vs RPM' function is used to determine how much advance is applied within a given time frame, while the 'WOT Spark Advance vs RPM' is the advance curve that is used before the other adder/retard functions once throttle position (as indicated by TPS readings) has exceeded the specified WOT breakpoint.
When modifying these two functions, keep in mind the following:
- while the factory MTX advance rate curve could stand some improvement, I would not exceed more than 2 degrees/sec at any point in the curve when modifying this function, especially in a boosted application. Doing so could result in the EEC advancing the timing too quickly and could easily encourage preignition on some setups.
- the WOT spark advance function is also supplemented by the other adder/retard functions you see grouped in the Functions listing (ECT, ACT, etc). As such, you should not look solely to the WOT spark advance function when attempting to calculate total WOT advance, nor should you be surprised if the amount that you are seeing is more (or less) than what you've entered via the WOT spark advance function.
Sho-Driver said:
All he needs to do is graph boost vs RPM and map timing out from there. For a first tune to work with, I would back off timing to about 22-24 degrees at max and work up from there until you see detonation. You can watch detonation on your TwEECer by watching timing advance. You know what timing is supposed to be at a given RPM, you just make sure it does not kick back 8* and you're not going to blow a piston.
While the above advice regarding boost vs. RPM mapping is quite sound, I wouldn't recommend utilizing the above method of knock detection on any SHO unless you know exactly how much advance you should be seeing for a given RPM (a job that is not easy thing to accurately pull off, even on an MTX with it's reduced number of adder/retard functions). IMO, the better solution would be to purchase, install and adapt a seperate but dedicated knock link monitor to your setup and monitor the readings via CalCon. Doing this will allow you to datalog the knock readings with the rest of your variables (allowing you to map the knock readings against RPM, load, etc.) and will allow you to be more accurate than you would be if you utilized the former method of "assuming" your total amount of advance.
Sho-Driver said:
The computer will retard the timing up to 8* from where ever it is set at. At what ever RPM he's running 28* advance, the computer can knock it down all the way to 20* if detonation is happening.
Actually, the maximum amount of spark retard for all V6 strategies is 10 degrees.
