Skip to main content

Request for developer access and OBD PID contribution for Seres 3

Bug Reports

Hello ABRP team, I’m an IT engineer and EV owner and I would like to help you add proper OBD support for the Seres 3 (also known as DFSK/Fengon E3)

I’m currently using your app with an OBD BLE dongle Vlink MC+ and I can successfully connect, but ABRP cannot find the battery SoC PID for this car (error “Unable to find SoC in vehicle data”).

Would it be possible to get developer / advanced OBD access (PID editor, extended logging, etc.) for my account so that I can:

• Capture detailed OBD frames from my Seres 3 during real driving.

• Provide you with logs and any information needed to define the correct SoC and battery‑related PIDs for this model.

I’m happy to run test builds or specific logging scenarios if needed, and to share all collected data so that you can create and maintain an official Seres 3 / Fengon E3 PID definition in your database.

Here is my setup:

• Vehicle: Seres 3 (European version)

• OBD dongle: Vlink MC+ (BLE)

• Platform: iOS (ABRP mobile app, latest version)

Thank you in advance for any developer access or instructions you can provide to help integrate this vehicle.

Best regards

Where does this happen?
ABRP version number (found at bottom of settings menu)
Posted by Franck BENDER ·
Status: Completed1 comment

Log in to comment and vote

Comments1

  • Linda ABRP

    Team•

    Dec 11, 2025

    Hi

    We don’t have any developer access for our users.

    I got this answer from my colleague:
    “He can use the OBD PID editor we have already but that is basically the last step on his journey.
    First he needs to get the proper pids and equations, this is nothing we do on our app.
    He might get these details from CarScanner, not sure it supports that car though.”