As a Dodge Challenger owner and someone who likes to keep an eye on my car’s health, I decided to try out the BlueDriver Bluetooth OBD2 Scanner. I’d heard good things about it, and was curious how it would perform with my 2019 Dodge Challenger RT Scat Pack Widebody. Here’s my experience, including a heads-up for anyone with a newer Dodge about a potential OBD2 port firewall issue.
Initially, I ran into a snag right out of the gate. I plugged the BlueDriver module into the OBD2 port, paired it with my phone, but nothing happened. It simply wouldn’t connect. Frustrated, I reached out to BlueDriver support. To my surprise, they responded almost instantly with some incredibly helpful information. Turns out, the issue was quite simple: the engine needs to be running for the BlueDriver to establish a connection. I had assumed that just having the car in ‘Run’ mode would suffice, but nope, the engine has to be fully started. Once I started the engine, the BlueDriver connected within seconds and began working perfectly. It even performed a firmware update right away.
One feature I immediately noticed and appreciated was the BlueDriver’s smog test and “smog test readiness check.” This is particularly useful here in Ontario, Canada, where vehicles 7 years and older require a DriveClean emissions test. While my 2019 Challenger is still far from that requirement, I have older vehicles in the family, so knowing the BlueDriver can handle this is a bonus. The “readiness check” is especially valuable. Nobody wants to waste time and money on an official smog test, only to fail due to a “PCM not ready” status, often after recent car repairs. In Ontario, you get one free test, but failing it due to readiness issues is frustrating. I remember when my 2011 Chevy Cruze failed a smog test after a coolant manifold repair because of this exact “PCM not ready” problem. The BlueDriver’s readiness check can save you both time and the $35 test fee by letting you know if your car is actually ready for the official emissions test.
Now, let’s talk about the Dodge OBD2 port firewall, also known as the “secure gateway.” Starting in 2018, Dodge implemented this security measure. Essentially, while OBD2 scanners like the BlueDriver can read data – allowing you to monitor engine parameters and diagnose issues – this firewall prevents “write” commands to the ECU/PCM through the front OBD2 port. This means you likely won’t be able to clear check engine lights (CELs) or perform other write-related functions using the standard OBD2 port on 2018 and newer Dodge Challengers.
Thankfully, there are workarounds available for this limitation. Z Automotive, a well-known name in the Dodge modification community, offers a couple of solutions. The first is their “Double Bypass.” This is a custom wiring harness that installs in the trunk and provides a secondary, non-firewalled OBD2 port at the rear of the car. The second option is the “T-harness,” which is a Y-splitter that adds a second, bypass OBD2 port without the security restrictions, while keeping the original port functional.
I haven’t yet installed a Z Automotive Double-Bypass or T-harness in my Challenger. I’m still considering which route to take. I’m curious to hear from other 2019+ Dodge Challenger owners: Has anyone successfully used the Z Automotive bypass solutions with their BlueDriver or other OBD2 scanners to clear codes or perform write functions? Share your experiences in the comments – it would be great to learn more and help other Challenger enthusiasts navigate this OBD2 firewall issue.
