OBD2 Trouble with Jscan on Your Jeep Patriot? Tire Size and DRL Issues Revealed

For Jeep Patriot owners looking to customize their vehicles using OBD2 apps, experiences can vary widely. One user encountered significant issues while using the popular Jscan app, specifically when attempting to adjust tire size and Daytime Running Lights (DRLs) settings on their Jeep Patriot. This article delves into these problems, offering insights for anyone considering similar modifications with an OBD2 scanner on their Patriot.

The user reported making changes via the Jscan app to accommodate a tire size change and to switch the DRLs from high beams to low beams and sidelights. However, the very next day, an unwelcome engine light illuminated the dashboard, and the Jeep Patriot entered limp mode. This severely restricted the vehicle’s performance and raised immediate concerns about the OBD2 modifications.

Troubleshooting became necessary to rectify the situation. The owner detailed a multi-step process to resolve the limp mode and engine light, which involved:

  • Battery Disconnection: Disconnecting the battery was the first crucial step.
  • Circuit Drain: Draining the electrical circuit by connecting the disconnected battery cables together (grounding) for about half an hour. This process likely resets various electronic control modules within the Jeep.
  • Battery Reconnection and Ignition Cycling: Reconnecting the battery and cycling the ignition on and off several times.
  • Engine Idle Relearning: Running the engine to allow it to relearn its idle settings, aiming for around 800 RPM.
  • Jscan Settings Restoration: Using the Jscan app to review and revert all modified settings back to their original configurations.
  • Advanced Scan and Code Deletion: Performing an advanced scan with Jscan and deleting all error codes, particularly the P0610 TRANS CONTROL code which was responsible for the limp mode.

After these steps, the P0610 code was successfully cleared, and the limp mode was resolved. However, further scans revealed persistent codes: B1634, B1630, and B1638, all related to HIGH BEAM CONTROL CIRCUIT FRONT CONTROL. Despite these remaining codes, the engine light turned off, and the Jeep Patriot returned to normal driving operation, albeit without the desired DRL and tire size modifications.

Contacting the Jscan manufacturer provided further clarity. The manufacturer confirmed that the Jscan app is known to have limitations when it comes to tire size adjustments on the Jeep Patriot. This crucial piece of information highlights the importance of verifying OBD2 app compatibility and limitations, especially when making parameter changes that can affect vehicle performance.

Currently, the vehicle continues to display the headlight-related codes (B1633, B1634, and B1638). The user also notes that the high beams activate when switching to low beams, indicating a potential issue stemming from the attempted DRL modification. Furthermore, the speedometer accuracy is slightly affected by the uncorrected tire size.

The user also experimented with enabling HIDs and other settings within Jscan, each time encountering the engine light and limp mode issue, reinforcing the incompatibility for certain modifications. The presence of aftermarket HID projector headlights, wired through relays, might also be contributing to the issue. The Jeep’s computer system could be detecting the altered electrical load or configuration of the headlights, triggering error codes.

Looking for alternatives, the user is now considering the Appcar Diagfca OBD2 app. The key question remains: will Appcar Diagfca offer better compatibility for tire size and DRL modifications on the Jeep Patriot, or will similar problems arise? This experience serves as a cautionary tale for Jeep Patriot owners using OBD2 scanners for modifications. While these tools offer customization potential, compatibility issues can lead to significant vehicle problems. Thorough research and understanding of app limitations are essential before making changes to your vehicle’s settings via OBD2.

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply

Your email address will not be published. Required fields are marked *