OBD Live Data Connection Fails After Saving – Fisker Ocean One / Custom PIDs

Hi ABRP Support Team,

I'm experiencing an issue with the built-in OBD live data connection in ABRP for my 2023 Fisker Ocean One, using a vLinker FD BLE 4.0 adapter and custom OBD PIDs.

I have managed to establish communication with the vehicle and successfully retrieve live telemetry through ABRP's PID editor and connection wizard. However, the connection stops working immediately after completing the setup and pressing Save.

What works:

• The BLE adapter connects successfully.

• All three steps in the OBD connection wizard complete successfully with green checkmarks:

  • Loading vehicle configuration

  • BLE connection

  • Vehicle connection

• The custom PID test successfully retrieves vehicle data, including battery SoC, voltage, current, battery temperature and speed.

• The values appear plausible and respond to changes in vehicle conditions.

• The connection wizard also displays the retrieved telemetry correctly.

The problem:

As soon as I press Save and return to the main ABRP interface, the vehicle changes to "Not connected".

The OBD connection is no longer providing live telemetry, even though it was working correctly just seconds earlier in the setup wizard.

I have reproduced the exact same behavior on two different Android devices:

1. Carlinkit TBOX Ultra (Android)

2. Samsung Android smartphone

The adapter is connected directly through ABRP, not through the Android Bluetooth pairing menu.

Troubleshooting performed:

• Tested with all configured custom PIDs.

• Disabled all PIDs except battery SoC (222050).

• Confirmed that the same disconnection occurs even with only one active PID.

• Tested different initialization commands.

With the initialization command ATSH7E1, the PID test and all three connection wizard steps complete successfully.

However, the PID test log includes:

failed to parse response OBD command: NaNTS Raw OBD response: ATSH7E1OK 

Despite this parsing message, the test successfully retrieves SoC.

When removing the initialization command entirely, the PID test reports:

error writing init commands could not get commands for type init from [object Object] fisker:ocean:23:100:one 

I also tested ATE0 as the initialization command. The PID test succeeded, but the normal connection wizard failed at the vehicle configuration loading stage, displaying:

"Vehicle configuration could not be loaded. Check your internet connection and try again."

This error does not occur with ATSH7E1.

Additionally, during troubleshooting, the ABRP OBD Connection entry unexpectedly disappeared from the available live data connections, leaving only Car Scanner and Custom Connection visible.

My questions:

1. Is there a known issue with custom OBD PID configurations for the Fisker Ocean One?

2. Does the PID test use a different connection or initialization mechanism than normal live data polling?

3. Could the issue be related to how ABRP loads or activates the saved vehicle configuration?

4. Is there a way to retrieve detailed diagnostic logs to identify why the connection fails after saving?

It seems that communication with the vehicle and the adapter works correctly, but something fails when ABRP transitions from the connection wizard to normal live data operation.

I would be happy to provide screenshots, configuration details, raw OBD responses, or additional diagnostic logs.

Thank you for your assistance.

Best regards