Skip to main content

2026 Peugeot e-rifter OBD incompatibility

Bug Reports

2026 Peugeot e-rifter.

When I connect an OBD dongle (OBDLink CX), my car gives warnings regarding some of the sensors.

I understand it’s because ABRP is polling the car at a fast rate and the car does not like this.

Is this a fair interpretation as to what is going on or is it something else?

If it is the speed of the polling, can this data rate be reduced in software or is there something else I could try to make it work?

Finally, will connecting the OBD cause any damage to the car?

thanks,

David

Where does this happen?
ABRP version number (found at bottom of settings menu)
Posted by ABRP User #2529794 ·
Status: Awaiting Clarification12 comments

Log in to comment and vote

Comments12

  • Mahde - ABRP changed status to Awaiting Clarification
    Team•

    Jun 29

    Pinned

    Hello @David Vincent,

    The OBD will not cause damage to the vehicle as we only use it to get live data.

    We are not aware of this being reported to us previously regarding the warnings you receive. Can you send us a screenshot of what the warnings are saying? Does it happen for every single time you plug the OBD device in the car or occasionally?

    • ABRP User #2529794

      •

      Jun 30

      Hi, thanks for the reply.

      Yes it did happen every time I started the car with the OBD connected.

      I can’t remember the exact wording but it was multiple warning about the sensors not starting. (The collision sensors).

      When I disconnected the OBD things worked ok.

      I saw on this forum that other people were having similar issues and that somebody had a work round method of using the profile for an e-208. I’ve tried this and it seems to work ok. Obviously the drag and weight coefficients will be different but I assume that ABRP will adapt as I drive it more.

      it would be nice to have a dedicated profile for the e-Rifter though.

      I hope this helps,

      Best regards,

      David

      • ABRP User #2529794

        •

        Jun 30

        This is where I got the work around method from…. Screenshot….