2014+ Jeep Cherokee Forums banner
21 - 40 of 59 Posts
The last time I used alfaOBD I had a custom-made cable that plugged into the canbus block under the center console. I now have an ECRI but I have not tried again since.
 
  • Like
Reactions: maxiflight
Unfortunately yes for any FCA car post-2019. It's actually kind of ironic.... They added to Security Gateway Module after someone was able to hack a GC WK2 or Cherokee wirelessly back in like 2013 or 2014 through the 3G uConnect. Now that 3G is gone, unless you have a 4G radio with active subscription, your car can't be wirelessly hacked hence the security module's raison d'être went away with 3G.
I suspect FCA used that debacle to make lemonade out of lemons for themselves. Ever since the SGW module, most folks now need to visit their friendly CDJR to do what used to be simple things, like clearing OBD codes, etc.
 
Discussion starter · #23 ·
I suspect FCA used that debacle to make lemonade out of lemons for themselves. Ever since the SGW module, most folks now need to visit their friendly CDJR to do what used to be simple things, like clearing OBD codes, etc.
I suspect FCA used that debacle to make lemonade out of lemons for themselves. Ever since the SGW module, most folks now need to visit their friendly CDJR to do what used to be simple things, like clearing OBD codes, etc.
And it probably worked for a while too. ka-ching!
 
Unfortunately yes for any FCA car post-2019. It's actually kind of ironic.... They added to Security Gateway Module after someone was able to hack a GC WK2 or Cherokee wirelessly back in like 2013 or 2014 through the 3G uConnect. Now that 3G is gone, unless you have a 4G radio with active subscription, your car can't be wirelessly hacked hence the security module's raison d'être went away with 3G.
But, unfortunately as well, you still get a complimentary trial subscription when you buy the vehicle new.
The only system that can't be hacked is the one that is disabled! :cool:
 
While your at it, go ahead and grab the hid kit

... because that's where "a certain company' gets theirs from

Have a great day and God bless 🙏
You mean the Hylux kit ? If so, I finally figured that one out a few months ago. Some black paint and 'Made in the USA' is a good distraction on the fake one ;)

 
You mean the Hylux kit ? If so, I finally figured that one out a few months ago. Some black paint and 'Made in the USA' is a good distraction on the fake one ;)

The entire setup can be put together for less than 20$
I haven't really seen true engineering, everyone is copying everyone else and putting a sticker on it as if it's their own

I've been looking at the 8.4 c3 uaq?? Whatever...
All that's needed is for two modules to be swapped out ☠
 
Discussion starter · #35 ·
I'm just catching up on some threads now. Regarding the eBay/Amazon blue ELM327 dongles, note it's a little deceiving...

  • Pretty much EVERY OBDII adapter will work with AlfaOBD (as well as iNCarDoc, Torque, and countless other OBDIIapps out there etc.). This is because basic ELM327 adapters only are intended to access the ECU for engine OBD features. Thus they access the standard high-speed CANBUS which all cars (incl. the Cherokee) use for engine, transmission, powertrain etc. management. (pulling codes, finding out if your car is emissions-ready etc.)
  • The difference is that more expensive adapters will also talk to the intermediate-speed CANBUS as well which is needed for some of the Cherokee (and Jeep, Dodge, etc.) features like HVAC, door modules, etc. To use an inexpensive OBDII adapter on the intermediate-speed CANBUS you need a special (blue) cross-over cable.
The larger hassle comes when you try to do a proxi align. If you're using an inexpensive adapter, you can't complete the proxi align without the blue swapped-pin (crossover) cable because the proxi align tries to talk to ALL the modules in the car.

