Toggle Side Panel

Shopping Cart

No products in the basket.

Shopping Cart

No products in the basket.

Close search
Home / DTC / P1592 — data logger vehicle data available

P1592 — data logger vehicle data available

Detailed page for trouble code P1592.

34,405codes
59brands
11,914generic
22,491specific
All codes P-codes (Powertrain) B-codes (Body) C-codes (Chassis) U-codes (Network/User) Tesla Alerts
Reset
Code

P1592

LAND ROVER P — Powertrain

data logger vehicle data available

Brand: LAND ROVER
Type: P — Powertrain
AI status
Completed
ready
Completed 100%
Page language: EN

Causes

  • Onboard data logger triggered by an event (engine, transmission, ABS, airbag, emissions, etc.)
  • Stored event file(s) present in control module memory
  • Diagnostic tool or telematics system flagged available data
  • Module detected a transient fault or boundary condition and logged data

Symptoms

  • No immediate drivability change in many cases
  • Instrument cluster message or indicator stating data/logger available
  • Malfunction Indicator Lamp (MIL) may or may not be illuminated depending on the triggering event
  • Related systems may have logged faults or limp-home behavior during the event

What to check

  • Connect manufacturer diagnostic tool (Jaguar Land Rover SDD/SDP/IDS or approved scanner) and read stored events/data logger files
  • Read all DTCs from all modules and note freeze-frame and occurrence counts
  • Check for pending or history codes related to the event (engine, transmission, ABS, airbag, etc.)
  • Inspect vehicle electrical system: battery state-of-charge, charging system voltage and ground connections
  • Verify module software level and recent service bulletins that reference data logger messages

Signal parameters

  • Engine RPM
  • Vehicle speed
  • Throttle/accelerator position
  • Ignition timing and fuel trim values
  • Coolant and intake air temperatures
  • Boost/boost control or MAP readings (if applicable)

Diagnostic algorithm

  1. Use the manufacturer diagnostic application to retrieve and download the data logger/event files from the relevant control module(s).
  2. Review event logs, freeze-frame data and timestamps to identify what parameters were out of range at the time of the event.
  3. Correlate logged data with any concurrent DTCs or driver-reported symptoms.
  4. If data indicates a specific sensor/actuator or circuit, perform targeted live-data checks, wiring inspection, and component tests (voltage, resistance, ground).
  5. Repair or replace suspect components or repair wiring/grounds as indicated by evidence from the logs and tests.
  6. Clear the data logger flag/DTCs, then recreate the conditions (road test or controlled test) to verify the fault does not reoccur. Re-scan for new or related codes.
  7. If logs indicate module communication issues, check CAN bus integrity and module power/grounds; update module software if applicable per service bulletins.

Likely causes

  • Transient sensor or actuator out-of-range condition recorded (e.g., overboost, high temp, limp mode activation)
  • Intermittent electrical issue captured (voltage dip, CAN comm glitch)
  • Emissions system event (DPF regen anomaly, EGR or injector problem) was logged
  • Crash/impact or restraint system event stored
  • A scheduled or user-initiated logging session completed and stored data

Fault status

⚠️ Status
Data logger event(s) stored — vehicle data available for download. Review logged events to diagnose underlying issue.
🟡 Repair difficulty: Medium
⏱️ Diagnostic time: 0.5-2.0 hours

Similar codes

P1590 P1591 P1593 P0600 U0100
274

Browse 274 LAND ROVER manuals: repair procedures, diagnostics, wiring diagrams, component locations, service data and Labor Times by year, model and trim.

LAND ROVER

Your experience will help others
+100 karma for a short comment :)
Keep it short and practical. Up to 500 characters.
Send to email
Code

P1592

SUBARU P — Powertrain

Neutral Position Switch Circuit MT Model

Brand: SUBARU
Type: P — Powertrain
AI status
Completed
ready
Completed 100%
Page language: EN

Causes

  • Onboard data logger triggered by an event (engine, transmission, ABS, airbag, emissions, etc.)
  • Stored event file(s) present in control module memory
  • Diagnostic tool or telematics system flagged available data
  • Module detected a transient fault or boundary condition and logged data

Symptoms

  • No immediate drivability change in many cases
  • Instrument cluster message or indicator stating data/logger available
  • Malfunction Indicator Lamp (MIL) may or may not be illuminated depending on the triggering event
  • Related systems may have logged faults or limp-home behavior during the event

What to check

  • Connect manufacturer diagnostic tool (Jaguar Land Rover SDD/SDP/IDS or approved scanner) and read stored events/data logger files
  • Read all DTCs from all modules and note freeze-frame and occurrence counts
  • Check for pending or history codes related to the event (engine, transmission, ABS, airbag, etc.)
  • Inspect vehicle electrical system: battery state-of-charge, charging system voltage and ground connections
  • Verify module software level and recent service bulletins that reference data logger messages

Signal parameters

  • Engine RPM
  • Vehicle speed
  • Throttle/accelerator position
  • Ignition timing and fuel trim values
  • Coolant and intake air temperatures
  • Boost/boost control or MAP readings (if applicable)

Diagnostic algorithm

  1. Use the manufacturer diagnostic application to retrieve and download the data logger/event files from the relevant control module(s).
  2. Review event logs, freeze-frame data and timestamps to identify what parameters were out of range at the time of the event.
  3. Correlate logged data with any concurrent DTCs or driver-reported symptoms.
  4. If data indicates a specific sensor/actuator or circuit, perform targeted live-data checks, wiring inspection, and component tests (voltage, resistance, ground).
  5. Repair or replace suspect components or repair wiring/grounds as indicated by evidence from the logs and tests.
  6. Clear the data logger flag/DTCs, then recreate the conditions (road test or controlled test) to verify the fault does not reoccur. Re-scan for new or related codes.
  7. If logs indicate module communication issues, check CAN bus integrity and module power/grounds; update module software if applicable per service bulletins.

Likely causes

  • Transient sensor or actuator out-of-range condition recorded (e.g., overboost, high temp, limp mode activation)
  • Intermittent electrical issue captured (voltage dip, CAN comm glitch)
  • Emissions system event (DPF regen anomaly, EGR or injector problem) was logged
  • Crash/impact or restraint system event stored
  • A scheduled or user-initiated logging session completed and stored data

Fault status

⚠️ Status
Data logger event(s) stored — vehicle data available for download. Review logged events to diagnose underlying issue.
🟡 Repair difficulty: Medium
⏱️ Diagnostic time: 0.5-2.0 hours

Similar codes

P1590 P1591 P1593 P0600 U0100
Your experience will help others
+100 karma for a short comment :)
Keep it short and practical. Up to 500 characters.
Send to email

Report

Harassment or bullying behavior
Contains mature or sensitive content
Contains misleading or false information
Contains abusive or derogatory content
Contains spam, fake content or potential malware

Block Member?

Please confirm you want to block this member.

You will no longer be able to:

  • See blocked member's posts
  • Mention this member in posts
  • Invite this member to groups
  • Message this member
  • Add this member as a connection

Please note: This action will also remove this member from your connections and send a report to the site admin. Please allow a few minutes for this process to complete.

Report

You have already reported this .