Engine-CodesChrysler – P1685 Chrysler

P1685 Chrysler Code - Wrong or Invalid Key Message Received from SKIM

Quick Answer

The P1685 Chrysler diagnostic trouble code indicates that the Engine Control Module (ECM) has received an incorrect or invalid key message from the Sentry Key Immobilizer Module (SKIM). Common causes include Faulty SKIM module, Malfunctioning key fob, Wiring issue between SKIM module and ECM. Severity is High - diagnose this code as soon as possible. Driving is not recommended if the warning light is flashing, the engine runs poorly, or safety-related symptoms are present.

What it means
P1685 Chrysler indicates Wrong or Invalid Key Message Received from SKIM.
Common causes
Common causes include Faulty SKIM module, Malfunctioning key fob, Wiring issue between SKIM module and ECM.
Severity
High - diagnose this code as soon as possible.
Can I drive?
Driving is not recommended if the warning light is flashing, the engine runs poorly, or safety-related symptoms are present.
Table of contents Created and updated by William Orellana on Sep 06, 2024
💬 Need more help? Ask Auto Expert for instant answers — it's free!
AutoCodes App

Fix Your Car Smarter

Try the New AutoCodes App!

Get complete OBDII diagnostics, repair solutions, and cost estimates, plus AI chat support on demand.

AutoCodes App on Google Play

Code P1685 Chrysler Description

The P1685 Chrysler diagnostic trouble code indicates that the Engine Control Module (ECM) has received an incorrect or invalid key message from the Sentry Key Immobilizer Module (SKIM). The SKIM is a security feature that prevents the vehicle from starting unless the correct key is used. When the ECM detects an issue with the key message, it will trigger this code and the vehicle may not start or have limited functionality.

OBDII Code P1685 Chrysler - Wrong or Invalid Key Message Received from SKIM
P1685 Chrysler Code - Wrong or Invalid Key Message Received from SKIM

Common Causes of P1685 Chrysler

  1. Faulty SKIM module
  2. Malfunctioning key fob
  3. Wiring issue between SKIM module and ECM
  4. ECM malfunction

Symptoms of P1685 Chrysler

  1. Engine not starting
  2. Engine stalling while driving
  3. Limited engine power
  4. Illumination of the security light on the dashboard
  5. Inability to program new keys

How to Fix P1685 Chrysler

  1. Check and replace the key fob battery
  2. Inspect and repair any damaged wiring between SKIM module and ECM
  3. Test and, if necessary, replace the SKIM module
  4. Program new keys if needed
  5. Clear the code from the ECM memory and perform a system reset

Cost to Fix P1685 Chrysler

The cost of repairing a P1685 Chrysler code can vary depending on the specific cause of the issue and the labor rates of the repair shop. On average, the cost of replacing a faulty SKIM module can range from $300 to $600, while replacing a key fob battery may only cost a few dollars. Wiring repairs and ECM replacements can be more expensive, potentially costing up to $1000 or more. It's recommended to consult with a qualified mechanic or dealership for a more accurate estimate based on your vehicle's make and model.

Need more information about the P1685 Chrysler code?

Need more information on how to fix the P1685 Chrysler code? Get Access to Factory Service Manuals

Need Help with the Code?

Get the P1685 Chrysler code diagnosed by a professional: Find a repair shop in your area

About the author: William Orellana is a Master Mechanic and Mechanical Engineer with over 30 years of experience diagnosing and repairing vehicles. Learn more about his background.

Frequently Asked Questions about P1685 Chrysler Code

1. What are the common symptoms of OBDII code P1685 Chrysler?

- Common symptoms include the engine not starting, the "Wrong Key Message" appearing on the dashboard, and the vehicle going into a security lockout mode.

2. What is the main cause of OBDII code P1685 Chrysler?

- The main cause of this code is a communication issue between the Sentry Key Immobilizer Module (SKIM) and the Engine Control Module (ECM).

3. How can I diagnose OBDII code P1685 Chrysler?

- Diagnosis involves using a scan tool to retrieve the code and checking for any related issues with the SKIM system or key fob.

4. Can a faulty key fob trigger OBDII code P1685 Chrysler?

- Yes, a faulty key fob or an improperly programmed key can trigger this code if it fails to communicate with the SKIM module.

5. What are some repair tips for fixing OBDII code P1685 Chrysler?

- Repair tips include checking the key fob battery, reprogramming the key fob, inspecting the SKIM module connections, and ensuring the key is properly synced with the vehicle.

6. Is it safe to drive with OBDII code P1685 Chrysler active?

- It is not recommended to drive with this code active as it can lead to starting issues and potential security lockouts while on the road.

7. Can a DIY enthusiast fix OBDII code P1685 Chrysler at home?

- Depending on the underlying cause, some DIY enthusiasts may be able to address this code at home by performing basic troubleshooting and repairs related to the SKIM system.

8. How much does it typically cost to repair OBDII code P1685 Chrysler at a mechanic?

- The cost of repair can vary depending on the exact cause of the issue, but it may range from $100 to $500 at a mechanic, including parts and labor.

9. Will resetting the ECM clear OBDII code P1685 Chrysler?

- Resetting the ECM may temporarily clear the code, but if the root cause of the issue is not addressed, the code is likely to reappear once the problem resurfaces.

10. Can OBDII code P1685 Chrysler be a recurring problem?

- Yes, if the underlying issue with the SKIM system or key fob is not properly resolved, the code may recur intermittently.

Discuss the causes and fixes for P1685 Chrysler OBDII Code

  • I have P1685 dtc code.
    2001 Chrysler Sebring
    The red light on the insterment panel goes out, so it is reading the chip.
    It is one of the original factory keys. It works the dor locks also. I try to start the car, but will only run for a couple of seconds.
    What's my problem?

  • Have you had any repairs done? Have you tried clearing the code? Any other codes?