01 It's Easier Than You Think To Make Your Headlights Look Bra… • 02 At What Mileage Do Most Cars Start Having Issues? • 03 Starter Motor: Functions, Parts, Troubleshooting, and Commo… • 04 Can a Bad Alternator Cause Power Steering Problems? • 05 When Should the Oxygen Sensor Be Replaced? A Comprehensive • 06 Why You Should Follow The Wheel Tightening Sequence • 07 Fuel Injectors: A Comprehensive Guide to Their Anatomy, Fun… • 08 Pressed the Gas, But Going Nowhere? Why Your Car Won't Acce… • 09 From Tires to Driveshafts: An Expert Explains Why Your Car … • 10 The Truth About Fuel Additives: Do They Work and Are They S… •

DTC codes / Mercedes-Benz codes / P1613

P1613 · Mercedes-BenzIFI Control Module N37

P1613 on Mercedes-Benz vehicles indicates that the instrument cluster control module, designated N37 in the manufacturer's wiring diagrams, has reported an internal fault or a communication failure within its own circuitry. The module continuously self-checks its memory, processors, and output drivers, and when a discrepancy is detected it stores this code and illuminates the instrument cluster warning lamp. This is a module-level fault rather than a sensor or actuator failure, so diagnosis must focus on power, ground, and CAN (Controller Area Network) integrity before condemning the cluster itself.

SystemPowertrain
Code typeMercedes-Benz specific
SeverityMedium
Fix difficultyProfessional
AreaComputer and output circuits

Symptoms you may notice

  • Instrument cluster warning lamp illuminated, often with no other obvious driveability complaint
  • Multiple gauges or indicator lamps behaving erratically or failing to illuminate
  • Intermittent loss of dashboard illumination or flickering display segments
  • Odometer, trip meter, or service interval display showing incorrect or frozen values
  • Other control modules logging communication codes because the cluster acts as a gateway on some chassis
  • Often no symptoms besides the warning light, especially if the fault is stored but not currently active

Common causes, most likely first

  1. Internal failure of the instrument cluster control module N37, such as corrupted memory or a failed processor
  2. Poor or corroded electrical connections at the cluster harness connectors, particularly the ground pins
  3. Voltage supply issues to the cluster, including a weak battery or failing voltage regulator causing low-voltage resets
  4. CAN bus communication faults between the cluster and other modules, often due to chafed wiring or a faulty transceiver
  5. Water ingress or condensation inside the instrument cluster causing circuit board corrosion
  6. Aftermarket radio or accessory installation that disturbed cluster wiring or introduced CAN bus interference
  7. Software corruption in the cluster requiring reflashing or coding, sometimes after a failed battery replacement procedure

How to diagnose and fix it

  1. Verify battery voltage and charging system output, as low voltage is a common trigger for spurious module codes
  2. Inspect the cluster harness connectors for corrosion, loose pins, or backed-out terminals and clean or repair as needed
  3. Perform a voltage drop test on the cluster power and ground circuits to confirm solid electrical supply
  4. Use a Mercedes-Benz-specific scan tool to read live data from the cluster and check for other stored communication codes
  5. Check the CAN bus for shorts or opens between the cluster and the central gateway, repairing wiring as required
  6. If electrical checks pass, reflash or code the instrument cluster with the latest software using manufacturer procedures
  7. Replace the instrument cluster control module N37 only after all wiring and power checks are confirmed good, then code the replacement

Before you replace the instrument cluster

  • A weak battery or a recent jump-start is one of the most overlooked triggers for P1613, because the cluster logs an internal fault when supply voltage dips during cranking.
  • Aftermarket audio or alarm installations frequently disturb the CAN wiring behind the dash, causing the cluster to set communication-related internal codes that mimic a failed module.
  • On several Mercedes-Benz chassis the instrument cluster acts as a gateway, so a fault elsewhere on the CAN bus can cause the cluster to store P1613 even though the cluster itself is healthy.
  • Water damage from a leaking windshield seal or clogged sunroof drains can corrode the cluster circuit board and set this code long before any visible symptoms appear.
  • Clearing the code and driving the vehicle through several ignition cycles is a valid step to confirm whether the fault is current or historic before committing to module replacement.

Can I keep driving with P1613?

The vehicle is generally safe to drive with P1613 because the fault usually affects instrumentation rather than engine or brake control, but you should avoid long trips until the cause is confirmed. If the cluster display fails completely or other warning lamps stop working, have the vehicle inspected promptly because you may lose critical driver information.

Tools that help

Tools we recommend are in the Auto Veteran shop on Amazon. As an Amazon Associate we earn from qualifying purchases.

Guidance is general and written for Mercedes-Benz vehicles. Exact tests and values vary by model, so confirm the fault before replacing parts.

Running on fumes Free guides aren't free to make. Top up the tank. Any amount, one time. Fuel the Garage