OBDII Modules

[patternman]

I have several ODDII BT modules from the high dollar OBDLINK MX+ to the lesser costly Veepeak and they both along with a few others all perform the same and I have had zero issues with any of mine using them with JSCAN and my SG bypass module.

I have tested (4) modules using trail view, TPMS view along with setpoint changes and there are some minimal speed issues on responses but I’m talking minimal and it should have no impact on the end result so I say save your coin and don’t spend $$ on the high dollar ones just use an approved one if using JSCAN

I didn't purchase the high dollar one either. I had one I'd bought several years ago that worked
but I got another that goes to sleep after approx 1/2 hour inactivity as I leave it plugged in.
It doesn't work with apple phones though. Paid $13.99 free ship on ebay.

Sponsored

 

[NULL POINTER]

Rhinebeck01 said:
@NULL POINTER

You mention you have had your OBDLink MX+ for "several years". When was the last time you updated the firmware on that OBDLink MX+ ? Update it if you have not done so recently and try that deed again... maybe ? you will have better luck.

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

Thanks, I appreciate your quick response. I check for updates everytime I use it. It was updated to the latest firmware version this past Saturday before I checked for the codes and tried to clear them. Maybe some codes can't be cleared with the MX+ or maybe the ECRI needs to be in place. I will give that a try tomorrow.

BTW, mine shows a mfg date of 12-17-2018 and I think I got it in early 2019. It clears codes on my F-150 just fine. Never got any codes on the vette, yet.

 

[NULL POINTER]

Rhinebeck01 said:
@NULL POINTER

You mention you have had your OBDLink MX+ for "several years". When was the last time you updated the firmware on that OBDLink MX+ ? Update it if you have not done so recently and try that deed again... maybe ? you will have better luck.

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

Thanks, I appreciate your quick response. I check for updates everytime I use it. It was updated to the latest firmware version this past Saturday before I checked for the codes and tried to clear them. Maybe some codes can't be cleared with the MX+ or maybe the ECRI needs to be in place. I will give that a try tomorrow.

BTW, mine shows a mfg date of 12-17-2018 and I think I got it in early 2019. It clears codes on my F-150 just fine. Never got any codes on the vette, yet.

Hooked up the ECRI, what a pain in the A $ $, even after removing the trim panel under the steering wheel.

The OBDLinkMX+ still could not clear those codes. I suspect they are codes that cannot be cleared until the problem source is fixed. Unfortunately there is very little info about what needs fixing anywhere on the web. Guess I'll put it on the lift and see if I can get to the connector to the T-Case and shoot some DeOxit gold on the connections and then see what happens.

 

[DooganDazs]

I had a $15 ELM327 OBD reader that worked perfectly with a few different apps to read codes, but didn't work at all with alfaOBD, wouldn't even connect. Bought the OBDLinkMX+ and had it working first try to connect. However, I do get an error when connecting to the Body Computer (and others) with ECU verification failed. I have a '22 Rubicon. Is this too new for alfaOBD? I just downloaded version 2.2.8.0 from the play store

I also have the ECRI SG bypass installed. When I ignore the alfaOBD error and go on, I'm not able to set the item that I want - trying to update the turn signals to LED. Appreciate if anyone can offer any advice. Thanks!

Sponsored