Académique Documents
Professionnel Documents
Culture Documents
Crank/Cam Setup
and Diagnostics
As of 2011-08-17
Ford TFI
ECU utilizes stock module for signal conditioning of Hall pickup in
distributor and switching coil primary current
ECU is triggered on the rising edge of the modules PIP signal at
~2.3V
An internal pullup is activated for the crank/PIP
The module controls timing and dwell for both start and run
The SPOUT signal is generated by the ECU to control timing and
dwell. Dwell is active when SPOUT is low, and spark happens when
SPOUT signal rises.
Baseline dwell is ~3.5ms, but will be reduced to keep non-dwell
>0.5ms at high speeds.
One vane of the target in the distributor is shorter than the others,
which allows the ECU to sync without a cam sensor
If the ECU cannot resolve the narrow pulse, the tens digit of the
Diag#1 variable will increment
GM LSx 58 Tooth
Crank input reacts to the falling edge of the crank sensors signal at
~2.3V
Cam input decodes both edges of the cam sensors signal when
crossing ~2.3V
An internal pullup is activated for the crank and the cam
The ECU decodes the 60-2 crank pattern and the 4x cam pattern. The
4x cam pattern should be within 90 crank degrees from the stock
location for proper decoding
Eight individual EST signals are generated by the ECU to control
timing and dwell. Dwell is active when EST is high, and spark
happens when EST signal falls.
If the cam signal drops out, falls out of proper phase, or cannot be
decoded (not a 4x pattern) the Diag#1 tens digit will increment
If the crank signal drops out the Diag#1 hundreds digit will increment
Extra or missing crank pulses will increment the Diag#1 tens digit
GM LSx 58 Tooth
GM LSx 58 Tooth
GM LSx 24 Tooth
Crank input decodes both edges of the crank sensors signal when crossing
~2.3V
Cam input reacts to the falling edge of the cam sensors signal at ~2.3V
An internal pullup is activated for the crank and the cam
The falling edge for the cam must happen between approximately 250 crank
deg before #1FTDC and 90 degrees after #1FTDC. There can be multiple falling
edges in this window, but none outside.
Eight individual EST signals are generated by the ECU to control timing and
dwell. Dwell is active when EST is high, and spark happens when EST signal
falls.
If the crank pulse width pattern is not recognized the Diag#1 tens digit will
increment
Missing crank pulses will increment the Diag#1 ones digit
Extra crank pulses will most likely increment the Diag#1 1k, tens, and ones
digits
Missing cam pulses will increment the Diag#1 tens digit
Extra cam pulses in the wrong place will increment the Diag#1 ones digit
GM LSx 24 Tooth
GM LSx 24 Tooth
Crank input reacts to the falling edge of the crank sensors signal at ~2.3V
Cam input reacts to the falling edge of the cam sensors signal at ~2.3V
An internal pullup is activated for the crank and the cam
The ECU decodes the 60-2 crank pattern and uses the cam pulse to establish cycle
sync
The crank tooth before the missing teeth establishes the valid window for the cam
signal. Nominally this is at ~78deg BFTDC#1, which means the falling edge of the
cam signal must be between 78 crank degrees before FTDC#1 and 438 degrees
before FTDC#1. To make it easy to remember I recommend 180 crank degrees
before FTDC#1, or BDC before compression.
Eight individual EST signals with two events per cycle are generated by the ECU to
control timing and dwell, but only four are used. Dwell is active when EST is high,
and spark happens when EST signal falls. Baseline dwell is ~1.8ms.
Extra or missing crank pulses will increment the Diag#1 tens digit
If the crank signal drops out the Diag#1 hundreds digit will increment
If the cam signal drops out, falls out of proper phase the Diag#1 tens digit will
increment
Extra cam pulses in the wrong place will increment the Diag#1 ones digit
Custom
There are options to use various combinations of target
geometry and sensor types for crank and cam
The ECU detects the falling zero crossing for magnetic
sensors, which is the opposite of many aftermarket
applications
Try to avoid magnetic cam sensors: Hall effect sensors
function much better during cranking and at low speeds.
The ignition output type and dwell are also selectable
The Points Out selection is to trigger a Points Input
of another device, NOT to drive a coil directly
EST outputs are logic signals and are not for driving
strongly biased inputs (CD box inputs)
Normal
Diag#1 Ones Digit- Steady
Diag#1 Tens Digit- Steady
Calculated RPM- Steady
Extra Crank Pulses Can Cause Real Pulses to be in the Blanking Window
If a noise pulse happens just before a real crank pulse, the noise will be treated as a real pulse and the real pulse will be
disregarded as noise. This can cause a timing shift.
Diag#1 Ones Digit- Steady
Diag#1 Tens Digit- Steady
Calculated RPM- False High Followed by False Low, or it could also be steady
Extra Crank Pulses Can Cause Real Pulses to be in the Blanking Window
If a noise pulse happens just before a real crank pulse, the noise will be treated as a real pulse and the real pulse will be
disregarded as noise. This can cause a timing shift.
Diag#1 Ones Digit- Steady
Diag#1 Tens Digit- Steady
Calculated RPM- False High Followed by False Low, or it could also be steady
Quick Generalizations
For Diag#1 with 1pulse/fire
Ones digit increment means not enough
crank pulses between cam pulses
(missing crank pulses or extra/early cam
pulses)
Tens digit increments means too many
crank pulses between cam pulses (extra
crank pulses or missing cam pulses)
Quick Generalizations
Normal Diag#1 activity
It is normal for the 10k digit to increment
during running, but the rest of the digits
should be static. This is essentially a cycle
counter (one increment per two crank revs)
and can be another tool to distinguish extra
cam pulses, which cause premature
incrementing.
It is also normal to have Diag#1 increments
of other digits during cranking while ECU is
establishing cycle sync
Quick Generalizations
Diag#1 activity when running
Do not ignore!
Many things that cause Diag#1 errors will result in timing
shifts
Problems that only occur at high speed and load can be
from sensor and/or target vibration
Future Changes
We are continually improving the functionality
of the diagnostic channels and software tools
System log functionality is already
implemented in current firmware but requires a
keycode to unlock
The SL viewer will be released with the next
major revision of PC software (2.x)
RTC Timestamp to on SL header
Notice of Diag#1 increments post engine startsomething similar to a check engine light