OBDLink CX connection issue / Missing BLE button for BYD Seal U (Android)
Dear ABRP Support Team,
I am writing to report a persistent issue trying to connect an OBDLink CX dongle to ABRP via BLE.
My Setup:
Car: BYD Seal U (Design trim, 87 kWh)
Dongle: OBDLink CX (officially recommended by you)
Device: Android Smartphone
The Problem:
When selecting my actual car model (BYD Seal U) in the ABRP vehicle settings, the "OBD (BLE)" button is completely missing under the live data connection menu. I am only offered "Enode" or "Generic".
As a workaround, I changed the vehicle profile to the regular BYD Seal (Sedan), which successfully made the "OBD (BLE)" button appear.
However, when trying to connect the OBDLink CX via this button, the connection fails immediately every time with a standard error message ("OBD connection failed").
Troubleshooting steps I have already taken (Hardware is 100% fine): To rule out any user or hardware errors, I have thoroughly tested the setup:
Hardware Check: The OBDLink CX works perfectly and connects when using the official native OBDLink app.
BLE Channel Cleared: I ensured the dongle is not paired in the Android Bluetooth system menu. I also force-closed the native OBDLink app to ensure the BLE channel is completely free for ABRP.
App & Cache Reset: I cleared both the ABRP app cache and the Android system Bluetooth cache.
Permissions: ABRP has full permissions for "Nearby Devices" and "Location" (Always On).
No Conflicts: I completely deleted my Enode connection in ABRP before attempting the BLE connection to avoid any session conflicts.
It seems that the ABRP app either lacks the proper OBD configuration for the BYD Seal U, or the workaround using the sedan profile gets rejected by the car's specific data structure.
Could you please look into this and advise on how I can get the OBDLink CX working with my BYD Seal U? Will there be an official BLE OBD profile update for the Seal U soon?
Thank you in advance for your help.
Log in to comment and vote
Comments3
Linda ABRP
Apr 9
Hi
After BYD updated their software it’s no longer possible to use an OBD. We have added Enode as an option instead.
Wolfram T.
Apr 9
Hi ABRP Support Team,
Thank you for the quick and honest reply. That is definitely disappointing to hear after buying the recommended OBDLink CX.
Regarding your suggestion to use Enode instead: This creates a major usability issue. Every time ABRP pulls data via Enode, I am instantly kicked out of the official BYD app on my phone. Since BYD only allows one active session at a time, I constantly have to re-login to my BYD app. This frustrating behavior is exactly why I bought the OBD dongle in the first place.
Just to clarify on the OBD lock: Does this recent BYD software update affect all BYD models across the board now? I am asking because inside the ABRP app, the "OBD (BLE)" option is still fully visible and selectable if I choose the regular BYD Seal (Sedan) profile.
Since the Seal U and the regular Seal share very similar underlying battery specs, is the OBD port completely blocked by BYD on the Seal U specifically, or is it just a lack of current mapping/development for this newer model?
If there is any workaround, or if you have a beta testing program for the Seal U or the newer BYD platforms, I have the OBDLink CX plugged in and would gladly help test it.
If it's a hard lock from BYD with absolutely zero chance of a fix in the future, please let me know so I can return the dongle to the store while I still can.
Thanks again for your help!
Best regards,
Linda ABRP
Apr 9
Yes it’s for all BYD cars. We are aware of the issues with Enode and BYD cars. We had some users who tested Enode and it went well. Since it’s the only live data option right now we decided to add it for all users. We don’t have any information if the OBD is going to work again so I think you should return the OBD.