Recent Posts

1

OBDLink EX / Re: Firmware Version 5.12.4 issues

« Last post by STN-Brian on Yesterday at 05:55:21 pm »

Thank you for reporting this issue. I'll look into it. For now you can use this link to download firmware.

Firmware updates

Also, if you didn't know, our new firmware update utility will automatically download the correct firmware for you. You can download it from the link above.

2

OBDLink EX / Re: Firmware Version 5.12.4 issues

« Last post by Shawnf350 on Yesterday at 05:15:30 pm »

I'll let staff know the file is not available for download.
What tool do you own that you are trying to update.

Kind regards,
Shawn

3

OBDLink MX+ / Re: 2020 Toyota Tacoma Service Mode

« Last post by Shawnf350 on Yesterday at 05:03:27 pm »

You may be able to find a third party application that's capable of resetting it,  but I'm not aware of an
Is this an OEM or aftermarket radio?


I'll see if I can locate anything in the service manuals as well.

Kind regards,
Shawn

4

OBDLink EX / Firmware Version 5.12.4 issues

« Last post by cyberdiamond on March 30, 2026, 05:15:37 pm »

Firmware Version 5.12.4 download zip file missing from downloads page.

When I did try via the phone app it had an error message (from memory) cannot read bootloader?

I also don't fully trust the OTG adaptor as it wiggles and loses connection some times and would not want that to happen during a firmware update.

5

OBDLink MX+ / 2020 Toyota Tacoma Service Mode

« Last post by paulrc on March 29, 2026, 02:28:45 pm »

I have a MX+ and wanted to know if I can reset the service mode on my Tacoma. I had some work done a few weeks ago and after that I had no remote service through the app. It said the truck was still being serviced and remote services would remain offline until the repairs were complete. After the repairs were complete normally you start the truck you get a message on the oem head unit that says Press OK to exit service mode and return to regular driving. Issue was that I replaced the head unit 5 months ago and everything worked fine until the repairs were done. With the new head unit I didn't get that message.

So I am wondering if the OBDLink MX+ can reset that service mode? There were no codes or alerts active when I scanned but I didn't dig further into all the things the MX+ can do yet.

Thanks

Paul

6

Third-Party Apps / Re: IOS Third party app development connection issue

« Last post by Shawnf350 on March 28, 2026, 05:08:22 pm »

Tom,  I've sent you an email.
Please respond to the email address that I've provided you.

Kind regards,
Shawn

7

Third-Party Apps / IOS Third party app development connection issue

« Last post by Tom34667 on March 28, 2026, 04:07:33 am »

Hello ScanTool.net Support Team,

My name is Tom, and I am currently developing a custom iOS diagnostic application that communicates with OBD adapters over Bluetooth. I am specifically working to integrate support for the OBDLink MX+.

I am able to successfully detect the MX+ device using CoreBluetooth and initiate a connection. However, I am unable to discover usable services/characteristics or establish a stable communication channel for sending and receiving ELM327 commands. The connection typically times out or returns no usable UART interface.

From your documentation, I understand that the MX+ fully emulates the ELM327 command set over a UART-style interface once communication is established. My challenge appears to be at the BLE transport layer rather than the command layer.

To properly support the MX+ in my app, I would greatly appreciate any guidance you can provide on the following:

1. BLE Service and Characteristic Information 
   - Are there specific service UUIDs and characteristic UUIDs used for UART communication? 
   - Are these services hidden until a handshake or initialization occurs?

2. Connection / Initialization Requirements 
   - Is there a required handshake, authentication sequence, or wake-up command before services become available? 
   - Does the MX+ require bonding/pairing at the OS level prior to communication?

3. Protocol / MFi Requirements 
   - Does communication require the ExternalAccessory framework instead of CoreBluetooth? 
   - Are there specific protocol strings (e.g., com.obdlink.mx, com.obdlink.mxplus) that must be declared in Info.plist?

4. BLE Mode Clarification 
   - Does the MX+ expose a standard BLE UART (transparent serial) profile, or is a proprietary GATT implementation used?

5. Developer Resources 
   - Is there any available SDK, sample code, or developer documentation specifically for third-party app integration on iOS?

For reference, I am able to connect and communicate successfully with standard BLE ELM327 adapters using generic UART services (e.g., FFE0/FFE1), which suggests my implementation is functioning correctly for non-proprietary devices.

I would greatly appreciate any technical details or guidance that would allow proper integration with the MX+. My goal is to build a robust diagnostic app with a professional interface similar to existing scan tools, and full MX+ support would be a key feature.

Thank you for your time and support.

Best regards, 
Tom

8

OBDLink CX / Comments about CX sleep

« Last post by wsanders on March 27, 2026, 09:25:57 pm »

[Rewritten version.]

After the last upgrade to my preferred app, Car Scanner OBD, the CX didn't seem to be going to sleep anymore. I've modified the "default" parameters to disable VL sleep and reduce the UART sleep to 300 sec and it behaves better.

The manual says voltage level sleep is disabled but the sleep parameters on mine were set as follows (output from STSLCS command):

CTRL MODE: NATIVE
PWR_CTRL: LOW PWR = LOW
UART SLEEP: ON, 600 s
UART WAKE: ON, 0-0 us
EXT INPUT: LOW = SLEEP
EXT SLEEP: OFF, LOW FOR 3000 ms
EXT WAKE: ON, HIGH FOR 2000 ms
VL SLEEP: ON, <13.00V FOR 10800 s
VL WAKE: OFF, >13.20V FOR 1 s
VCHG WA

As far as I can tell, the app is not sending any commands that would change the CX sleep parameters.

While the device goes to sleep, it is still listening for bluetooth connections, which will trigger UART activity. iOS will not trigger a reconnection itself, just apps. Since the Car Scanner app runs in the background, it will stay connected to the CX unless explicity diconnected if the CX remains withing range.

After upgrading the firmware to 5.12.4 the power LED no longer blinks periodically when the device is asleep.

Using VL sleep wake might be inappropriate for my Niro EV because the car wakes up at random every few hours when idle to do "stuff." What is does, I have no idea, but one of the things it does is top off the 12V battery charge from the HV traction battery, so this probably fires the VL wakeup.




[/size][/size][/font]

9

OBDLink CX / Re: Would CX work with a 2023 Kia Niro EV?

« Last post by wsanders on March 27, 2026, 09:07:36 pm »

Yes, I purchased one and it works fine. The only issue is the CX doesn't seem to be able to read both K-line KWP2000 (pins 7/15)  and CAN  ISO 15765-4 (pins 6/13) at the same time, at least given the commands that Car Scanner OBD uses (the iphone app I use.)  The Niro may have multiple K-lines on other pins like some other Kias, but the CX will only read the ones on pins 7/15. These are not documented anywhere anyway, so it's not a big deal.

10

OBDLink LX Bluetooth / Re: Fimerware

« Last post by STN-Manny on March 27, 2026, 10:40:56 am »

La versión de firmware 5.6.19 es la última versión para el LX.