Voters 0
Live telemetry incorrectly processed (Rivian R1T)
- User Feedback
- Subscribe
 |
Ilya Zilber |
I have Rivian R1T telemetry pushed to ABRP, including speed. However, after a trip that was mostly highway driving it will show: (image attached). The actual API calls were like: api.iternio.com/1/tlm/send?api_key=XXXXX &token=XXXXXtlm={"utc":1710275749,"soc":37.900002,"lat":30.3955517,"lon":-97.8632889,"speed":109.2636,"is_charging":false,"is_dcfc":false,"is_parked":false,"odometer":21691.70208547078,"est_battery_range":196.99951035950085}
I drove about 50km, most of it on the highway. I would expect ABRP to recognize it as non "Low Speed".
Also, it calculated the "Calibrated reference consumption" as 3 miles per kwh - in reality, it was ~2.3.
Something is wrong here ...
Activity Newest / Oldest
Bo_ABRP
Status changed to: User Feedback
Bo_ABRP
Thank you, the dialog and graph will be fixed in ABRP 4.7.8. The reason for the single bar is that the telemetry data only contains SoC and no power, which means we have to revert to a less precise method of calibration.
Your ref consumption of 296 Wh/km is quite on spot with most R1Ts so it looks reasonable to me.
Bo_ABRP
Status changed to: Investigate
Ilya Zilber
BTW, I reset consumption in ABRP and redid the drive - same result.
Ilya Zilber
Just to add, the latest version, 4.7.9 still has the problem and the screen looks like this:
Ilya Zilber