OBD2 enhanced code scanners - Appcar DiagFCA, BlueDriver, Jscan, AlfaOBD, etc.
I have the OBDLink LX and use it with both the OBDLink app as well as Jscan, works great and the LX costs a good amount less than the MX, I didn't need GMCAN or FordCAN which is the main differences between the regular MX and the LX.The MX Plus has apparently some add ons that the others dont, but I haven't had a need for them.
In the spirit of this thread, I also use HPTuners for advanced logging and tuning needs, which really isn't what this thread is about but it also has the ability to pull enhanced codes so worth mentioning
(I also have EFILive which doesn't support Jeep, but these are why I went with the OBDLink LX instead of the MX, since I have GM/Ford occasional needs and advanced functions fully covered elsewhere)
In the spirit of this thread, I also use HPTuners for advanced logging and tuning needs, which really isn't what this thread is about but it also has the ability to pull enhanced codes so worth mentioning
(I also have EFILive which doesn't support Jeep, but these are why I went with the OBDLink LX instead of the MX, since I have GM/Ford occasional needs and advanced functions fully covered elsewhere)
I've read recently that the OBDlink MX+ now has an OBDlink App which is suppose to read the advanced OBD codes. If OBDLink MX+ can read advanced codes as well as supports other 3rd party apps, this is starting to sound like a really good option. Anyone try the OBDlink App? Is the App free?
Does it allow you to use it on multiple vehicles like BlueDriver?
It's currently $70 on Amazon.
https://www.amazon.com/OBDLink-Bluet...xpY2s9dHJ1ZQ==
Does it allow you to use it on multiple vehicles like BlueDriver?
It's currently $70 on Amazon.
https://www.amazon.com/OBDLink-Bluet...xpY2s9dHJ1ZQ==
I don't like getting this thread more off topic, but in an effort to help....I noted up higher having similar issue. Jscan identified my front passenger sensor giving an erratic signal. It was a different sensor than my previous as it came with my axle swap. Anyhow, similar symptoms but randomly would throw ABS light and then it would go off a bit later. Finally replaced the sensor this week and it has yet to throw the code again. Sensors only $25 or so for Mopar one. Getting it in to the unit bearing is a pain though if you have dumb dust shields in the way behind the unit bearing. I'd identify which side is the issue and just replace the sensor. I suspect you'll see a similar code in the ABS module as I saw.
Just did a test by setting 2 DTC's in the TIPM and HP Tuners did not read them. I believe HP Tuners just reads the PCM codes, and maybe some enhanced Jeep/Chrysler codes in the PCM.
If HPT added the features in DiagFCA, it would be a killer package that did everything.
I tune with HP Tuners as well -- It does not read Jeep/FCA advanced codes as far as I can tell.
Just did a test by setting 2 DTC's in the TIPM and HP Tuners did not read them. I believe HP Tuners just reads the PCM codes, and maybe some enhanced Jeep/Chrysler codes in the PCM.
If HPT added the features in DiagFCA, it would be a killer package that did everything.

Just did a test by setting 2 DTC's in the TIPM and HP Tuners did not read them. I believe HP Tuners just reads the PCM codes, and maybe some enhanced Jeep/Chrysler codes in the PCM.
If HPT added the features in DiagFCA, it would be a killer package that did everything.

I don't know how that piece would work honestly. I'd set everything back to where it was with Jscan, then set your Superchips back to stock, then reapply your Jscan settings- if possible. I've changed a few things on Jscan and I can't say I recall all of them so I'm not sure if that would change things with my Superchips.
I'm not sure how the SC works. I know with my BullyDog it takes a snapshot of what "stock" is before it makes changes. That is what it is rewriting things back to upon uninstall. I would think that it doesn't matter necessarily what it's changing things from when it goes back to stock, but not 100% sure. For example, I can't imagine that if the programmer thinks it's changing tires back from 35 to 32 it's going to freak out if the actual jeep computer currently says tires are 37 (due to a change from another programmer). IE....it doesn't care what the current settings are, it only knows it has rewrite things back to what it thinks the factory settings were.








