Recent Posts

1

OBDLink MX+ / Developer Documentation Request

« Last post by tallgees3 on Today at 06:18:20 pm »

I was looking for integration documentation for iOS and Android for The OBDLink MX+.  I'm writing Android and iOS apps.

2

OBDLink MX+ / MX+ reading 2016 Toyota Sequoia tire pressure

« Last post by jsippel on Today at 09:52:58 am »

Hi,

I set the pressure units to psi, but when I use the MX+ to read the tire pressure on my 2016 Toyota Sequoia the reading appears to be psi (atmospheric), not psi (gauge), so the readings are high by about 14.7 lbs.  Is there any way to adjust the reported tire pressure so that it displays gauge tire pressure and not atmospheric?

3

Developer Forum / Re: MY25 Mustang Mach-E lockout

« Last post by sillygoose on Yesterday at 06:38:26 am »

We have seen vehicles where the module will not support physical addressing (H:7E2 for example). Try sending 1001 or 1003 using header 7DF.

I may not have tried using 7DF, the direct addressing  modules are MIA:

  .stpx(.stpx0 [STPX h:7E0, d:1001, r:1 → 5001003201F4]
  .stpx(.stpx1 [STPX h:7E0, d:1003, r:1 → 5003003201F4]
  .stpx(.stpx2 [STPX h:7E2, d:1001, r:1 → NO DATA]
  .stpx(.stpx3 [STPX h:7E2, d:1003, r:1 → NO DATA]
  .stpx(.stpx4 [STPX h:7E4, d:1001, r:1 → NO DATA]
  .stpx(.stpx5 [STPX h:7E4, d:1003, r:1 → NO DATA]
  .stpx(.stpx6 [STPX h:7E6, d:1001, r:1 → 5001003201F4]
  .stpx(.stpx7 [STPX h:7E6, d:1003, r:1 → 5003003201F4]

Today I am trying the MSCAN bus to see if they moved, I'll try your suggestion next, it is a slow process as I don't have access to a MY2025 Mach-E and have to post a build on TestFlight for the tester to try.

4

Developer Forum / Re: MY25 Mustang Mach-E lockout

« Last post by STN-Brian on March 05, 2026, 05:14:02 pm »

We have seen vehicles where the module will not support physical addressing (H:7E2 for example). Try sending 1001 or 1003 using header 7DF.

5

Developer Forum / Re: MY25 Mustang Mach-E lockout

« Last post by sillygoose on March 05, 2026, 10:09:28 am »

Here's what I found.

Made some progress by pinging 7DF and seeing what modules replied. Turns out that the PCM (7E0), SOBDMC (7E6), and SOBDMB (7E7) are all accessible. Since gear commanded, HVB voltage and current PIDs replied on SOBDMC, I am able to record trips on the 2025 Mach-E.

Given the lack of response from the SOBDM (7E2) and BECM (7E4) modules, I think I'll try the MSCAN bus in case they moved them. Ford did that in the Lightning so maybe I will get lucky.

6

Third-Party Apps / Re: new iOS app in development

« Last post by dtimestwo on March 03, 2026, 10:06:37 pm »

Thank you!

7

Developer Forum / Re: UDS Service 3E: TesterPresent

« Last post by STN-Brian on March 03, 2026, 08:11:23 pm »

Sounds like "STPTO 0" is what you need then.

STPTO will set the timeout for all messages, until a reset or you change it again.

8

OBDLink MX+ / Re: Developer documentation

« Last post by STN-Brian on March 03, 2026, 08:07:51 pm »

It look like we have sent you the documentation to your email. Let us know if you have any more questions.

9

Third-Party Apps / Re: new iOS app in development

« Last post by STN-Brian on March 03, 2026, 08:05:13 pm »

I have sent you an email.

10

Developer Forum / Re: MY25 Mustang Mach-E lockout

« Last post by sillygoose on March 03, 2026, 07:57:06 pm »

Thanks for the link and insight.

According to the MY25 Mach-E owner, Forscan can read the gear commanded PID.

I wrote some test code and I still get replies from the PCM and SOBDMC but not the SOBDM or BECM, makes me wonder they just moved to a different module address or the gateway module is dropping the reads:

03:04.350 .vehicleCapabilities(
  .stpx(.stpx0 [STPX h:7E0, d:1001, r:1 → 5001003201F4].     -- PCM
  .stpx(.stpx1 [STPX h:7E0, d:1003, r:1 → 5003003201F4]
  .stpx(.stpx2 [STPX h:7E2, d:1001, r:1 → NO DATA]               -- SOBDM
  .stpx(.stpx3 [STPX h:7E2, d:1003, r:1 → NO DATA]
  .stpx(.stpx4 [STPX h:7E4, d:1001, r:1 → NO DATA]              -- BECM
  .stpx(.stpx5 [STPX h:7E4, d:1003, r:1 → NO DATA]
  .stpx(.stpx6 [STPX h:7E6, d:1001, r:1 → 5001003201F4].    -- SOBDMC
  .stpx(.stpx7 [STPX h:7E6, d:1003, r:1 → 5003003201F4]
)

The same code on my MY24 Lightning:

24:18.950 .vehicleCapabilities(
  .stpx(.stpx0 [STPX h:7E0, d:1001, r:1 → 5001003201F4]
  .stpx(.stpx1 [STPX h:7E0, d:1003, r:1 → 5003003201F4]
  .stpx(.stpx2 [STPX h:7E2, d:1001, r:1 → 5001003201F4]
  .stpx(.stpx3 [STPX h:7E2, d:1003, r:1 → 5003003201F4]
  .stpx(.stpx4 [STPX h:7E4, d:1001, r:1 → 5001003201F4]
  .stpx(.stpx5 [STPX h:7E4, d:1003, r:1 → 5003003201F4]
  .stpx(.stpx6 [STPX h:7E6, d:1001, r:1 → 5001003201F4]
  .stpx(.stpx7 [STPX h:7E6, d:1003, r:1 → 5003003201F4]
)

Any how, Forscan shows me Gear Commanded on the SOBDMC (and BECM/SOBDM/GSM) on an older Mach-E so I will try reading it there and see if I get anywhere.

Thanks for your help.