line out of block 32 leads to block 35, which directs you to the
starting point of test 1100. The YES flow line of this block leads
you to block 34.
for test 1550, "xmsn solenoid check." You perform this test following
the same troubleshooting steps as those in the test you just ran. As
before, the SETCOM may give display a general instruction message
(block 38); assemble, connect, disconnect, reconnect, or remove
message (block 39); special instruction message (block 41); or fault
message (block 43).
Completing the Troubleshooting Procedure.
Each test you run using
another test or follow-on procedure.
After following the fault
isolation chart through this fault (TSS-1) you have seen how each
test will either correct or eliminate wire harnesses and components
as faults. When actually troubleshooting a tank, you would stop when
you had corrected the specific fault and the transmission was
You use the same process to troubleshoot all transmission shift
subsystem faults. All faults require you to set up the tank controls
for standard initial test conditions. Once you have set the controls
to these conditions, use the fault isolation chart to troubleshoot
the wire harnesses and components that could cause the different
The fault isolation chart starts with the faults grouped together,
where the failure of a wire harness or component causes more than one
For example, TSS-1 and TSS-3 start out together and stay
together since the wire harnesses and components you troubleshoot
could cause either fault.
The transmission faults TSS-2 and TSS-4
through TSS-10 start out together, but they split when a wire harness
or component will not cause all faults.
For example, TSS-4 splits
from the group at block 16, and TSS-7 splits from the group at block
48 (appendix B).
Alternate Troubleshooting Procedure.
If you re-examine the fault isolation chart, you will find that all
symptoms (TSS-1 through TSS-10) start the STE troubleshooting at
fault TSS-1 (earlier in this lesson), you followed the YES flow to
use the STE test set.
Now, follow the NO flow line and troubleshoot using the alternate
troubleshooting procedure (block 19). If you look at table