--------------------------
Just as a point of reference, below is the data architecture of the Cherokee CANBUS.

  • From the OBDII port (yellow arrow) communication goes to the Body Control Module (BCM) which can be thought of as the 'master module'. On 2019+ cars there would be a new module, the Security Gateway Module (SGM), here before the BCM. You can read values with the SGM in place but cannot edit/write values. To do that you need the SGM bypass cable.
  • The BCM can talk to both the high-speed CANBUS (shown by the red arrow branch) and the intermediate-speed CANBUS (the purple arrowed branch). For IT guys out there, while the BCM can talk to both networks, it does not bridge both networks.
    • Cheap OBDII dongles can only speak to the red-arrow modules; the Powertrain Control Module, ABS, Instrument Panel Cluster (IPC), Adaptive Cruise Control (ACC), etc.
    • More expensive OBDII dongles can speak to the the red-arrowed modules PLUS the purple-arrowed modules; HVAC, Premium audio AMP, Passenger Door Module (PDM), Integrated Center Stack (ICS) etc.
A proxi align tries to recognize and save the state of ('align') ALL the modules in the car. Cheaper dongles will fail on any of the purple-arrowed modules.

Image


CHEROKEE MODULES
ABS
Anti Lock Brakes
ACC Adaptive Cruise Control
AHLM Headlamp Leveling
AMP Amplifier
BCM Body Controller
CSWM Comfort Seat Wheel Module
DDM Driver Door Module
DTCM Drive Train Control Module
EDM External Disc Module
EPB Electrical Parking Brake
EPS Electric Power Steering
ESL Electronic Steering Lock
ESM Electronic Shifter
FFCM Forward Facing Camera Module
HVAC Heat, Ventilation and A/C
ICS Integrated Center Stack
IPC Instrument Panel Cluster
LBSS Left Blind Spot Sensor
MSM Memory Seat Module
OCM Occupant Classification
ORC Occupant Restraint Air Bag
PAM Parking Aid Module
PCM Powertrain Control Module
PDM Passenger Door Module
PLGM Power Liftgate
PTU Power Transfer Unit
RADIO Radio
RBSS Right Blind Spot Sensor
RDM Rear Drive Module
RFH Radio Frequency Hub
RRM Radio Receiver Module
SCCM Steering Column Control Module
TCM Transmission Control Module
 
That's a lot of modules to fry in a lightning storm. That list is a prime example of why modern cars are a love hate relationship for mechanics. Release the gremlins...

Here, have some foglights --- Temu specials 😆
Next time you're hunting Amazon just know that the majority of individuals on there make their monies by reselling items. That extra 20$ is the next day delivery tax.

AlphaOBD will be fully functional if you find the photo with obdator written on it. That's also one of the ones alphaobd lists in it's FAQ or somewhere I read. You want the obdator one, I don't know why but just adding that word on the dongle fixes everything 🥂

What all have y'all unlocked in the programmming? Remember, most companies production factories are based in China. Huawei chipmaker just figured that out the hard way, SCIM - KIRIN.
i
Image

Image
 
Discussion starter · #39 · (Edited)
Thanks everyone
Just helping @Gary Kline find your post....
Thanks @Lindy!

Sorry folks, I've been away the last few weeks and have been posting remotely so I'm slowly been catching up.

------------------------------------------------

OBD-II Adapter/Dongle Review: vLinker MC+ vs. OBDLink MX+

So, last month I had the chance to actually test head-to-head the new OBD-II adapter, vLinker MC+, with the tried & true, OBDLink MX+ using AlfaOBD.

Here's a review....


1. COST
The vLinker MC+ clearly wins here. Coupled with the cost of AlfaOBD ($49), the total AlfaOBD/vLinker MC+ package can be had for $90. The same AlfaOBD/OBDLink MX+ package is almost $200.​
Image



2. Form factor/design
It's a tie. Both are well built. It's clear the vLinker MC+ was meant as a direct competitor (aka: copy :cool:) of the OBDLink MX+.

Image


Image




3. Connectivity
It's a tie. Both the vLinker MC+ and OBDLink MX+ fully support Android and iOS on Bluetooth. Connecting them to the Cherokee is straight-forward and reliable.​
Image
Image





4. Speed
The win goes to OBDLink MX+ with 115,200 baud support. Advertising itself as the "World's fastest BT OBD-II adapter" it's reliable all the way up to the highest speed in AlfaOBD. The vLinker MC+ works perfectly through 38,400 baud but starts experiencing errors at the highest speed (115,200). The speed difference is really only noticeable in one place; when doing a proxy align. With the 115,200 baud OBDLink MX+ a proxy align takes about 20 seconds to complete. With the 38,400 baud vLinker MC+, a proxy align takes about 60 seconds to complete. For any manual operation in AlfaOBD, there's no discernable difference between the two speeds.​
Image
Settings to use below for each adapter
Image

