P1660
A/T FI Data Line Failure
Causes
- Open, short or intermittent wiring on the transmission-to-engine/ECM data line
- Corroded, loose or damaged connector pins at TCM, ECM or inline connectors
- Blown fuse or loss of power/ground to one of the controllers on the bus
- Failed or intermittent Transmission Control Module (TCM) or Engine Control Module (ECM/PCM)
- Aftermarket electronics, improper repairs or chafed harness causing intermittent contact
- Software or firmware mismatch/corruption in one of the control modules
Symptoms
- Malfunction Indicator Lamp (MIL) illuminated
- Transmission may go to limp/limitation mode or display abnormal shift behavior
- Loss of transmission-related data on scan tool or inability to communicate with TCM
- Stored and/or pending communication-related DTCs
- Intermittent driveability issues if engine and transmission data are out of sync
What to check
- Use a scan tool to read stored and pending codes and confirm P1660 is current, not history-only
- Attempt communication with both ECM and TCM; note any 'no response' or 'module not present' messages
- Visually inspect wiring harnesses and connectors for damage, corrosion, pin push-out or water intrusion
- Verify battery voltage and chassis/engine grounds are clean and secure
- Check fuses and power feeds for ECM and TCM circuits
- Perform a wiggle test on harness/connectors while monitoring live data for communication dropouts
Signal parameters
- Data line is a bidirectional communication bus (CAN or manufacturer proprietary serial). Confirm protocol from service manual.
- Typical idle single-ended voltages for CAN nodes ~2.5 V; CANH rises and CANL falls during active bits (refer to manual for exact expected voltages and bit timing).
- When communicating normally, data packets should be present on the bus; signals absent or constant voltage indicate open/short.
- Any sudden jumps to battery voltage or to ground on the data line indicate hard short to power/ground.
Diagnostic algorithm
- Retrieve all related codes and freeze‑frame data with a capable scan tool. Note whether TCM and ECM respond and their software IDs.
- Verify battery voltage is within spec and inspect/clean main engine and chassis grounds.
- Inspect connectors at the TCM and ECM, plus any inline connectors and junctions along the harness. Look for corrosion, bent pins, moisture or damage.
- Check fuses and power feeds for both modules. Repair any blown fuses and trace cause if fuse blows again.
- With ignition ON, use a DVM or oscilloscope to probe the data lines at the module connectors. Compare observed voltages and waveform activity to service manual specifications.
- Perform continuity checks (with battery disconnected) from module pins to intermediate connectors and to the other module to locate opens or high resistance. Repair wiring harness as needed.
- If intermittent, perform wiggle test while monitoring bus activity to reproduce fault. Secure and repair any harness chafe points or loose connectors.
- If wiring, power and grounds are good but communication still fails, consider swapping in a known-good TCM or ECM (if available) or perform module bench testing per manufacturer procedures.
- After repairs, clear codes and road test to verify the DTC does not return and that communication is stable.
- If code returns after module replacement, re-check wiring and perform advanced diagnostics per dealer service information (may require module reprogramming or network topology checks).
Likely causes
- Damaged connector or corroded pin at TCM or ECM (most common)
- Open or shorted data wire (pinched, chafed harness)
- Bad ground or supply to one of the modules on the data bus
- Faulty TCM or ECM after wiring and power/ground verified
- Intermittent contact due to vibration or water intrusion
Fault status
Similar codes
P1660
Cooling Fans Control Circuit
Causes
- Open, short or intermittent wiring on the transmission-to-engine/ECM data line
- Corroded, loose or damaged connector pins at TCM, ECM or inline connectors
- Blown fuse or loss of power/ground to one of the controllers on the bus
- Failed or intermittent Transmission Control Module (TCM) or Engine Control Module (ECM/PCM)
- Aftermarket electronics, improper repairs or chafed harness causing intermittent contact
- Software or firmware mismatch/corruption in one of the control modules
Symptoms
- Malfunction Indicator Lamp (MIL) illuminated
- Transmission may go to limp/limitation mode or display abnormal shift behavior
- Loss of transmission-related data on scan tool or inability to communicate with TCM
- Stored and/or pending communication-related DTCs
- Intermittent driveability issues if engine and transmission data are out of sync
What to check
- Use a scan tool to read stored and pending codes and confirm P1660 is current, not history-only
- Attempt communication with both ECM and TCM; note any 'no response' or 'module not present' messages
- Visually inspect wiring harnesses and connectors for damage, corrosion, pin push-out or water intrusion
- Verify battery voltage and chassis/engine grounds are clean and secure
- Check fuses and power feeds for ECM and TCM circuits
- Perform a wiggle test on harness/connectors while monitoring live data for communication dropouts
Signal parameters
- Data line is a bidirectional communication bus (CAN or manufacturer proprietary serial). Confirm protocol from service manual.
- Typical idle single-ended voltages for CAN nodes ~2.5 V; CANH rises and CANL falls during active bits (refer to manual for exact expected voltages and bit timing).
- When communicating normally, data packets should be present on the bus; signals absent or constant voltage indicate open/short.
- Any sudden jumps to battery voltage or to ground on the data line indicate hard short to power/ground.
Diagnostic algorithm
- Retrieve all related codes and freeze‑frame data with a capable scan tool. Note whether TCM and ECM respond and their software IDs.
- Verify battery voltage is within spec and inspect/clean main engine and chassis grounds.
- Inspect connectors at the TCM and ECM, plus any inline connectors and junctions along the harness. Look for corrosion, bent pins, moisture or damage.
- Check fuses and power feeds for both modules. Repair any blown fuses and trace cause if fuse blows again.
- With ignition ON, use a DVM or oscilloscope to probe the data lines at the module connectors. Compare observed voltages and waveform activity to service manual specifications.
- Perform continuity checks (with battery disconnected) from module pins to intermediate connectors and to the other module to locate opens or high resistance. Repair wiring harness as needed.
- If intermittent, perform wiggle test while monitoring bus activity to reproduce fault. Secure and repair any harness chafe points or loose connectors.
- If wiring, power and grounds are good but communication still fails, consider swapping in a known-good TCM or ECM (if available) or perform module bench testing per manufacturer procedures.
- After repairs, clear codes and road test to verify the DTC does not return and that communication is stable.
- If code returns after module replacement, re-check wiring and perform advanced diagnostics per dealer service information (may require module reprogramming or network topology checks).
Likely causes
- Damaged connector or corroded pin at TCM or ECM (most common)
- Open or shorted data wire (pinched, chafed harness)
- Bad ground or supply to one of the modules on the data bus
- Faulty TCM or ECM after wiring and power/ground verified
- Intermittent contact due to vibration or water intrusion
Fault status
Similar codes
P1660
Cooling Fans Control Circuit
Causes
- Open, short or intermittent wiring on the transmission-to-engine/ECM data line
- Corroded, loose or damaged connector pins at TCM, ECM or inline connectors
- Blown fuse or loss of power/ground to one of the controllers on the bus
- Failed or intermittent Transmission Control Module (TCM) or Engine Control Module (ECM/PCM)
- Aftermarket electronics, improper repairs or chafed harness causing intermittent contact
- Software or firmware mismatch/corruption in one of the control modules
Symptoms
- Malfunction Indicator Lamp (MIL) illuminated
- Transmission may go to limp/limitation mode or display abnormal shift behavior
- Loss of transmission-related data on scan tool or inability to communicate with TCM
- Stored and/or pending communication-related DTCs
- Intermittent driveability issues if engine and transmission data are out of sync
What to check
- Use a scan tool to read stored and pending codes and confirm P1660 is current, not history-only
- Attempt communication with both ECM and TCM; note any 'no response' or 'module not present' messages
- Visually inspect wiring harnesses and connectors for damage, corrosion, pin push-out or water intrusion
- Verify battery voltage and chassis/engine grounds are clean and secure
- Check fuses and power feeds for ECM and TCM circuits
- Perform a wiggle test on harness/connectors while monitoring live data for communication dropouts
Signal parameters
- Data line is a bidirectional communication bus (CAN or manufacturer proprietary serial). Confirm protocol from service manual.
- Typical idle single-ended voltages for CAN nodes ~2.5 V; CANH rises and CANL falls during active bits (refer to manual for exact expected voltages and bit timing).
- When communicating normally, data packets should be present on the bus; signals absent or constant voltage indicate open/short.
- Any sudden jumps to battery voltage or to ground on the data line indicate hard short to power/ground.
Diagnostic algorithm
- Retrieve all related codes and freeze‑frame data with a capable scan tool. Note whether TCM and ECM respond and their software IDs.
- Verify battery voltage is within spec and inspect/clean main engine and chassis grounds.
- Inspect connectors at the TCM and ECM, plus any inline connectors and junctions along the harness. Look for corrosion, bent pins, moisture or damage.
- Check fuses and power feeds for both modules. Repair any blown fuses and trace cause if fuse blows again.
- With ignition ON, use a DVM or oscilloscope to probe the data lines at the module connectors. Compare observed voltages and waveform activity to service manual specifications.
- Perform continuity checks (with battery disconnected) from module pins to intermediate connectors and to the other module to locate opens or high resistance. Repair wiring harness as needed.
- If intermittent, perform wiggle test while monitoring bus activity to reproduce fault. Secure and repair any harness chafe points or loose connectors.
- If wiring, power and grounds are good but communication still fails, consider swapping in a known-good TCM or ECM (if available) or perform module bench testing per manufacturer procedures.
- After repairs, clear codes and road test to verify the DTC does not return and that communication is stable.
- If code returns after module replacement, re-check wiring and perform advanced diagnostics per dealer service information (may require module reprogramming or network topology checks).
Likely causes
- Damaged connector or corroded pin at TCM or ECM (most common)
- Open or shorted data wire (pinched, chafed harness)
- Bad ground or supply to one of the modules on the data bus
- Faulty TCM or ECM after wiring and power/ground verified
- Intermittent contact due to vibration or water intrusion
Fault status
Similar codes
P1660
Cooling Fans Control Circuit
Causes
- Open, short or intermittent wiring on the transmission-to-engine/ECM data line
- Corroded, loose or damaged connector pins at TCM, ECM or inline connectors
- Blown fuse or loss of power/ground to one of the controllers on the bus
- Failed or intermittent Transmission Control Module (TCM) or Engine Control Module (ECM/PCM)
- Aftermarket electronics, improper repairs or chafed harness causing intermittent contact
- Software or firmware mismatch/corruption in one of the control modules
Symptoms
- Malfunction Indicator Lamp (MIL) illuminated
- Transmission may go to limp/limitation mode or display abnormal shift behavior
- Loss of transmission-related data on scan tool or inability to communicate with TCM
- Stored and/or pending communication-related DTCs
- Intermittent driveability issues if engine and transmission data are out of sync
What to check
- Use a scan tool to read stored and pending codes and confirm P1660 is current, not history-only
- Attempt communication with both ECM and TCM; note any 'no response' or 'module not present' messages
- Visually inspect wiring harnesses and connectors for damage, corrosion, pin push-out or water intrusion
- Verify battery voltage and chassis/engine grounds are clean and secure
- Check fuses and power feeds for ECM and TCM circuits
- Perform a wiggle test on harness/connectors while monitoring live data for communication dropouts
Signal parameters
- Data line is a bidirectional communication bus (CAN or manufacturer proprietary serial). Confirm protocol from service manual.
- Typical idle single-ended voltages for CAN nodes ~2.5 V; CANH rises and CANL falls during active bits (refer to manual for exact expected voltages and bit timing).
- When communicating normally, data packets should be present on the bus; signals absent or constant voltage indicate open/short.
- Any sudden jumps to battery voltage or to ground on the data line indicate hard short to power/ground.
Diagnostic algorithm
- Retrieve all related codes and freeze‑frame data with a capable scan tool. Note whether TCM and ECM respond and their software IDs.
- Verify battery voltage is within spec and inspect/clean main engine and chassis grounds.
- Inspect connectors at the TCM and ECM, plus any inline connectors and junctions along the harness. Look for corrosion, bent pins, moisture or damage.
- Check fuses and power feeds for both modules. Repair any blown fuses and trace cause if fuse blows again.
- With ignition ON, use a DVM or oscilloscope to probe the data lines at the module connectors. Compare observed voltages and waveform activity to service manual specifications.
- Perform continuity checks (with battery disconnected) from module pins to intermediate connectors and to the other module to locate opens or high resistance. Repair wiring harness as needed.
- If intermittent, perform wiggle test while monitoring bus activity to reproduce fault. Secure and repair any harness chafe points or loose connectors.
- If wiring, power and grounds are good but communication still fails, consider swapping in a known-good TCM or ECM (if available) or perform module bench testing per manufacturer procedures.
- After repairs, clear codes and road test to verify the DTC does not return and that communication is stable.
- If code returns after module replacement, re-check wiring and perform advanced diagnostics per dealer service information (may require module reprogramming or network topology checks).
Likely causes
- Damaged connector or corroded pin at TCM or ECM (most common)
- Open or shorted data wire (pinched, chafed harness)
- Bad ground or supply to one of the modules on the data bus
- Faulty TCM or ECM after wiring and power/ground verified
- Intermittent contact due to vibration or water intrusion
Fault status
Similar codes
P1660
Cruise crct fault
Causes
- Open, short or intermittent wiring on the transmission-to-engine/ECM data line
- Corroded, loose or damaged connector pins at TCM, ECM or inline connectors
- Blown fuse or loss of power/ground to one of the controllers on the bus
- Failed or intermittent Transmission Control Module (TCM) or Engine Control Module (ECM/PCM)
- Aftermarket electronics, improper repairs or chafed harness causing intermittent contact
- Software or firmware mismatch/corruption in one of the control modules
Symptoms
- Malfunction Indicator Lamp (MIL) illuminated
- Transmission may go to limp/limitation mode or display abnormal shift behavior
- Loss of transmission-related data on scan tool or inability to communicate with TCM
- Stored and/or pending communication-related DTCs
- Intermittent driveability issues if engine and transmission data are out of sync
What to check
- Use a scan tool to read stored and pending codes and confirm P1660 is current, not history-only
- Attempt communication with both ECM and TCM; note any 'no response' or 'module not present' messages
- Visually inspect wiring harnesses and connectors for damage, corrosion, pin push-out or water intrusion
- Verify battery voltage and chassis/engine grounds are clean and secure
- Check fuses and power feeds for ECM and TCM circuits
- Perform a wiggle test on harness/connectors while monitoring live data for communication dropouts
Signal parameters
- Data line is a bidirectional communication bus (CAN or manufacturer proprietary serial). Confirm protocol from service manual.
- Typical idle single-ended voltages for CAN nodes ~2.5 V; CANH rises and CANL falls during active bits (refer to manual for exact expected voltages and bit timing).
- When communicating normally, data packets should be present on the bus; signals absent or constant voltage indicate open/short.
- Any sudden jumps to battery voltage or to ground on the data line indicate hard short to power/ground.
Diagnostic algorithm
- Retrieve all related codes and freeze‑frame data with a capable scan tool. Note whether TCM and ECM respond and their software IDs.
- Verify battery voltage is within spec and inspect/clean main engine and chassis grounds.
- Inspect connectors at the TCM and ECM, plus any inline connectors and junctions along the harness. Look for corrosion, bent pins, moisture or damage.
- Check fuses and power feeds for both modules. Repair any blown fuses and trace cause if fuse blows again.
- With ignition ON, use a DVM or oscilloscope to probe the data lines at the module connectors. Compare observed voltages and waveform activity to service manual specifications.
- Perform continuity checks (with battery disconnected) from module pins to intermediate connectors and to the other module to locate opens or high resistance. Repair wiring harness as needed.
- If intermittent, perform wiggle test while monitoring bus activity to reproduce fault. Secure and repair any harness chafe points or loose connectors.
- If wiring, power and grounds are good but communication still fails, consider swapping in a known-good TCM or ECM (if available) or perform module bench testing per manufacturer procedures.
- After repairs, clear codes and road test to verify the DTC does not return and that communication is stable.
- If code returns after module replacement, re-check wiring and perform advanced diagnostics per dealer service information (may require module reprogramming or network topology checks).
Likely causes
- Damaged connector or corroded pin at TCM or ECM (most common)
- Open or shorted data wire (pinched, chafed harness)
- Bad ground or supply to one of the modules on the data bus
- Faulty TCM or ECM after wiring and power/ground verified
- Intermittent contact due to vibration or water intrusion
Fault status
Similar codes
P1660
Output Circuit Check Signal High
Causes
- Open, short or intermittent wiring on the transmission-to-engine/ECM data line
- Corroded, loose or damaged connector pins at TCM, ECM or inline connectors
- Blown fuse or loss of power/ground to one of the controllers on the bus
- Failed or intermittent Transmission Control Module (TCM) or Engine Control Module (ECM/PCM)
- Aftermarket electronics, improper repairs or chafed harness causing intermittent contact
- Software or firmware mismatch/corruption in one of the control modules
Symptoms
- Malfunction Indicator Lamp (MIL) illuminated
- Transmission may go to limp/limitation mode or display abnormal shift behavior
- Loss of transmission-related data on scan tool or inability to communicate with TCM
- Stored and/or pending communication-related DTCs
- Intermittent driveability issues if engine and transmission data are out of sync
What to check
- Use a scan tool to read stored and pending codes and confirm P1660 is current, not history-only
- Attempt communication with both ECM and TCM; note any 'no response' or 'module not present' messages
- Visually inspect wiring harnesses and connectors for damage, corrosion, pin push-out or water intrusion
- Verify battery voltage and chassis/engine grounds are clean and secure
- Check fuses and power feeds for ECM and TCM circuits
- Perform a wiggle test on harness/connectors while monitoring live data for communication dropouts
Signal parameters
- Data line is a bidirectional communication bus (CAN or manufacturer proprietary serial). Confirm protocol from service manual.
- Typical idle single-ended voltages for CAN nodes ~2.5 V; CANH rises and CANL falls during active bits (refer to manual for exact expected voltages and bit timing).
- When communicating normally, data packets should be present on the bus; signals absent or constant voltage indicate open/short.
- Any sudden jumps to battery voltage or to ground on the data line indicate hard short to power/ground.
Diagnostic algorithm
- Retrieve all related codes and freeze‑frame data with a capable scan tool. Note whether TCM and ECM respond and their software IDs.
- Verify battery voltage is within spec and inspect/clean main engine and chassis grounds.
- Inspect connectors at the TCM and ECM, plus any inline connectors and junctions along the harness. Look for corrosion, bent pins, moisture or damage.
- Check fuses and power feeds for both modules. Repair any blown fuses and trace cause if fuse blows again.
- With ignition ON, use a DVM or oscilloscope to probe the data lines at the module connectors. Compare observed voltages and waveform activity to service manual specifications.
- Perform continuity checks (with battery disconnected) from module pins to intermediate connectors and to the other module to locate opens or high resistance. Repair wiring harness as needed.
- If intermittent, perform wiggle test while monitoring bus activity to reproduce fault. Secure and repair any harness chafe points or loose connectors.
- If wiring, power and grounds are good but communication still fails, consider swapping in a known-good TCM or ECM (if available) or perform module bench testing per manufacturer procedures.
- After repairs, clear codes and road test to verify the DTC does not return and that communication is stable.
- If code returns after module replacement, re-check wiring and perform advanced diagnostics per dealer service information (may require module reprogramming or network topology checks).
Likely causes
- Damaged connector or corroded pin at TCM or ECM (most common)
- Open or shorted data wire (pinched, chafed harness)
- Bad ground or supply to one of the modules on the data bus
- Faulty TCM or ECM after wiring and power/ground verified
- Intermittent contact due to vibration or water intrusion
Fault status
Similar codes
P1660
Cooling Fans Control Circuit
Causes
- Open, short or intermittent wiring on the transmission-to-engine/ECM data line
- Corroded, loose or damaged connector pins at TCM, ECM or inline connectors
- Blown fuse or loss of power/ground to one of the controllers on the bus
- Failed or intermittent Transmission Control Module (TCM) or Engine Control Module (ECM/PCM)
- Aftermarket electronics, improper repairs or chafed harness causing intermittent contact
- Software or firmware mismatch/corruption in one of the control modules
Symptoms
- Malfunction Indicator Lamp (MIL) illuminated
- Transmission may go to limp/limitation mode or display abnormal shift behavior
- Loss of transmission-related data on scan tool or inability to communicate with TCM
- Stored and/or pending communication-related DTCs
- Intermittent driveability issues if engine and transmission data are out of sync
What to check
- Use a scan tool to read stored and pending codes and confirm P1660 is current, not history-only
- Attempt communication with both ECM and TCM; note any 'no response' or 'module not present' messages
- Visually inspect wiring harnesses and connectors for damage, corrosion, pin push-out or water intrusion
- Verify battery voltage and chassis/engine grounds are clean and secure
- Check fuses and power feeds for ECM and TCM circuits
- Perform a wiggle test on harness/connectors while monitoring live data for communication dropouts
Signal parameters
- Data line is a bidirectional communication bus (CAN or manufacturer proprietary serial). Confirm protocol from service manual.
- Typical idle single-ended voltages for CAN nodes ~2.5 V; CANH rises and CANL falls during active bits (refer to manual for exact expected voltages and bit timing).
- When communicating normally, data packets should be present on the bus; signals absent or constant voltage indicate open/short.
- Any sudden jumps to battery voltage or to ground on the data line indicate hard short to power/ground.
Diagnostic algorithm
- Retrieve all related codes and freeze‑frame data with a capable scan tool. Note whether TCM and ECM respond and their software IDs.
- Verify battery voltage is within spec and inspect/clean main engine and chassis grounds.
- Inspect connectors at the TCM and ECM, plus any inline connectors and junctions along the harness. Look for corrosion, bent pins, moisture or damage.
- Check fuses and power feeds for both modules. Repair any blown fuses and trace cause if fuse blows again.
- With ignition ON, use a DVM or oscilloscope to probe the data lines at the module connectors. Compare observed voltages and waveform activity to service manual specifications.
- Perform continuity checks (with battery disconnected) from module pins to intermediate connectors and to the other module to locate opens or high resistance. Repair wiring harness as needed.
- If intermittent, perform wiggle test while monitoring bus activity to reproduce fault. Secure and repair any harness chafe points or loose connectors.
- If wiring, power and grounds are good but communication still fails, consider swapping in a known-good TCM or ECM (if available) or perform module bench testing per manufacturer procedures.
- After repairs, clear codes and road test to verify the DTC does not return and that communication is stable.
- If code returns after module replacement, re-check wiring and perform advanced diagnostics per dealer service information (may require module reprogramming or network topology checks).
Likely causes
- Damaged connector or corroded pin at TCM or ECM (most common)
- Open or shorted data wire (pinched, chafed harness)
- Bad ground or supply to one of the modules on the data bus
- Faulty TCM or ECM after wiring and power/ground verified
- Intermittent contact due to vibration or water intrusion
Fault status
Similar codes
P1660
Cooling Fans Control Circuit
Causes
- Open, short or intermittent wiring on the transmission-to-engine/ECM data line
- Corroded, loose or damaged connector pins at TCM, ECM or inline connectors
- Blown fuse or loss of power/ground to one of the controllers on the bus
- Failed or intermittent Transmission Control Module (TCM) or Engine Control Module (ECM/PCM)
- Aftermarket electronics, improper repairs or chafed harness causing intermittent contact
- Software or firmware mismatch/corruption in one of the control modules
Symptoms
- Malfunction Indicator Lamp (MIL) illuminated
- Transmission may go to limp/limitation mode or display abnormal shift behavior
- Loss of transmission-related data on scan tool or inability to communicate with TCM
- Stored and/or pending communication-related DTCs
- Intermittent driveability issues if engine and transmission data are out of sync
What to check
- Use a scan tool to read stored and pending codes and confirm P1660 is current, not history-only
- Attempt communication with both ECM and TCM; note any 'no response' or 'module not present' messages
- Visually inspect wiring harnesses and connectors for damage, corrosion, pin push-out or water intrusion
- Verify battery voltage and chassis/engine grounds are clean and secure
- Check fuses and power feeds for ECM and TCM circuits
- Perform a wiggle test on harness/connectors while monitoring live data for communication dropouts
Signal parameters
- Data line is a bidirectional communication bus (CAN or manufacturer proprietary serial). Confirm protocol from service manual.
- Typical idle single-ended voltages for CAN nodes ~2.5 V; CANH rises and CANL falls during active bits (refer to manual for exact expected voltages and bit timing).
- When communicating normally, data packets should be present on the bus; signals absent or constant voltage indicate open/short.
- Any sudden jumps to battery voltage or to ground on the data line indicate hard short to power/ground.
Diagnostic algorithm
- Retrieve all related codes and freeze‑frame data with a capable scan tool. Note whether TCM and ECM respond and their software IDs.
- Verify battery voltage is within spec and inspect/clean main engine and chassis grounds.
- Inspect connectors at the TCM and ECM, plus any inline connectors and junctions along the harness. Look for corrosion, bent pins, moisture or damage.
- Check fuses and power feeds for both modules. Repair any blown fuses and trace cause if fuse blows again.
- With ignition ON, use a DVM or oscilloscope to probe the data lines at the module connectors. Compare observed voltages and waveform activity to service manual specifications.
- Perform continuity checks (with battery disconnected) from module pins to intermediate connectors and to the other module to locate opens or high resistance. Repair wiring harness as needed.
- If intermittent, perform wiggle test while monitoring bus activity to reproduce fault. Secure and repair any harness chafe points or loose connectors.
- If wiring, power and grounds are good but communication still fails, consider swapping in a known-good TCM or ECM (if available) or perform module bench testing per manufacturer procedures.
- After repairs, clear codes and road test to verify the DTC does not return and that communication is stable.
- If code returns after module replacement, re-check wiring and perform advanced diagnostics per dealer service information (may require module reprogramming or network topology checks).
Likely causes
- Damaged connector or corroded pin at TCM or ECM (most common)
- Open or shorted data wire (pinched, chafed harness)
- Bad ground or supply to one of the modules on the data bus
- Faulty TCM or ECM after wiring and power/ground verified
- Intermittent contact due to vibration or water intrusion
Fault status
Similar codes
P1660
A/T FI Data Line Failure
Causes
- Open, short or intermittent wiring on the transmission-to-engine/ECM data line
- Corroded, loose or damaged connector pins at TCM, ECM or inline connectors
- Blown fuse or loss of power/ground to one of the controllers on the bus
- Failed or intermittent Transmission Control Module (TCM) or Engine Control Module (ECM/PCM)
- Aftermarket electronics, improper repairs or chafed harness causing intermittent contact
- Software or firmware mismatch/corruption in one of the control modules
Symptoms
- Malfunction Indicator Lamp (MIL) illuminated
- Transmission may go to limp/limitation mode or display abnormal shift behavior
- Loss of transmission-related data on scan tool or inability to communicate with TCM
- Stored and/or pending communication-related DTCs
- Intermittent driveability issues if engine and transmission data are out of sync
What to check
- Use a scan tool to read stored and pending codes and confirm P1660 is current, not history-only
- Attempt communication with both ECM and TCM; note any 'no response' or 'module not present' messages
- Visually inspect wiring harnesses and connectors for damage, corrosion, pin push-out or water intrusion
- Verify battery voltage and chassis/engine grounds are clean and secure
- Check fuses and power feeds for ECM and TCM circuits
- Perform a wiggle test on harness/connectors while monitoring live data for communication dropouts
Signal parameters
- Data line is a bidirectional communication bus (CAN or manufacturer proprietary serial). Confirm protocol from service manual.
- Typical idle single-ended voltages for CAN nodes ~2.5 V; CANH rises and CANL falls during active bits (refer to manual for exact expected voltages and bit timing).
- When communicating normally, data packets should be present on the bus; signals absent or constant voltage indicate open/short.
- Any sudden jumps to battery voltage or to ground on the data line indicate hard short to power/ground.
Diagnostic algorithm
- Retrieve all related codes and freeze‑frame data with a capable scan tool. Note whether TCM and ECM respond and their software IDs.
- Verify battery voltage is within spec and inspect/clean main engine and chassis grounds.
- Inspect connectors at the TCM and ECM, plus any inline connectors and junctions along the harness. Look for corrosion, bent pins, moisture or damage.
- Check fuses and power feeds for both modules. Repair any blown fuses and trace cause if fuse blows again.
- With ignition ON, use a DVM or oscilloscope to probe the data lines at the module connectors. Compare observed voltages and waveform activity to service manual specifications.
- Perform continuity checks (with battery disconnected) from module pins to intermediate connectors and to the other module to locate opens or high resistance. Repair wiring harness as needed.
- If intermittent, perform wiggle test while monitoring bus activity to reproduce fault. Secure and repair any harness chafe points or loose connectors.
- If wiring, power and grounds are good but communication still fails, consider swapping in a known-good TCM or ECM (if available) or perform module bench testing per manufacturer procedures.
- After repairs, clear codes and road test to verify the DTC does not return and that communication is stable.
- If code returns after module replacement, re-check wiring and perform advanced diagnostics per dealer service information (may require module reprogramming or network topology checks).
Likely causes
- Damaged connector or corroded pin at TCM or ECM (most common)
- Open or shorted data wire (pinched, chafed harness)
- Bad ground or supply to one of the modules on the data bus
- Faulty TCM or ECM after wiring and power/ground verified
- Intermittent contact due to vibration or water intrusion
Fault status
Similar codes
P1660
Cooling Fan Control Circuits
Causes
- Open, short or intermittent wiring on the transmission-to-engine/ECM data line
- Corroded, loose or damaged connector pins at TCM, ECM or inline connectors
- Blown fuse or loss of power/ground to one of the controllers on the bus
- Failed or intermittent Transmission Control Module (TCM) or Engine Control Module (ECM/PCM)
- Aftermarket electronics, improper repairs or chafed harness causing intermittent contact
- Software or firmware mismatch/corruption in one of the control modules
Symptoms
- Malfunction Indicator Lamp (MIL) illuminated
- Transmission may go to limp/limitation mode or display abnormal shift behavior
- Loss of transmission-related data on scan tool or inability to communicate with TCM
- Stored and/or pending communication-related DTCs
- Intermittent driveability issues if engine and transmission data are out of sync
What to check
- Use a scan tool to read stored and pending codes and confirm P1660 is current, not history-only
- Attempt communication with both ECM and TCM; note any 'no response' or 'module not present' messages
- Visually inspect wiring harnesses and connectors for damage, corrosion, pin push-out or water intrusion
- Verify battery voltage and chassis/engine grounds are clean and secure
- Check fuses and power feeds for ECM and TCM circuits
- Perform a wiggle test on harness/connectors while monitoring live data for communication dropouts
Signal parameters
- Data line is a bidirectional communication bus (CAN or manufacturer proprietary serial). Confirm protocol from service manual.
- Typical idle single-ended voltages for CAN nodes ~2.5 V; CANH rises and CANL falls during active bits (refer to manual for exact expected voltages and bit timing).
- When communicating normally, data packets should be present on the bus; signals absent or constant voltage indicate open/short.
- Any sudden jumps to battery voltage or to ground on the data line indicate hard short to power/ground.
Diagnostic algorithm
- Retrieve all related codes and freeze‑frame data with a capable scan tool. Note whether TCM and ECM respond and their software IDs.
- Verify battery voltage is within spec and inspect/clean main engine and chassis grounds.
- Inspect connectors at the TCM and ECM, plus any inline connectors and junctions along the harness. Look for corrosion, bent pins, moisture or damage.
- Check fuses and power feeds for both modules. Repair any blown fuses and trace cause if fuse blows again.
- With ignition ON, use a DVM or oscilloscope to probe the data lines at the module connectors. Compare observed voltages and waveform activity to service manual specifications.
- Perform continuity checks (with battery disconnected) from module pins to intermediate connectors and to the other module to locate opens or high resistance. Repair wiring harness as needed.
- If intermittent, perform wiggle test while monitoring bus activity to reproduce fault. Secure and repair any harness chafe points or loose connectors.
- If wiring, power and grounds are good but communication still fails, consider swapping in a known-good TCM or ECM (if available) or perform module bench testing per manufacturer procedures.
- After repairs, clear codes and road test to verify the DTC does not return and that communication is stable.
- If code returns after module replacement, re-check wiring and perform advanced diagnostics per dealer service information (may require module reprogramming or network topology checks).
Likely causes
- Damaged connector or corroded pin at TCM or ECM (most common)
- Open or shorted data wire (pinched, chafed harness)
- Bad ground or supply to one of the modules on the data bus
- Faulty TCM or ECM after wiring and power/ground verified
- Intermittent contact due to vibration or water intrusion
Fault status
Similar codes
P1660
A/T FI Data Line Failure
Causes
- Open, short or intermittent wiring on the transmission-to-engine/ECM data line
- Corroded, loose or damaged connector pins at TCM, ECM or inline connectors
- Blown fuse or loss of power/ground to one of the controllers on the bus
- Failed or intermittent Transmission Control Module (TCM) or Engine Control Module (ECM/PCM)
- Aftermarket electronics, improper repairs or chafed harness causing intermittent contact
- Software or firmware mismatch/corruption in one of the control modules
Symptoms
- Malfunction Indicator Lamp (MIL) illuminated
- Transmission may go to limp/limitation mode or display abnormal shift behavior
- Loss of transmission-related data on scan tool or inability to communicate with TCM
- Stored and/or pending communication-related DTCs
- Intermittent driveability issues if engine and transmission data are out of sync
What to check
- Use a scan tool to read stored and pending codes and confirm P1660 is current, not history-only
- Attempt communication with both ECM and TCM; note any 'no response' or 'module not present' messages
- Visually inspect wiring harnesses and connectors for damage, corrosion, pin push-out or water intrusion
- Verify battery voltage and chassis/engine grounds are clean and secure
- Check fuses and power feeds for ECM and TCM circuits
- Perform a wiggle test on harness/connectors while monitoring live data for communication dropouts
Signal parameters
- Data line is a bidirectional communication bus (CAN or manufacturer proprietary serial). Confirm protocol from service manual.
- Typical idle single-ended voltages for CAN nodes ~2.5 V; CANH rises and CANL falls during active bits (refer to manual for exact expected voltages and bit timing).
- When communicating normally, data packets should be present on the bus; signals absent or constant voltage indicate open/short.
- Any sudden jumps to battery voltage or to ground on the data line indicate hard short to power/ground.
Diagnostic algorithm
- Retrieve all related codes and freeze‑frame data with a capable scan tool. Note whether TCM and ECM respond and their software IDs.
- Verify battery voltage is within spec and inspect/clean main engine and chassis grounds.
- Inspect connectors at the TCM and ECM, plus any inline connectors and junctions along the harness. Look for corrosion, bent pins, moisture or damage.
- Check fuses and power feeds for both modules. Repair any blown fuses and trace cause if fuse blows again.
- With ignition ON, use a DVM or oscilloscope to probe the data lines at the module connectors. Compare observed voltages and waveform activity to service manual specifications.
- Perform continuity checks (with battery disconnected) from module pins to intermediate connectors and to the other module to locate opens or high resistance. Repair wiring harness as needed.
- If intermittent, perform wiggle test while monitoring bus activity to reproduce fault. Secure and repair any harness chafe points or loose connectors.
- If wiring, power and grounds are good but communication still fails, consider swapping in a known-good TCM or ECM (if available) or perform module bench testing per manufacturer procedures.
- After repairs, clear codes and road test to verify the DTC does not return and that communication is stable.
- If code returns after module replacement, re-check wiring and perform advanced diagnostics per dealer service information (may require module reprogramming or network topology checks).
Likely causes
- Damaged connector or corroded pin at TCM or ECM (most common)
- Open or shorted data wire (pinched, chafed harness)
- Bad ground or supply to one of the modules on the data bus
- Faulty TCM or ECM after wiring and power/ground verified
- Intermittent contact due to vibration or water intrusion
Fault status
Similar codes
P1660
Power Stage Group 'B'
Causes
- Open, short or intermittent wiring on the transmission-to-engine/ECM data line
- Corroded, loose or damaged connector pins at TCM, ECM or inline connectors
- Blown fuse or loss of power/ground to one of the controllers on the bus
- Failed or intermittent Transmission Control Module (TCM) or Engine Control Module (ECM/PCM)
- Aftermarket electronics, improper repairs or chafed harness causing intermittent contact
- Software or firmware mismatch/corruption in one of the control modules
Symptoms
- Malfunction Indicator Lamp (MIL) illuminated
- Transmission may go to limp/limitation mode or display abnormal shift behavior
- Loss of transmission-related data on scan tool or inability to communicate with TCM
- Stored and/or pending communication-related DTCs
- Intermittent driveability issues if engine and transmission data are out of sync
What to check
- Use a scan tool to read stored and pending codes and confirm P1660 is current, not history-only
- Attempt communication with both ECM and TCM; note any 'no response' or 'module not present' messages
- Visually inspect wiring harnesses and connectors for damage, corrosion, pin push-out or water intrusion
- Verify battery voltage and chassis/engine grounds are clean and secure
- Check fuses and power feeds for ECM and TCM circuits
- Perform a wiggle test on harness/connectors while monitoring live data for communication dropouts
Signal parameters
- Data line is a bidirectional communication bus (CAN or manufacturer proprietary serial). Confirm protocol from service manual.
- Typical idle single-ended voltages for CAN nodes ~2.5 V; CANH rises and CANL falls during active bits (refer to manual for exact expected voltages and bit timing).
- When communicating normally, data packets should be present on the bus; signals absent or constant voltage indicate open/short.
- Any sudden jumps to battery voltage or to ground on the data line indicate hard short to power/ground.
Diagnostic algorithm
- Retrieve all related codes and freeze‑frame data with a capable scan tool. Note whether TCM and ECM respond and their software IDs.
- Verify battery voltage is within spec and inspect/clean main engine and chassis grounds.
- Inspect connectors at the TCM and ECM, plus any inline connectors and junctions along the harness. Look for corrosion, bent pins, moisture or damage.
- Check fuses and power feeds for both modules. Repair any blown fuses and trace cause if fuse blows again.
- With ignition ON, use a DVM or oscilloscope to probe the data lines at the module connectors. Compare observed voltages and waveform activity to service manual specifications.
- Perform continuity checks (with battery disconnected) from module pins to intermediate connectors and to the other module to locate opens or high resistance. Repair wiring harness as needed.
- If intermittent, perform wiggle test while monitoring bus activity to reproduce fault. Secure and repair any harness chafe points or loose connectors.
- If wiring, power and grounds are good but communication still fails, consider swapping in a known-good TCM or ECM (if available) or perform module bench testing per manufacturer procedures.
- After repairs, clear codes and road test to verify the DTC does not return and that communication is stable.
- If code returns after module replacement, re-check wiring and perform advanced diagnostics per dealer service information (may require module reprogramming or network topology checks).
Likely causes
- Damaged connector or corroded pin at TCM or ECM (most common)
- Open or shorted data wire (pinched, chafed harness)
- Bad ground or supply to one of the modules on the data bus
- Faulty TCM or ECM after wiring and power/ground verified
- Intermittent contact due to vibration or water intrusion
Fault status
Similar codes
P1660
Output Circuit Check Signal High
Causes
- Open, short or intermittent wiring on the transmission-to-engine/ECM data line
- Corroded, loose or damaged connector pins at TCM, ECM or inline connectors
- Blown fuse or loss of power/ground to one of the controllers on the bus
- Failed or intermittent Transmission Control Module (TCM) or Engine Control Module (ECM/PCM)
- Aftermarket electronics, improper repairs or chafed harness causing intermittent contact
- Software or firmware mismatch/corruption in one of the control modules
Symptoms
- Malfunction Indicator Lamp (MIL) illuminated
- Transmission may go to limp/limitation mode or display abnormal shift behavior
- Loss of transmission-related data on scan tool or inability to communicate with TCM
- Stored and/or pending communication-related DTCs
- Intermittent driveability issues if engine and transmission data are out of sync
What to check
- Use a scan tool to read stored and pending codes and confirm P1660 is current, not history-only
- Attempt communication with both ECM and TCM; note any 'no response' or 'module not present' messages
- Visually inspect wiring harnesses and connectors for damage, corrosion, pin push-out or water intrusion
- Verify battery voltage and chassis/engine grounds are clean and secure
- Check fuses and power feeds for ECM and TCM circuits
- Perform a wiggle test on harness/connectors while monitoring live data for communication dropouts
Signal parameters
- Data line is a bidirectional communication bus (CAN or manufacturer proprietary serial). Confirm protocol from service manual.
- Typical idle single-ended voltages for CAN nodes ~2.5 V; CANH rises and CANL falls during active bits (refer to manual for exact expected voltages and bit timing).
- When communicating normally, data packets should be present on the bus; signals absent or constant voltage indicate open/short.
- Any sudden jumps to battery voltage or to ground on the data line indicate hard short to power/ground.
Diagnostic algorithm
- Retrieve all related codes and freeze‑frame data with a capable scan tool. Note whether TCM and ECM respond and their software IDs.
- Verify battery voltage is within spec and inspect/clean main engine and chassis grounds.
- Inspect connectors at the TCM and ECM, plus any inline connectors and junctions along the harness. Look for corrosion, bent pins, moisture or damage.
- Check fuses and power feeds for both modules. Repair any blown fuses and trace cause if fuse blows again.
- With ignition ON, use a DVM or oscilloscope to probe the data lines at the module connectors. Compare observed voltages and waveform activity to service manual specifications.
- Perform continuity checks (with battery disconnected) from module pins to intermediate connectors and to the other module to locate opens or high resistance. Repair wiring harness as needed.
- If intermittent, perform wiggle test while monitoring bus activity to reproduce fault. Secure and repair any harness chafe points or loose connectors.
- If wiring, power and grounds are good but communication still fails, consider swapping in a known-good TCM or ECM (if available) or perform module bench testing per manufacturer procedures.
- After repairs, clear codes and road test to verify the DTC does not return and that communication is stable.
- If code returns after module replacement, re-check wiring and perform advanced diagnostics per dealer service information (may require module reprogramming or network topology checks).
Likely causes
- Damaged connector or corroded pin at TCM or ECM (most common)
- Open or shorted data wire (pinched, chafed harness)
- Bad ground or supply to one of the modules on the data bus
- Faulty TCM or ECM after wiring and power/ground verified
- Intermittent contact due to vibration or water intrusion
Fault status
Similar codes
P1660
Output Circuit Check Signal High
Causes
- Open, short or intermittent wiring on the transmission-to-engine/ECM data line
- Corroded, loose or damaged connector pins at TCM, ECM or inline connectors
- Blown fuse or loss of power/ground to one of the controllers on the bus
- Failed or intermittent Transmission Control Module (TCM) or Engine Control Module (ECM/PCM)
- Aftermarket electronics, improper repairs or chafed harness causing intermittent contact
- Software or firmware mismatch/corruption in one of the control modules
Symptoms
- Malfunction Indicator Lamp (MIL) illuminated
- Transmission may go to limp/limitation mode or display abnormal shift behavior
- Loss of transmission-related data on scan tool or inability to communicate with TCM
- Stored and/or pending communication-related DTCs
- Intermittent driveability issues if engine and transmission data are out of sync
What to check
- Use a scan tool to read stored and pending codes and confirm P1660 is current, not history-only
- Attempt communication with both ECM and TCM; note any 'no response' or 'module not present' messages
- Visually inspect wiring harnesses and connectors for damage, corrosion, pin push-out or water intrusion
- Verify battery voltage and chassis/engine grounds are clean and secure
- Check fuses and power feeds for ECM and TCM circuits
- Perform a wiggle test on harness/connectors while monitoring live data for communication dropouts
Signal parameters
- Data line is a bidirectional communication bus (CAN or manufacturer proprietary serial). Confirm protocol from service manual.
- Typical idle single-ended voltages for CAN nodes ~2.5 V; CANH rises and CANL falls during active bits (refer to manual for exact expected voltages and bit timing).
- When communicating normally, data packets should be present on the bus; signals absent or constant voltage indicate open/short.
- Any sudden jumps to battery voltage or to ground on the data line indicate hard short to power/ground.
Diagnostic algorithm
- Retrieve all related codes and freeze‑frame data with a capable scan tool. Note whether TCM and ECM respond and their software IDs.
- Verify battery voltage is within spec and inspect/clean main engine and chassis grounds.
- Inspect connectors at the TCM and ECM, plus any inline connectors and junctions along the harness. Look for corrosion, bent pins, moisture or damage.
- Check fuses and power feeds for both modules. Repair any blown fuses and trace cause if fuse blows again.
- With ignition ON, use a DVM or oscilloscope to probe the data lines at the module connectors. Compare observed voltages and waveform activity to service manual specifications.
- Perform continuity checks (with battery disconnected) from module pins to intermediate connectors and to the other module to locate opens or high resistance. Repair wiring harness as needed.
- If intermittent, perform wiggle test while monitoring bus activity to reproduce fault. Secure and repair any harness chafe points or loose connectors.
- If wiring, power and grounds are good but communication still fails, consider swapping in a known-good TCM or ECM (if available) or perform module bench testing per manufacturer procedures.
- After repairs, clear codes and road test to verify the DTC does not return and that communication is stable.
- If code returns after module replacement, re-check wiring and perform advanced diagnostics per dealer service information (may require module reprogramming or network topology checks).
Likely causes
- Damaged connector or corroded pin at TCM or ECM (most common)
- Open or shorted data wire (pinched, chafed harness)
- Bad ground or supply to one of the modules on the data bus
- Faulty TCM or ECM after wiring and power/ground verified
- Intermittent contact due to vibration or water intrusion
Fault status
Similar codes
P1660
Cooling Fans Control Circuit
Causes
- Open, short or intermittent wiring on the transmission-to-engine/ECM data line
- Corroded, loose or damaged connector pins at TCM, ECM or inline connectors
- Blown fuse or loss of power/ground to one of the controllers on the bus
- Failed or intermittent Transmission Control Module (TCM) or Engine Control Module (ECM/PCM)
- Aftermarket electronics, improper repairs or chafed harness causing intermittent contact
- Software or firmware mismatch/corruption in one of the control modules
Symptoms
- Malfunction Indicator Lamp (MIL) illuminated
- Transmission may go to limp/limitation mode or display abnormal shift behavior
- Loss of transmission-related data on scan tool or inability to communicate with TCM
- Stored and/or pending communication-related DTCs
- Intermittent driveability issues if engine and transmission data are out of sync
What to check
- Use a scan tool to read stored and pending codes and confirm P1660 is current, not history-only
- Attempt communication with both ECM and TCM; note any 'no response' or 'module not present' messages
- Visually inspect wiring harnesses and connectors for damage, corrosion, pin push-out or water intrusion
- Verify battery voltage and chassis/engine grounds are clean and secure
- Check fuses and power feeds for ECM and TCM circuits
- Perform a wiggle test on harness/connectors while monitoring live data for communication dropouts
Signal parameters
- Data line is a bidirectional communication bus (CAN or manufacturer proprietary serial). Confirm protocol from service manual.
- Typical idle single-ended voltages for CAN nodes ~2.5 V; CANH rises and CANL falls during active bits (refer to manual for exact expected voltages and bit timing).
- When communicating normally, data packets should be present on the bus; signals absent or constant voltage indicate open/short.
- Any sudden jumps to battery voltage or to ground on the data line indicate hard short to power/ground.
Diagnostic algorithm
- Retrieve all related codes and freeze‑frame data with a capable scan tool. Note whether TCM and ECM respond and their software IDs.
- Verify battery voltage is within spec and inspect/clean main engine and chassis grounds.
- Inspect connectors at the TCM and ECM, plus any inline connectors and junctions along the harness. Look for corrosion, bent pins, moisture or damage.
- Check fuses and power feeds for both modules. Repair any blown fuses and trace cause if fuse blows again.
- With ignition ON, use a DVM or oscilloscope to probe the data lines at the module connectors. Compare observed voltages and waveform activity to service manual specifications.
- Perform continuity checks (with battery disconnected) from module pins to intermediate connectors and to the other module to locate opens or high resistance. Repair wiring harness as needed.
- If intermittent, perform wiggle test while monitoring bus activity to reproduce fault. Secure and repair any harness chafe points or loose connectors.
- If wiring, power and grounds are good but communication still fails, consider swapping in a known-good TCM or ECM (if available) or perform module bench testing per manufacturer procedures.
- After repairs, clear codes and road test to verify the DTC does not return and that communication is stable.
- If code returns after module replacement, re-check wiring and perform advanced diagnostics per dealer service information (may require module reprogramming or network topology checks).
Likely causes
- Damaged connector or corroded pin at TCM or ECM (most common)
- Open or shorted data wire (pinched, chafed harness)
- Bad ground or supply to one of the modules on the data bus
- Faulty TCM or ECM after wiring and power/ground verified
- Intermittent contact due to vibration or water intrusion
Fault status
Similar codes
P1660
Output Circuit Check Signal High
Causes
- Open, short or intermittent wiring on the transmission-to-engine/ECM data line
- Corroded, loose or damaged connector pins at TCM, ECM or inline connectors
- Blown fuse or loss of power/ground to one of the controllers on the bus
- Failed or intermittent Transmission Control Module (TCM) or Engine Control Module (ECM/PCM)
- Aftermarket electronics, improper repairs or chafed harness causing intermittent contact
- Software or firmware mismatch/corruption in one of the control modules
Symptoms
- Malfunction Indicator Lamp (MIL) illuminated
- Transmission may go to limp/limitation mode or display abnormal shift behavior
- Loss of transmission-related data on scan tool or inability to communicate with TCM
- Stored and/or pending communication-related DTCs
- Intermittent driveability issues if engine and transmission data are out of sync
What to check
- Use a scan tool to read stored and pending codes and confirm P1660 is current, not history-only
- Attempt communication with both ECM and TCM; note any 'no response' or 'module not present' messages
- Visually inspect wiring harnesses and connectors for damage, corrosion, pin push-out or water intrusion
- Verify battery voltage and chassis/engine grounds are clean and secure
- Check fuses and power feeds for ECM and TCM circuits
- Perform a wiggle test on harness/connectors while monitoring live data for communication dropouts
Signal parameters
- Data line is a bidirectional communication bus (CAN or manufacturer proprietary serial). Confirm protocol from service manual.
- Typical idle single-ended voltages for CAN nodes ~2.5 V; CANH rises and CANL falls during active bits (refer to manual for exact expected voltages and bit timing).
- When communicating normally, data packets should be present on the bus; signals absent or constant voltage indicate open/short.
- Any sudden jumps to battery voltage or to ground on the data line indicate hard short to power/ground.
Diagnostic algorithm
- Retrieve all related codes and freeze‑frame data with a capable scan tool. Note whether TCM and ECM respond and their software IDs.
- Verify battery voltage is within spec and inspect/clean main engine and chassis grounds.
- Inspect connectors at the TCM and ECM, plus any inline connectors and junctions along the harness. Look for corrosion, bent pins, moisture or damage.
- Check fuses and power feeds for both modules. Repair any blown fuses and trace cause if fuse blows again.
- With ignition ON, use a DVM or oscilloscope to probe the data lines at the module connectors. Compare observed voltages and waveform activity to service manual specifications.
- Perform continuity checks (with battery disconnected) from module pins to intermediate connectors and to the other module to locate opens or high resistance. Repair wiring harness as needed.
- If intermittent, perform wiggle test while monitoring bus activity to reproduce fault. Secure and repair any harness chafe points or loose connectors.
- If wiring, power and grounds are good but communication still fails, consider swapping in a known-good TCM or ECM (if available) or perform module bench testing per manufacturer procedures.
- After repairs, clear codes and road test to verify the DTC does not return and that communication is stable.
- If code returns after module replacement, re-check wiring and perform advanced diagnostics per dealer service information (may require module reprogramming or network topology checks).
Likely causes
- Damaged connector or corroded pin at TCM or ECM (most common)
- Open or shorted data wire (pinched, chafed harness)
- Bad ground or supply to one of the modules on the data bus
- Faulty TCM or ECM after wiring and power/ground verified
- Intermittent contact due to vibration or water intrusion
Fault status
Similar codes
Available brands with manuals
AUDI 11
6-speed manual gearbox 0B1, front-wheel drive — Workshop Manual (Edition 05.2014)
Workshop ManualAudi A3 (1997) – 1.6L 4-cylinder (2‑valve) Engine Mechanical Components Service Manual (AEH, AKL, APF) – Edition 07.2002
Workshop ManualAUDI A3 (2004) Workshop Manual — 2.0L FSI Turbo (4‑cyl, 4‑valve) Engine, Mechanics — Edition 03.2017
Workshop ManualAudi A3 2004 — Electrical System (Workshop Manual, Edition 02.2018)
Workshop ManualAudi A4 / A4 Cabriolet – 4.2 l V8 (5‑valve, timing chains) – Workshop Manual (Mechanics) – Edition 04.2007
Workshop ManualAudi A4 / A4 Cabriolet — Auxiliary Heater Workshop Manual (Edition 08.2004)
Workshop ManualAudi A4 / A4 Cabriolet (1.8T 4‑cyl turbo) — Motronic Injection & Ignition System Service Manual (Edition 01.2015)
Workshop ManualAudi A8 (2003) — Electrical System Workshop Manual (Edition 08.2014)
Workshop ManualAudi Q4 e-tron (Type F4) - Self-study Programme SSP 685
Workshop ManualAudi Q8 (2018) — Electrical System Workshop Manual (Edition 05.2019)
Workshop ManualAudi Servicing Manual — 7‑Speed Dual Clutch Transmission 0CJ / 0CL / 0CK / 0DN / 0DP / 0HL (Edition 05.2018)
Workshop ManualLAND ROVER 3
Land Rover Defender 300Tdi — Workshop Manual (1996 model year)
Workshop ManualLand Rover Defender Workshop Manual Supplement & Body Repair Manual (1999 & 2002 MY)
Workshop ManualLand Rover Range Rover — Electrical Library (LRL 0453ENG, 2002)
Workshop ManualP1660
Emergency Stop Fuel Shut-Off Solenoid
Causes
- Open, short or intermittent wiring on the transmission-to-engine/ECM data line
- Corroded, loose or damaged connector pins at TCM, ECM or inline connectors
- Blown fuse or loss of power/ground to one of the controllers on the bus
- Failed or intermittent Transmission Control Module (TCM) or Engine Control Module (ECM/PCM)
- Aftermarket electronics, improper repairs or chafed harness causing intermittent contact
- Software or firmware mismatch/corruption in one of the control modules
Symptoms
- Malfunction Indicator Lamp (MIL) illuminated
- Transmission may go to limp/limitation mode or display abnormal shift behavior
- Loss of transmission-related data on scan tool or inability to communicate with TCM
- Stored and/or pending communication-related DTCs
- Intermittent driveability issues if engine and transmission data are out of sync
What to check
- Use a scan tool to read stored and pending codes and confirm P1660 is current, not history-only
- Attempt communication with both ECM and TCM; note any 'no response' or 'module not present' messages
- Visually inspect wiring harnesses and connectors for damage, corrosion, pin push-out or water intrusion
- Verify battery voltage and chassis/engine grounds are clean and secure
- Check fuses and power feeds for ECM and TCM circuits
- Perform a wiggle test on harness/connectors while monitoring live data for communication dropouts
Signal parameters
- Data line is a bidirectional communication bus (CAN or manufacturer proprietary serial). Confirm protocol from service manual.
- Typical idle single-ended voltages for CAN nodes ~2.5 V; CANH rises and CANL falls during active bits (refer to manual for exact expected voltages and bit timing).
- When communicating normally, data packets should be present on the bus; signals absent or constant voltage indicate open/short.
- Any sudden jumps to battery voltage or to ground on the data line indicate hard short to power/ground.
Diagnostic algorithm
- Retrieve all related codes and freeze‑frame data with a capable scan tool. Note whether TCM and ECM respond and their software IDs.
- Verify battery voltage is within spec and inspect/clean main engine and chassis grounds.
- Inspect connectors at the TCM and ECM, plus any inline connectors and junctions along the harness. Look for corrosion, bent pins, moisture or damage.
- Check fuses and power feeds for both modules. Repair any blown fuses and trace cause if fuse blows again.
- With ignition ON, use a DVM or oscilloscope to probe the data lines at the module connectors. Compare observed voltages and waveform activity to service manual specifications.
- Perform continuity checks (with battery disconnected) from module pins to intermediate connectors and to the other module to locate opens or high resistance. Repair wiring harness as needed.
- If intermittent, perform wiggle test while monitoring bus activity to reproduce fault. Secure and repair any harness chafe points or loose connectors.
- If wiring, power and grounds are good but communication still fails, consider swapping in a known-good TCM or ECM (if available) or perform module bench testing per manufacturer procedures.
- After repairs, clear codes and road test to verify the DTC does not return and that communication is stable.
- If code returns after module replacement, re-check wiring and perform advanced diagnostics per dealer service information (may require module reprogramming or network topology checks).
Likely causes
- Damaged connector or corroded pin at TCM or ECM (most common)
- Open or shorted data wire (pinched, chafed harness)
- Bad ground or supply to one of the modules on the data bus
- Faulty TCM or ECM after wiring and power/ground verified
- Intermittent contact due to vibration or water intrusion
Fault status
Similar codes
P1660
Control Module Pins NOT Used Are Connected To B+
Causes
- Open, short or intermittent wiring on the transmission-to-engine/ECM data line
- Corroded, loose or damaged connector pins at TCM, ECM or inline connectors
- Blown fuse or loss of power/ground to one of the controllers on the bus
- Failed or intermittent Transmission Control Module (TCM) or Engine Control Module (ECM/PCM)
- Aftermarket electronics, improper repairs or chafed harness causing intermittent contact
- Software or firmware mismatch/corruption in one of the control modules
Symptoms
- Malfunction Indicator Lamp (MIL) illuminated
- Transmission may go to limp/limitation mode or display abnormal shift behavior
- Loss of transmission-related data on scan tool or inability to communicate with TCM
- Stored and/or pending communication-related DTCs
- Intermittent driveability issues if engine and transmission data are out of sync
What to check
- Use a scan tool to read stored and pending codes and confirm P1660 is current, not history-only
- Attempt communication with both ECM and TCM; note any 'no response' or 'module not present' messages
- Visually inspect wiring harnesses and connectors for damage, corrosion, pin push-out or water intrusion
- Verify battery voltage and chassis/engine grounds are clean and secure
- Check fuses and power feeds for ECM and TCM circuits
- Perform a wiggle test on harness/connectors while monitoring live data for communication dropouts
Signal parameters
- Data line is a bidirectional communication bus (CAN or manufacturer proprietary serial). Confirm protocol from service manual.
- Typical idle single-ended voltages for CAN nodes ~2.5 V; CANH rises and CANL falls during active bits (refer to manual for exact expected voltages and bit timing).
- When communicating normally, data packets should be present on the bus; signals absent or constant voltage indicate open/short.
- Any sudden jumps to battery voltage or to ground on the data line indicate hard short to power/ground.
Diagnostic algorithm
- Retrieve all related codes and freeze‑frame data with a capable scan tool. Note whether TCM and ECM respond and their software IDs.
- Verify battery voltage is within spec and inspect/clean main engine and chassis grounds.
- Inspect connectors at the TCM and ECM, plus any inline connectors and junctions along the harness. Look for corrosion, bent pins, moisture or damage.
- Check fuses and power feeds for both modules. Repair any blown fuses and trace cause if fuse blows again.
- With ignition ON, use a DVM or oscilloscope to probe the data lines at the module connectors. Compare observed voltages and waveform activity to service manual specifications.
- Perform continuity checks (with battery disconnected) from module pins to intermediate connectors and to the other module to locate opens or high resistance. Repair wiring harness as needed.
- If intermittent, perform wiggle test while monitoring bus activity to reproduce fault. Secure and repair any harness chafe points or loose connectors.
- If wiring, power and grounds are good but communication still fails, consider swapping in a known-good TCM or ECM (if available) or perform module bench testing per manufacturer procedures.
- After repairs, clear codes and road test to verify the DTC does not return and that communication is stable.
- If code returns after module replacement, re-check wiring and perform advanced diagnostics per dealer service information (may require module reprogramming or network topology checks).
Likely causes
- Damaged connector or corroded pin at TCM or ECM (most common)
- Open or shorted data wire (pinched, chafed harness)
- Bad ground or supply to one of the modules on the data bus
- Faulty TCM or ECM after wiring and power/ground verified
- Intermittent contact due to vibration or water intrusion
Fault status
Similar codes
P1660
Cooling Fans Control Circuit
Causes
- Open, short or intermittent wiring on the transmission-to-engine/ECM data line
- Corroded, loose or damaged connector pins at TCM, ECM or inline connectors
- Blown fuse or loss of power/ground to one of the controllers on the bus
- Failed or intermittent Transmission Control Module (TCM) or Engine Control Module (ECM/PCM)
- Aftermarket electronics, improper repairs or chafed harness causing intermittent contact
- Software or firmware mismatch/corruption in one of the control modules
Symptoms
- Malfunction Indicator Lamp (MIL) illuminated
- Transmission may go to limp/limitation mode or display abnormal shift behavior
- Loss of transmission-related data on scan tool or inability to communicate with TCM
- Stored and/or pending communication-related DTCs
- Intermittent driveability issues if engine and transmission data are out of sync
What to check
- Use a scan tool to read stored and pending codes and confirm P1660 is current, not history-only
- Attempt communication with both ECM and TCM; note any 'no response' or 'module not present' messages
- Visually inspect wiring harnesses and connectors for damage, corrosion, pin push-out or water intrusion
- Verify battery voltage and chassis/engine grounds are clean and secure
- Check fuses and power feeds for ECM and TCM circuits
- Perform a wiggle test on harness/connectors while monitoring live data for communication dropouts
Signal parameters
- Data line is a bidirectional communication bus (CAN or manufacturer proprietary serial). Confirm protocol from service manual.
- Typical idle single-ended voltages for CAN nodes ~2.5 V; CANH rises and CANL falls during active bits (refer to manual for exact expected voltages and bit timing).
- When communicating normally, data packets should be present on the bus; signals absent or constant voltage indicate open/short.
- Any sudden jumps to battery voltage or to ground on the data line indicate hard short to power/ground.
Diagnostic algorithm
- Retrieve all related codes and freeze‑frame data with a capable scan tool. Note whether TCM and ECM respond and their software IDs.
- Verify battery voltage is within spec and inspect/clean main engine and chassis grounds.
- Inspect connectors at the TCM and ECM, plus any inline connectors and junctions along the harness. Look for corrosion, bent pins, moisture or damage.
- Check fuses and power feeds for both modules. Repair any blown fuses and trace cause if fuse blows again.
- With ignition ON, use a DVM or oscilloscope to probe the data lines at the module connectors. Compare observed voltages and waveform activity to service manual specifications.
- Perform continuity checks (with battery disconnected) from module pins to intermediate connectors and to the other module to locate opens or high resistance. Repair wiring harness as needed.
- If intermittent, perform wiggle test while monitoring bus activity to reproduce fault. Secure and repair any harness chafe points or loose connectors.
- If wiring, power and grounds are good but communication still fails, consider swapping in a known-good TCM or ECM (if available) or perform module bench testing per manufacturer procedures.
- After repairs, clear codes and road test to verify the DTC does not return and that communication is stable.
- If code returns after module replacement, re-check wiring and perform advanced diagnostics per dealer service information (may require module reprogramming or network topology checks).
Likely causes
- Damaged connector or corroded pin at TCM or ECM (most common)
- Open or shorted data wire (pinched, chafed harness)
- Bad ground or supply to one of the modules on the data bus
- Faulty TCM or ECM after wiring and power/ground verified
- Intermittent contact due to vibration or water intrusion
Fault status
Similar codes
P1660
Fuel cut control circuit malfunction
Causes
- Open, short or intermittent wiring on the transmission-to-engine/ECM data line
- Corroded, loose or damaged connector pins at TCM, ECM or inline connectors
- Blown fuse or loss of power/ground to one of the controllers on the bus
- Failed or intermittent Transmission Control Module (TCM) or Engine Control Module (ECM/PCM)
- Aftermarket electronics, improper repairs or chafed harness causing intermittent contact
- Software or firmware mismatch/corruption in one of the control modules
Symptoms
- Malfunction Indicator Lamp (MIL) illuminated
- Transmission may go to limp/limitation mode or display abnormal shift behavior
- Loss of transmission-related data on scan tool or inability to communicate with TCM
- Stored and/or pending communication-related DTCs
- Intermittent driveability issues if engine and transmission data are out of sync
What to check
- Use a scan tool to read stored and pending codes and confirm P1660 is current, not history-only
- Attempt communication with both ECM and TCM; note any 'no response' or 'module not present' messages
- Visually inspect wiring harnesses and connectors for damage, corrosion, pin push-out or water intrusion
- Verify battery voltage and chassis/engine grounds are clean and secure
- Check fuses and power feeds for ECM and TCM circuits
- Perform a wiggle test on harness/connectors while monitoring live data for communication dropouts
Signal parameters
- Data line is a bidirectional communication bus (CAN or manufacturer proprietary serial). Confirm protocol from service manual.
- Typical idle single-ended voltages for CAN nodes ~2.5 V; CANH rises and CANL falls during active bits (refer to manual for exact expected voltages and bit timing).
- When communicating normally, data packets should be present on the bus; signals absent or constant voltage indicate open/short.
- Any sudden jumps to battery voltage or to ground on the data line indicate hard short to power/ground.
Diagnostic algorithm
- Retrieve all related codes and freeze‑frame data with a capable scan tool. Note whether TCM and ECM respond and their software IDs.
- Verify battery voltage is within spec and inspect/clean main engine and chassis grounds.
- Inspect connectors at the TCM and ECM, plus any inline connectors and junctions along the harness. Look for corrosion, bent pins, moisture or damage.
- Check fuses and power feeds for both modules. Repair any blown fuses and trace cause if fuse blows again.
- With ignition ON, use a DVM or oscilloscope to probe the data lines at the module connectors. Compare observed voltages and waveform activity to service manual specifications.
- Perform continuity checks (with battery disconnected) from module pins to intermediate connectors and to the other module to locate opens or high resistance. Repair wiring harness as needed.
- If intermittent, perform wiggle test while monitoring bus activity to reproduce fault. Secure and repair any harness chafe points or loose connectors.
- If wiring, power and grounds are good but communication still fails, consider swapping in a known-good TCM or ECM (if available) or perform module bench testing per manufacturer procedures.
- After repairs, clear codes and road test to verify the DTC does not return and that communication is stable.
- If code returns after module replacement, re-check wiring and perform advanced diagnostics per dealer service information (may require module reprogramming or network topology checks).
Likely causes
- Damaged connector or corroded pin at TCM or ECM (most common)
- Open or shorted data wire (pinched, chafed harness)
- Bad ground or supply to one of the modules on the data bus
- Faulty TCM or ECM after wiring and power/ground verified
- Intermittent contact due to vibration or water intrusion
