New ABRP Feature : Live Data via OBD

[benk016]

This is pretty amazing, but the nerd in me sees this as a major security vulnerability particularly if someone is going to leave the OBD device plugged in all the time. Anyone connected to this device would have direct access to the vehicle computer, and it is devices like these which are essentially used by thieves to defeat vehicle security protocols during theft by resetting security tokens and reverting to known defaults after they break in. Essentially you would be potentially be making it that much easier for sophisticated thieves, as they no longer need to even get into the vehicle first, since you were kind enough to install the OBD adapter for them allowing them to do it from a distance, while taking their sweet ass time doing so as well.

I really like the idea of giving ABRP direct access to live vehicle data, but those doing so should be made well aware of the risks involved, particularly if leaving it plugged in all the time.

This is why you have to go through this during the device setup.

And the page that it links to has this

Sponsored

 

[JimmyMachE]

for now I guess I'm back to considering a 'custom display' via the CarScanner app. I just haven't read thru how to multiply the battery volts x battery current to show kW interactively.

Car Scanner shows battery power kW since long time ago. Look for parameter: Hybrid/EV Battery System Power kW

Actually, after software update the sensor might show incorrent kW value in some cars, here is simple solution: https://www.macheforum.com/site/thr...oftware-now-supports-mach-e.8922/#post-262036

 

[scoopman]

I'm on version 4.1.10 thru Play Store and I can see the support in the Android app. Unfortunately, like everyone else, I don't have a BLE dongle until tomorrow to play with it.

But the support for paring the OBD dongle under the "Car Model" section is enabled for me.

 

[benk016]

I'm on version 4.1.10 thru Play Store and I can see the support in the Android app. Unfortunately, like everyone else, I don't have a BLE dongle until tomorrow to play with it.

But the support for paring the OBD dongle under the "Car Model" section is enabled for me.

I believe the button is there, but the commands for the Mach E don't work in that release and need updated. It will fail to connect or it will just give no data.

 

[scoopman]

I believe the button is there, but the commands for the Mach E don't work in that release and need updated. It will fail to connect or it will just give no data.

oh. bummerz. anyone know if carplay version works?

 

[The Electric Duo]

oh. bummerz. anyone know if carplay version works?

It looks like the iOS version has been updated in the App Store. Now I just need my BLE ODB2 dongle (and my car, since it is at the dealer shop) to do some testing.

 

[GoGoGadgetMachE]

They wanted to get the most compatibility in the initial launch. ALL BLE adapters work on Android and iOS. Regular bluetooth works on android fine, but very few are supported witn iOS.

They may add in regular bluetooth support later, but for now focused on the best compatibility.

So Android users are more limited because iOS sucks? That's great. /s

Bluetooth Low Energy or BLE is a totally different protocol than the Bluetooth you are thinking of. The concern isn’t actually about the energy, it is that BLE doesn’t require pairing since it was made for sensors that broadcast data. This makes it easier to integrate with more devices and apps.

Pairing isn't really an issue compared to being super limited in the choice of adapters - who is going to be using this capability that can't manage the Bluetooth pairing process? The APIs are different at least on Android so they had to make some choice I guess to get it out the door. Just seems like they chose the one a lot harder to source., at least for now.

 

[GoGoGadgetMachE]

Yes you have to login and you have to add the MachE and then after you add it you have to pick the option to "Add my Car" which saves it to your profile. Then you'll get the cogwheel icon where you can go into the settings of that vehicle.

It's probably the worst UX implementation I've seen in a while.

"And I've used FordPass!" ?

 

[GoGoGadgetMachE]

There was talk a while back about limited plug / unplug cycles on the physical OBD-II port before failure. Assuming that is true, a simple OBD-II extension cable might be warranted to support the frequent cycles suggested for security reasons.

 

[benk016]

So Android users are more limited because iOS sucks? That's great. /s


Pairing isn't really an issue compared to being super limited in the choice of adapters - who is going to be using this capability that can't manage the Bluetooth pairing process? The APIs are different at least on Android so they had to make some choice I guess to get it out the door. Just seems like they chose the one a lot harder to source., at least for now.

Bluetooth classic won't work at all for iOS in this instance. I believe it's an apple limitation.

 

[Gullwingdmc]

**Known Mach E Issues**

- I have had some connectivity issues when using PAAK. If you experience connection issues, force stop the fordpass app, and disable and re-enable bluetooth and try again.

If you just wanted to run this for info, not for route planning. Could you pair the dongle to an iPad and run ABRP on there? Avoid the PAAK conflict.

 

[benk016]

If you just wanted to run this for info, not for route planning. Could you pair the dongle to an iPad and run ABRP on there? Avoid the PAAK conflict.

You would need to uninstall ABRP from your phone or force close it. The pairing is saved on your account and carries to other devices. So the phone could still try and connect if it was running in the background.

 

[DaMeatMan]

This is why you have to go through this during the device setup.

And the page that it links to has this

Glad to see they did their due diligence here in warning the user of potential risks! ?

 

[scoopman]

So Android users are more limited because iOS sucks? That's great. /s


Pairing isn't really an issue compared to being super limited in the choice of adapters - who is going to be using this capability that can't manage the Bluetooth pairing process? The APIs are different at least on Android so they had to make some choice I guess to get it out the door. Just seems like they chose the one a lot harder to source., at least for now.

I have 3 OBD adapters of various ages and flavors, including a recent OBDLink MX+ which I got because of its (relatively better) security and power cut-off features to use with Car Scanner. None of them will work with this due to their focus on BLE.

So I'm now purchasing a fourth adapter. There are limited choices for BLE adapters, but more worrisome is that the OBDLink CX (recommended by ABRP) isn't made anymore, and is basically the only BLE one that doesn't leave discovery and pairing on all the time. Kinda annoying, but hopefully this may be worth it for better road trip planning on our Mach-E and ID.4.

 

[Gullwingdmc]

You would need to uninstall ABRP from your phone or force close it. The pairing is saved on your account and carries to other devices. So the phone could still try and connect if it was running in the background.

Thanks for the heads up. I may create a separate account for the iPad then.

Sponsored