Image




4. CANBUS Compatability
It's a tie. Both the vLinker MC+ and OBDLink MX+ fully support both the Cherokee's standard high speed CANBUS network and intermediate speed (MS-CAN) network with no adapters or cables.

a. For example, the screenshot below shows a test of the HVAC blower motor. The HVAC module is on the intermediate speed network and normally requires a MS-CAN "blue cable" when used with a non-supported adapter. The HVAC module could be fully accessed with both the vLinker MC+ and OBDLink MX+ with no additional cables.​

Image



b. Test below is a proxy align with the vLinker MC+. Here also, both networks can be fully accessed without needing an adapter or blue cable leading to a successful proxy align. (as mentioned above, the only difference between the two adapters on a proxy align is the speed; 20 seconds vs. 60 seconds to completion.).​

PSA : Always do a proxy backup before doing a proxy align in case you screw the pooch
Image




------------------------

CONCLUSION/TAKE-AWAYS

  • Both the vLinker MC+ and OBDLink MX+ are fully compatible with AlfaOBD and can utilize all its features.
  • The main difference between the two adapters are (1) cost and (2) the speed of the UART chip. The vLinker MC+ ($37) is good through 38,400 baud whereas the OBDLink MX+ ($140) is good to 115,200 baud. The main discernable difference between the two speeds it the time it takes to perform a proxy alignment; 20 seconds vs. 60 seconds. When using the app manually such as when going through the parameters, changing settings, setting up and activating graphs of engine parameters etc., there's no discernable difference between the two speeds.
  • If you already have an OBDLink MX+ there's probably little reason to switch (since you've already bought it) however if you're (A) currently using a generic ELM 327-compatible adapter and the blue-cable swapping game is getting old or (B) don't have any adapter at all yet and want to start experimenting with AlfaOBD, the vLinker MC+ is a good option
  • If you're planning on doing regular, extensive configuration work on your Cherokee or other FCA vehicles where seconds count, then you may want to invest in the higher-priced adapter OBDLink MX+ to shave a little time off proxy aligns.
  • While I didn't mention it earlier, both adapters are fully "ELM 327" compatible so you can use most OBD-II software with them. For example, I tested both adapters with my other main go-to app inCarDoc which I use to read $Mode06 data to see misfire counts and other pending issues that might not have triggered a CEL light yet. Both worked with it and other generic OBD-II apps fine so with either of these you can toss your AliExpress-specials.
  • Also, note that both of these products end in a 'plus' (+). Their respective manufacturers also make "non plus" versions (e.g. vLinker MC and OBDLink MX) I would not recommend them as the savings is small and certain features are not the same. For example, the vLinker MC+ works on both iOS and Android. The vLinker MC is Android-only. Unless you know for certain you'll never need to connect using the other platform, it's best to have an adapter that supports both Android and iOS.

In the end, both work, so you can't go wrong either way.

Reply back if any questions. (y)


ps: *Note, at the time of this posting, vGate was selling their 'old shell design' vLinker MC+ for a reduced price until stocks are depleted which is what I purchased. Assume at some point in the future only the new design shell will be available which is like $10-$15 more. Note both are claimed to be the same inside with same versioning, support, chips etc., only cosmetic shell differences.
 
Thanks everyone

Thanks @Lindy!

Sorry folks, I've been away the last few weeks and have been posting remotely so I'm slowly been catching up.

------------------------------------------------

OBD-II Adapter/Dongle Review: vLinker MC+ vs. OBDLink MX+

So, last month I had the chance to actually test head-to-head the new OBD-II adapter, vLinker MC+ , with the tried & true, OBDLink MX+ using AlfaOBD app.

Here's a review....


