Request for developer access and OBD PID contribution for Seres 3

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?
iOS
ABRP version number (found at bottom of settings menu)
6.1.9

Please authenticate to join the conversation.

Upvoters
Status

Completed

Board

🐛 Bug Reports

Date

5 months ago

Author

Franck BENDER

Subscribe to post

Get notified by email when there are changes.