Navigating the world of car modifications and diagnostics often involves using OBDII scanners to tweak settings and troubleshoot issues. For Jeep Patriot owners, apps like Jscan are popular for accessing and modifying vehicle parameters. However, experiences can vary, and sometimes, using these tools doesn’t go as smoothly as planned. This article delves into a firsthand account of a Jeep Patriot owner encountering problems after using the Jscan app to make seemingly simple modifications.
The user initially aimed to adjust two settings on their Jeep Patriot using Jscan: tire size to correct speedometer readings after tire upgrades, and Daytime Running Lights (DRLs) to switch from high beams to a combination of low beams and sidelights for a less intrusive daytime illumination. These are common modifications many car enthusiasts undertake, expecting a straightforward process. However, in this case, the modifications led to unexpected complications.
The day after making these changes via the Jscan app, the Jeep Patriot presented an engine light and entered limp mode. Limp mode, a safety feature that reduces engine power to prevent further damage, is often triggered by significant system errors. The diagnostic trouble code (DTC) associated with this issue was P0610, indicating a “TRANS CONTROL” problem, suggesting a malfunction within the transmission control system.
Resolving this issue required a series of troubleshooting steps. The owner disconnected the battery and, crucially, drained the electrical circuit by connecting the disconnected battery cables together (grounding the circuit). This process, left for about half an hour, is intended to fully reset the car’s computer systems. After reconnecting the battery, a specific ignition sequence was followed, and the engine was allowed to idle to relearn its settings. Subsequently, using the Jscan app again, the user meticulously reverted all changed settings back to their original configurations. An advanced scan and code clearing within Jscan removed the P0610 code.
Interestingly, while the P0610 code and limp mode were resolved, new codes emerged: B1634, B1630, and B1638, all related to “HIGH BEAM CONTROL CIRCUIT FRONT CONTROL.” Despite these new codes, the engine light went off, and the car returned to normal driving operation, albeit with the persistent high beam related codes and the original speedometer inaccuracy due to tire size.
Contacting the Jscan manufacturer provided some clarity. The manufacturer reportedly indicated that the Jscan app may not be fully compatible with tire size changes on the Jeep Patriot. This suggests potential limitations within the app’s programming for certain vehicle models or specific functions. The user’s experience highlights that while OBDII apps offer powerful customization options, they may not always function flawlessly across all vehicle makes and models.
Further experimentation by the user, such as attempting to activate HIDs and other features within Jscan, also resulted in the reappearance of the engine light and limp mode, reinforcing the initial findings. The user notes their Jeep Patriot is equipped with aftermarket HID projector headlights wired through relays, with the relay coils connected to the original headlight wires. This setup might be perceived as a modification by the car’s computer, potentially contributing to the error codes, especially concerning the headlight control circuits.
Considering these challenges, the user is now contemplating exploring alternative OBDII apps like Appcar Diagfca, questioning whether similar issues might arise when attempting tire size or DRL modifications with different software. This experience serves as a cautionary tale for those using OBDII apps for vehicle modifications. While these tools offer significant control, compatibility issues and unintended consequences can occur. It underscores the importance of researching compatibility, understanding potential risks, and proceeding with caution when making changes to vehicle settings via OBDII interfaces, especially when starting your diagnostic journey, or “Mestart Obdii” considerations, with any new vehicle or software.