1. COST
The vLinker MC+ clearly wins here. Coupled with the cost of AlfaOBD ($49), the total AlfaOBD/vLinker MC+ package can be had for $90. The same AlfaOBD/OBDLink MX+ package is almost $200.​
View attachment 227244


2. Form factor/design
It's a tie. Both are well built. It's clear the vLinker MC+ was meant as a direct competitor (aka: copy :cool:) of the OBDLink MX+.

View attachment 227212

View attachment 227213



3. Connectivity
It's a tie. Both the vLinker MC+ and OBDLink MX+ fully support Android and iOS on Bluetooth. Connecting them to the Cherokee is straight-forward and reliable.​
View attachment 227215 View attachment 227216




4. Speed
The win does to OBDLink MX+ with 115,200 baud support. Advertising itself as the "World's fastest BT OBD-II adapter" it's reliable all the way up to the highest speed in AlfaOBD. The vLinker MC+ works perfectly through 38,400 baud but starts experiencing errors at the highest speed (115,200). The speed difference is really only noticeable in one place; when doing a proxy align. With the 115,200 baud OBDLink MX+ a proxy align takes about 20 seconds to complete. With the 38,400 baud vLinker MC+, a proxy align takes about 60 seconds to complete. For any manual operation in AlfaOBD, there's no discernable difference between the two speeds.​
Settings to use below for each adapter
View attachment 227229
View attachment 227230



4. CANBUS Compatability
It's a tie. Both the vLinker MC+ and OBDLink MX+ fully support both the Cherokee's standard high speed CANBUS network and intermediate speed (MS-CAN) network with no adapters or cables.

a. For example, the screenshot below shows a test of the HVAC blower motor. The HVAC module is on the intermediate speed network and normally requires a MS-CAN "blue cable" when used with a non-supported adapter. The HVAC module could be fully accessed with both the vLinker MC+ and OBDLink MX+ with no additional cables.​

View attachment 227231


b. Test below is a proxy align with the vLinker MC+. Here also, both networks can be fully accessed without needing an adapter or blue cable leading to a successful proxy align. (as mentioned above, the only difference between the two adapters on a proxy align is the speed; 20 seconds vs. 60 seconds to completion.)​

View attachment 227235



------------------------

CONCLUSION/TAKE-AWAYS

  • Both the vLinker MC+ and OBDLink MX+ are fully compatible with AlfaOBD and can utilize all its features.
  • The main difference between the two adapters are (1) cost and (2) the speed of the UART chip. The vLinker MC+ ($37) is good through 38,400 baud whereas the OBDLink MX+ ($140) is good to 115,200 baud. The main discernable difference between the two speeds it the time it takes to perform a proxy alignment; 20 seconds vs. 60 seconds. When using the app manually such as when going through the parameters, changing settings, setting up and activating graphs of engine parameters etc., there's no discernable difference between the two speeds.
  • If you already have an OBDLink MX+ there's probably little reason to switch (since you've already bought it) however if you're (A) currently using a generic ELM 327-compatible adapter and switching to the blue adapter cable all the time or (B) don't have any adapter at all yet and want to start experimenting with AlfaOBD, the vLinker MC+ is a good option
  • If you're planning on doing regular, extensive configuration work on your Cherokee or other FCA vehicles where seconds count, then you may want to invest in the higher-priced adapter OBDLink MX+ to shave a little time off proxy aligns.
  • While I didn't mention it earlier, both adapters are fully "ELM 327" compatible so you can use most OBD-II software with them. For example, I tested both adapters with my other main go-to app inCarDoc which I use to read $Mode06 data to see misfire counts and other pending issues that might not have triggered a CEL light yet. Both worked with it and other generic OBD-II apps fine.

In the end, both work, so you can't go wrong either way.

Reply back if any questions. (y)


ps: *Note, at the time of this posting, vGate was selling their 'old shell design' vLinker MC+ for a reduced price until stocks are depleted which is what I purchased. Assume at some point in the future only the new design shell will be available which is like $10-$15 more. Note both are claimed to be the same inside with same versioning, support, chips etc., only cosmetic shell differences.
Awesome review ! Thank you :)
 
21 - 40 of 59 Posts