Collect Data at High Frequency, Send Data in Batches

[kezarjg]

I would like to propose an enhancement to support collecting data at a high frequency and sending it in batches. Specifically, I am interested in understanding if there is an API call to support:

1. Collect consumption data at high frequency – For example, gathering data every 5 seconds.
2. Send data in batches – Instead of sending each data point individually, it would be sent in a batch after a specified interval or when certain conditions (e.g., network availability) are met.

This would be particularly useful in scenarios where:

• There is intermittent network coverage (e.g., being out of cell phone coverage for some time).
• We want to reduce the number of API calls by batching data and sending it in a more efficient manner when coverage is restored.

[jason-abrp]

We actually have a bulk endpoint that's available for exactly this sort of thing. I'll update the API docs to include it, but this is definitely possible.

[jason-abrp]

https://documenter.getpostman.com/view/7396339/SWTK5a8w#4f77e0b8-aa60-4a6e-83df-3c3f7fe19aec

The format is fairly simple, and the innermost "tlm_list" elements are identical to the tlm field of the current format.

[kezarjg]

OK. I'll take a look. Do the entries need to be sorted by time? I've been getting some odd jumps in my trip data (like when I might have connectivity problems)

[jason-abrp]

Assuming the timestamp (UTC seconds) on the entry itself is correct, it should be added to the database and displayed properly. We do discard out of order data for calibration though, as we need to go sequentially.

It is definitely better to send the points in sorted by time though, oldest to newest.

[kezarjg]

https://documenter.getpostman.com/view/7396339/SWTK5a8w#4f77e0b8-aa60-4a6e-83df-3c3f7fe19aec

The format is fairly simple, and the innermost "tlm_list" elements are identical to the tlm field of the current format.

Does the API key need to be authorized for bulk uploads? I'm receiving the following error; 401 Unauthorized Key

[kezarjg]

@jason-abrp My current thinking is to send bulk telemetry every 60 seconds. Will that cause any issues with ABRP?

[jason-abrp]

That should be fine, but maybe a little choppy on the displayed SoC in-app while driving since it could then lag behind by up to a minute.

[kezarjg]

OK. I'll do some testing with every 10 seconds.

[kezarjg]

@jason-abrp - Any suggestion what to do with data when no connection is available. Is there value to ABRP to send the data 'later'? Does it help with average consumption or charging data for vehicles?

[jason-abrp]

Sending the data later is good for filling in missing segments in your drive history, but it's not really used by the calibration process. Up to you if you want to include that.