Citroën ë-C3 Custom OBD2: Connection Drops / Keep-Alive Fails After "Test"

Hi ABRP Team,

I am trying to set up custom OBD2 PIDs for my Citroën ë-C3 using an ELM327 v1.5 (PIC18F25K80 chip) via Bluetooth on iOS.

The Issue:

The connection is momentarily successful when I click the "Test" button in the custom OBD settings. The adapter's Link LED turns on, and it successfully fetches the UDS data (SoC, Voltage, Current). However, the moment the test finishes or I return to the map/navigation screen, the Link LED turns off, and ABRP completely stops polling data.

It seems the UDS session drops, or ABRP's parser terminates the Bluetooth socket due to a strict timeout or a keep-alive mismatch.

Troubleshooting Done:

The exact same adapter, OBD dongle, and PID/Init configuration work flawlessly in continuous polling mode using the "Car Scanner" app without dropping the connection. This isolates the issue to how ABRP handles the background polling loop or UDS session keep-alive for this specific setup.

My Configuration:

Init commands (Standard Stellantis Flow Control): ⁠ATZ, ATWS, ATE0, ATH0, ATAT1, ATL0, ATS0, ATSTFF, ATBI, ATSP6, ATSH6B4, ATFCSH6B4, ATFCSD300000, ATFCSM1, ATCRA694⁠

Keep-Alive tested: ⁠3E00⁠, ⁠AT RV⁠, and ⁠22D408⁠ (None kept the loop alive outside the test menu).

Could you please investigate if the polling loop, keep-alive handling, or timeout tolerance for custom PIDs can be optimized to maintain the UDS session?

Thank you!