Vehicle Telemetry

Processing Telemetry in the Jedlix Platform

Telemetry, which refers to the data frequently updated by a vehicle's onboard hardware towards the car manufacturer's backend IT systems, is crucial to Jedlix for determining the state of a vehicle at a specific moment. The frequency at which vehicles update their status to the brand server varies depending on the brand and model, as well as any restrictions on the number of vehicle interactions. To manage this, most brands have rules determining when a vehicle should send information to the server, such as fixed intervals combined with built-in triggers like plugging in/out, charging resuming/pausing, or every X% increase in battery state of charge (SoC).

Telemetry is collected for individual vehicles through two main mechanisms:

1. Push Telemetry - The data is sent by the car brand's server to the Jedlix Smart Charging platform.
2. Pull Telemetry - The data is collected by the Jedlix Smart Charging platform.

The vehicle data transfer method depends on the car brand, model, production year, or version. The applicable method can be found in the vehicle details' capabilities.

Push Telemetry

In this scenario, the car brand manages the telemetry and sends data directly to the Jedlix platform during specific events. The telemetry retrieval cannot be initiated by Jedlix, making it dependent on the car brand to send data.

Pull Telemetry

When the server/vehicle provides pull-based telemetry, Jedlix collects the information by sending requests to the car brand's server. This occurs at certain moments, depending on the vehicle status:

• Jedlix requests telemetry at a fixed time interval (by default, every 5 minutes) to track important metrics like the state of charge. A 'State Machine' logic is in place to reduce the time the vehicle is kept awake as a result of this process. More information about the State Machine can be found here.
• Immediately after sending a command to the vehicle, Jedlix requests telemetry and again after 30 seconds to check whether the command has been received and if the vehicle's charge status has changed. If not, the command is resent, allowing Jedlix to determine whether a vehicle is responding to charge commands.

Although vehicles might not constantly update their own state for various reasons, some vehicles allow for forced status updates. This overrules the standard retrieval schedule of the brand and requests an update right away. The Jedlix platform does this when new telemetry is requested, provided it can be done within the car brand's restrictions.