recommended odb2 reader with app for 4xe?

[mrtm1970]

The two cables you disconnect from the security gateway plug into the ECRI dedicated bypass module. The OBDLink scan tool plugs into the OBDll port.

I strongly .... very strongly encourage you to buy the security gateway extension cable from ZAutomotive and wait for it to arrive before you fool with the SGW connections.. This way, you will only have to deal with the SGW cables once...

Here is a pic of the connectors (circled in red) way up there that you will deal with..

Just bought the Z-Automotive extension cable… I might eventually go to the JL Tazer in the future.

Will I keep these always attached or only when doing things? I am way out of warranty and plan to never go to a dealership unless I REALLY need to.

Sponsored

 

[Rhinebeck01]

Just bought the Z-Automotive extension cable…

Will I keep these always attached or only when doing things? I am way out of warranty and plan to never go to a dealership unless I REALLY need to.

You will leave the ZAutomotive security gateway extension cable hooked up permanently. You can remove it when you sell the JL and re-coop what you paid for the cable or just leave the extension in place when you eventually sell the JL.

You can leave the ECRI dedicated bypass module hooked up 24/7, 365 days of the year. This way it is in play whenever you want to use your OBDLink can tool.

IF you take the JL into a dealership service dept., do before the visit, be sure you remove the ECRI bypass module and attach the 2 cables you had going to it to the ends of the ZAutomotive security gateway extension cable.

Important: Be sure to update the firmware on your OBDLink MX+ OBD2 Bluetooth Scanner.
Read here: https://www.jlwranglerforums.com/forum/threads/update-your-bluetooth-obd2-scanner-firmware-updates-important.97511/

Also.... if you want you can daisy chain a @SmartStopStart unit with the ECRI dedicated bypass module so you can deal with ESS.
https://www.jlwranglerforums.com/fo...-should-have-been-designed.13946/post-2294877

 

[Rhinebeck01]

@mrtm1970

I know you are into lighting.. Here is a JSCAN setting that will light up those dark dark Florida back roads..

Fogs with High Beams:
ADAPTATION ---> Vehicle user settings --> Front Fog Lamp Dropout Enable On/Off --> Target Value = Deactivated

------

This is a cool one that will make your JL stand out from the others on the road..

Turn Signals for DRL's:
Maybe need: ADAPTATION ---> DRL--> Day time running lights Configuration- Canada DRL
ADAPTATION ---> DRL - Day time running lights - settings --> DRL Lamp Location --> Turn Signal DRL

 

[aputnam]

The two cables you disconnect from the security gateway plug into the ECRI dedicated bypass module. The OBDLink scan tool plugs into the OBDll port.

I strongly .... very strongly encourage you to buy the security gateway extension cable from ZAutomotive and wait for it to arrive before you fool with the SGW connections.. This way, you will only have to deal with the SGW cables once...

Here is a pic of the connectors (circled in red) way up there that you will deal with..

thanks for all the detail!
Just ordered mine (new OBD reader, the security gateway plug into the ECRI dedicated bypass module) as you recommended. will get the jscan app next. I've got OBD readers, but they're basic or dedicated for other vehicles. had a hiccup this morning I wanted to check out and realized, through threads like this, that I needed to have the right stuff for it. thanks again!

 

[jaymz]

Kinda pointless though to have the OBDll scan tool, have paid for JSCAN and.... and all you can do is read the code(s).

1st time your JL goes into limp mode, etc., you will wish you had a dedicated SGW bypass module or an old school Chrysler 12+8 Programming Cable, in play so you can clear the code that is causing the issue.

I was wondering why the OP, thought there was something special lets say with a 4xe, JL that would necessitate a certain OBDll scan tool other then a scan tool "Highly Rated" by JSCAN or another app. he were opting to use..

I know this thread is a bit old, and not that I disagree with what you're saying, but the code doesn't cause the issue. The issue causes the code. And in addition to that, permanent codes cannot be cleared without resolving the issue that set it, and most other codes won't prevent you from driving the vehicle anyway.

That said, it is kinda pointless to have the ability to read codes, but not clear them.

 

[Rhinebeck01]

I know this thread is a bit old, and not that I disagree with what you're saying, but the code doesn't cause the issue. The issue causes the code. And in addition to that, permanent codes cannot be cleared without resolving the issue that set it, and most other codes won't prevent you from driving the vehicle anyway.

That said, it is kinda pointless to have the ability to read codes, but not clear them.

I never said or implied the code causes the issue...

A guy or gal, that has never had his JL throw a code and then immediately go into limp mode... and then used his/her OBDll scan tool to quickly clear the code so he could at the very least, get out of limp mode for a bit so he could get the JL home/or off the trail, etc., would think like you do...

Agreed though .... indeed it is "kinda pointless to have the ability to read codes, but not clear them."

An example of something that causes a code to be thrown and immediately the JL/JK goes into limp mode is improper/incorrect use of a throttle controller. Say you change throttle controller modes while actively using the gas pedal... code gets thrown and limp mode occurs immediately.
You then just clear the code. With that said, in this incidence there is nothing to fix.... BUT, you do need to clear the code.. -> and from then on do not change modes while actively working the gas pedal. (This is just one example)

.

 

[jaymz]

I never said or implied the code causes the issue...

A guy or gal, that has never had his JL throw a code and then immediately go into limp mode... and then used his/her OBDll scan tool to quickly clear the code so he could at the very least, get out of limp mode for a bit so he could get the JL home/or off the trail, etc., would think like you do...

Agreed though .... indeed it is "kinda pointless to have the ability to read codes, but not clear them."

An example of something that causes a code to be thrown and immediately the JL/JK goes into limp mode is improper/incorrect use of a throttle controller. Say you change throttle controller modes while actively using the gas pedal... code gets thrown and limp mode occurs immediately.
You then just clear the code. With that said, in this incidence there is nothing to fix.... BUT, you do need to clear the code.. -> and from then on do not change modes while actively working the gas pedal. (This is just one example)

.

No desire to start an argument, but you literally said “….so you can clear the code that is causing the issue”.

That’s what prompted me to respond in the first place.

 

[Rhinebeck01]

No desire to start an argument, but you literally said “….so you can clear the code that is causing the issue”.

That’s what prompted me to respond in the first place.

No argument... I just edited that post.

I see what you mean. For sure, I did not want to relay the idea that the code caused the issue.
Kind of a given but I guess there are those that do not know better.

Anyway, edited it. Thanks for pointing out my wording error.

Sponsored