Issue with SoC drop and extreme reference consumption when combining Enode + OBD2 (Stellantis / Peugeot e-308)

Bug ReportsJun 13

When using both a cloud connection (Enode) and a direct OBD2 BLE dongle simultaneously in ABRP, a conflict occurs between the two data sources at the start of a trip. This causes a major error in the calibration of the reference consumption.

The Cause: While parked, Enode reads the net (dashboard) SoC (e.g., 72%). As soon as the trip starts and the OBD2 dongle connects live, ABRP switches to the gross (real) SoC provided by the BMS via the OBD2 port (e.g., 67%).
The Result: ABRP registers this ~5% discrepancy as a sudden, massive drop in battery capacity during the very first minute of driving. Because of this, the calibrated reference consumption instantly spikes to unrealistic values (such as 756 Wh/km), which completely ruins the route planning.

Where does this happen?
ABRP version number (found at bottom of settings menu)

Posted by ABRP User #2782225 · Jun 13

Awaiting Clarification10

ABRP User #2782225

•

Jun 16

Unfortunately, the same problem occurs without Enode

Bo (ABRP)

Team•

Jun 17

Thanks for reporting! I can see an e208 and and e308 on your account, but it does not seem like the e308 has live data. Can you help us find the right vehicle?

ABRP User #2782225
•
Jun 17
It is a Peugeot E-308, but there is no account option for this and according to the internet, the E-208 is the same car.
It all seems to work well if I first turn on the car for 30 seconds and then start the car. But this is not very convenient.
- Bo (ABRP)
  Team•
  Jun 17
  Ah, that’s good information for us; so the E-208 OBD commands work fine for the E-308?
  We will look into why this affects your reference consumption because it should not when you are using OBD - we ignore SoC changes if we get the additional data.
  Bo (ABRP)
  Team•
  Jun 17
  Update: The ref consumption is 185 Wh/km for the “E-208” which is very reasonable. Are you referring to the consumption seen in “Drive & Charge History”?
  ABRP User #2782225
  •
  Jun 17
  The consumption is getting more accurate because I now turn the car on briefly before starting it every time, which ensures the SOC is correct. Then it is almost identical to the car's consumption, see image
  Bo (ABRP)
  Team•
  Jun 18
  Thanks for the clarification! Thankfully what you see in the Drive&Charge history is just a representation of the recording of the drive. The actual reference consumption (measured as Wh/km at 110 km/h in good conditions) is correctly estimated based on your OBD data only.
  We will look into if we can wait for proper OBD data before recording the first point to avoid the visual issues you see.
  ABRP User #2782225
  •
  Jun 17
  Jup, SEC, Vermogen (KW), bereik (KM), Spanning (V), Ref verbruik (WH/km), accu temp, Degradatie (%), Resteerde Accu (kwh) works wel.
  Bo (ABRP)
  Team•
  Jun 18
  The E-208 from 2024 uses a different platform based on BYD, and requires different OBD commands - this is what you use for your E-308 today. Is your E-308 also based on this BYD battery, do you know? Did it also change for the 24 model year? (I see we don’t have a 24 or later in the library yet)
  ABRP User #2782225
  •
  Jun 18
  Thanks for getting back to me! the Peugeot e-308 does not use a BYD battery. It uses a 54 kWh (51 kWh usable) NMC 811 battery pack. This battery is manufactured by CATL (and Stellantis' joint-venture ACC)
  The 2024 Peugeot e-208 (the 156 hp / 115 kW version) uses the exact same CATL NMC battery and eMotors powertrain as my e-308. This is why they share the exact same OBD commands.
  Regarding the performance: once the connection is established, everything works perfectly and the data is accurate. The only issue is the start-up phase: for the first 10 a 30 seconds

Issue with SoC drop and extreme reference consumption when combining Enode + OBD2 (Stellantis / Peugeot e-308)

Comments10